Repository navigation
Checklists
Comprehensive security checklists for penetration testing, security audits, and compliance assessments
Part of the ULTIMATE CYBERSECURITY MASTER GUIDE
- Overview
- Current Checklists
- Checklist Categories
- How to Use These Checklists
- Security & Legal Disclaimer
- Contributing
- Resources
This directory contains comprehensive security checklists, assessment templates, and methodologies for cybersecurity professionals conducting authorized security testing, audits, and compliance assessments.
What You'll Find Here:
- ๐ Penetration testing attack path checklists
- ๐ Security assessment methodologies
- ๐ฅ๏ธ System hardening and configuration reviews
- ๐ Network and infrastructure security checklists
- ๐ฑ Application security testing guides
- ๐ Active Directory security assessments
- โก Privilege escalation methodologies
- ๐ Security configuration baselines
These checklists serve as:
- Methodology guides for systematic security assessments
- Quality assurance to ensure comprehensive testing coverage
- Documentation aids for tracking assessment progress
- Training materials for developing security assessment skills
- Attack path references for penetration testing
| Checklist | Description | Focus Area |
|---|---|---|
| ActiveDirectory.md | Comprehensive Active Directory security assessment and attack vectors | AD Security |
| Domain-Escalation.md | Domain privilege escalation techniques and paths | Escalation |
| Domain-Persistence.md | Domain-level persistence mechanisms and detection | Persistence |
| Checklist | Description | Focus Area |
|---|---|---|
| Initial-Access.md | Initial access techniques and vectors (MITRE ATT&CK) | Entry Points |
| Credential-Access.md | Credential dumping, theft, and access techniques | Credentials |
| Environment-Breakout-Checklist.md | Container and sandbox escape techniques | Breakout |
| Checklist | Description | Focus Area |
|---|---|---|
| Windows-Privilege-Escalation.md | Windows privilege escalation vectors and techniques | Windows PrivEsc |
| Linux-Privilege-Escalation.md | Linux/Unix privilege escalation methodologies | Linux PrivEsc |
| Checklist | Description | Focus Area |
|---|---|---|
| Lateral-Movement.md | Lateral movement techniques across networks | Movement |
| Persistence.md | System-level persistence mechanisms | Persistence |
| command-and-control.md | Command and Control (C2) techniques and channels | C2 |
| Checklist | Description | Focus Area |
|---|---|---|
| Defense-Evasion.md | Defense evasion techniques and anti-forensics | Evasion |
| AppLocker.md | AppLocker bypass techniques and misconfigurations | Bypass |
| Checklist | Description | Focus Area |
|---|---|---|
| Android-Applications-Checklist.md | Android application security assessment | Mobile Security |
| voip-checklist.md | Voice over IP security testing and assessment | VoIP Security |
| microsoft-exchange.md | Microsoft Exchange server security assessment | Exchange |
| Checklist | Description | Focus Area |
|---|---|---|
| Windows-Build-Review-Checklist.md | Windows system build and configuration review | Hardening |
Purpose: Comprehensive assessment of Active Directory environments and domain security controls.
What's Covered:
- Domain enumeration techniques
- Trust relationship exploitation
- Kerberos attacks (Kerberoasting, AS-REP roasting)
- Domain privilege escalation paths
- Persistence mechanisms in AD
- Golden/Silver ticket attacks
- DCSync and replication attacks
Use Cases:
- Internal penetration testing
- Red team operations
- Active Directory security assessments
- Domain compromise simulation
- Security hardening validation
Purpose: Techniques for gaining initial foothold and obtaining credentials.
What's Covered:
- Phishing and social engineering vectors
- Exploit delivery mechanisms
- Credential dumping (LSASS, SAM, LSA Secrets)
- Pass-the-hash/ticket attacks
- Kerberos delegation abuse
- NTLM relay attacks
Use Cases:
- Initial access testing
- Credential security assessment
- Password policy evaluation
- Authentication mechanism testing
- User awareness training validation
Purpose: Systematic methodology for escalating privileges on Windows and Linux systems.
What's Covered:
- Kernel exploits
- Service misconfigurations
- Scheduled task abuse
- DLL hijacking
- Token manipulation
- Sudo/SUID misconfigurations
- Capabilities abuse
Use Cases:
- Local privilege escalation testing
- System hardening validation
- Configuration review
- Exploit chain development
- Security baseline verification
Purpose: Techniques for moving laterally across networks and maintaining access.
What's Covered:
- Remote execution methods (WMI, PSExec, WinRM)
- Pass-the-hash lateral movement
- RDP/VNC pivoting
- Service installation
- Registry persistence
- Scheduled tasks
- WMI event subscriptions
- Startup folder abuse
Use Cases:
- Network segmentation testing
- Detection capability assessment
- Persistence mechanism identification
- Post-exploitation operations
- Blue team detection validation
Purpose: Techniques for evading security controls and anti-malware solutions.
What's Covered:
- AppLocker/WDAC bypass
- AMSI bypass techniques
- PowerShell logging evasion
- AV/EDR evasion
- Process injection
- Code obfuscation
- Living-off-the-land binaries (LOLBins)
Use Cases:
- Detection capability testing
- Security control validation
- Purple team exercises
- EDR/AV efficacy assessment
- Security monitoring gaps
Purpose: Security assessment of mobile applications and specialized infrastructure.
What's Covered:
- Android application vulnerabilities
- VoIP security weaknesses
- Microsoft Exchange misconfigurations
- API security issues
- Authentication/authorization flaws
- Data storage security
Use Cases:
- Mobile application security testing
- VoIP infrastructure assessment
- Exchange server security review
- Third-party application assessment
- Compliance verification
A checklist helps ensure consistent coverage but is not proof of complete security.
1. Pre-Engagement
โโ> Select appropriate checklist(s) for engagement type
โโ> Review MITRE ATT&CK mapping
โโ> Obtain written authorization
โโ> Prepare testing environment and tools
2. During Assessment
โโ> Follow checklist systematically by phase
โโ> Document all findings with evidence
โโ> Use checklists to ensure coverage
โโ> Track successful and unsuccessful techniques
โโ> Note defense mechanisms encountered
3. Post-Assessment
โโ> Map findings to checklist items
โโ> Identify attack paths and chains
โโ> Provide remediation recommendations
โโ> Archive checklist with engagement documentation
4. Quality Assurance
โโ> Verify all applicable items tested
โโ> Ensure proper documentation
โโ> Review for missed techniques
1. Planning Phase
โโ> Select checklists aligned with objectives
โโ> Map to adversary TTPs
โโ> Plan attack paths using checklists
โโ> Identify required tools and capabilities
2. Execution Phase
โโ> Use checklists as technique reference
โโ> Adapt based on environment
โโ> Document successful techniques
โโ> Note detection and response
3. Reporting Phase
โโ> Map activities to MITRE ATT&CK
โโ> Highlight successful attack paths
โโ> Provide detection recommendations
โโ> Suggest defensive improvements
1. Understanding Threats
โโ> Study attack techniques in checklists
โโ> Map to MITRE ATT&CK framework
โโ> Identify relevant threats to environment
โโ> Prioritize high-risk techniques
2. Detection Development
โโ> Create detection rules for techniques
โโ> Develop hunting queries
โโ> Build correlation rules
โโ> Test detection coverage
3. Hardening & Mitigation
โโ> Implement preventive controls
โโ> Harden configurations per checklists
โโ> Validate security baselines
โโ> Test detection capabilities
4. Purple Team Exercises
โโ> Use checklists for controlled testing
โโ> Validate detection and response
โโ> Measure coverage and gaps
โโ> Improve security posture iteratively
1. Audit Planning
โโ> Select relevant security checklists
โโ> Map to compliance requirements
โโ> Schedule assessment activities
โโ> Request necessary access
2. Assessment Execution
โโ> Conduct systematic review per checklist
โโ> Verify security control implementation
โโ> Document findings and evidence
โโ> Test configuration effectiveness
3. Reporting
โโ> Compare findings against checklist
โโ> Assess risk and severity
โโ> Provide actionable recommendations
โโ> Create audit report with checklist results
โ ๏ธ LEGAL AND ETHICAL USE ONLY โ ๏ธ
These security checklists contain attack techniques and methodologies for:
โ
AUTHORIZED USES:
โข Penetration testing with explicit written authorization
โข Red team operations with organizational approval
โข Security assessments with client permission
โข Blue team training and detection development
โข Purple team exercises in controlled environments
โข Security research in isolated lab environments
โข Educational purposes with proper supervision
โข CTF competitions and authorized challenges
๐ซ STRICTLY PROHIBITED:
โข Unauthorized penetration testing or "hacking"
โข Attacking systems without explicit written permission
โข Exceeding authorized scope of engagement
โข Testing techniques on production systems without approval
โข Using attack techniques for malicious purposes
โข Bypassing security controls without authorization
โข Causing harm, disruption, or data loss
โข Any illegal or unethical activities
CRITICAL: ALWAYS obtain written authorization that explicitly includes:
- โ Specific systems, networks, and IP ranges in scope
- โ Testing methodology and techniques approved
- โ Time windows for testing activities
- โ Out-of-scope systems and explicit restrictions
- โ Emergency contact information and escalation
- โ Data handling and confidentiality requirements
- โ Liability, indemnification, and insurance terms
- โ Deliverables, reporting requirements, and format
โ
IN SCOPE (With Explicit Authorization):
โข Systems explicitly listed in engagement letter
โข Networks defined in written agreement
โข Specific techniques approved by client
โข Test accounts created for engagement
โข Designated time windows only
๐ซ OUT OF SCOPE (Even If Discovered):
โข Third-party systems or cloud services
โข Production systems not explicitly authorized
โข Personal devices of employees
โข Partner or vendor systems
โข Anything not explicitly in writing
โข Techniques not approved (e.g., DoS, destructive)
Essential Guidelines for Attack Technique Testing:
- Stop Immediately if Uncertain: If scope is ambiguous, STOP and get clarification
- Report Critical Vulns Immediately: Don't wait for final report if system is at risk
- No Destructive Actions: Unless explicitly authorized (ransomware, wipers, etc.)
- No Denial of Service: Unless specifically approved and planned
- Data Protection: Never exfiltrate, modify, or delete real production data
- Communication Protocol: Use established secure channels for updates
- Social Engineering Limits: Respect agreed boundaries (no physical threats, etc.)
- Physical Access: Only if specifically authorized in writing
- Time Windows: Test only during approved times
- Document Everything: Every command, technique, and finding
โ ๏ธ CRITICAL LEGAL WARNING:
The Computer Fraud and Abuse Act (18 U.S.C. ยง 1030) criminalizes:
โข Unauthorized access to protected computers
โข Exceeding authorized access
โข Damaging protected computers
โข Trafficking in passwords
โข Extortion involving computers
PENALTIES:
โข Up to 10 years imprisonment (first offense)
โข Up to 20 years (repeat offense)
โข Significant financial penalties
โข Civil liability in addition to criminal charges
CRITICAL: Authorization must be:
โ Explicit and in writing
โ From someone with authority to grant it
โ Specific about scope and techniques
โ Current and not expired
- UK Computer Misuse Act 1990: Unauthorized access is criminal offense
- EU Cybercrime Directives: Harmonized computer crime laws across EU
- Canada Criminal Code Section 342.1: Unauthorized computer use
- Australia Cybercrime Act 2001: Computer-related offenses
Key Point: These laws apply even when using the techniques in these checklists without proper authorization.
โ ๏ธ WARNING: Credential Access Techniques
LEGAL CONSIDERATIONS:
โข Dumping credentials is unauthorized access
โข Pass-the-hash attacks may violate CFAA
โข Stealing credentials can be theft charges
โข Use ONLY with explicit authorization
REQUIRED AUTHORIZATION:
โ Explicit permission to access credentials
โ Approval for specific dumping techniques
โ Data handling and storage requirements
โ Credential disposal procedures
PROHIBITED WITHOUT AUTHORIZATION:
๐ซ Accessing others' accounts or credentials
๐ซ Using stolen credentials on unauthorized systems
๐ซ Exfiltrating credential databases
๐ซ Selling or sharing stolen credentials
โ ๏ธ WARNING: Privilege Escalation Techniques
LEGAL CONSIDERATIONS:
โข Exceeding authorized access is a crime
โข Gaining admin/root without permission is illegal
โข Exploiting systems may constitute unauthorized access
โข Even "just testing" without approval is illegal
REQUIRED AUTHORIZATION:
โ Permission to attempt privilege escalation
โ Approval for exploit usage
โ Clear scope of accounts and systems
โ Rollback and restoration procedures
PROHIBITED:
๐ซ Escalating privileges without authorization
๐ซ Using exploits on unauthorized systems
๐ซ Leaving backdoors or persistence
๐ซ Modifying system security settings
โ ๏ธ WARNING: Defense Evasion Techniques
LEGAL CONSIDERATIONS:
โข Disabling security controls may violate authorization
โข AMSI/AppLocker bypass requires explicit approval
โข AV/EDR evasion must be within scope
โข Creating malware-like tools has legal risks
REQUIRED AUTHORIZATION:
โ Explicit permission to test evasion techniques
โ Approval for security control bypass
โ Agreement on tools and methods
โ Restoration of security controls post-test
PROHIBITED:
๐ซ Disabling security on unauthorized systems
๐ซ Distributing evasion tools publicly
๐ซ Using evasion for malicious purposes
๐ซ Leaving systems in insecure state
Core Principles:
- Authorization: Never test without explicit written permission
- Integrity: Act honestly and transparently with clients
- Confidentiality: Protect all client information and findings
- Competence: Only use techniques you fully understand
- Responsibility: Accept accountability for all actions
- Legal Compliance: Follow all applicable laws and regulations
- Do No Harm: Minimize risk and impact of testing
โ
DO:
โข Obtain written authorization before every test
โข Verify authorization is current and valid
โข Document all activities and techniques used
โข Report findings responsibly and promptly
โข Protect client confidentiality at all times
โข Restore systems to secure state after testing
โข Maintain professional liability insurance
โข Continue professional development and training
๐ซ DON'T:
โข Test without written authorization (ever)
โข Exceed authorized scope "just to see"
โข Use findings for personal gain or harm
โข Share client vulnerabilities publicly
โข Disclose techniques used without permission
โข Leave systems in compromised state
โข Misrepresent your qualifications or findings
โข Guarantee results or claim infallibility
System Impact:
- Exploitation attempts may cause system instability
- Privilege escalation can crash services
- Credential dumping may trigger lockouts
- Persistence mechanisms may conflict with production
- Lateral movement may cause network disruption
Detection & Response:
- Security tools will detect and alert on techniques
- EDR/AV may quarantine testing tools
- SOC teams may respond to testing activities
- Incident response may be triggered
- Legal/compliance may be notified
Data Risks:
- Accidental access to sensitive data
- Credential theft may expose real passwords
- Logs may contain PII or confidential information
- Evidence must be properly secured
- Data disposal must follow procedures
Criminal Liability:
- Federal computer crime charges (CFAA)
- State computer crime charges
- Wire fraud or identity theft charges
- Conspiracy or aiding/abetting charges
- International prosecution under various laws
Civil Liability:
- Damages from system disruption
- Data breach liability
- Privacy violations and lawsuits
- Breach of contract (exceeding scope)
- Loss of business or reputation
Professional Consequences:
- Loss of security certifications (OSCP, CEH, etc.)
- Professional license revocation
- Employment termination
- Industry blacklisting
- Inability to work in cybersecurity
โ
Mitigation Measures:
Authorization & Documentation:
โข Comprehensive written authorization
โข Clear scope and boundaries defined
โข Regular authorization verification
โข Detailed activity logging
โข Evidence preservation procedures
โข Client communication protocols
Technical Controls:
โข Test in non-production first
โข Use snapshots and backups
โข Implement rollback procedures
โข Monitor testing impact
โข Have emergency contacts ready
โข Prepare incident response plan
Professional Practices:
โข Maintain $1M+ E&O insurance
โข Consult legal counsel when uncertain
โข Follow industry standards (PTES, OSSTMM)
โข Participate in professional organizations
โข Continuous education and training
โข Peer review of methodologies
๐จ IMMEDIATE ACTIONS:
1. STOP all testing immediately
2. Document exactly what happened
3. Notify client using emergency contact
4. Preserve all evidence and logs
5. Assess system status and impact
6. Assist with remediation if requested
7. Document incident for final report
8. Conduct post-incident review
9. Update procedures to prevent recurrence
๐ด CRITICAL VULNERABILITY PROTOCOL:
1. Document finding thoroughly with evidence
2. Assess immediate risk to organization
3. Verify exploitability and impact
4. Notify client IMMEDIATELY (don't wait for report)
5. Provide temporary mitigation recommendations
6. Offer emergency remediation assistance
7. Follow up to ensure remediation
8. Document in final report with timeline
โ ๏ธ DISCLAIMER OF WARRANTIES โ ๏ธ
These security checklists are provided "AS IS" without warranty of any kind,
either expressed or implied, including but not limited to:
โข Warranties of accuracy or completeness
โข Warranties of technique effectiveness
โข Warranties of safety or non-disruption
โข Warranties of legal compliance
โข Warranties of fitness for a particular purpose
THE AUTHORS, CONTRIBUTORS, AND MAINTAINERS:
โข Make no guarantees about checklist completeness
โข Are not responsible for damages from checklist use
โข Do not warrant techniques will work in all environments
โข Are not liable for legal consequences of misuse
โข May update content without notice
โข Disclaim all liability for unauthorized use
USERS EXPLICITLY ACKNOWLEDGE:
โข They use these checklists at their own risk
โข They are responsible for obtaining authorization
โข They must comply with all applicable laws
โข They are liable for their testing activities
โข They understand legal implications of techniques
โข They accept all risks of using attack methodologies
CRITICAL REMINDER:
These are ATTACK TECHNIQUES that can cause:
- System disruption or damage
- Data loss or corruption
- Security control bypass
- Legal prosecution if misused
- Professional and personal consequences
The Authors, Contributors, and Maintainers are NOT liable for:
- Direct, indirect, incidental, or consequential damages
- Criminal charges resulting from unauthorized use
- Civil lawsuits from testing activities
- System failures, crashes, or data loss
- Security breaches or compromises
- Network disruption or service outages
- Privacy violations or regulatory fines
- Professional license loss or termination
- Employment termination
- Legal fees or criminal defense costs
- Any damages whatsoever arising from checklist use
Maximum Liability: To the extent permitted by law, total liability shall not exceed the amount paid for these checklists (which is zero for free distribution).
User Assumption of Risk: By using these attack technique checklists, users explicitly acknowledge and accept all risks, including criminal prosecution, civil liability, professional consequences, and any other damages that may result.
We welcome contributions from security professionals to improve and expand this collection.
To Submit a New Checklist:
- Fork the repository
- Create checklist following MITRE ATT&CK format where applicable
- Include clear sections for each technique
- Add tool recommendations and commands
- Include detection/mitigation guidance
- Add comprehensive legal warnings
- Test techniques in authorized environments
- Submit pull request with detailed description
Checklist Quality Standards:
- โ Clear, systematic technique organization
- โ MITRE ATT&CK technique mapping
- โ Tool and command examples
- โ Detection and mitigation guidance
- โ Risk ratings for each technique
- โ Authorization reminders throughout
- โ Proper attribution for sources
- โ Legal warnings prominently displayed
High Priority:
- Cloud platform attack techniques (AWS, Azure, GCP)
- Container security and Kubernetes attacks
- API security testing methodologies
- Modern authentication bypass techniques
- EDR/XDR evasion techniques
- Zero-trust architecture testing
- DevSecOps security assessments
- MITRE ATT&CK: https://attack.mitre.org/
- PTES: Penetration Testing Execution Standard
- OWASP Testing Guide: https://owasp.org/www-project-web-security-testing-guide/
- OSSTMM: Open Source Security Testing Methodology Manual
- NIST SP 800-115: Technical Guide to Information Security Testing
- MITRE ATT&CK Enterprise: https://attack.mitre.org/matrices/enterprise/
- LOLBAS Project: Living Off The Land Binaries and Scripts
- GTFOBins: Unix binaries for privilege escalation
- WADComs: Windows/AD attack cheat sheets
- HackTricks: Pentesting methodology and techniques
- OSCP: Offensive Security Certified Professional
- OSCE: Offensive Security Certified Expert
- OSEP: Offensive Security Experienced Penetration Tester
- GPEN: GIAC Penetration Tester
- GXPN: GIAC Exploit Researcher and Advanced Penetration Tester
- CRTP: Certified Red Team Professional
- ๐ Main Repository
- ๐ฏ START HERE Guide
- ๐ป Cybersecurity Master Guide
- ๐ก๏ธ Tradecraft Deep Dives - full write-ups behind several of these checklists
- ๐ Playbooks - blue-team investigation procedures
- ๐ PDF Library - reference PDFs behind several of these checklists
- ๐ป Security Scripts & Tools - scripts that implement several of these techniques
- ๐ OSINT Resources
- ๐ Documentation
- ๐ OPSEC Guidelines
๐ Current Checklists: 17 comprehensive checklists
๐ Categories: AD Security, Initial Access, PrivEsc, Lateral Movement, Evasion, Applications
๐ Last Updated: November 2024
๐ฅ Maintained by: Pacific Northwest Computers (PNWC)
๐ Status: Active & Growing
Legal Requirements:
- โ Written authorization is MANDATORY (no exceptions)
- โ Clear scope and boundaries documented
- โ Current, valid authorization verified
- โ Professional liability insurance maintained
- โ All activities documented with timestamps
Technical Safety:
- โ Test in non-production first when possible
- โ Have rollback and restoration procedures
- โ Monitor system impact during testing
- โ Maintain emergency contacts and procedures
- โ Document every technique and command used
Professional Ethics:
- โ Never exceed authorized scope
- โ Report findings responsibly
- โ Protect client confidentiality
- โ Restore systems to secure state
- โ Accept responsibility for all actions
- Open an issue on GitHub
- Review documentation and warnings thoroughly first
- Provide specific context about your situation
- Include authorization status (never share client details)
- Respect response times
- Report inaccuracies or outdated techniques
- Suggest additional attack techniques
- Share detection/mitigation strategies
- Contribute new checklists
- Help improve documentation
- MITRE Corporation - ATT&CK Framework
- Offensive Security - OSCP methodology
- SANS Institute - GPEN methodology
- SpecterOps - Active Directory research
- Security research community - Technique disclosure
- Penetration testers sharing methodologies
- Red team operators documenting TTPs
- Blue team defenders providing detection logic
- Security researchers discovering techniques
- Open source tool developers
Thank you for responsible security testing and ethical hacking.
๐ Use These Checklists Responsibly: Authorization is MANDATORY
Attack techniques are powerful - use them ethically and legally.
Repository: ULTIMATE CYBERSECURITY MASTER GUIDE
Maintained by: Pacific Northwest Computers
โญ Star this repo if you find it useful! โญ
- Active Directory
- Android Mobile Application
- AppLocker Bypass
- Command & Control
- Credential Access
- Defense Evasion
- Domain Escalation
- Domain Persistence
- Environment Breakout
- Initial Access
- Lateral Movement
- Linux Privilege Escalation
- Microsoft Exchange
- Persistence
- VoIP Checklist
- Windows Build Review
- Windows Privilege Escalation
๐ Folder: Checklists | โ๏ธ Suggest an edit | ๐บ๏ธ Browse by Topic
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics