pt-maintaining-access
Pen Test Maintaining Access
Authorized Use Only
Persistence simulation requires explicit approval. Prefer temporary, reversible techniques and remove all artifacts during cleanup. Never leave backdoors, accounts, or scheduled tasks in place after testing.
Objectives
- Determine whether access can survive control changes and reboots.
- Assess lateral movement opportunities from compromised context.
- Measure detection and response effectiveness.
Workflow
- Confirm persistence permissions:
- Allowed mechanisms
- Maximum dwell time
- Mandatory cleanup expectations
- Simulate persistence safely:
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-analysis-reporting
Produces penetration test reports with executive summary, technical findings, and remediation guidance. Use when consolidating test evidence, prioritizing risk, and preparing stakeholder-ready deliverables.
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-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