Repository navigation
FedRAMP Security Inbox: SES receiving, acknowledgement, paging, deadlines (AFC-CSO-INB/NOC/TFG/RCV/CRA/EMR/IMA/ACK) - #507
Closed
sam-aydlette wants to merge 1 commit into
Closed
sam-aydlette wants to merge 1 commit into
sam-aydlette wants to merge 1 commit into
Conversation
…deadlines (AFC-CSO-*) Adds a FedRAMP Security Inbox on the system's own domain. The address is one value in data/cds/offering.json; Terraform, the CPO and the change-notice check read it from there. - infrastructure/fedramp-inbox.tf: SES receiving in us-east-2 (MX, one receipt rule that stores then hands off and cannot bounce, stop or drop), Easy DKIM, custom MAIL FROM with SPF, DMARC, a CMK-encrypted inbox bucket, the inbox function, an hourly check, three alarms on the watchdog's alert path. - infrastructure/fedramp-inbox/: classifies @fedramp.gov / @gsa.gov mail as FedRAMP whatever its spam verdict (TFG), designates from the subject, registers Emergency deadlines at the Class C default (CRA), pages Emergency and Important mail (EMR, IMA), acknowledges authenticated FedRAMP mail once (ACK), checks the live configuration hourly (RCV). Message bodies are never read by the function or published. - scripts/check-fsi-notice.py + a unit-test job step: an address change fails without a dated FedRAMP notification record (NOC). - scripts/fsi.py: operator list/show/triage/close and the dated exercise. - Inventory, boundary map, service model, CPO, IR docs and a runbook. - Bootstrap: deploy-role and operator grants for the inbox. - Rule records: NOC Implemented; INB, TFG, RCV, CRA, EMR, IMA, ACK Partially Implemented until deployed and exercised. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
|
Reworked as a simulation and consolidated into #508. |
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.
Changed
Adds the FedRAMP Security Inbox (AFC-CSO-INB and the rest of the AFC provider rules).
data/cds/offering.jsonunderfedramp_security_inbox.address(fedramp-security@samaydlette.com), with an append-only change history. Terraform, the CPO and the change-notice check all read it from there. A test fails if the address appears anywhere else underinfrastructure/,scripts/or.github/.infrastructure/fedramp-inbox.tf).mail.subdomain with SPF), apex SPF-all, and DMARCp=quarantine.kms:Decrypt.infrastructure/fedramp-inbox/, Node 22, AWS SDK from the runtime, no dependencies).@fedramp.govor@gsa.gov. Spam and authentication verdicts never change this.fsi-config,fsi-overdueandfsi-errorsuse the watchdog's alarm-name prefix. That prefix already scopes the topic policy, the CMK's CloudWatch grant, the deploy role's alarm grant and the operators' test/silence grant, so none of those grants needed to change.scripts/check-fsi-notice.pyruns as the unit-test job step "FedRAMP Security Inbox change notice (AFC-CSO-NOC)". It fails a change of address unless a new history entry carries a datedfedramp_notifiedmarker that names the channel. Compared with the merge base, it also fails if the history was edited. Known-bad fixtures are intests/fixtures/fsi/.scripts/fsi.py(list,show,triage,close,exercise) uses the aws CLI. It prints messages as text only: HTML is reduced to text, attachments are listed but not opened, and control and bidi characters are stripped.mail_receiver(AWS::SES::ReceiptRuleSet). The rule, the activation and the sending identity fold into it as attributes. Changes:fsigroup, a declaredfedrampactor, flows L/M/N, and SES added to the leveraged services. SES is listed in scope for FedRAMP East/West on AWS's services-in-scope page, last updated 2026-10-15.fsiservice.certification_data.fedramp_security_inboxpublishes the address, the rule and the runbook.docs/runbooks/fedramp-security-inbox.md.docs/incident-response.mdanddocs/policies/ir-policy.mdno longer say FSI does not apply.docs/cr26-applicability.mdno longer lists AFC as N/A; the rule records already treat AFC as applicable.infrastructure/bootstrap/main.tf).fedramp-inbox-managementpolicy covers the inbox role and PassRole, the schedule, the bucket, the domain identity, and the receipt rules. The receipt-rule actions have no resource type, so they are region-conditioned. The inbox log group is added tocompliance-logs-management.fedramp-inbox-operatorpolicy allows reading messages and the register, triaging and closing register items, decrypting with the at-rest key (scoped by alias), reading the SES configuration, and sending asfsi-exercise@only.Effect
After the bootstrap apply and a deploy:
Rule records (
python3 scripts/_frr.py), before and after:tests/test_fsi_notice.pytests, plus the stepdeploy-with-opa.yml#FedRAMP Security Inbox change notice (AFC-CSO-NOC).Verified
make checkpasses (1068 passed, 1 skipped). The CI-only checks also pass: Regal, policy annotations, exceptions, wasm-safe, and the new NOC check.terraform validatepasses for the main and bootstrap stacks.terraform fmtis clean.fedramp-inbox.tf(35 passed, 0 failed). Two inline skips carry their rationale: CKV2_AWS_62 for the bucket and CKV_AWS_355 for the account-level SES reads._dmarcrecord, so the new records conflict with nothing.samaydlette-com-*Lambda grants.@gsa.govsender could make the inbox mail attacker-chosen subject text to a government address. This is fixed: acknowledgements now require SPF/DKIM/DMARC to pass, and such mail is still registered and paged. No other findings: no secrets in env vars or code, no shell invocation, bounded regexes, validated IDs and addresses.Residual
--smtpleg covers the path end to end.data/decisions.jsonwas not edited.tools/boundary-map/corroborate.pyandwebsite/assets/js/boundary-map.jshave no mapping formail_receiver. Both were left alone: the first is local-only and the second is website code.Needs human
fedramp-inbox-managementpolicy. Syncinfrastructure/bootstrap/toorigin/mainfirst. The plan should show onlyaws_iam_role_policy.fedramp_inbox_management(new),aws_iam_group_policy.operators_fedramp_inbox(new) andaws_iam_role_policy.compliance_logs(one log-group ARN added). Do not apply while a deploy is in flight.fsi-overdue, andfsi-configreports the sandbox. Receiving is not affected.python3 scripts/fsi.py exercise --reply-to <verified address> --smtp --record docs/exercises. While SES is in the sandbox, the reply-to address must be verified in SES. Commit the record it writes, then close the exercise item. This is the remaining evidence for the seven Partially Implemented records.p=quarantinewith no aggregate reports.-all.security_contactshould become the inbox address. FedRAMP uses the Marketplace Security Email unless told otherwise.Couldn't verify
kms:ViaService= S3 in the region and by the bucket's encryption context, following the documented pattern. Only a live message or the exercise's--smtpleg shows it works.🤖 Generated with Claude Code