Repository navigation
Compliance
Governance, Risk, and Compliance - frameworks, regulations, and control mapping
Part of the ULTIMATE CYBERSECURITY MASTER GUIDE
Hardening and security governance source lists: Awesome Security, annual reports, and PNWC's curated source map.
Versioned assurance: ASVS/WSTG requirements and tests and CISA SCuBA baselines produce evidence IDs, exceptions and remedial work tracked via client findings.
Dedicated home for Governance, Risk, and Compliance - the major security control frameworks, the data-protection regulations, and a practical approach to mapping one set of controls to many requirements.
Indexes the Compliance & GRC section: GRC fundamentals and a control-mapping approach (this file), the major control frameworks (NIST CSF 2.0, ISO/IEC 27001:2022, SOC 2, PCI DSS 4.0.1, CIS Controls v8, NIST 800-53/800-171), and the key data-protection regulations (GDPR, HIPAA, CCPA/CPRA).
Give practitioners a single reference for which framework applies when, how the frameworks relate, and how to implement controls once and satisfy multiple requirements - tying governance back to the technical controls elsewhere in this repo.
- Choosing a framework for an organization or a customer requirement
- Preparing for an audit or certification (SOC 2, ISO 27001, PCI DSS)
- Mapping existing technical controls to compliance requirements
- Understanding a data-protection obligation (GDPR/HIPAA/CCPA)
- Overview
- What GRC Is
- Choosing a Framework
- Control Mapping (Do It Once, Satisfy Many)
- Folder Contents
- Important Notice
- Resources
Compliance is heavily referenced across this repository but previously had no home. This section consolidates it. The theme throughout: compliance is the evidence that good security controls exist and operate - the technical work lives in the IncidentResponse, Cloud, WebAppSecurity, and Checklists sections; GRC organizes, requires, and demonstrates it.
- Governance - the policies, roles, and accountability that direct a security program (leadership ownership, risk appetite, standards).
- Risk - identifying, assessing, and treating risk (accept / mitigate / transfer / avoid), usually via a risk register and periodic assessment.
- Compliance - demonstrating adherence to chosen frameworks and applicable laws/regulations, with evidence.
A framework provides the control set; risk management decides which controls matter most; governance ensures they are owned and maintained.
| If you need toโฆ | Consider |
|---|---|
| A flexible, risk-based program (US-centric, widely recognized) | NIST CSF 2.0 |
| An internationally recognized certification | ISO/IEC 27001:2022 |
| Assure customers/partners of your controls (SaaS/service orgs) | SOC 2 |
| Handle payment card data | PCI DSS 4.0.1 (mandatory) |
| A prioritized, prescriptive starting set of controls | CIS Controls v8 |
| A US federal / government-adjacent baseline | NIST SP 800-53 / 800-171 |
Details in frameworks.md. Regulatory obligations (GDPR, HIPAA, CCPA) are not optional and apply based on data and jurisdiction - see regulations.md.
A framework mapping supports audits but does not establish compliance or certification.
The frameworks overlap heavily. Rather than implement each in isolation:
- Pick a primary framework (often NIST CSF 2.0 or ISO 27001) as the backbone.
- Implement the underlying technical controls (MFA, logging, encryption, access control, patching) - the substance lives in this repo's technical sections.
- Map those controls to each framework/regulation you must satisfy, so one control (e.g. centralized logging) provides evidence for CSF Detect, ISO A.8.15/A.8.16, SOC 2 CC7, and PCI Req. 10 at once.
- Collect evidence continuously (config, logs, tickets) rather than scrambling at audit time.
The Secure Controls Framework (SCF) and NIST's OLIR mappings publish cross-framework crosswalks to accelerate this.
| File | Description | Status |
|---|---|---|
| frameworks.md | Control frameworks - NIST CSF 2.0, ISO 27001:2022, SOC 2, PCI DSS 4.0.1, CIS Controls v8, NIST 800-53/800-171 | โ Complete |
| regulations.md | Data-protection regulations - GDPR, HIPAA, CCPA/CPRA, and breach-notification duties | โ Complete |
Important
This is educational reference material, not legal or compliance advice. Framework versions, regulatory thresholds, and applicability change and depend on your jurisdiction, industry, and data. Verify against the authoritative source and consult qualified legal/compliance counsel and, where required, a qualified assessor (e.g. a PCI QSA or ISO certification body) before relying on it.
- NIST Cybersecurity Framework
- ISO/IEC 27001
- AICPA SOC 2
- PCI Security Standards Council
- CIS Controls
- Secure Controls Framework (crosswalks)
Repository: ULTIMATE CYBERSECURITY MASTER GUIDE
Maintained by: Pacific Northwest Computers
- frameworks.md - Security control frameworks
- regulations.md - Data-protection regulations
- ../IncidentResponse/README.md - the detection/response controls compliance requires
- ../Checklists/README.md - operational checklists that implement controls
| โฌ ๏ธ Back to Master Index |
๐ Folder: Compliance | โ๏ธ 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