An extensible, open-source platform for Information Security Governance, Risk, and Compliance (GRC) standardization and automation.
Organizations and security practitioners face significant fragmentation when managing multiple regulatory and security frameworks simultaneously. Open GRC Framework is being architected to solve core challenges in security standardization by providing a unified, machine-readable, and community-extensible platform.
- Cross-Standard Control Mapping: Seamlessly map and harmonize security controls across ISO/IEC 27001, NIS2 Directive, DORA, GDPR, and NIST CSF.
- Modular Plugin Architecture: Designed from the ground up so GRC specialists and security engineers can build and share custom compliance modules, audit checklists, and risk assessment templates.
- Compliance-as-Code: Transform static spreadsheets and documents into structured, version-controlled schemas (JSON/YAML).
The project is currently in its initial design and core infrastructure phase. The planned modular structure includes:
open-grc-framework/
├── core/
│ ├── schema_validator.py # Validates compliance mapping YAML files
│ └── cli_reporter.py # Generates unified cross-framework coverage reports
├── schemas/ # Machine-readable JSON/YAML definitions (ISO 27001, NIS2, DORA, GDPR)
├── plugins/ # Community-contributed extensions & automated evidence collectors
├── templates/ # Standardized ISMS & GRC documentation templates
└── docs/ # Architecture guides & contributor documentation
You can locally validate the compliance mapping schemas and generate a unified coverage report using Python 3.10+.
git clone https://github.com
cd open-grc-framework
pip install -r requirements.txtRun the core validator against any YAML mapping file in the schemas/ directory:
python core/schema_validator.py schemas/iso27001-nis2-mapping-sample.yamlScan all mapped frameworks and display a consolidated governance summary:
python core/cli_reporter.py- Phase 1: Concept & Core Requirements — Define primary GRC bottlenecks and cross-mapping logic.
- Phase 2: Foundational Infrastructure — Finalize baseline YAML schemas, validation engine, and CI/CD workflows.
- Phase 3: Core Engine MVP — Expand risk scoring logic and modular plugin APIs.
- Phase 4: Community Ecosystem — Scale community-contributed compliance modules and documentation.
We welcome collaboration from Information Security Specialists, GRC Consultants, Auditors, and Open-Source Developers.
Please read our Contributing Guidelines or open an Issue to suggest compliance frameworks, data schemas, or architectural improvements.
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.