Penetration Test Plan
Plan penetration testing for "$ARGUMENTS" covering test type, scope, methodology, rules of engagement, success criteria, and reporting requirements.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"security-pentest-plan","workflow":"security","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Process
Define penetration test type:
- Black box — testers have no prior knowledge of the target (simulates external attacker)
- Grey box — testers have partial knowledge (user credentials, architecture docs, API documentation)
- White box — testers have full knowledge (source code, architecture, admin access)
- Select type based on testing objectives: black box for external threat simulation, grey box for authenticated attack paths, white box for comprehensive coverage
- Document rationale for selected approach
Define scope:
- In-scope systems — list specific applications, APIs, networks, hosts, and cloud resources to test
- In-scope test types — network penetration, web application, API, mobile, social engineering, physical
- Out-of-scope systems — explicitly list systems, networks, or techniques that are excluded
- Data constraints — define handling of any sensitive data encountered during testing
- Third-party systems — identify any third-party systems in scope and confirm authorization
- Document scope boundaries clearly to prevent unauthorized testing
Select methodology:
- OWASP Testing Guide — for web application and API testing
- PTES (Penetration Testing Execution Standard) — for comprehensive network and application testing
- NIST SP 800-115 — for government and regulated environments
- OWASP Mobile Security Testing Guide — for mobile application testing
- Define testing phases: reconnaissance, scanning, exploitation, post-exploitation, reporting
- Specify tools permitted and prohibited (if any restrictions apply)
Define rules of engagement:
- Testing windows — permitted hours and days (business hours only, after hours, weekends)
- Notification — who is aware testing is occurring (security team, SOC, management)
- Emergency contacts — who to call if testing causes an outage or discovers active breach
- Prohibited techniques — denial of service (unless explicitly authorized), social engineering of specific individuals, physical intrusion (unless in scope)
- Data handling — no exfiltration of real customer data, test data only, secure deletion after testing
- Credential handling — obtained credentials must be reported immediately and not reused outside testing
- Communication channel — encrypted channel for reporting critical findings during testing
- Stop conditions — circumstances that require immediate cessation of testing
Define success criteria:
- What constitutes a successful test? (comprehensive coverage, critical findings identified, defense validation)
- Minimum coverage requirements (percentage of in-scope systems tested, OWASP categories covered)
- Expected deliverables: executive summary, technical findings, evidence (screenshots, logs), remediation recommendations
- Finding severity classification aligned with organization's risk framework
Define reporting requirements:
- Executive summary — non-technical overview for leadership
- Technical findings — detailed vulnerability descriptions with CVSS scores
- Evidence — proof-of-concept details, screenshots, reproduction steps
- Risk rating — severity aligned with CVSS and business context
- Remediation recommendations — specific, actionable guidance per finding
- Retest plan — scope and timeline for verifying remediation
- Report delivery: encrypted, limited distribution, defined retention period
Set remediation timeline expectations:
- Critical findings — remediation within 72 hours, retest within 1 week
- High findings — remediation within 2 weeks, retest within 1 month
- Medium findings — remediation within 1 month, retest within next scheduled test
- Low/informational — remediation within 1 quarter, tracked in vulnerability management
- Define escalation process for overdue remediation
Define tester qualifications:
- Required certifications (OSCP, CEH, GPEN, CREST, or equivalent)
- Industry experience requirements (years, relevant sectors)
- Background check and NDA requirements
- Insurance requirements (professional liability, cyber insurance)
- Preference for testers with experience in the organization's technology stack
Write the artifact to .singularskills/security/<project>/pentest-plan.md with heading:
Penetration Test Plan
Include sections:
- Test Type — selected approach with rationale
- Scope — in-scope and out-of-scope systems and test types
- Methodology — selected testing standard and phases
- Rules of Engagement — testing windows, contacts, prohibited techniques, and stop conditions
- Success Criteria — coverage requirements and expected deliverables
- Reporting Requirements — report structure, severity classification, and distribution
- Remediation Timeline — expected fix timelines per severity level
- Tester Qualifications — certification, experience, and contractual requirements
Output
The penetration test plan written to .singularskills/security/<project>/pentest-plan.md. Present a summary to the user highlighting:
- Test type and scope definition
- Key rules of engagement and prohibited techniques
- Reporting and remediation timeline expectations
- Tester qualification requirements
End the artifact with this paragraph, verbatim:
Not a penetration test or audit. This artifact is generated analysis; validate findings against the live system and have material controls reviewed by a qualified security professional.
1---2name: security-pentest-plan3description: Plan one penetration test — black, grey or white box, in- and out-of-scope systems, methodology, rules of engagement, stop conditions, reporting, remediation timelines and tester qualifications. Use when the user is commissioning or preparing a pen test and needs its scope and rules of engagement written down. Not for an ongoing scanning program; see /security-security-testing.4metadata:5 source: https://skillmd.com/skills/bromso/security-pentest-plan6 argument-hint: "[project] [--skip-checks]"7---89# Penetration Test Plan1011Plan penetration testing for "$ARGUMENTS" covering test type, scope, methodology, rules of engagement, success criteria, and reporting requirements.1213**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"security-pentest-plan","workflow":"security","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1415## Process16171. **Define penetration test type:**18 - **Black box** — testers have no prior knowledge of the target (simulates external attacker)19 - **Grey box** — testers have partial knowledge (user credentials, architecture docs, API documentation)20 - **White box** — testers have full knowledge (source code, architecture, admin access)21 - Select type based on testing objectives: black box for external threat simulation, grey box for authenticated attack paths, white box for comprehensive coverage22 - Document rationale for selected approach23242. **Define scope:**25 - **In-scope systems** — list specific applications, APIs, networks, hosts, and cloud resources to test26 - **In-scope test types** — network penetration, web application, API, mobile, social engineering, physical27 - **Out-of-scope systems** — explicitly list systems, networks, or techniques that are excluded28 - **Data constraints** — define handling of any sensitive data encountered during testing29 - **Third-party systems** — identify any third-party systems in scope and confirm authorization30 - Document scope boundaries clearly to prevent unauthorized testing31323. **Select methodology:**33 - **OWASP Testing Guide** — for web application and API testing34 - **PTES (Penetration Testing Execution Standard)** — for comprehensive network and application testing35 - **NIST SP 800-115** — for government and regulated environments36 - **OWASP Mobile Security Testing Guide** — for mobile application testing37 - Define testing phases: reconnaissance, scanning, exploitation, post-exploitation, reporting38 - Specify tools permitted and prohibited (if any restrictions apply)39404. **Define rules of engagement:**41 - **Testing windows** — permitted hours and days (business hours only, after hours, weekends)42 - **Notification** — who is aware testing is occurring (security team, SOC, management)43 - **Emergency contacts** — who to call if testing causes an outage or discovers active breach44 - **Prohibited techniques** — denial of service (unless explicitly authorized), social engineering of specific individuals, physical intrusion (unless in scope)45 - **Data handling** — no exfiltration of real customer data, test data only, secure deletion after testing46 - **Credential handling** — obtained credentials must be reported immediately and not reused outside testing47 - **Communication channel** — encrypted channel for reporting critical findings during testing48 - **Stop conditions** — circumstances that require immediate cessation of testing49505. **Define success criteria:**51 - What constitutes a successful test? (comprehensive coverage, critical findings identified, defense validation)52 - Minimum coverage requirements (percentage of in-scope systems tested, OWASP categories covered)53 - Expected deliverables: executive summary, technical findings, evidence (screenshots, logs), remediation recommendations54 - Finding severity classification aligned with organization's risk framework55566. **Define reporting requirements:**57 - **Executive summary** — non-technical overview for leadership58 - **Technical findings** — detailed vulnerability descriptions with CVSS scores59 - **Evidence** — proof-of-concept details, screenshots, reproduction steps60 - **Risk rating** — severity aligned with CVSS and business context61 - **Remediation recommendations** — specific, actionable guidance per finding62 - **Retest plan** — scope and timeline for verifying remediation63 - Report delivery: encrypted, limited distribution, defined retention period64657. **Set remediation timeline expectations:**66 - **Critical findings** — remediation within 72 hours, retest within 1 week67 - **High findings** — remediation within 2 weeks, retest within 1 month68 - **Medium findings** — remediation within 1 month, retest within next scheduled test69 - **Low/informational** — remediation within 1 quarter, tracked in vulnerability management70 - Define escalation process for overdue remediation71728. **Define tester qualifications:**73 - Required certifications (OSCP, CEH, GPEN, CREST, or equivalent)74 - Industry experience requirements (years, relevant sectors)75 - Background check and NDA requirements76 - Insurance requirements (professional liability, cyber insurance)77 - Preference for testers with experience in the organization's technology stack78799. **Write the artifact** to `.singularskills/security/<project>/pentest-plan.md` with heading:8081 ## Penetration Test Plan8283 Include sections:84 - **Test Type** — selected approach with rationale85 - **Scope** — in-scope and out-of-scope systems and test types86 - **Methodology** — selected testing standard and phases87 - **Rules of Engagement** — testing windows, contacts, prohibited techniques, and stop conditions88 - **Success Criteria** — coverage requirements and expected deliverables89 - **Reporting Requirements** — report structure, severity classification, and distribution90 - **Remediation Timeline** — expected fix timelines per severity level91 - **Tester Qualifications** — certification, experience, and contractual requirements9293## Output9495The penetration test plan written to `.singularskills/security/<project>/pentest-plan.md`. Present a summary to the user highlighting:96- Test type and scope definition97- Key rules of engagement and prohibited techniques98- Reporting and remediation timeline expectations99- Tester qualification requirements100101End the artifact with this paragraph, verbatim:102103> **Not a penetration test or audit.** This artifact is generated analysis; validate findings against the live system and have material controls reviewed by a qualified security professional.