Sign in
Menu
Sign up
Docs

FedRAMP Moderate Baseline Rev 4

ActiveCore framework

Best for: FedRAMP is mandatory for federal agency cloud deployments and service models at the low, moderate, and high-risk impact levels. Companies that employ cloud technologies in products or services used by the federal government may be required to obtain an ATO.

Mandatory?Mandatory for CSPs selling to U.S. federal agencies
Who validates?3PAO (Third Party Assessment Organization). No self-assessment.
RenewalContinuous monitoring; annual assessment
ScopeCloud service offering for federal use (moderate impact)
Governing bodyGeneral Services Administration (GSA), FedRAMP Moderate Rev 4. Official source

Controls by category

145 controls are Mapped to FedRAMP Moderate Baseline Rev 4.

AC-17 Remote Access

ControlStatus
App Configuration should use private linkMapped
Function apps should have remote debugging disabledMapped
Disk access resources should use private linkMapped
Windows virtual machines should have the Windows Guest Configuration extension installed for assignmentsMapped
Virtual machines with no identities should use system-assigned managed identity for Guest Configuration assignmentsMapped
Virtual machines with a user-assigned identity should also use system-assigned managed identity for Guest Configuration assignmentsMapped
Linux machines should prohibit remote connections from accounts without passwordsMapped
Container registries should use private linkMapped
Cosmos DB accounts should use private linkMapped
Data factories should use private linkMapped
Event Hub namespaces should use private linkMapped
Azure API for FHIR should use private linkMapped
MariaDB servers should have private endpoints enabledMapped
MySQL servers should have private endpoints enabledMapped
PostgreSQL servers should have private endpoints enabledMapped
Azure Cache for Redis should use private linkMapped
Azure Cognitive Search services should use a SKU that supports private linkMapped
Azure Service Bus namespaces should use private linkMapped
Azure SignalR Service should use private linkMapped
Azure Spring Cloud should use network injectionMapped
Azure SQL databases should have private endpoint connections enabledMapped
Storage accounts should have the default network access rule set to denyMapped
Storage accounts should have network access restrictions configuredMapped
Storage accounts should use virtual network rules to restrict network accessMapped
Azure Synapse workspaces should use private linkMapped

AC-17(1) Automated Monitoring/Control

ControlStatus
App Configuration should use private linkMapped
Function apps should have remote debugging disabledMapped
Disk access resources should use private linkMapped
Windows virtual machines should have the Windows Guest Configuration extension installed for assignmentsMapped
Virtual machines with no identities should use system-assigned managed identity for Guest Configuration assignmentsMapped
Virtual machines with a user-assigned identity should also use system-assigned managed identity for Guest Configuration assignmentsMapped
Linux machines should prohibit remote connections from accounts without passwordsMapped
Container registries should use private linkMapped
Cosmos DB accounts should use private linkMapped
Data factories should use private linkMapped
Event Hub namespaces should use private linkMapped
Azure API for FHIR should use private linkMapped
MariaDB servers should have private endpoints enabledMapped
MySQL servers should have private endpoints enabledMapped
PostgreSQL servers should have private endpoints enabledMapped
Azure Cache for Redis should use private linkMapped
Azure Cognitive Search services should use a SKU that supports private linkMapped
Azure Service Bus namespaces should use private linkMapped
Azure SignalR Service should use private linkMapped
Azure Spring Cloud should use network injectionMapped
Azure SQL databases should have private endpoint connections enabledMapped
Storage accounts should have the default network access rule set to denyMapped
Storage accounts should have network access restrictions configuredMapped
Storage accounts should use virtual network rules to restrict network accessMapped
Azure Synapse workspaces should use private linkMapped

AC-2 Account Management

AC-2(1) Automated System Account Management

AC-2(12) Account Monitoring

AC-2(7) Role-Based Schemes

AC-3 Access Enforcement

AC-4 Information Flow Enforcement

ControlStatus
API Management services should use a virtual networkMapped
App Configuration should use private linkMapped
App Service apps should not allow CORS access from every resourceMapped
App Service apps should not allow CORS access from every resourceMapped
Cognitive Services accounts should have network access restrictions configuredMapped
Disk access resources should use private linkMapped
Container registries should use private linkMapped
Cosmos DB accounts should use private linkMapped
Cosmos DB accounts should have 'Firewalls & Networks' limited to selected networks instead of all networksMapped
Azure Cosmos DB accounts should have firewall rulesMapped
Data factories should use private linkMapped
Event Hub namespaces should use private linkMapped
Azure API for FHIR should use private linkMapped
Kubernetes clusters should have authorized IP ranges configuredMapped
MariaDB servers should have private endpoints enabledMapped
MariaDB servers should have public network access disabledMapped
MySQL servers should have private endpoints enabledMapped
MySQL servers should have public network access disabledMapped
Virtual machine network interfaces should have IP forwarding disabledMapped
PostgreSQL servers should have private endpoints enabledMapped
PostgreSQL servers should have public network access disabledMapped
Azure Cache for Redis should use private linkMapped
Azure Cognitive Search services should use a SKU that supports private linkMapped
Azure Service Bus namespaces should use private linkMapped
Azure SignalR Service should use private linkMapped
Azure SQL databases should have private endpoint connections enabledMapped
Storage accounts should have the default network access rule set to denyMapped
Storage accounts should have network access restrictions configuredMapped
Storage accounts should use virtual network rules to restrict network accessMapped
Azure Synapse workspaces should use private linkMapped

AC-5 Separation Of Duties

AC-6 Least Privilege

AU-11 Audit Record Retention

AU-12 Audit Generation

AU-6 Audit Record Review, Analysis And Reporting

CM-6 Configuration Settings

CP-6 Alternate Storage Sites

CP-6(1) Separation From Primary Site

CP-7 Alternate Processing Site

CP-9 Information System Backup

IA-2 Identification and Authentication (Organizational users)

IA-4 Identifier Management

IA-5 Authenticator Management

IA-5(1) Password-Based Authentication

IR-4 Incident Handling

IR-5 Incident Monitoring

RA-5 Vulnerability Scanning

SC-12 Cryptographic Key Establishment And Management

ControlStatus
Batch accounts should use customer-managed keys to encrypt dataMapped
Cognitive Services accounts should use customer-managed keys to encrypt dataMapped
OS and data disks should use customer-managed keys for encryptionMapped
Managed disks should use both platform-managed and customer-managed keys for double encryptionMapped
Container Instance container groups should use customer-managed keys for encryptionMapped
Container registries should use customer-managed keys for encryptionMapped
Data factories should use customer-managed keys for encryptionMapped
Event Hub namespaces should use a customer-managed key for encryptionMapped
Azure HDInsight clusters should use customer-managed keys to encrypt data at restMapped
Azure HDInsight clusters should use encryption at host to encrypt data at restMapped
Azure API for FHIR should use a customer-managed key to encrypt data at restMapped
HPC Cache accounts should use customer-managed keys for encryptionMapped
AKS clusters should use customer-managed keys to encrypt both OS and data disksMapped
Azure Data Explorer clusters should use customer-managed keys for encryption at restMapped
Azure Machine Learning workspaces should use customer-managed keys for encryptionMapped
SQL managed instances should use customer-managed keys to encrypt data at restMapped
MySQL servers should use customer-managed keys to encrypt data at restMapped
Service Bus Premium namespaces should use a customer-managed key for encryptionMapped
SQL servers should use customer-managed keys to encrypt data at restMapped
Storage accounts should use customer-managed key for encryptionMapped
Storage account encryption scopes should use customer-managed keys to encrypt data at restMapped
Azure Synapse workspaces should use customer-managed keys to encrypt data at restMapped

SC-28 Protection Of Information At Rest

SC-28(1) Cryptographic Protection

SC-5 Denial Of Service Protection

SC-7 Boundary Protection

ControlStatus
API Management services should use a virtual networkMapped
App Configuration should use private linkMapped
Application gateways should have Web Application Firewall (WAF) enabledMapped
Cognitive Services accounts should have network access restrictions configuredMapped
Disk access resources should use private linkMapped
Container registries should use private linkMapped
Cosmos DB accounts should use private linkMapped
Cosmos DB accounts should have 'Firewalls & Networks' limited to selected networks instead of all networksMapped
Azure Cosmos DB accounts should have firewall rulesMapped
Data factories should use private linkMapped
Event Hub namespaces should use private linkMapped
Azure Front Door services should have Web Application Firewall (WAF) enabledMapped
Azure API for FHIR should use private linkMapped
Kubernetes clusters should have authorized IP ranges configuredMapped
MariaDB servers should have private endpoints enabledMapped
MariaDB servers should have public network access disabledMapped
MySQL servers should have private endpoints enabledMapped
MySQL servers should have public network access disabledMapped
Virtual machine network interfaces should have IP forwarding disabledMapped
PostgreSQL servers should have private endpoints enabledMapped
PostgreSQL servers should have public network access disabledMapped
Azure Cache for Redis should use private linkMapped
Azure Cognitive Search services should use a SKU that supports private linkMapped
Azure Service Bus namespaces should use private linkMapped
Azure SignalR Service should use private linkMapped
Azure SQL databases should have private endpoint connections enabledMapped
Storage accounts should have the default network access rule set to denyMapped
Storage accounts should have network access restrictions configuredMapped
Storage accounts should use virtual network rules to restrict network accessMapped
Azure Synapse workspaces should use private linkMapped

SC-7(3) Access Points

ControlStatus
API Management services should use a virtual networkMapped
App Configuration should use private linkMapped
Application gateways should have Web Application Firewall (WAF) enabledMapped
Cognitive Services accounts should have network access restrictions configuredMapped
Disk access resources should use private linkMapped
Container registries should use private linkMapped
Cosmos DB accounts should use private linkMapped
Cosmos DB accounts should have 'Firewalls & Networks' limited to selected networks instead of all networksMapped
Azure Cosmos DB accounts should have firewall rulesMapped
Data factories should use private linkMapped
Event Hub namespaces should use private linkMapped
Azure Front Door services should have Web Application Firewall (WAF) enabledMapped
Azure API for FHIR should use private linkMapped
Kubernetes clusters should have authorized IP ranges configuredMapped
MariaDB servers should have private endpoints enabledMapped
MariaDB servers should have public network access disabledMapped
MySQL servers should have private endpoints enabledMapped
MySQL servers should have public network access disabledMapped
Virtual machine network interfaces should have IP forwarding disabledMapped
PostgreSQL servers should have private endpoints enabledMapped
PostgreSQL servers should have public network access disabledMapped
Azure Cache for Redis should use private linkMapped
Azure Cognitive Search services should use a SKU that supports private linkMapped
Azure Service Bus namespaces should use private linkMapped
Azure SignalR Service should use private linkMapped
Azure SQL databases should have private endpoint connections enabledMapped
Storage accounts should have the default network access rule set to denyMapped
Storage accounts should have network access restrictions configuredMapped
Storage accounts should use virtual network rules to restrict network accessMapped
Azure Synapse workspaces should use private linkMapped

SC-8 Transmission Confidentiality And Integrity

SC-8(1) Cryptographic Or Alternate Physical Protection

SI-16 Memory Protection

SI-2 Flaw Remediation

SI-3 Malicious Code Protection

SI-3(1) Central Management

SI-4 Information System Monitoring

FrameworkControl overlapNote
CMMC 2.0 Level 2High 96%
NIST SP 800-53 Rev 5High 89%
NIST SP 800-171 Rev 2High 85%

Frequently asked questions

How many controls does the FedRAMP Moderate baseline have?

The FedRAMP Moderate baseline has 325 controls, whereas the FedRAMP High baseline has 421 controls. The number of controls in a baseline increases as the impact level increases.

What are the FedRAMP impact levels?

Authorizations are granted at three impact levels based on NIST FIPS 199 guidelines: Low (limited effect), Moderate (serious adverse effect), and High (severe or catastrophic effect).

What are the paths for a cloud provider to demonstrate FedRAMP compliance?

A Cloud Service Provider can earn a Provisional ATO from the FedRAMP Joint Authorization Board, receive an ATO from a federal agency, or develop a CSP Supplied Package independently. Each path requires an assessment by an accredited 3PAO.

Is FedRAMP a point-in-time certification?

FedRAMP is not a point-in-time certification or accreditation. It is an assessment and authorization program with provisions for continuous monitoring, so deployed security controls in a cloud service offering remain effective as the environment changes.

On this page

Ask AI about this

Help improve this page