PT0-001 · Question #9
Which of the following is the reason why a penetration tester would run the chkconfig --del command at the end of an engagement? servicename
The correct answer is A. To remove the persistence. The chkconfig --del command removes a service from the system startup sequence, which is how a penetration tester cleans up persistence mechanisms installed during an engagement.
Question
Which of the following is the reason why a penetration tester would run the chkconfig --del command at the end of an engagement? servicename
Options
- ATo remove the persistence
- BTo enable persistence
- CTo report persistence
- DTo check for persistence
How the community answered
(20 responses)- A90% (18)
- B5% (1)
- D5% (1)
Why each option
The chkconfig --del command removes a service from the system startup sequence, which is how a penetration tester cleans up persistence mechanisms installed during an engagement.
During a penetration test, testers often establish persistence by adding a malicious service to the init system using chkconfig --add. Running chkconfig --del servicename at the end of the engagement removes that service from all runlevel startup scripts, effectively eliminating the persistence and restoring the system to its pre-test state.
chkconfig --add or chkconfig servicename on would enable persistence, not --del, which does the opposite.
Reporting persistence is a documentation activity done in a written report, not accomplished by running a shell command.
Checking for existing persistence would use chkconfig --list, not --del, which is a destructive operation that removes the entry.
Concept tested: Penetration test cleanup removing service persistence
Source: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/s2-services-chkconfig
Topics
Community Discussion
No community discussion yet for this question.