PolicyForge is a portfolio-grade information-security governance suite for the fictional fintech organisation FinNexus Solutions. It shows how a policy programme can move from business context to enforceable controls, evidence expectations, traceability, and ongoing governance.
This is a demonstration artefact, not legal advice or a complete compliance programme. Organisations should tailor the materials, control owners, risk assessments, and legal obligations to their own environment.
- Browse the live policy suite for the best reading experience.
- Read the organisation profile first. It defines FinNexus's scope, operating model, regulatory context, and risk appetite.
- Review the policy style guide to understand the drafting conventions and control-ID format.
- Use the control traceability matrix to trace controls to the mapped frameworks.
| Capability | Evidence in this repository |
|---|---|
| Governance scope and accountability | Organisation profile and policy style guide |
| Enforceable security requirements | Eight focused policies with numbered safeguards and normative language |
| Control-to-framework traceability | Control traceability matrix and audit report |
| Operational governance | Exception log and review cadence tracker |
The suite maps controls to ISO/IEC 27001:2022, NIST CSF 2.0, PCI DSS v4.0.1, the Digital Personal Data Protection Act, 2023 (India), and the GDPR. A framework citation supports traceability; it does not by itself establish compliance.
context/ # Organisation context and policy-authoring standards
org-profile.md # Read first: scope, risk appetite, regulatory context
policy-style-guide.md # Drafting rules and control-ID conventions
policies/ # Authoritative policy source documents
acceptable-use.md
access-management.md
asset-management.md
business-continuity-backup.md
data-classification-handling.md
incident-response.md
password-authentication.md
vendor-third-party-risk.md
mapping/ # Control traceability and its independent review
register/ # Exception and review-cadence governance records
docs/index.html # Hand-authored GitHub Pages viewer
.github/workflows/ # Builds and deploys the viewer from source documents
Organisation profile
↓
Policy style guide ──→ Policies and control IDs
↓ ↓
Review / exception registers ← Control traceability matrix ← Framework requirements
The Markdown outside docs/ is the source of truth. On every push to main, GitHub Actions assembles a temporary Pages site from those source documents and docs/index.html, then deploys it. The generated document copies are deliberately not versioned in this repository.
No build tools, dependencies, credentials, or environment variables are required to review the source documents.
git clone https://github.com/dedsec-terminal/PolicyForge.git
cd PolicyForgeOpen the Markdown files in your editor, or serve the deployed viewer after creating its generated site output through the GitHub Actions workflow. The live site is the simplest option for navigating the complete set.
- Start with the organisation profile.
- Read the policy style guide, then the policies relevant to your domain.
- Inspect the control traceability matrix and its audit report.
- Close with the exception log and review cadence tracker to see how the programme is maintained.
Distributed under the MIT License.