grc-lake 0.3.2

Open-source trust operations, on your evidence lake. Self-hosted GRC engineering: collect read-only evidence from cloud, identity, code, and existing security lakes; evaluate it with deterministic, version-pinned control tests; export snapshots, workpapers, and OSCAL.

• 20 framework packs, 2,252 catalogued requirements (1,965 distinct; FedRAMP Moderate's 287 rows restate NIST SP 800-53 controls), linked through 96 common safeguards. 1,417 requirements have safeguard mappings; 339 have reviewed mappings and the other 1,078 are proposed.
• 25 read-only source adapters (7 in preview), plus OCSF presets for existing security lakes.
• Fails closed: missing, stale, or partial evidence never produces a pass, and proposed mappings are not attestable.
• One engine, four surfaces: console, REST API, CLI, and MCP server. Agents propose; humans approve.

Quick start · Architecture · Evidence modes · Product tour · Self-host · Frameworks · Documentation

Quick start

With Docker Compose v2:

git clone https://github.com/msaad00/grc-lake.git
cd grc-lake
docker compose up

Open localhost:8787/console/dashboard/. The demo binds to loopback and has authentication disabled. Follow the 5-minute tutorial to connect a source and export results.

pip install "grc-lake[server]"
grc-lake fixtures load --company golden --out ./lake --rebase-times
grc-lake assessment status --lake ./lake
grc-lake serve --server --allow-insecure-no-auth --lake ./lake --port 8787

uv sync --frozen --extra dev --extra server
make demo-local

pip install 'grc-lake[mcp]'
GRC_LAKE_LAKE=./lake grc-lake-mcp

Renamed from TrustOps. See the upgrade guide for command aliases, existing volumes and release availability.

The PyPI package is grc-lake, the CLI is grc-lake, and the MCP server is grc-lake-mcp.

Screens show the bundled synthetic company. They demonstrate workflows, not a customer deployment or an audit opinion.

Architecture

flowchart LR
  Sources["Sources<br/>cloud · identity · code · existing lakes"]
  Collect["Collect<br/>read-only · normalize · hash"]
  Evaluate["Evaluate<br/>deterministic, version-pinned control tests"]
  Generations["Assessment generations<br/>hash-verified, published atomically"]
  Snapshots["Snapshots<br/>hash-chained ledger"]
  API["REST API"]
  Console["Console"]
  MCP["MCP server"]
  CLI["CLI"]
  Sources --> Collect --> Evaluate --> Generations --> Snapshots
  Generations --> API
  API --> Console
  API --> MCP
  Generations -. local lake .-> CLI
  Generations -. local lake .-> MCP

Connectors only read from source systems. Deterministic rules own every result; agents can propose changes but do not decide them. Each run publishes a new generation whose artifact hashes are verified before it becomes current, and each snapshot records its predecessor's hash. The CLI works on a local lake; the MCP server reads a local lake or calls the authenticated API. See architecture.

Evidence modes

Both modes feed the same evaluation engine, assessments, and review workflows.

Already have a lake? Start with bring your own lake. Collecting new evidence? Start with connector setup. Lake mappings are experimental; preview and live-provider qualification vary by reader. See the connector catalog for status. Existing-lake readers preserve the source system and materialize assessment evidence into the GRC Lake lake; they do not move the GRC Lake application into your warehouse.

Product tour

Know what is covered

Framework coverage separates assessed controls, missing evidence, and unreviewed mappings. A passing sample does not establish full framework compliance.

Follow evidence to a decision

Inspect the source, freshness, and affected controls before assigning a finding. Closing a task requires fresh verification; approval actions require an eligible human session. Agents can collect, explain, and propose work.

Self-host

Use Docker or Helm, configure SSO and scoped credentials, and choose the storage and writer topology. Evidence stays in storage you operate; data leaves through the connectors, sinks, and model integrations you configure.

• Local mode: one writable replica with a local JSONL lake and SQLite or PostgreSQL.
• Distributed mode: multiple API replicas and tenant workers share PostgreSQL and S3-compatible object storage, with private scratch space and fenced publication. Enable it explicitly using the distributed deployment guide. A single tenant evaluation still runs on one worker; production capacity and provider failover require deployment-specific qualification.
• Warehouse exports have separate setup and qualification requirements. See data flow.
• Authentication is required for production. The loopback demo is a separate setup. Human approval, tenant isolation, and read-only auditor access are enforced at the API boundary.
• Retain evidence deliberately. Use the operations guide for generation archival, history costs, and external integrity checkpoints.

See the connector catalog for implementation and preview status, and credential setup for each source.

Verify a release

Wheels and sdists carry SLSA build provenance, and each GitHub release attaches a CycloneDX SBOM of the locked runtime dependencies:

gh release download v0.3.1 -R msaad00/grc-lake -p '*.whl'
gh attestation verify grc_lake-0.3.1-py3-none-any.whl -R msaad00/grc-lake

Frameworks

Common safeguards connect source evidence to framework requirements. Proposed crosswalks remain review work; reviewed mappings are version-pinned and still need applicable evidence. The legacy fedramp-moderate pack represents the NIST 800-53B Moderate foundation, not a complete FedRAMP authorization package.

Framework packs · Coverage catalog · Common controls · Control families screen · Crosswalk screen

Evidence boundaries

Missing, stale, blocked, or partial evidence cannot establish a passing control. Inventory observations establish presence, not the effectiveness of a control. Exceptions and compensating measures are review records, not automatic passes.

Local fixture tests, exported hashes, and screenshots do not establish live provider qualification, production capacity, certification, or customer adoption. An independently retained checkpoint is needed to detect a complete local history replacement. See evidence recovery and audit readiness.

Documentation

Develop

uv sync --frozen --extra dev --extra server --extra mcp
uv run pytest -q
uv run pre-commit run --all-files
npm --prefix app/web ci
npm --prefix app/web run build

Regenerate documentation images from the running synthetic demo with npm --prefix app/web run demo-screenshots. License: Apache 2.0.