Skip to content
Closed
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
18 changes: 18 additions & 0 deletions .github/workflows/deploy-with-opa.yml
Original file line number Diff line number Diff line change
Expand Up @@ -243,6 +243,24 @@ jobs:
- name: Exception register expiry check
run: python3 scripts/check-exceptions.py

# AFC-CSO-NOC: the FedRAMP Security Inbox address (data/cds/offering.json)
# cannot change without a history entry recording that FedRAMP was
# notified. Compared with the merge base on a pull request and with the
# previous commit on a push, so the history is also append-only.
- name: FedRAMP Security Inbox change notice (AFC-CSO-NOC)
env:
BASE_REF: ${{ github.event_name == 'pull_request' && github.base_ref || '' }}
BEFORE_SHA: ${{ github.event_name == 'push' && github.event.before || '' }}
run: |
base=""
if [ -n "$BASE_REF" ] && git fetch --no-tags --depth=1 origin "$BASE_REF"; then
git show FETCH_HEAD:data/cds/offering.json > fsi-base.json 2>/dev/null && base="--base fsi-base.json"
elif [ -n "$BEFORE_SHA" ] && git fetch --no-tags --depth=1 origin "$BEFORE_SHA"; then
git show "$BEFORE_SHA":data/cds/offering.json > fsi-base.json 2>/dev/null && base="--base fsi-base.json"
fi
# shellcheck disable=SC2086 # $base is an optional flag pair
python3 scripts/check-fsi-notice.py $base

# Known Go-vs-Wasm builtin divergences (%q, %v-on-sets, host time) are
# banned at lint time; the parity test catches what the corpus exercises,
# this catches the rest before it exists. It also requires every sprintf
Expand Down
13 changes: 13 additions & 0 deletions data/cds/offering.json
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,19 @@
"uei": "<not assigned — no SAM.gov registration>",
"sales_contact": { "name": "Sam Aydlette", "url": "https://samaydlette.com/pages/contact.html" },
"security_contact": { "name": "Sam Aydlette", "email": "sam.aydlette@gmail.com", "source": "/.well-known/security.txt" },
"fedramp_security_inbox": {
"_note": "The FedRAMP Security Inbox (AFC-CSO-INB): the one place this address is written. infrastructure/fedramp-inbox.tf receives mail for it, the CPO publishes it, and scripts/check-fsi-notice.py fails any change to it that does not record notifying FedRAMP (AFC-CSO-NOC). To change it: add a history entry with fedramp_notified, then change address.",
"address": "fedramp-security@samaydlette.com",
"runbook": "https://github.com/sam-aydlette/samaydlette.com/blob/main/docs/runbooks/fedramp-security-inbox.md",
"history": [
{
"address": "fedramp-security@samaydlette.com",
"since": "2026-11-05",
"fedramp_notified": null,
"basis": "Established. No earlier FedRAMP Security Inbox or Marketplace Security Email is on file with FedRAMP for this unsponsored system, so there was no prior address to change from."
}
]
},
"product_website": "https://samaydlette.com",
"logo_url": "https://samaydlette.com/assets/images/brand/logo.png",
"service_description": "A static personal website on AWS that doubles as a working continuous-compliance pipeline: every deploy derives signed, machine-readable compliance artifacts from one canonical inventory and publishes them under /.well-known/. Includes the Silk Reeling Mirror application, a Cognito-gated Tai Chi coaching API.",
Expand Down
206 changes: 165 additions & 41 deletions data/frr-records.json

Large diffs are not rendered by default.

16 changes: 13 additions & 3 deletions docs/boundary/boundary-classification.json
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@
"match": ["aws::event_schedule::opa_compliance", "aws::function::opa_compliance", "aws::log_group::opa_compliance", "aws::iam_role::lambda_opa", "aws::iam_policy::lambda_opa", "aws::message_queue::compliance_dlq", "aws::kms_key::runtime_signing"]},
{"key": "watchdog", "zone": "system", "label": "Evidence-freshness watchdog and alerting",
"match": ["aws::*::evidence_watchdog", "aws::metric_alarm::evidence*", "aws::notification_topic::evidence_alerts"]},
{"key": "fsi", "zone": "system", "label": "FedRAMP Security Inbox (AFC-CSO-INB)",
"match": ["aws::mail_receiver::*", "aws::*::fedramp_inbox", "aws::object_store::fsi_mail", "aws::metric_alarm::fsi*"]},
{"key": "app", "zone": "system", "label": "Application sub-system (Silk Reeling)",
"match": ["aws::api_gateway::silk_reeling", "aws::identity_provider::silk_reeling", "aws::function::silk_reeling", "aws::iam_role::silk_reeling", "aws::iam_policy::silk_reeling", "aws::log_group::silk_*", "aws::secrets_manager::silk_*", "aws::kms_key::silk_reeling"]},
{"key": "audit", "zone": "system", "label": "Audit and shared keys",
Expand All @@ -34,7 +36,9 @@
{"key": "operator", "label": "Operator (dev machine)", "zone": "outside", "kind": "actor",
"why": "Out per Rule of Thumb #4: development environment, no federal information."},
{"key": "operator-email", "label": "Operator email and SaaS", "zone": "outside", "kind": "actor",
"why": "Out per Rule of Thumb #3; receives the evidence-alarm email (flow I), which carries alarm metadata only."},
"why": "Out per Rule of Thumb #3; receives the evidence-alarm email (flow I), which carries alarm metadata only, and the FedRAMP Security Inbox page (flow M), which carries a FedRAMP message's sender, subject, designation and deadline, never its body."},
{"key": "fedramp", "label": "FedRAMP (@fedramp.gov, @gsa.gov senders)", "zone": "outside", "kind": "actor",
"why": "The program office writing to the FedRAMP Security Inbox (AFC-CSO-INB); its mail is treated as FedRAMP by default (AFC-CSO-TFG)."},
{"key": "public", "label": "Public Internet (readers, verifiers)", "zone": "outside", "kind": "actor",
"why": "Anonymous consumers of the site and the /.well-known/ evidence."},
{"key": "app-users", "label": "App users (Silk Reeling)", "zone": "outside", "kind": "actor",
Expand All @@ -44,7 +48,7 @@
"package_id": "AGENCYAMAZONEW",
"name": "AWS East/West",
"status": "FedRAMP Certified Class C",
"services": ["VPC networking", "KMS HSM", "IAM control plane", "S3", "CloudFront edge", "Lambda", "API Gateway", "Cognito", "Secrets Manager", "EventBridge", "ACM", "CloudTrail", "CloudWatch", "SNS", "SQS", "Route 53"],
"services": ["VPC networking", "KMS HSM", "IAM control plane", "S3", "CloudFront edge", "Lambda", "API Gateway", "Cognito", "Secrets Manager", "EventBridge", "ACM", "CloudTrail", "CloudWatch", "SNS", "SQS", "Route 53", "SES"],
"why": "Per Key Concept #6: the underlying infrastructure is inherited from the AWS package under the customer responsibility matrix."
},
"flows": [
Expand All @@ -69,6 +73,12 @@
{"id": "J", "label": "Evidence Nightly → S3 (.well-known/vdr-*)", "path": [{"component": "ext::github-oidc"}, {"component": "aws::iam_role::evidence_nightly"}, {"component": "aws::object_store::website"}],
"protocol": "HTTPS 443 (TLS 1.2+, SigV4)", "auth": "GitHub OIDC → STS; the role can write only .well-known/vdr-* (unattended)", "encryption": "In transit TLS; at rest SSE-S3", "data": "Refreshed VDR and trend (Sigstore-signed)"},
{"id": "K", "label": "Watchdog → S3 (evidence freshness read)", "path": [{"component": "aws::event_schedule::evidence_watchdog"}, {"component": "aws::function::evidence_watchdog"}, {"component": "aws::object_store::website"}],
"protocol": "AWS-internal", "auth": "Watchdog Lambda role: s3:GetObject on the published evidence keys only", "encryption": "In transit: TLS", "data": "Published evidence timestamps; results go out as CloudWatch metrics that drive flow I's alarms"}
"protocol": "AWS-internal", "auth": "Watchdog Lambda role: s3:GetObject on the published evidence keys only", "encryption": "In transit: TLS", "data": "Published evidence timestamps; results go out as CloudWatch metrics that drive flow I's alarms"},
{"id": "L", "label": "FedRAMP → SES receiving → inbox bucket", "path": [{"declared": "fedramp"}, {"component": "aws::mail_receiver::fsi"}, {"component": "aws::object_store::fsi_mail"}],
"protocol": "SMTP 25 (STARTTLS when the sender offers it; not required, AFC-CSO-RCV)", "auth": "None required of the sender; SPF, DKIM and DMARC verdicts recorded and shown to the operator", "encryption": "In transit: opportunistic TLS; at rest: SSE-KMS (at-rest CMK)", "data": "FedRAMP messages, full content"},
{"id": "M", "label": "Inbox function → SNS topic → operator email (out)", "path": [{"component": "aws::mail_receiver::fsi"}, {"component": "aws::function::fedramp_inbox"}, {"component": "aws::notification_topic::evidence_alerts"}, {"declared": "operator-email"}],
"protocol": "AWS-internal (SES async invoke, SNS publish); then email (SMTP)", "auth": "Inbox Lambda role: sns:Publish on the alert topic only", "encryption": "At rest: CMK · email not end-to-end encrypted", "data": "Message metadata only (sender, subject, designation, deadline); never the body"},
{"id": "N", "label": "Inbox function → SES → FedRAMP (acknowledgement)", "path": [{"component": "aws::function::fedramp_inbox"}, {"component": "aws::mail_receiver::fsi"}, {"declared": "fedramp"}],
"protocol": "SES send (DKIM-signed, custom MAIL FROM); SMTP with TLS", "auth": "Inbox Lambda role: ses:SendRawEmail as the inbox address only", "encryption": "In transit: TLS", "data": "Automatic acknowledgement naming the received subject and a reference"}
]
}
3 changes: 1 addition & 2 deletions docs/cr26-applicability.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,6 @@ The POA&M is retired (2026-11-04): CR26 has no POA&M. Open findings and their de

- **IVV — Independent Verification and Validation.** `IVV-CSO-FIA` (Class C MUST) requires a persistent independent assessment by a **FedRAMP Recognized independent assessment service** (the artifact formerly called a 3PAO) or by FedRAMP. This system is self-attested and has engaged no such assessor, so the *independent* half cannot be met. The provider-side verification and validation an assessor would consume **are** produced (in the Security Decision Record); the independent half is unmet by design and recorded N/A.
- **MKT — Marketplace Listing.** `MKT-IIP-AGU` requires demonstrating the offering is for agency use within 44 USC § 3506 scope, and the rule text is explicit that *"services used by private companies to meet other compliance requirements (such as CMMC) that do not also meet one of the above use cases are outside the scope of FedRAMP."* There is no agency use case and no intent to list, so MKT is N/A by statutory scope.
- **AFC — Addressing FedRAMP Communication.** `AFC-CSO-INB` and the rest require maintaining a FedRAMP Security Inbox and handling FedRAMP correspondence. With no listing and no sponsor, FedRAMP has no reason to correspond, so there is no channel to maintain. AFC's grace period already ended **2026-07-01**; it is recorded N/A absent a sponsor.
- **IEC — Incident Evaluation and Communication.** A FedRAMP Reportable Incident under `IEC-CSO-EFR` is triggered by an effect on the confidentiality or integrity of **federal customer data**. This system holds none, so no incident is FedRAMP-reportable and the `IEC-CSO-IIR` reporting clocks never start. The evaluation step still runs — the VDR aggregator assigns a PAIN rating to every finding — so the machinery is in place the moment federal data ever enters scope.

These four are N/A because of *what this system is*, not because of an engineering gap. If the system were ever sponsored, listed, assessed, or handling federal data, each would activate, and the mechanisms above (the SDR's V&V evidence, the CDS overview package, the PAIN evaluation) are the inputs those activated obligations would consume.
These three are N/A because of *what this system is*, not because of an engineering gap. If the system were ever sponsored, listed, assessed, or handling federal data, each would activate, and the mechanisms above (the SDR's V&V evidence, the CDS overview package, the PAIN evaluation) are the inputs those activated obligations would consume.
4 changes: 3 additions & 1 deletion docs/incident-response.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,5 +117,7 @@ Single-tier. Author → author. External escalations:
- **GitHub Support** — if the issue is GitHub-side (account, repo, workflow infrastructure)
- The mailbox in `security.txt` for acknowledging external reporters

There is no actual FedRAMP authorization in scope, so the FedRAMP Security Inbox (FSI) and Incident Communications Procedures (ICP) do not apply.
- **FedRAMP Security Inbox (FSI)** — the address in `data/cds/offering.json` (`fedramp_security_inbox`) receives FedRAMP's messages (AFC-CSO-INB). Mail from @fedramp.gov or @gsa.gov is acknowledged automatically and pages the operator; Emergency and Emergency Test messages carry a tracked deadline. Handling is in [`runbooks/fedramp-security-inbox.md`](runbooks/fedramp-security-inbox.md).

There is no actual FedRAMP authorization in scope, so the Incident Communications Procedures (ICP) do not apply.

2 changes: 1 addition & 1 deletion docs/policies/ir-policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ External communication paths:

- **Public reporter:** [`/.well-known/security.txt`](../../website/.well-known/security.txt) is the published vulnerability-reporting mailbox.
- **Incident Communications Procedures (ICP, 20x):** the ICP rules apply at the procedure-documented level even though the system has no actual FedRAMP-customer reporting obligation. The runbook describes what would be communicated and to whom for a real FedRAMP-certified service.
- **FedRAMP Security Inbox (FSI, 20x):** the system is not FedRAMP-certified; no actual FSI obligation applies. Notification path is documented in the runbook for reference.
- **FedRAMP Security Inbox (FSI, 20x AFC):** the address in `data/cds/offering.json` (`fedramp_security_inbox`), received by SES and handled by `infrastructure/fedramp-inbox.tf`. FedRAMP mail is acknowledged automatically; Emergency and Important messages page the operator, the senior security official, and carry a tracked deadline; the hourly configuration check and the overdue check page through the evidence-alert topic. A change of address is blocked in CI until the change records that FedRAMP was notified (AFC-CSO-NOC). Procedure: [`fedramp-security-inbox.md`](../runbooks/fedramp-security-inbox.md).

**20x rule integration.** KSI-INR (Incident Response), ICP (Incident Communications Procedures), FSI (FedRAMP Security Inbox).

Expand Down
8 changes: 8 additions & 0 deletions docs/portfolio/service-model.json
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,14 @@
"consumed_by": ["website", "silk-reeling"],
"features": []
},
{
"key": "fsi",
"name": "FedRAMP Security Inbox",
"group": "fsi",
"owner_domain": "observability",
"consumed_by": ["website", "silk-reeling"],
"features": []
},
{
"key": "audit",
"name": "Audit trail and shared keys",
Expand Down
Loading
Loading