pt-analysis-reporting
Pen Test Analysis and Reporting
Objectives
- Translate technical outcomes into business risk.
- Provide reproducible technical detail for remediation teams.
- Deliver prioritized, actionable fixes with retest criteria.
Workflow
- Consolidate evidence:
- Gather outputs from recon, scanning, exploitation, and persistence testing
- Normalize severity/risk ratings and remove duplicates
- Build executive narrative:
- Overall security posture
- Top risks and likely business impact
- Immediate leadership actions
- Build technical findings:
- One finding per vulnerability or attack path
More from santosomar/ethical-hacking-agent-skills
pt-scanning
Performs authorized security scanning using static, dynamic, and vulnerability-focused methods. Use when mapping exposed services, profiling application behavior, and identifying known weaknesses for validation.
1pt-report-creation
Creates penetration test deliverables for executive and technical audiences, including prioritized findings and remediation plans. Use when drafting, structuring, or finalizing pen test reports from collected evidence.
1pt-fuzzing-web-api
Performs authorized fuzzing of web applications and APIs to discover input validation failures, parser bugs, and stability issues. Use when testing HTTP endpoints, request parameters, payload handling, and error behavior under malformed or unexpected inputs.
1pt-post-exploitation
Performs authorized post-exploitation activities to assess impact, lateral movement paths, credential exposure, and detection gaps after initial compromise. Use when a foothold has been validated and the test requires controlled impact expansion analysis.
1pt-maintaining-access
Evaluates whether an attacker could retain foothold and move laterally after initial compromise, within strict authorization limits. Use when testing persistence, session resilience, and detection/response effectiveness during a pen test.
1pt-lotl-techniques
Demonstrates Living-off-the-Land (LotL) techniques using native OS tools to simulate realistic threat actor behavior during authorized penetration tests. Use when proving attack feasibility without custom malware, testing detection coverage, and validating what a real adversary could achieve with only built-in system capabilities.
1