Skip to content

G.U.A.R.D. Documentation Hub

Generalized Universal Automated Regulatory Deployment

G.U.A.R.D. is an automated compliance verification tool that bridges the gap between regulatory requirements and software development. By leveraging a Compliance-as-Code (CaC) model, it enables organizations to map abstract compliance standards (such as NEN 7510 and ISO 27001) directly to codebase-level controls and enforce them continuously in CI/CD pipelines.

High-Level Verification Flow

G.U.A.R.D. shifts compliance verification earlier in the delivery lifecycle. Instead of auditing code post-deployment, legal requirements are formalized into a machine-readable compliance registry and validated on every commit.

graph LR
    A[Legal Intent] -->|Formalize| B("Compliance Registry YAML")
    B --> C{Guard Audit Gate}
    C -->|Auto-Enforce| D[CI/CD Pipelines]
    D -->|Verify| E[Secure Deployment]

Repository Structure

The codebase is organized into three main components:

  • guard-audit-gate/: The core CLI compliance compiler and checker engine. Written in Node.js & TypeScript.
  • mock-epr/: A demonstration Electronic Patient Record (EHR) application implemented in TypeScript.
  • mock-epr-python/: An alternative demonstration Electronic Patient Record application implemented in Python.
  • docs/: System documentation and architectural guides.

Explore the documentation to understand, configure, and integrate the G.U.A.R.D. framework:

  • Motivation: The problem of compliance drift and how G.U.A.R.D. addresses it through continuous compliance.
  • Design & Architecture: Deep-dive into registry schema design, code change tracking, and internal components.
  • Usage Guide: Instructions on installing the CLI, using parameters, and setting up CI/CD pipeline integration.

Project Governance & License

G.U.A.R.D. is open-source software released under the Apache License 2.0. This ensures that the Compliance-as-Code logic and enforcement checks are transparent, auditable, and reusable.

For the full legal terms, see the LICENSE file. For third-party notices, refer to the NOTICE file.