CompTIA Updated PT0-003 Exam Questions and Answers by vladimir

Preserving artifacts ensures that key outputs from the penetration test, such as logs, screenshots, captured data, and any generated reports, are retained for analysis, reporting, and future reference.

Importance of Preserving Artifacts:

Documentation: Provides evidence of the test activities and findings.

Verification: Allows for verification and validation of the test results.

Reporting: Ensures that all critical data is available for the final report.

Types of Artifacts:

Logs: Capture details of the tools used, commands executed, and their outputs.

Screenshots: Visual evidence of the steps taken and findings.

Captured Data: Includes network captures, extracted credentials, and other sensitive information.

Reports: Interim and final reports summarizing the findings and recommendations.

Best Practices:

Secure Storage: Ensure artifacts are stored securely to prevent unauthorized access.

Backups: Create backups of critical artifacts to avoid data loss.

Documentation: Maintain detailed documentation of all artifacts for future reference.

References from Pentesting Literature:

Preserving artifacts is a standard practice emphasized in penetration testing methodologies to ensure comprehensive documentation and reporting of the test.

HTB write-ups often include references to preserved artifacts to support the findings and conclusions.

Step-by-Step ExplanationReferences:

Penetration Testing - A Hands-on Introduction to Hacking

HTB Official Writeups

======

The correct answer is C. Running Metasploit utilizing the EternalBlue module

The scan results show TCP port 445 open, which indicates SMB is available. The host is also identified with partial confidence as Windows 7 SP0, an older Windows version historically associated with SMB vulnerabilities. EternalBlue targets SMBv1 and is known to be potentially unstable, especially against older or unpatched Windows systems. Exploiting SMB kernel-level vulnerabilities can cause system crashes or blue screens if the exploit fails or is not compatible with the target.

A is incorrect because Responder and Impacket are commonly used for SMB/NTLM relay or credential capture activities. They can be risky in some environments, but they are less likely than EternalBlue to directly crash a target when creating a session.

B is incorrect because Nmap safe scripts are designed to be non-intrusive. Targeting RDP with safe scripts is less likely to cause system instability.

D is incorrect because Hydra at one attempt per second is a slow password attack. It may trigger account lockout depending on policy, but it is not the most likely option to create host stability issues.

In PenTest+ terms, this falls under Attacks and Exploits, specifically exploit selection, exploit safety, and understanding the operational risk of using unstable exploits against production systems.

Shodan is a search engine that specializes in finding internet-connected devices, including ICS, IoT, webcams, routers, and servers. Attackers and security professionals use Shodan to scan for publicly accessible systems that may be vulnerable.

Option A (theHarvester) ❌: theHarvester is primarily used for OSINT (Open-Source Intelligence) gathering, such as email addresses, subdomains, and hostnames, but it does not specialize in ICS/IoT discovery.

Option B (Shodan) ✅: Correct. Shodan scans the internet for connected devices and services, allowing penetration testers to find ICS/IoT systems that are exposed.

Option C (Amass) ❌: Amass is used for subdomain enumeration and DNS reconnaissance, not for ICS or IoT discovery.

Option D (Nmap) ❌: Nmap is a port scanner that can identify live hosts and open ports, but it does not search for publicly available systems on a large scale like Shodan.

???? Reference: CompTIA PenTest+ PT0-003 Official Guide – OSINT and Reconnaissance

The tester’s activity involves analyzing the contents of a JAR file to identify potentially vulnerable components. This process is known as Software Composition Analysis (SCA). Here’s why:

Understanding SCA:

Definition: SCA involves analyzing software to identify third-party and open-source components, checking for known vulnerabilities, and ensuring license compliance.

Purpose: To detect and manage risks associated with third-party software components.

Comparison with Other Terms:

SAST (A): Static Application Security Testing involves analyzing source code for security vulnerabilities without executing the code.

SBOM (B): Software Bill of Materials is a detailed list of all components in a software product, often used in SCA but not the analysis itself.

ICS (C): Industrial Control Systems, not relevant to the context of software analysis.

The tester’s activity of examining a JAR file for vulnerable components aligns with SCA, making it the correct answer.

======