FedRAMP Controls Mapping
This document maps FedRAMP (Federal Risk and Authorization Management Program) NIST SP 800-53 Rev 5 controls to the CloudForge CI checks planned for them.
Status: in development. FedRAMP support is incomplete and cannot be enabled yet:
complianceFrameworksaccepts onlysoc2,pci-dss,hipaa, andgdpr;FEDRAMPandFEDRAMP-HIGHfail configuration parsing.FedRampRulesandFedRampHighRulesare not registered inMETA-INF/services/com.cloudforge.core.interfaces.FrameworkRules, soFrameworkLoaderdoes not discover them.- The
fedramp-*AWS Config rules listed below are not created byComplianceFactory.- No cdk-nag pack is applied for FedRAMP.
This mapping describes the intended design. It is not evidence of FedRAMP authorization or of controls running in a deployment.
Overview
The planned FedRAMP implementation consists of:
- FedRampRules.java: synthesis-time validation checks for the Moderate baseline (
FEDRAMP, priority 25) - FedRampHighRules.java: additional checks for the High baseline (
FEDRAMP-HIGH, priority 26) - ComplianceFactory.java: AWS Config rules for continuous monitoring (not yet implemented for FedRAMP)
- ComplianceMatrix.java: framework control mappings
Both rule classes apply only to staging and production security profiles.
Baselines
| Baseline | Total Controls | Planned Coverage |
|---|---|---|
| FedRAMP Low | 156 | Not planned |
| FedRAMP Moderate | 323 | FedRampRules |
| FedRAMP High | 410 | FedRampRules plus FedRampHighRules |
Most FedRAMP controls are procedural or organizational and cannot be checked from infrastructure configuration. The tables below list only the technical controls with a planned check.
Control Family Mapping
A ✅ in the Status column means a check for the control is written in FedRampRules or FedRampHighRules, or an AWS Config rule is planned for it. None of these checks run until FedRAMP can be enabled.
AC - Access Control
| Control | Name | Implementation | Status |
|---|---|---|---|
| AC-2 | Account Management | IAM profile configuration, AWS Config rules | ✅ |
| AC-2(1) | Automated Account Management | IAM_USER_UNUSED_CREDENTIALS_CHECK Config rule | ✅ |
| AC-2(3) | Disable Inactive Accounts | AWS Config 90-day credential check | ✅ |
| AC-3 | Access Enforcement | Security groups, IAM policies, least privilege | ✅ |
| AC-4 | Information Flow Enforcement | VPC Flow Logs, network segmentation | ✅ |
| AC-5 | Separation of Duties | IAM role separation validation | ✅ |
| AC-6 | Least Privilege | IAM_POLICY_NO_STATEMENTS_WITH_ADMIN_ACCESS | ✅ |
| AC-6(10) | Prohibit Non-Privileged Execute | IAM_ROOT_ACCESS_KEY_CHECK | ✅ |
| AC-7 | Unsuccessful Logon Attempts | Cognito lockout configuration | ✅ |
| AC-17 | Remote Access | VPN/bastion requirement validation | ✅ |
AU - Audit and Accountability
| Control | Name | Implementation | Status |
|---|---|---|---|
| AU-2 | Audit Events | CloudTrail enabled, multi-region | ✅ |
| AU-3 | Content of Audit Records | CloudTrail log file validation | ✅ |
| AU-6 | Audit Review | CloudTrail → CloudWatch Logs integration | ✅ |
| AU-9 | Protection of Audit Info | S3 encryption, versioning for logs | ✅ |
| AU-11 | Audit Record Retention | 3-year minimum retention validation | ✅ |
| AU-12 | Audit Record Generation | CloudTrail, VPC Flow Logs, ALB logs |