Q: 8
[Information Gathering and Vulnerability Scanning] A penetration tester is enumerating a Linux system. The goal is to modify the following script to provide more comprehensive system information:
#!/bin/bash ps aux >> linux_enum.txt
Which of the following lines would provide the most comprehensive enumeration of the system?
Options
Discussion
Option A saw this on a practice test. It collects user accounts, open ports, and config files so it's more complete.
A . It grabs user accounts (cat /etc/passwd), network services (netstat -tuln), and config files all in one go, which matches what you'd call comprehensive enumeration. B is good but misses key details like service listings. Open to pushback if someone thinks bash.bashrc isn't needed though.
Option A. Has the passwd file for user accounts, netstat for open ports, and bash config info. Pretty sure that's what they want for "most comprehensive" on Pentest+. If you think B or D is better, let me know!
Its A, pretty sure. Official Pentest+ study guides and practice tests tend to recommend those same commands for a broad Linux enum. If someone found different in their exam prep, curious to hear it.
Had something like this in a mock, A was the correct pick there. It covers users, network services, and system config in one command line which matches what "comprehensive" wants. If anyone disagrees, let me know.
A
It’s A, not B. cat /etc/passwd is key for seeing all users, netstat gives open ports, and grabbing the bash.bashrc hits config details. B looks tempting since it’s quick recon but I think it misses some depth the question wants. Pretty sure about A from similar practice tests.
A
B vs D-if the scope is just network and system basics, B could be enough. The others add extra config info that isn't always relevant for fast enumeration. Might depend on what the pentest lead wants.
B tbh
Be respectful. No spam.