Repository navigation
Playbooks
Operational playbooks for incident response, security operations, and team collaboration
Part of the ULTIMATE CYBERSECURITY MASTER GUIDE
Training-to-field progression: Safe CTF and cybersecurity learning pathways maps exercises into scoped PNWC assessment and reporting workflows.
Field system: PNWC Cyberdeck Public Reference covers architecture, an authorization-first assessment process and evidence-handling examples. The new Portable Wireless Device Workflow covers Flipper, Pineapple, Bruce and Marauder as supervised field tools. The private portal is not part of this public companion.
| Reference | Description |
|---|---|
| PNWC Cyberdeck Public Reference | Portable network assessment architecture, staged authorization, evidence handling and offline-only hashing |
| Staged Client Assessment Map | Consent-first phases and tool integration |
| Atomic Red Team, Sigma & Wazuh Validation | Repeatable defensive detection testing |
| DefectDojo Findings & Retesting | Report, triage, remediate and retest findings |
These are documentation/workflow references, not deployed scanners or customer automation.
- Overview
- Playbook Collection
- Playbook Categories
- How to Use These Playbooks
- Security & Legal Disclaimer
- Contributing
- Resources
This directory contains operational security playbooks and procedures for cybersecurity teams, security operations centers (SOC), incident responders, and security professionals. These playbooks provide structured, repeatable processes for security operations, incident response, and team collaboration.
What You'll Find Here:
- ๐ต Blue Team incident response playbooks
- ๐ฃ Purple Team collaborative security testing procedures
- ๐ Network security audit methodologies
- ๐ Security operations procedures
- ๐ Team collaboration frameworks
- ๐จ Incident handling workflows
- ๐ Security assessment playbooks
These playbooks serve as:
- Operational guides for consistent security operations
- Incident response frameworks for handling security events
- Team collaboration tools for red/blue/purple team exercises
- Training materials for security team development
- Quality assurance for repeatable security processes
- Documentation standards for security operations
CTF practice companion: Cypherpunk Symposium archived toolkit curation gives source-backed lessons for legal CTF, memory, cryptography and packet-analysis drills without importing attack scripts.

Reference lifecycle from scope/authorization to testing, analysis, reporting and remediation review. Always follow the approved rules of engagement and document evidence custody.
| Playbook | Description | Complexity |
|---|---|---|
| BlueTeam_IncResp_Simple.md | Simplified blue team incident response playbook for quick reference | Beginner-Friendly |
| BlueTeam_IncResp_Enhanced.md | Comprehensive blue team incident response with detailed procedures | Advanced |
| Playbook | Description | Complexity |
|---|---|---|
| PurpleTeam_Simple.md | Basic purple team collaboration playbook | Beginner-Friendly |
| PurpleTeam_Detailed.md | Detailed purple team operations and procedures | Intermediate |
| PurpleTeam_Multi-Scrip.md | Multi-scenario purple team playbook with various attack simulations | Advanced |
| Playbook | Description | Complexity |
|---|---|---|
| PNWC Cyberdeck Public Reference | Portable hardware and seven-stage authorized network review workflow; no private app published | Reference |
| NetworkAuditPlayBook.md | Comprehensive network security audit and penetration testing playbook | Intermediate |
| HackRFAuditPlayBook.md | RF survey engagement, evidence collection, and controlled bench validation; pair with the SDR index | Intermediate |
| ../Mobile/mobile_pentest_sop.md | Full engagement SOP for pentesting with Kali NetHunter on OnePlus 6: pre-engagement, passive/active recon, Evil AP, HID, BadUSB, Metasploit, evidence handling, reporting | Intermediate |
| Playbook | Description | Complexity |
|---|---|---|
| GitHubPlaybooks.md | GitHub security operations and DevSecOps procedures | Intermediate |
| Playbook | Description | Complexity |
|---|---|---|
| cybersecurity_playbooks.md | General cybersecurity operational playbooks and procedures | Comprehensive |
| Playbook | Description | Complexity |
|---|---|---|
| sop_phishing_analysis.md | Standard operating procedure for triaging and analyzing reported phishing emails | Beginner-Friendly |
| unauth_access.md | Investigation procedures for brute force attacks and impossible-travel account compromise alerts | Intermediate |
Purpose: Defensive security operations and incident response procedures.
What's Covered:
- Incident detection and triage
- Threat hunting procedures
- Log analysis and correlation
- Security monitoring workflows
- Incident containment strategies
- Eradication and recovery procedures
- Post-incident analysis
- Security control validation
Playbooks:
- BlueTeam_IncResp_Simple.md: Quick-reference guide for common incidents
- BlueTeam_IncResp_Enhanced.md: Comprehensive incident response framework
Use Cases:
- SOC operations and monitoring
- Security incident response
- Threat detection and hunting
- Security event analysis
- Defensive security operations
- Incident management
- Security monitoring
Target Audience:
- SOC analysts
- Incident responders
- Security operations teams
- CSIRT/CERT teams
- Security managers
- IT operations teams
Purpose: Collaborative security testing combining offensive and defensive perspectives.
What's Covered:
- Red team and blue team collaboration
- Attack simulation scenarios
- Detection capability testing
- Security control validation
- Gap analysis procedures
- Continuous improvement workflows
- Threat-informed defense
- Detection rule development
Playbooks:
- PurpleTeam_Simple.md: Basic collaborative testing framework
- PurpleTeam_Detailed.md: Comprehensive purple team methodology
- PurpleTeam_Multi-Scrip.md: Multiple attack scenario simulations
Use Cases:
- Security control validation
- Detection capability testing
- Red team/blue team collaboration
- Threat emulation exercises
- Security posture assessment
- Detection rule tuning
- Security team training
Target Audience:
- Purple team operators
- Red team members
- Blue team analysts
- Security architects
- Security trainers
- SOC managers
Purpose: Systematic network security assessment and penetration testing procedures.
What's Covered:
- Network reconnaissance methodology
- Vulnerability assessment procedures
- Penetration testing workflows
- Wireless security auditing
- Network segmentation testing
- Security control validation
- Configuration review processes
- Reporting and documentation
Playbooks:
- NetworkAuditPlayBook.md: Complete network security audit framework
Use Cases:
- Internal network penetration testing
- Wireless security assessments
- Network security audits
- Compliance validation
- Security architecture review
- Network segmentation testing
- Perimeter security assessment
Target Audience:
- Penetration testers
- Network security engineers
- Security auditors
- Network administrators
- Security consultants
- Compliance teams
Purpose: Security procedures for development environments and code repositories.
What's Covered:
- GitHub security best practices
- Code repository security
- DevSecOps workflows
- Secure development procedures
- Access control management
- Secret scanning and management
- Vulnerability management in code
- Supply chain security
Playbooks:
- GitHubPlaybooks.md: GitHub security operations procedures
Use Cases:
- Code repository security
- DevSecOps implementation
- Secure development practices
- Access management
- Secret management
- Vulnerability remediation
- Supply chain security
Target Audience:
- DevSecOps engineers
- Developers
- Security engineers
- DevOps teams
- Security architects
- Application security teams
Purpose: Comprehensive security operational procedures across multiple domains.
What's Covered:
- Cross-functional security operations
- Security program management
- Operational procedures library
- Security team coordination
- Multi-domain security workflows
- Security orchestration
- Compliance procedures
- Security governance
Playbooks:
- cybersecurity_playbooks.md: General operational procedures
Use Cases:
- Security operations management
- Cross-team coordination
- Security program operations
- Compliance management
- Security governance
- Operational excellence
- Process standardization
Target Audience:
- Security managers
- CISO/security leadership
- Security operations teams
- Compliance officers
- Security architects
- Risk management teams
Purpose: Focused, single-incident-type response procedures for the two alert categories a SOC handles most often - phishing reports and access-abuse alerts (brute force, impossible travel, credential stuffing).
What's Covered:
- Phishing email header, URL, and attachment analysis
- Secure Email Gateway (SEG) alert triage
- Brute force and password-spraying investigation
- Impossible-travel and geo-anomaly login analysis
- Credential-stuffing detection and containment
- MITRE ATT&CK mapping (T1110 Brute Force, T1078 Valid Accounts, T1566 Phishing)
- Evidence collection for both incident types
- Escalation and closure criteria
Playbooks:
- sop_phishing_analysis.md: Short-form SOP - header analysis, URL/attachment sandboxing, and containment steps for a single reported phishing email
- unauth_access.md: Longer-form investigation playbook for brute force and impossible-travel alerts, from initial triage through containment
Use Cases:
- Triaging a user-reported phishing email
- Investigating a SIEM/Microsoft Entra ID/Okta brute-force or impossible-travel alert
- Building tier-1 SOC analyst runbooks
- Standardizing phishing/access-abuse response across a team
Target Audience:
- Tier-1/Tier-2 SOC analysts
- Incident responders
- Help desk / IT support staff handling escalations
- Security awareness teams (source material for training)
Daily Operations:
โโ> Use blue team playbooks for incident handling
โโ> Follow incident response procedures systematically
โโ> Document all actions using playbook templates
โโ> Track incidents through defined workflows
โโ> Maintain playbook updates based on lessons learned
Incident Response:
โโ> Reference appropriate incident type playbook
โโ> Follow triage and assessment procedures
โโ> Execute containment strategies per playbook
โโ> Document timeline and actions taken
โโ> Conduct post-incident review
โโ> Update playbooks with new findings
Continuous Improvement:
โโ> Review playbook effectiveness regularly
โโ> Update procedures based on new threats
โโ> Incorporate lessons learned from incidents
โโ> Train team members on playbook usage
โโ> Validate playbooks through purple team exercises
Planning Phase:
โโ> Select appropriate purple team playbook
โโ> Define objectives and success criteria
โโ> Coordinate with red and blue teams
โโ> Schedule testing windows
โโ> Prepare testing environment
Execution Phase:
โโ> Follow attack simulation procedures
โโ> Monitor blue team detection and response
โโ> Document detection gaps and successes
โโ> Test specific security controls
โโ> Validate detection rules and alerts
Analysis Phase:
โโ> Compare attacker actions vs. detections
โโ> Identify coverage gaps
โโ> Assess response effectiveness
โโ> Document improvement recommendations
โโ> Update detection rules and playbooks
Improvement Phase:
โโ> Implement recommended changes
โโ> Re-test improved controls
โโ> Update documentation
โโ> Train teams on new procedures
โโ> Schedule follow-up exercises
Pre-Assessment:
โโ> Review network audit playbook
โโ> Obtain written authorization
โโ> Define scope and boundaries
โโ> Prepare testing environment and tools
โโ> Review rules of engagement
Assessment Execution:
โโ> Follow playbook methodology systematically
โโ> Document all findings with evidence
โโ> Track progress through checklist
โโ> Maintain detailed activity logs
โโ> Report critical findings immediately
Post-Assessment:
โโ> Compile findings using playbook template
โโ> Provide risk ratings and recommendations
โโ> Deliver comprehensive report
โโ> Present findings to stakeholders
โโ> Archive assessment documentation
Repository Security:
โโ> Implement GitHub security playbook procedures
โโ> Configure security controls per playbook
โโ> Monitor for security events
โโ> Manage access controls systematically
โโ> Scan for secrets and vulnerabilities
Continuous Security:
โโ> Integrate security into CI/CD pipelines
โโ> Automate security testing per playbook
โโ> Monitor code quality and security
โโ> Track and remediate vulnerabilities
โโ> Maintain security documentation
Incident Response:
โโ> Follow code security incident procedures
โโ> Investigate security alerts promptly
โโ> Contain and remediate issues
โโ> Document and communicate findings
โโ> Update security controls
Adapting Playbooks to Your Environment:
1. Environment Assessment:
โโ> Evaluate your specific security context
โโ> Identify relevant playbook sections
โโ> Note environment-specific constraints
2. Customization:
โโ> Modify procedures for your tools
โโ> Add organization-specific steps
โโ> Update contact information and escalation paths
โโ> Incorporate internal policies
โโ> Adjust timelines and SLAs
3. Testing:
โโ> Validate playbooks through tabletop exercises
โโ> Test procedures in controlled environments
โโ> Gather feedback from team members
โโ> Refine based on testing results
4. Maintenance:
โโ> Review playbooks quarterly
โโ> Update based on lessons learned
โโ> Incorporate new threat intelligence
โโ> Train team on updates
โโ> Version control all changes
โ ๏ธ IMPORTANT: AUTHORIZED USE ONLY โ ๏ธ
These security playbooks contain operational procedures for:
โ
AUTHORIZED USES:
โข Security operations within your organization
โข Authorized incident response activities
โข Internal security testing with proper approval
โข Purple team exercises with authorization
โข Network security audits with written permission
โข SOC operations and monitoring
โข Security training in controlled environments
โข Compliance and audit activities with authorization
๐ซ STRICTLY PROHIBITED:
โข Unauthorized penetration testing or security assessments
โข Testing on systems without explicit written permission
โข Using playbooks to attack unauthorized systems
โข Exceeding authorized scope of security operations
โข Conducting incident response without authority
โข Accessing systems or data without authorization
โข Using procedures for malicious purposes
โข Any activities violating laws or organizational policies
Before executing any playbook procedures that involve:
- Network scanning or vulnerability assessment
- Penetration testing or security testing
- Access to production systems
- Incident response on organizational assets
- Purple team testing or attack simulation
- Security monitoring or log analysis
You MUST have:
โ Explicit written authorization from appropriate authority
โ Clear scope definition and boundaries
โ Defined rules of engagement
โ Emergency contact information
โ Authorization for specific procedures and techniques
โ Data handling and confidentiality requirements
โ Approved time windows and restrictions
โ Incident escalation procedures
โ
REQUIRED:
โข Follow organizational security policies
โข Comply with IT acceptable use policies
โข Adhere to data handling requirements
โข Respect privacy and confidentiality rules
โข Follow change management procedures
โข Maintain audit trails and documentation
โข Report security incidents per policy
โข Protect sensitive information
๐ซ PROHIBITED:
โข Violating organizational policies or procedures
โข Exceeding granted authority or access levels
โข Bypassing security controls without authorization
โข Accessing data beyond your authorized scope
โข Sharing sensitive information inappropriately
โข Conducting unauthorized security activities
โข Causing service disruption without approval
โ ๏ธ WARNING: Incident Response Operations
AUTHORIZATION REQUIREMENTS:
โข Explicit authority to access affected systems
โข Permission to collect and analyze data
โข Authorization for containment actions
โข Approval for forensic activities
โข Clear chain of command and escalation
LEGAL CONSIDERATIONS:
โข Privacy laws apply to data collection (GDPR, CCPA, etc.)
โข Chain of custody required for evidence
โข Legal hold procedures may be necessary
โข Attorney-client privilege considerations
โข Regulatory notification requirements may apply
CRITICAL REMINDERS:
โ Document all actions with timestamps
โ Maintain chain of custody for evidence
โ Follow proper escalation procedures
โ Preserve evidence integrity
โ Coordinate with legal and compliance teams
โ ๏ธ WARNING: Purple Team Testing
AUTHORIZATION REQUIREMENTS:
โข Written authorization for attack simulation
โข Approval from system owners and management
โข Clear scope and boundaries defined
โข Coordination with IT and security teams
โข Approval for specific attack techniques
TESTING CONSIDERATIONS:
โข Test in non-production when possible
โข Have rollback procedures ready
โข Monitor system stability during testing
โข Communicate status to stakeholders
โข Document all activities thoroughly
PROHIBITED:
๐ซ Testing without proper authorization
๐ซ Exceeding approved scope or techniques
๐ซ Causing service disruption without approval
๐ซ Accessing production data without permission
๐ซ Using testing as pretext for unauthorized access
โ ๏ธ WARNING: Network Security Testing
LEGAL REQUIREMENTS:
โข Computer Fraud and Abuse Act (CFAA) applies
โข Unauthorized access is a federal crime
โข Wiretap Act applies to network interception
โข State computer crime laws also apply
AUTHORIZATION MUST INCLUDE:
โ Specific IP ranges and systems in scope
โ Approved testing methodologies
โ Time windows for testing activities
โ Out-of-scope systems explicitly noted
โ Emergency contact procedures
โ Data handling requirements
PENALTIES FOR UNAUTHORIZED TESTING:
โข Up to 10 years imprisonment (CFAA)
โข Significant financial penalties
โข Civil liability for damages
โข Professional license revocation
โข Career-ending consequences
Core Principles:
- Authorization: Always operate within granted authority
- Integrity: Act honestly and document accurately
- Confidentiality: Protect organizational information
- Competence: Execute only procedures you understand
- Responsibility: Accept accountability for actions
- Professionalism: Maintain high standards
- Legal Compliance: Follow all applicable laws
โ
DO:
โข Verify authorization before executing playbooks
โข Follow playbook procedures systematically
โข Document all actions and findings thoroughly
โข Escalate issues through proper channels
โข Protect sensitive information discovered
โข Maintain professional certifications
โข Continue training and education
โข Coordinate with relevant teams
๐ซ DON'T:
โข Execute playbooks without proper authorization
โข Exceed your granted authority or scope
โข Skip documentation or logging steps
โข Share sensitive findings inappropriately
โข Use playbooks for personal gain or malicious purposes
โข Ignore organizational policies or procedures
โข Bypass security controls without authorization
โข Cause unnecessary risk or disruption
Incident Response:
- Inadvertent evidence destruction
- System instability from containment actions
- Service disruption during investigation
- Privacy violations during data collection
- Improper evidence handling
- Legal exposure from improper procedures
Purple Team Testing:
- Unintended system damage or disruption
- Production impact from testing
- Detection evasion leading to real compromises
- Confusion between real and simulated attacks
- Credential theft during testing
- Data exposure or loss
Network Security Audits:
- System crashes from vulnerability scanning
- Network congestion from testing
- False positive alerts overwhelming SOC
- Accidental access to sensitive data
- Service disruption
- Detection and blocking by security controls
โ
Mitigation Measures:
Planning & Authorization:
โข Comprehensive written authorization
โข Clear scope and boundaries
โข Risk assessment before execution
โข Coordination with stakeholders
โข Emergency response procedures
Technical Controls:
โข Test in non-production first
โข Use snapshots and backups
โข Monitor system health during operations
โข Have rollback procedures ready
โข Maintain emergency contacts
Operational Practices:
โข Follow playbook procedures exactly
โข Document every action taken
โข Communicate status regularly
โข Escalate issues promptly
โข Conduct post-operation reviews
โ ๏ธ DISCLAIMER OF WARRANTIES โ ๏ธ
These security playbooks 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 effectiveness or suitability
โข Warranties of non-disruption
โข Warranties of legal compliance
โข Warranties of fitness for particular purpose
THE AUTHORS, CONTRIBUTORS, AND MAINTAINERS:
โข Make no guarantees about playbook effectiveness
โข Are not responsible for damages from playbook use
โข Do not warrant procedures will work in all environments
โข Are not liable for operational or legal consequences
โข May update or change content without notice
โข Disclaim all liability for unauthorized use
USERS EXPLICITLY ACKNOWLEDGE:
โข They use these playbooks at their own risk
โข They are responsible for obtaining proper authorization
โข They must comply with organizational policies and laws
โข They are liable for their operational activities
โข They understand risks of security operations
โข They accept all consequences of playbook execution
CRITICAL REMINDER:
These playbooks involve SECURITY OPERATIONS that can:
- Cause system disruption or outages
- Result in data loss or exposure
- Lead to legal consequences if misused
- Trigger security alerts and responses
- Have significant organizational impact
The Authors, Contributors, and Maintainers are NOT liable for:
- Direct, indirect, incidental, or consequential damages
- System failures, crashes, or service disruptions
- Data loss, corruption, or exposure
- Security breaches or compromises
- Legal consequences from unauthorized use
- Organizational policy violations
- Professional consequences or termination
- Regulatory penalties or fines
- Operational failures or errors
- Any damages arising from playbook use
Maximum Liability: To the extent permitted by law, total liability shall not exceed the amount paid for these playbooks (zero for free distribution).
We welcome contributions from security professionals to improve and expand this collection.
To Submit a New Playbook:
- Fork the repository
- Create playbook following operational standards
- Include clear procedures and decision points
- Add appropriate warnings and authorization requirements
- Test playbook in controlled environment
- Document expected outcomes and metrics
- Submit pull request with detailed description
Playbook Quality Standards:
- โ Clear, step-by-step procedures
- โ Decision trees and escalation paths
- โ Authorization requirements clearly stated
- โ Risk assessments included
- โ Expected outcomes documented
- โ Metrics and success criteria defined
- โ Communication templates provided
- โ Lessons learned section included
High Priority:
- Cloud security operations playbooks (AWS, Azure, GCP)
- Container security incident response
- Zero-trust architecture operations
- Threat hunting playbooks
- Security automation workflows
- SOAR integration playbooks
- Ransomware response procedures
- Supply chain security operations
- NIST SP 800-61: Computer Security Incident Handling Guide
- SANS Incident Response: https://www.sans.org/security-resources/
- NIST Cybersecurity Framework: https://www.nist.gov/cyberframework
- ISO/IEC 27035: Information security incident management
- CISA Incident Response: https://www.cisa.gov/topics/cyber-threats-and-response/incident-response
- MITRE ATT&CK: https://attack.mitre.org/
- Cyber Kill Chain: Lockheed Martin framework
- Diamond Model: Threat intelligence framework
- OODA Loop: Decision-making framework
- Purple Team Framework: https://www.mitre.org/
- GCIH: GIAC Certified Incident Handler
- GCFA: GIAC Certified Forensic Analyst
- GCIA: GIAC Certified Intrusion Analyst
- CISSP: Certified Information Systems Security Professional
- CISM: Certified Information Security Manager
- CEH: Certified Ethical Hacker
- SANS Reading Room: https://www.sans.org/reading-room/
- US-CERT: https://www.cisa.gov/
- FIRST: Forum of Incident Response and Security Teams
- NIST Computer Security Resource Center: https://csrc.nist.gov/
- ๐ Main Repository
- ๐ฏ START HERE Guide
- ๐ป Cybersecurity Master Guide
- ๐ OSINT Resources
- โ Security Checklists
- ๐ Documentation
- ๐ OPSEC Guidelines
- ๐ PDF Library
๐ Current Playbooks: 8 operational playbooks
๐ Categories: Blue Team, Purple Team, Network Audit, DevSecOps, General Operations
๐ Last Updated: November 2024
๐ฅ Maintained by: Pacific Northwest Computers (PNWC)
๐ Status: Active & Growing
Authorization & Approval:
- โ Written authorization for all security operations
- โ Proper approval from management and system owners
- โ Clear scope and boundaries documented
- โ Emergency procedures and contacts defined
- โ Regular communication with stakeholders
Operational Excellence:
- โ Follow playbook procedures systematically
- โ Document all actions with timestamps
- โ Maintain chain of custody for evidence
- โ Escalate through proper channels
- โ Conduct post-operation reviews
Professional Standards:
- โ Maintain confidentiality of findings
- โ Protect organizational information
- โ Follow ethical guidelines
- โ Continue professional development
- โ Collaborate with relevant teams
- Open an issue on GitHub
- Review playbook procedures thoroughly
- Consult with your security team
- Seek guidance from management when uncertain
- Respect organizational policies
- Share lessons learned from playbook use
- Propose procedure enhancements
- Contribute new playbooks
- Report inaccuracies or gaps
- Help improve documentation
- NIST - Incident response and cybersecurity frameworks
- SANS Institute - Incident response methodology
- MITRE - ATT&CK framework and threat intelligence
- FIRST - Incident response community
- CISA - Cybersecurity resources and guidance
- SOC analysts and incident responders
- Purple team practitioners
- Security operations professionals
- Network security engineers
- DevSecOps practitioners
- Security researchers and educators
Thank you for professional security operations and incident response.
๐ Execute Playbooks Responsibly: Authorization and Professionalism Required
Operational security requires authorization, documentation, and accountability.
Repository: ULTIMATE CYBERSECURITY MASTER GUIDE
Maintained by: Pacific Northwest Computers
โญ Star this repo if you find it useful! โญ
- Client Assessment Findings: DefectDojo and Retesting Workflow
- Cybersecurity Operational Playbooks
- Ethical CTF, research and professional assessment training pathways
- GitHub Security Playbooks & DevSecOps Resources
- HACKRF RF SPECTRUM & WIRELESS SECURITY AUDIT PLAYBOOK
- Incident Response Playbook
- Incident Response Playbook (Enhanced)
- PNWC Staged Security Assessment: Integration Blueprint
- Purple Team Detection Validation: Atomic Red Team, Sigma and Wazuh
- Purple Team Playbook (Detailed)
- Purple Team Playbook (Simple)
- Purple Team Playbook - Multi-Platform Scripts
- ๐ฃ SOP: Phishing Email Analysis
- ๐ Unauthorized Access Investigation Playbook
- WIRELESS & NETWORK SECURITY AUDIT PLAYBOOK
๐ Folder: PlayBooks | โ๏ธ 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