Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
0f5e4fb
KSI catalog: FedRAMP's current KSI-to-control mappings, from the pinn…
sam-aydlette Nov 5, 2026
f189643
feat(sdr): Security Decision Record in FedRAMP's SDR schema
sam-aydlette Nov 5, 2026
1db3a03
feat(frr): SDR records state what the schema-shaped SDR delivers on d…
sam-aydlette Nov 5, 2026
4c492c4
feat(assessor): simulated assessor signs a keyless set on every deplo…
sam-aydlette Nov 5, 2026
567109b
test(decisions): migration assertions cover DEC-001..099; later recor…
sam-aydlette Nov 5, 2026
f4e7f97
Merge remote-tracking branch 'origin/feat/frr-records' into feat/sdr-…
sam-aydlette Nov 5, 2026
e390c0a
feat(mas): Minimum Assessment Scope generated and gated on every depl…
sam-aydlette Nov 5, 2026
8fa18ee
feat(trust): agency access register, denial clock and exercise; shari…
sam-aydlette Nov 5, 2026
6de6236
feat(trust): independent availability monitor, private access logging…
sam-aydlette Nov 5, 2026
5f7723e
feat(scg,cmu): secure configuration guide as data, live comparison, p…
sam-aydlette Nov 5, 2026
ff5903a
feat(trust): policy index covers procedures, concrete practices, publ…
sam-aydlette Nov 5, 2026
4078bb6
Merge remote-tracking branch 'origin/feat/sdr-schema' into feat/trust…
sam-aydlette Nov 5, 2026
bc54354
Merge branch 'feat/g5-mas' into feat/trust-scope-assessor
sam-aydlette Nov 5, 2026
b93adb9
Merge branch 'feat/g5-edge' into feat/trust-scope-assessor
sam-aydlette Nov 5, 2026
3601772
Merge branch 'feat/g5-scg' into feat/trust-scope-assessor
sam-aydlette Nov 5, 2026
036a720
Trust manifest, human views, trust page data and access section
sam-aydlette Nov 5, 2026
bb81522
Bring the W8/W10 trust-center, scope and assessor records to Implemented
sam-aydlette Nov 5, 2026
1f0a029
Lint: zip strict in the manifest test
sam-aydlette Nov 5, 2026
f219a96
Simulated assessor: fetch only https from the site; sign in a job tha…
sam-aydlette Nov 5, 2026
002a4db
Certification package and quarterly cycle in FedRAMP's schemas (group…
sam-aydlette Nov 5, 2026
04c58ef
chore: stop tracking a worktree's .venv symlink
sam-aydlette Nov 5, 2026
fd67f27
Merge remote-tracking branch 'origin/feat/frr-records' into feat/sdr-…
sam-aydlette Nov 5, 2026
dcf866e
Merge origin/feat/sdr-schema (group 2's schema-shaped CPO) into feat/…
sam-aydlette Nov 5, 2026
7e87ff0
CPO: trust center, secure configuration guidance, third parties and t…
sam-aydlette Nov 5, 2026
00af685
Merge pull request #509 from sam-aydlette/feat/trust-scope-assessor
sam-aydlette Nov 6, 2026
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
36 changes: 36 additions & 0 deletions .github/ISSUE_TEMPLATE/agency-access.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
name: Agency access to the certification package
description: For a federal agency (or FedRAMP) to be put on record, to withdraw, or to ask for the access inventory. The package itself is public and needs no request.
title: "Agency access: "
labels: ["agency-access"]
body:
- type: markdown
attributes:
value: |
**Everything in the certification package is already public** at https://samaydlette.com/trust/ and https://samaydlette.com/.well-known/trust-manifest.json; you do not need to ask to read it.
File this form to put your agency or system **on record** (so you are counted in the access inventory and can be told about changes), to **withdraw** an earlier record, or, for FedRAMP, to **request the inventory**.
This repository is public, so this issue is public. **Name agencies and systems, never people**; do not include names, email addresses or phone numbers. For a private request, use the security contact in `/.well-known/security.txt` instead.
This is a proof of concept with no federal data and no agency sponsor. Procedure: docs/procedures/agency-access.md.
- type: dropdown
id: kind
attributes:
label: Request
options:
- Put my agency or system on record (access)
- Withdraw an earlier record (withdrawal)
- FedRAMP request for the access inventory (inventory-request)
validations:
required: true
- type: input
id: agency
attributes:
label: Agency (or FedRAMP)
validations:
required: true
- type: input
id: system
attributes:
label: System or service (optional)
- type: input
id: withdraws
attributes:
label: For a withdrawal, the earlier request (AAR-...)
25 changes: 25 additions & 0 deletions .github/ISSUE_TEMPLATE/ocr-feedback.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
name: Ongoing Certification Report feedback
description: Ask a question or give feedback about one Ongoing Certification Report (CCM-OCR-FBM). This is public; for anything sensitive, use the security contact in /.well-known/security.txt instead.
title: "OCR feedback: "
labels: ["ocr-feedback"]
body:
- type: markdown
attributes:
value: |
Questions and feedback about an Ongoing Certification Report. Reports are listed at https://samaydlette.com/.well-known/ocr-issues.json.
This channel is public. Each quarter the operator publishes an anonymized summary of the questions and answers in the next report (CCM-OCR-AFS): names, agencies and anything identifying are removed.
Do not include sensitive information here. For anything sensitive, use the security contact in https://samaydlette.com/.well-known/security.txt.
- type: input
id: ocr
attributes:
label: Report issue date
description: The issue date of the report you are asking about (YYYY-MM-DD). Links from a report fill this in.
placeholder: "2026-11-24"
validations:
required: true
- type: textarea
id: question
attributes:
label: Question or feedback
validations:
required: true
24 changes: 24 additions & 0 deletions .github/ISSUE_TEMPLATE/quarterly-review-registration.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
name: Quarterly Review registration
description: Register for a Quarterly Review (CCM-QTR-REG). The operator sends the video-call link to registered parties. This is public; to register privately, use the security contact in /.well-known/security.txt.
title: "Quarterly Review registration: "
labels: ["quarterly-review-registration"]
body:
- type: markdown
attributes:
value: |
Quarterly Reviews follow each Ongoing Certification Report by 5 business days. Dates are in https://samaydlette.com/.well-known/quarterly-review.ics and in the Certification Package Overview.
Reviews are for agencies and FedRAMP; other parties attend only with specific relevance (CCM-QTR-RTP). Registration here is public. To register privately, use the security contact in https://samaydlette.com/.well-known/security.txt.
- type: input
id: review
attributes:
label: Review date
placeholder: "2026-12-02"
validations:
required: true
- type: input
id: organization
attributes:
label: Organization and role in relation to this offering
description: For example, an agency considering the offering, or FedRAMP.
validations:
required: true
88 changes: 88 additions & 0 deletions .github/workflows/availability-probe.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
# =============================================================================
# Availability probe (CDS-CSO-AVR, CDS-TRC-USH)
# =============================================================================
# An availability monitor on infrastructure independent of the offering: it
# runs on GitHub Actions, not AWS, probes the core services over HTTPS every 15
# minutes (scripts/availability-probe.py), keeps 35 days of history, derives
# availability incidents, and publishes JSON + Markdown to the repository's
# `availability-status` branch. GitHub serves that branch, so the status stays
# readable when the offering's CloudFront or S3 is down:
# https://raw.githubusercontent.com/sam-aydlette/samaydlette.com/availability-status/availability-status.json
# https://github.com/sam-aydlette/samaydlette.com/blob/availability-status/availability-status.md
#
# The branch holds one commit, replaced on every run (history lives in the
# JSON), so the repository does not grow by a commit every 15 minutes. The
# workflow's token can write contents (no narrower scope exists); the job only
# ever pushes refs/heads/availability-status, and main is protected by its own
# branch rules. The deploy reads this feed and fails when it is missing or more
# than 2 hours old, so the published package never cites a monitor that has
# stopped (scripts/availability-probe.py --check-fresh).
#
# Caveats stated in the feed: history begins at the first run; GitHub may delay
# a scheduled run under load, and disables schedules on a repository with no
# activity for 60 days (the deploy's freshness check then fails).
# =============================================================================
name: Availability probe

on:
schedule:
- cron: '*/15 * * * *'
push:
branches: [main]
workflow_dispatch:

permissions: {}

concurrency:
group: availability-probe
cancel-in-progress: false

jobs:
probe:
name: Probe the core services from outside AWS
runs-on: ubuntu-latest
timeout-minutes: 10
permissions:
contents: write # push the status branch; nothing else
steps:
- name: Checkout the probe
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
ref: main
persist-credentials: false

- name: Read the previous status feed
run: |
set -euo pipefail
# Public repository: an anonymous fetch. No branch yet means a first run.
if git fetch --depth 1 --quiet origin availability-status 2>/dev/null; then
git show FETCH_HEAD:availability-status.json > previous-status.json || echo '{}' > previous-status.json
else
echo '{}' > previous-status.json
fi

- name: Probe the core services
run: python3 scripts/availability-probe.py --previous previous-status.json --out-dir status-out

- name: Publish the status feed to the availability-status branch
env:
GH_TOKEN: ${{ github.token }}
REPO: ${{ github.repository }}
run: |
set -euo pipefail
cd status-out
git init --quiet
git checkout --quiet --orphan availability-status
git add availability-status.json availability-status.md
git -c user.name="availability-probe" -c user.email="availability-probe@users.noreply.github.com" \
commit --quiet -m "Availability status $(jq -r .generated_at availability-status.json)"
auth=$(printf 'x-access-token:%s' "$GH_TOKEN" | base64 -w0)
echo "::add-mask::$auth"
git -c http.extraheader="AUTHORIZATION: basic $auth" \
push --quiet --force "https://github.com/${REPO}.git" HEAD:refs/heads/availability-status

# After publishing: an ongoing incident fails the run, and GitHub notifies
# the operator of the failed scheduled run (email). The status is already
# published either way.
- name: Alert on an ongoing availability incident
run: python3 scripts/availability-probe.py --fail-on-incident status-out/availability-status.json
Loading
Loading