Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ Full detail lives in [`docs/operations/DEPLOYMENT_RULES.md`](docs/operations/DEP
6. **stpa-freshness-check** — STPA source changed without regenerating artifacts. Fix: run `uv run python scripts/check_stpa_freshness.py`.
7. **pytest-logic** — address the failing test. Confirm no background `kubectl port-forward` tunnels are leaking live GKE state into local tests.
8. **Bandit / security-scan** — rotate credentials or address Bandit SAST (run in `pytest-logic`) or CVE findings (`security-scan.yml`); never suppress the scan.
9. **Documentation reference check (Gate G9, `lint` job)** — a document cites a file path, link target, or Python symbol that does not exist at HEAD. Fix: run `make docs-check` (or `uv run python scripts/check_doc_references.py --path <scope>`) and correct the reference — never delete the gate's scope to make it pass. The scope is `DOC_SCOPE` in that script, its only copy. `CHANGELOG.md` and `docs/partners/**` are outside the gate's scope by design. A document that must name a path removed from HEAD (for example, a closed POA&M entry describing a deleted file) pins it to a mainline commit where it existed, as `<sha>^:<path>` (git's revision syntax), and G9 verifies the pin against history; the `lint` job checks out full history for this. Never add a removed path to the `KNOWN_DOCUMENTED_GAPS` waiver, which nothing verifies. Pins break if `main`'s history is rewritten: whoever rewrites it owns re-pinning every citation the rewrite orphans, and G9 names each one.
9. **Documentation reference check (Gate G9, `lint` job)** — a document cites a file path, link target, or Python symbol that does not exist at HEAD. Fix: run `make docs-check` (or `uv run python scripts/check_doc_references.py --path <scope>`) and correct the reference — never delete the gate's scope to make it pass. The scope is `DOC_SCOPE` in that script, its only copy. `CHANGELOG.md` and `docs/partners/**` are outside it by design, and most of the rest of `docs/` is outside it until `POAM-2026-224` widens it area by area: a document outside `DOC_SCOPE` is unverified, not verified. A document that must name a path removed from HEAD (for example, a closed POA&M entry describing a deleted file) pins it to a mainline commit where it existed, as `<sha>^:<path>` (git's revision syntax), and G9 verifies the pin against history; the `lint` job checks out full history for this. There is no waiver: a reference to an artifact that never existed is corrected, not excused. A record withdrawn as untrue moves verbatim to `compliance/archive/retracted/` under a first-line `> **RETRACTED <date>**` notice naming its POAM item; G9 verifies the notice and the POAM row and skips the preserved body. Pins break if `main`'s history is rewritten: whoever rewrites it owns re-pinning every citation the rewrite orphans, and G9 names each one.

**Never suggest disabling or skipping a CI check as a fix.**

Expand Down
Original file line number Diff line number Diff line change
@@ -1,3 +1,13 @@
> **RETRACTED 2026-11-15** — Withdrawn in full under `POAM-2026-224`. This report records a security assessment that did not take place. It is preserved below verbatim as last committed at `a2a338b8`; nothing in it is a current claim.
>
> - **No assessment artifacts.** It describes interviews with system administrators, AI model operators, and compliance engineers, and tests including Lula execution, TLS endpoint tests, HMAC bypass scenarios, pip-audit, Trivy, and red-team exercises. No interview record or test output exists in the repository, and the assessor is not identified.
> - **It cites a plan at a path that never existed.** Its related Security Assessment Plan is cited at `docs/compliance/us_fed/SECURITY_ASSESSMENT_PLAN.md`, which exists in no commit. The draft plan it first cited (`00442dec^:docs/security/SECURITY_ASSESSMENT_PLAN.md`) was deleted on 2026-07-30 (`00442dec`), and `a2a338b8` (2026-09-16) re-pointed the citation to the path above instead of removing it. No record exists of the formal assessment that plan scheduled for 2026-Q2.
> - **Its disclosure of a rewrite was removed.** It is dated 2026-03-06 and was edited six times afterwards (`c7174e05`, `edba329b`, `65949083`, `00442dec`, `94f920bc`, `a2a338b8`). `c7174e05` (2026-06-06) rewrote its findings and added the note "this SAR was written against an earlier architecture version and has been updated to reflect the current pipeline". `65949083` (2026-07-08), a rewrite of internal-facing documents for public release, deleted that note without replacing it, and the Document History still shows a single 1.0 entry. From then on the report presented later content as a record dated 2026-03-06.
> - **It reports a mechanism that does not exist.** FIND-010's "monitoring alert added for bypass detection" has no alert policy in `infra/`.
> - **The §7 Assessor Certification is withdrawn.**
>
> Findings that remain valid are tracked in [`docs/POAM.md`](../../../docs/POAM.md).

# Security Assessment Report (SAR) — Q1 2026

> **Public Context Note:** This Security Assessment Report (SAR) is published as part of CAGE's commitment to open-source security transparency. It documents the findings of the initial pre-authorization gap assessment conducted in Q1 2026 against the NIST SP 800-53 Rev. 5 HIGH baseline. This is a pre-ATO gap assessment — not a formal authorization package. Findings marked "Resolved" or "Closed" have been remediated; open findings are tracked in [`docs/POAM.md`](../../docs/POAM.md). Internal role assignments (ISSO, SCA, AO) are omitted from this public version.
Expand Down
4 changes: 2 additions & 2 deletions compliance/boundary/AUTHORIZATION_BOUNDARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
| Authorizing Official (AO) | [AO NAME — TBD] |
| Cloud Platform | Google Kubernetes Engine (GKE) on Google Cloud Platform (GCP) |
| Deployment Namespace | `governance-stack` |
| Related Documents | `compliance/categorization/FIPS199_CATEGORIZATION.md`, `compliance/rar/RISK_ASSESSMENT_REPORT.md`, `compliance/sar/SAR_2026Q1.md`, `docs/compliance/us_fed/SECURITY_ASSESSMENT_PLAN.md` |
| Related Documents | `compliance/categorization/FIPS199_CATEGORIZATION.md`, `compliance/rar/RISK_ASSESSMENT_REPORT.md`. No security assessment plan is in force, and the 2026-Q1 security assessment report was retracted on 2026-11-15 (`compliance/archive/retracted/SAR_2026Q1.md`, `POAM-2026-224`). |

---

Expand All @@ -33,7 +33,7 @@ This Authorization Boundary Document defines the logical and technical boundary
4. Identifies security controls that are inherited from the Common Control Provider (GCP/GKE)
5. Provides a visual representation of the system boundary

The authorization boundary governs the scope of the Security Assessment Plan (`docs/compliance/us_fed/SECURITY_ASSESSMENT_PLAN.md`), the Security Assessment Report (`compliance/sar/SAR_2026Q1.md`), and the System Security Plan (SSP).
The authorization boundary sets the scope of the System Security Plan (SSP) and of any future security assessment. No security assessment plan is in force: the draft plan was deleted on 2026-07-30 (`00442dec`), and the 2026-Q1 security assessment report was retracted on 2026-11-15 because the assessment it records did not take place (`POAM-2026-224`).

### 1.2 Scope

Expand Down
2 changes: 1 addition & 1 deletion compliance/rar/RISK_ASSESSMENT_REPORT.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
| Risk Assessment Lead | [ISSO NAME — TBD] |
| Authorizing Official (AO) | [AO NAME — TBD] |
| Assessment Methodology | NIST SP 800-30 Rev. 1 |
| Related Documents | `docs/POAM.md`, `compliance/sar/SAR_2026Q1.md`, `compliance/categorization/FIPS199_CATEGORIZATION.md`, `compliance/boundary/AUTHORIZATION_BOUNDARY.md` |
| Related Documents | `docs/POAM.md`, `compliance/archive/retracted/SAR_2026Q1.md` (retracted 2026-11-15), `compliance/categorization/FIPS199_CATEGORIZATION.md`, `compliance/boundary/AUTHORIZATION_BOUNDARY.md` |

---

Expand Down
10 changes: 10 additions & 0 deletions compliance/risk_acceptance/THRESHOLD_TRACEABILITY_MATRIX.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@
> **ISO 42001:** A.5.2 (Policies for AI risk), A.9.4 (Monitoring)
> **Reference:** NIST SP 800-53 Rev. 5, EO 14028, NIST SP 800-218 (SSDF)

> **⚠️ Evidence Withdrawal and Signing Hold (2026-11-15, `POAM-2026-222` in [`docs/POAM.md`](../../docs/POAM.md)):** The `Langfuse Metric` column of §2.1 and Appendix B were written as a design specification and describe a Langfuse custom-metric backend that was never built. None of the `cage.<subsystem>.<metric>` names they list has ever been emitted by `src/` or `infra/`; every metric CAGE emits is a `cage_*` Prometheus series. The column and Appendix B are withdrawn as monitoring evidence, along with the two compensating controls that rest on mechanisms as written that do not exist: RA-001 (1), which names a Langfuse compliance-project log as the 100% governance-decision record (decision custody is the Redis DB 1 `cage:evidence:stream` hot custody buffer feeding KMS-signed WORM archival), and RA-002 (1), since `CronJob/lula-audit` injects no synthetic evaluations. Rows are left unchanged until each has an owner-recorded disposition under `POAM-2026-222`: implement the metric, re-point to real telemetry, or withdraw the monitoring claim and reopen the risk.
>
> **Signing hold:** RA-001, RA-002, RA-003, and RA-004 (§5) and the §6 approval block **must not be signed** until every §2.1 row has a recorded disposition under `POAM-2026-222`. An acceptance signed before then would rest on monitoring that does not exist.

---

## Table of Contents
Expand Down Expand Up @@ -83,6 +87,8 @@ Threshold IDs follow the pattern `THR-<CATEGORY>-<NNN>`:

### 2.1 Full Threshold Registry Table

> **Note (2026-11-15):** The `Langfuse Metric` column below is withdrawn as monitoring evidence pending per-row dispositions under `POAM-2026-222` (see the notice at the top of this document). The THR-AUD-003 entry was corrected in `#769` under `POAM-2026-010`.

| Threshold ID | Threshold Name | Value | Unit | Source Control | Code Location | Lula Validation | Langfuse Metric | POAM Ref | Risk Acceptance |
| ---------------- | ---------------------------------------------------- | ----------- | ------------------- | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **THR-FIN-001** | Minimum Cash Balance Floor | 1,000.00 | USD | CM-6, AC-3, RA-3 | `governance_thresholds.json` → `cbf.min_cash_balance`; enforced in [`src/gateway/governance/safety/cbf_engine.py`](../../src/gateway/governance/safety/cbf_engine.py) (**v3.0.0:** `safety.py` removed) | `lula-validation-cm6.yaml` (CM-6 config enforcement) | `cage.fin.cash_balance_floor_usd` (gauge) | — | Operational floor; set by risk management. Lower bound must be ≥ $500 per financial services policy. |
Expand Down Expand Up @@ -297,6 +303,8 @@ This section documents thresholds that represent **known risk acceptances** —

## 6. Approval Block

> **Signing hold (2026-11-15):** Do not sign this page until every §2.1 row has a recorded disposition under `POAM-2026-222` (see the notice at the top of this document). The AO attestation below accepts RA-001 through RA-004 "with the compensating controls described in Section 5", and two of those compensating controls are withdrawn.

```
================================================================================
CAGE THRESHOLD TRACEABILITY MATRIX — SIGNATURE PAGE
Expand Down Expand Up @@ -367,6 +375,8 @@ it carries formal risk acceptance authority:

## Appendix B: Langfuse Metric Naming Convention

> **Note (2026-11-15):** No metric following this convention has ever been emitted, and Langfuse holds no custom counters, gauges, or histograms in CAGE's design. The governance-critical metrics listed below do not exist (`POAM-2026-222`). Emitted metrics are `cage_*` Prometheus series scraped from `:9090/metrics`.

All CAGE Langfuse metrics follow the schema: `cage.<subsystem>.<metric_name>`

Metric types:
Expand Down
4 changes: 2 additions & 2 deletions compliance/ssp/SYSTEM_SECURITY_PLAN_OUTLINE.md
Original file line number Diff line number Diff line change
Expand Up @@ -362,8 +362,8 @@ _The following documents constitute the NIST RMF authorization package and relat
| System Security Plan — EU_ECB | `compliance/oscal/system-security-plan-eu-ecb.yaml` | OSCAL SSP — EU AI Act / GDPR Art. 22 / DORA | ✅ Exists |
| System Security Plan — APAC_MAS | `compliance/oscal/system-security-plan-apac-mas.yaml` | OSCAL SSP — MAS FEAT / MAS Notice 655 / MAS TRM §6.3 | ✅ Exists |
| Assessment Results | `compliance/lula/assessment-results.yaml` | OSCAL assessment results (Lula-generated) | ✅ Exists |
| Assessment Plan | `compliance/oscal/assessment-plan.yaml` | OSCAL assessment plan | ⬜ Pending |
| POA&M (OSCAL) | `compliance/oscal/plan-of-action-milestones.yaml` | OSCAL POA&M representation | ⬜ Pending |
| Assessment Plan | None: no OSCAL assessment plan has been written | OSCAL assessment plan | ⬜ Not created |
| POA&M (OSCAL) | None: the POA&M is maintained in Markdown ([`docs/POAM.md`](../../docs/POAM.md)) | OSCAL POA&M representation | ⬜ Not created |
| Lula Specifications | `compliance/lula/lula-validation-*.yaml` | Automated control validation specifications (29 manifests) | ✅ Exists |

---
Expand Down
Loading
Loading