Repository navigation
Certification package and quarterly cycle in FedRAMP's schemas (group 2: CPO, OCR, SDR, CCM) - #503
Merged
Merged
Conversation
sam-aydlette
force-pushed
the
feat/ksi-catalog-corpus
branch
from
November 5, 2026 20:51
46dfc8e to
7a2dc49
Compare
sam-aydlette
force-pushed
the
feat/sdr-schema
branch
from
November 5, 2026 20:52
fc288fd to
8195978
Compare
…ed rules The vendored ksi-catalog.json predated FedRAMP's 2026-10-13 mapping revision: 40 of 46 KSIs mapped fewer (or different) controls than the pinned Consolidated Rules. scripts/sync-ksi-catalog.py now derives the KSI block from the pinned rules (Class C statements where a KSI varies by class, titles from the NIST Rev5 catalog), and a test fails while they differ. Within the Moderate baseline no implementation status changes; SC-45 and SC-45.1 become shared. The projection reaches 59 controls beyond Moderate (was 10). s3.rego drops si-12, which no KSI maps any more. The SSP parity test runs on the catalog as it stood at the SSP's retirement. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every applicable 20x Class C rule, every KSI and every Rev5 Moderate control, each no stronger than what backs it; semver versioning; consumers moved to the schema shape. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…eploy SDR-CSO-MTD Implemented; SDR-CSO-FRR, SDR-CSX-KSI, FRC-CSX-VVK and FRC-CSX-VVR gaps restated for the post-deploy state. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sam-aydlette
force-pushed
the
feat/ksi-catalog-corpus
branch
from
November 5, 2026 21:31
7a2dc49 to
0f5e4fb
Compare
sam-aydlette
force-pushed
the
feat/sdr-schema
branch
from
November 5, 2026 21:31
8195978 to
1db3a03
Compare
sam-aydlette
changed the base branch from
feat/ksi-catalog-corpus
to
feat/frr-records
November 5, 2026 21:32
…y; SDR carries it; cited tests must pass Totally Real Assessment Services, LLC (simulated) runs as a reusable workflow before the deploy job, works from the generated assessor guide, re-runs every cited check, and signs one set under its own workflow identity, which infrastructure/keys/assessor-identity.json pins. The SDR build requires and verifies the set. The unit-test job fails when a test cited as rule evidence did not pass (FRC-CSX-VVR). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ds in allocated blocks Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…oy (MAS-CSO-IIR/FLO/MDI/TPR, FRC-CSX-MAS) - Inventory: the app's browser origins (jsDelivr, Google Cloud Storage) and the VDR's remaining feeds (FIRST EPSS, Grype database) become external services; the CloudTrail trail joins the logging KSIs' evidence domain. - scripts/build-mas.py publishes /.well-known/minimum-assessment-scope.json (+ .md, signed, freshness-governed): information resources, every CSP off-origin host placed or out of scope with a reason, flows with a high-water-mark security category, a metadata inventory, the third-party records with FedRAMP's four fields, and the KSI-to-scope application. It fails the deploy, before the SDR, on any gap. - Classification: 17 new flows covering every external service and data store; an app-delivery group (and its service in the service model). - Third-party records: the four MAS-CSO-TPR fields on all 11; decision fields AI-drafted for the operator to confirm; a decided record without them fails. - scripts/_tpr.py: the CPO's thirdPartyInformationResources, for the CPO hook. - Five rule records flip to Implemented with resolving evidence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ng standard; DEC-165..167 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…, CORS on /.well-known/ - availability-probe.yml + scripts/availability-probe.py: a monitor on GitHub Actions (outside AWS) probes the site, trust center, /.well-known/, the Silk Reeling app and its sign-in every 15 minutes, keeps 35 days, derives incidents, and publishes JSON + Markdown to the availability-status branch; an ongoing incident fails the run. The deploy fails when that feed is missing or stale, and availability.json is now built from it, never from deploys. - CloudFront standard logging v2 (bootstrap/trust-access-logs.tf) with a field allowlist that drops IP, cookies, query string, user agent and referrer; raw records expire after 90 days (logging.tf). The deploy fails unless the delivery exists within the allowlist, and publishes monthly aggregates for /.well-known/ and /trust/ only (access-summary.json, 13 months). - /.well-known/* gets its own response-headers policy with read-only CORS; the deploy checks CORS, JSON Content-Type and nosniff live. - DEC-160 (AI-drafted for the operator): what is logged, and a party's own records on request. - CDS-CSO-AVR, CDS-TRC-USH, CDS-TRC-ACL flip to Implemented. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er-service crypto modules The Secure Configuration Guide is generated on every deploy from one source (data/secure-configuration.json) and published signed as /.well-known/secure-configuration-guide.json and .md: each top-level and privileged account with how it is named, accessed, configured, operated and decommissioned; each setting with who can operate it, the recommended value, its implication and the API that reads and changes it; a version and release history whose defaults digest the build enforces. It states the system as it is: virtual TOTP MFA on root and the operator user, an accepted finding (DEC-150, extending DEC-025). scripts/check-secure-config.py reads the live settings read-only before the SDR is built, compares them with the guide and publishes the export as /.well-known/security-settings.json; an uncovered deviation or an unreadable setting fails the deploy. The deploy role's reads are a new bootstrap policy (infrastructure/bootstrap/deploy-config-reads.tf), applied by the operator. The guide also carries the cryptographic module per service, joined with the inventory (the build fails on an unmapped component type), citing the KMS HSM's CMVP certificate (#4884) and stating where AWS publishes none (DEC-152). Flips SCG-CSO-AUP/PUB/RSC/SDF, SCG-ENH-API/CMP/EXP/MRG/VRH and CMU-CSO-CMD/UVM/CAT to Implemented. Decision records DEC-150..152 and the guide's text are AI-drafted for the operator to confirm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ished documents; lossless human views with round-trip check Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # data/decisions.json # infrastructure/schemas/freshness-config.json
# Conflicts: # .github/workflows/deploy-with-opa.yml # data/decisions.json # tests/test_decisions.py
Generate the signed trust manifest and the complete .view.md views (round trip checked) on every deploy, rebuild the VDR views nightly, and add a static trust page section: the certification data index, the simulated assessment, how to request access, the sharing standard and the access logging privacy notice (moved from docs/trust). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Flip CDS-CSO-CBF, IRP, RIS, RPS, UTC; CDS-TRC-AAI, HMR, PAC, SSM; CDS-UTC-AAD, AGA; FRC-CSX-VVR; IVV-CSO-DUS, STE, FIA, ICP; IVV-CSX-AIA; SDR-CSO-FRR, citing the deploy steps, tests, artifacts and decisions that make each true. Agency records are flagged simulated (agency), assessor records simulated (assessor). Add the assessor guide tests (fail closed on an ungoverned artifact), and have the simulated assessor fail a KSI the signal does not report passing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t installs nothing CodeGuard findings: the assessor's fetcher accepted any URL scheme and host, and the job holding id-token: write also installed unpinned PyPI tooling and ran the provider's tests. The fetch is now limited to https://samaydlette.com, and signing moves to a separate job that installs only cosign. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… 2: W3 + W4) CPO rebuilt in FedRAMP's 2026-06-24 schema (folds in build-cds-overview: per-service categories, simulated FedRAMP ID and UEI, semver metadata); OCR in schema with incidents, feedback summary, review schedule and a sensitivity screen; fixed CCM calendar with holiday-aware review dates and an .ics; frozen quarterly issues with signed snapshots; FedRAMP Certification Reports published byte-identical (simulated FedRAMP); simulated package submission log; FedRAMP ID deploy gate; SDR per-KSI statements and per-KSI daily metrics with 30-day and 1-year summaries; unattended package-maintenance workflow with its own narrow bootstrap role and deploy preflight. DEC-100..107 AI-drafted for the operator to confirm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…trust-scope-assessor Conflicts: deploy-with-opa.yml (edge steps kept before group 2's renamed CDS step; the folded-in COP dropped from the trust-scope lists; group 2's report signing and redaction entries kept), offering.json (the SCG fork's module validations in group 2's layout), decisions.json (union by ID), test_frr_records.py (theirs). DEC-150 now names the operators group, not an IAM user, so the new no-IAM-user-name test holds; IRP evidence follows the renamed CDS step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…he assessor's summary; FedRAMP ID on the trust-center files Wire group 5's four CPO fields into build-cpo.py, one small function each: serviceProperties.trustCenter, serviceProperties.secureConfigurationGuidance, thirdPartyInformationResources (scripts/_tpr.py) and the simulated assessor's overall summary, quoted verbatim from its verified signed set under providerExtensions.independentAssessment. The CPO refuses to build without the set; the deploy and the daily package maintainer pass it (the maintainer also passes it to the SDR rebuild, which previously dropped the assessor results). The package submission now refuses a CPO missing any of the four (known-bad fixture). Stamp the offering's FedRAMP ID at top level on trust-center.json, trust-manifest.json, availability.json and the independent availability feed, policy-index.json, assessor-guide.json, simulated-assessment.json, agency-access-exercise.json and frr-evidence.json, add them to the gate's REPORTS, make a named site file without one fail (known-bad fixture), and run the gate once the last listed file is built, before publication. Flip CPO-CSO-OSA (simulated assessor), CPO-CSO-OVR, CDS-CSO-PUB (UEI simulated sam-gov), FRC-CSO-JSN and FRC-CSO-PKG (simulated fedramp) to Implemented. CDS-CSO-FID stays Partially Implemented for integration. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Trust center, scope and simulated assessor (W8, W10)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SCN-Type: not-significant
SCN-Rationale: Reshapes and adds self-published certification artifacts and their build/maintenance automation; no change to the service's boundary, data, interconnections or customer-facing behavior.
Changed
scripts/build-cpo.py, rewritten in small section functions; written throughwrite_validated). Folds inbuild-cds-overview.py(deleted;certification-overview-package.*retired and listed for removal in the publish step). Per-service FIPS 199 categories and boundary groups (builder fails on a category above the system's or an unknown group), a not-included list, semvermetadata.versionpluslastUpdated/updateSource, and the accountable official. FedRAMP ID = FedRAMP's fallback (provider name and acronym) suffixedPROOF-OF-CONCEPT-NOT-A-REAL-FEDRAMP-ID, flaggedfedramp. UEINOT-A-REAL-UEI-0000, flaggedsam-gov. No email field ever holds a URL; the FedRAMP Security Inbox contact comes fromoffering.fedramp_security_inboxwhen present.impact_level_canonical(which says "Rev 5") is dropped from the CPO. Group 5's four fields (OSA, SCG, TPR, trust center) are left out, so each can be added by one small function.scripts/build-ocr.py): rolling report plus--issuemode. Incidents come fromdata/incidents.jsonwhen present (exercises are labelled). It also carries the anonymized feedback summary (data/ocr-feedback.json), the review schedule and standing agenda, the public-release determination (DEC-101), and a sensitivity screen (scripts/_sensitivity.py) that fails the build on account IDs, foreign email addresses, IPs, AWS keys, tokens or @Handles.infrastructure/schemas/ccm-calendar.json,scripts/_ccm.py):/.well-known/quarterly-review.ics;.github/ISSUE_TEMPLATE/).scripts/issue-ocr.py): on each issue date, a frozenocr-issue-<date>.json/.md,snapshots/<date>/with a signed manifest, and the indexocr-issues.json. An issued file is never rebuilt or overwritten.scripts/publish-certification-reports.py,data/fedramp-certification-reports/): each report is checked against its recorded sha256 and published byte-identical, with a signed index that records the 2-week window. The one report is plainly fake (simulated FedRAMP).scripts/submit-package.py): checks schema validity, that every applicable rule appears exactly once, one FedRAMP ID, andcertificationType20x. It then hands the package to a simulated intake function and appends a signed entry topackage-submission-log.jsonwhen the content changes. Nothing is sent.scripts/check-fedramp-id.py): the files it checks are theREPORTSconstant, one line per report.simulatedflag inproviderExtensions.simulated, plus a summary count;.github/workflows/package-maintenance.yml):workflow_call), and on demand, in thepackage-maintenanceenvironment;It also has a new bootstrap role,
infrastructure/bootstrap/package-maintenance.tf, with PutObject on exactly the package keys and prefixes plus CreateInvalidation (no delete, no read). The deploy job gets aPackage maintainer preflightstep (scripts/check-package-maintainer.py).deploy-with-opa.yml: build, sign, redaction-list and publish entries; three new gate steps; thepackage-maintainerjob;freshness-config.json: the SDR, CPO and OCR at 336 h onmetadata.lastUpdated, plus four new entries;evidence-nightly.ymlandverify-published.sh: also accept the maintenance identity for the SDR, CPO and OCR;reconcile.py: reads the CPO'sproviderExtensions;data/frr-records.json: this group's 34 records;tests/test_freshness_config.py: includes the maintenance publisher;tests/test_frr_records.py: the simulated-count test is now relative to the committed records.Effect
python3 scripts/_frr.py:Simulated counterparties: assessor 2 (IVV-CSO-SEE, IVV-CSO-SEI), fedramp 1 (CDS-CSO-FRC).
Of this group's 34 records, 29 are now Implemented. Five remain Partially Implemented:
REPORTSVerified
make checkpasses.check-policy-annotations.py,check-exceptions.py,check-wasm-safe.py.tests/test_certification_cycle.py(66) andtests/test_sdr_ksi_metrics.py(11), with known-bad fixtures undertests/fixtures/cycle/bad/, each failing for its named reason. They fail on the base: import errors, and two failures intest_freshness_config.py.${{ }}reaches arun:, and nothing is hardcoded. One fix was applied: the maintainer now starts a new issue index only on a definite 404 or 403, and any other fetch failure stops the run.Residual
fedramp-certification-reportsindex: the report'sreceived_onis 2026-11-05. If the first deploy lands after 2026-11-19, the index records it as published late. This is a warning, never hidden.--completedeploy gate still fails, by design, until the other groups close their records.Needs human
package-maintenance.ymlpublishes the CPO, SDR, OCR, issues and snapshots without a reviewer. Needed for it:infrastructure/bootstrap/package-maintenance.tf(Sam).AWS_PACKAGE_MAINTENANCE_ROLE_ARNfrom thepackage_maintenance_role_arnoutput.package-maintenanceGitHub Environment, restricted tomainwith no required reviewer.incident-reports.tf), so the two could be merged later.ocr-feedback,quarterly-review-registrationandpackage-maintenanceso the issue forms and the alert apply them.security.txt,ksi-signal.json(build-ksi-signal.pyoperator_contact) and the retired overview. The new CPO and OCR avoid it. Consider a samaydlette.com address.data/frr-records.jsonimplementation text, the issue-form wording, and the simulated FedRAMP Certification Report.metadata.lastUpdated.Couldn't verify
.icscontent type is not observed.🤖 Generated with Claude Code