Sign in
Menu
Sign up
Docs

NIST SP 800-53 Rev 5

ActiveCore framework

The National Institute of Standards and Technology (NIST) Special Publication 800-53 Revision 5 provides a comprehensive catalog of security and privacy controls for information systems and organizations. Published by the U.S. Department of Commerce in September 2020, this framework supports risk management processes and compliance with federal legislation including FISMA. It is used by U.S. federal agencies and organizations globally seeking a risk-based approach to security and privacy controls.

Mandatory?Mandatory for U.S. federal agencies; voluntary for private sector
Who validates?Authorizing Official; 3PAO for FedRAMP overlays. No self-assessment.
RenewalATO reauthorization every 3 years (federal)
ScopeFederal information systems; also used as private-sector baseline
Governing bodyThe page lists the Joint Task Force as the author., NIST SP 800-53 Rev 5 (Sep 2020). Official source

Controls by category

191 controls are Mapped to NIST SP 800-53 Rev 5.

AC-16 Security and Privacy Attributes

AC-17 Remote Access

ControlStatus
App Configuration should use private linkMapped
App Service apps should have remote debugging disabledMapped
Function apps should have remote debugging disabledMapped
Cognitive Services should use private linkMapped
Disk access resources should use private linkMapped
Linux virtual machines should have the Linux Guest Configuration extension installed for assignmentsMapped
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
Azure Event Grid domains should use private linkMapped
Azure Event Grid topics should use private linkMapped
Event Hub namespaces should use private linkMapped
Azure API for FHIR should use private linkMapped
IoT Hub device provisioning service instances should use private linkMapped
Azure Key Vaults 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 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 network access restrictions configuredMapped
Storage accounts should use private linkMapped
Azure File Sync should use private linkMapped
Azure Synapse workspaces should use private linkMapped

AC-17(1) Monitoring and Control

ControlStatus
App Configuration should use private linkMapped
App Service apps should have remote debugging disabledMapped
Function apps should have remote debugging disabledMapped
Cognitive Services should use private linkMapped
Disk access resources should use private linkMapped
Linux virtual machines should have the Linux Guest Configuration extension installed for assignmentsMapped
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
Azure Event Grid domains should use private linkMapped
Azure Event Grid topics should use private linkMapped
Event Hub namespaces should use private linkMapped
Azure API for FHIR should use private linkMapped
IoT Hub device provisioning service instances should use private linkMapped
Azure Key Vaults 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 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 network access restrictions configuredMapped
Storage accounts should use private linkMapped
Azure File Sync should use private linkMapped
Azure Synapse workspaces should use private linkMapped

AC-2 Account Management

AC-2(1) Automated System Account Management

AC-2(12) Account Monitoring for Atypical Usage

AC-2(7) Privileged User Accounts

AC-3 Access Enforcement

AC-3(7) Role-based Access Control

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
Cognitive Services should use private linkMapped
Cognitive Services accounts should have public network access disabledMapped
Cognitive Services accounts should have network access restrictions configuredMapped
Disk access resources should use private linkMapped
Virtual machines should use just-in-time network access control for management portsMapped
Virtual machines should have all network ports restricted by their associated network security groupsMapped
Internet-facing virtual machines should use network security groups for protectionMapped
Container registries should not allow unrestricted network accessMapped
Container registries should use private linkMapped
Cosmos DB accounts should use private linkMapped
Azure Cosmos DB accounts should have firewall rulesMapped
Data factories should use private linkMapped
Azure Event Grid domains should use private linkMapped
Azure Event Grid topics should use private linkMapped
Event Hub namespaces should use private linkMapped
Azure API for FHIR should use private linkMapped
IoT Hub device provisioning service instances should use private linkMapped
Key vaults should have a firewall enabledMapped
Azure Key Vaults 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
Virtual machines should have management ports closedMapped
Subnets should have a network security group configuredMapped
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 have public network access disabledMapped
Azure Cognitive Search services 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 public network access disabledMapped
Azure SQL databases should have private endpoint connections enabledMapped
Storage accounts should prohibit public accessMapped
Storage accounts should have network access restrictions configuredMapped
Storage accounts should use virtual network rules to restrict network accessMapped
Storage accounts should use private linkMapped
Azure File Sync should use private linkMapped
Azure Synapse workspaces should use private linkMapped

AC-4(3) Dynamic Information Flow Control

AC-5 Separation of Duties

AC-6 Least Privilege

AC-6(7) Review of User Privileges

AU-11 Audit Record Retention

AU-12 Audit Record Generation

ControlStatus
App Service apps should have resource logs enabledMapped
Linux Azure Arc machines should have the Log Analytics extension installedMapped
Windows Azure Arc machines should have the Log Analytics extension installedMapped
Batch accounts should have resource logs enabledMapped
Virtual machines should have the Guest Configuration extension installedMapped
Virtual machines should use system-assigned managed identity with the Guest Configuration extensionMapped
Virtual machines should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Linux virtual machines should have the network traffic data collection agent installedMapped
Windows virtual machines should have the network traffic data collection agent installedMapped
Virtual machine scale sets should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Data Lake Analytics accounts should have resource logs enabledMapped
Data Lake Store accounts should have resource logs enabledMapped
Event Hub namespaces should have resource logs enabledMapped
IoT hubs should have resource logs enabledMapped
Key vaults should have resource logs enabledMapped
Logic App workflows should have resource logs enabledMapped
Azure subscriptions should have Network Watcher enabledMapped
Search services should have resource logs enabledMapped
Azure subscriptions should have auto provisioning of the Log Analytics agent enabledMapped
Azure subscriptions should have Microsoft Defender for App Service enabledMapped
Azure subscriptions should have Microsoft Defender for Containers enabledMapped
Azure subscriptions should have Azure Defender for DNS enabledMapped
Azure subscriptions should have Microsoft Defender for Key Vault enabledMapped
Azure subscriptions should have Azure Defender for Resource Manager enabledMapped
Azure subscriptions should have Microsoft Defender for Servers enabledMapped
Azure subscriptions should have Microsoft Defender for Azure SQL Database servers enabledMapped
Unprotected SQL Server virtual machines should have Azure Defender for SQL enabledMapped
Azure subscriptions should have Microsoft Defender for Storage enabledMapped
Service Bus namespaces should have resource logs enabledMapped
SQL servers should have auditing enabledMapped
Unprotected Azure SQL servers should have Azure Defender for SQL enabledMapped
Stream Analytics jobs should have resource logs enabledMapped

AU-12(1) System-wide and Time-correlated Audit Trail

ControlStatus
App Service apps should have resource logs enabledMapped
Linux Azure Arc machines should have the Log Analytics extension installedMapped
Windows Azure Arc machines should have the Log Analytics extension installedMapped
Batch accounts should have resource logs enabledMapped
Virtual machines should have the Guest Configuration extension installedMapped
Virtual machines should use system-assigned managed identity with the Guest Configuration extensionMapped
Virtual machines should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Linux virtual machines should have the network traffic data collection agent installedMapped
Windows virtual machines should have the network traffic data collection agent installedMapped
Virtual machine scale sets should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Data Lake Analytics accounts should have resource logs enabledMapped
Data Lake Store accounts should have resource logs enabledMapped
Event Hub namespaces should have resource logs enabledMapped
IoT hubs should have resource logs enabledMapped
Key vaults should have resource logs enabledMapped
Logic App workflows should have resource logs enabledMapped
Azure subscriptions should have Network Watcher enabledMapped
Search services should have resource logs enabledMapped
Azure subscriptions should have auto provisioning of the Log Analytics agent enabledMapped
Azure subscriptions should have Microsoft Defender for App Service enabledMapped
Azure subscriptions should have Microsoft Defender for Containers enabledMapped
Azure subscriptions should have Azure Defender for DNS enabledMapped
Azure subscriptions should have Microsoft Defender for Key Vault enabledMapped
Azure subscriptions should have Azure Defender for Resource Manager enabledMapped
Azure subscriptions should have Microsoft Defender for Servers enabledMapped
Azure subscriptions should have Microsoft Defender for Azure SQL Database servers enabledMapped
Unprotected SQL Server virtual machines should have Azure Defender for SQL enabledMapped
Azure subscriptions should have Microsoft Defender for Storage enabledMapped
Service Bus namespaces should have resource logs enabledMapped
SQL servers should have auditing enabledMapped
Unprotected Azure SQL servers should have Azure Defender for SQL enabledMapped
Stream Analytics jobs should have resource logs enabledMapped

AU-6 Audit Record Review, Analysis, and Reporting

AU-6(4) Central Review and Analysis

ControlStatus
App Service apps should have resource logs enabledMapped
Linux Azure Arc machines should have the Log Analytics extension installedMapped
Windows Azure Arc machines should have the Log Analytics extension installedMapped
Batch accounts should have resource logs enabledMapped
Virtual machines should have the Guest Configuration extension installedMapped
Virtual machines should use system-assigned managed identity with the Guest Configuration extensionMapped
Virtual machines should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Linux virtual machines should have the network traffic data collection agent installedMapped
Windows virtual machines should have the network traffic data collection agent installedMapped
Virtual machine scale sets should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Data Lake Analytics accounts should have resource logs enabledMapped
Data Lake Store accounts should have resource logs enabledMapped
Event Hub namespaces should have resource logs enabledMapped
IoT hubs should have resource logs enabledMapped
Key vaults should have resource logs enabledMapped
Logic App workflows should have resource logs enabledMapped
Azure subscriptions should have Network Watcher enabledMapped
Search services should have resource logs enabledMapped
Azure subscriptions should have auto provisioning of the Log Analytics agent enabledMapped
Azure subscriptions should have Microsoft Defender for App Service enabledMapped
Azure subscriptions should have Microsoft Defender for Containers enabledMapped
Azure subscriptions should have Azure Defender for DNS enabledMapped
Azure subscriptions should have Microsoft Defender for Key Vault enabledMapped
Azure subscriptions should have Azure Defender for Resource Manager enabledMapped
Azure subscriptions should have Microsoft Defender for Servers enabledMapped
Azure subscriptions should have Microsoft Defender for Azure SQL Database servers enabledMapped
Unprotected SQL Server virtual machines should have Azure Defender for SQL enabledMapped
Azure subscriptions should have Microsoft Defender for Storage enabledMapped
Service Bus namespaces should have resource logs enabledMapped
SQL servers should have auditing enabledMapped
Unprotected Azure SQL servers should have Azure Defender for SQL enabledMapped
Stream Analytics jobs should have resource logs enabledMapped

AU-6(5) Integrated Analysis of Audit Records

ControlStatus
App Service apps should have resource logs enabledMapped
Linux Azure Arc machines should have the Log Analytics extension installedMapped
Windows Azure Arc machines should have the Log Analytics extension installedMapped
Batch accounts should have resource logs enabledMapped
Virtual machines should have the Guest Configuration extension installedMapped
Virtual machines should use system-assigned managed identity with the Guest Configuration extensionMapped
Virtual machines should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Linux virtual machines should have the network traffic data collection agent installedMapped
Windows virtual machines should have the network traffic data collection agent installedMapped
Virtual machine scale sets should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Data Lake Analytics accounts should have resource logs enabledMapped
Data Lake Store accounts should have resource logs enabledMapped
Event Hub namespaces should have resource logs enabledMapped
IoT hubs should have resource logs enabledMapped
Key vaults should have resource logs enabledMapped
Logic App workflows should have resource logs enabledMapped
Azure subscriptions should have Network Watcher enabledMapped
Search services should have resource logs enabledMapped
Azure subscriptions should have auto provisioning of the Log Analytics agent enabledMapped
Azure subscriptions should have Microsoft Defender for App Service enabledMapped
Azure subscriptions should have Microsoft Defender for Containers enabledMapped
Azure subscriptions should have Azure Defender for DNS enabledMapped
Azure subscriptions should have Microsoft Defender for Key Vault enabledMapped
Azure subscriptions should have Azure Defender for Resource Manager enabledMapped
Azure subscriptions should have Microsoft Defender for Servers enabledMapped
Azure subscriptions should have Microsoft Defender for Azure SQL Database servers enabledMapped
Unprotected SQL Server virtual machines should have Azure Defender for SQL enabledMapped
Azure subscriptions should have Microsoft Defender for Storage enabledMapped
Service Bus namespaces should have resource logs enabledMapped
SQL servers should have auditing enabledMapped
Unprotected Azure SQL servers should have Azure Defender for SQL enabledMapped
Stream Analytics jobs should have resource logs enabledMapped

CM-6 Configuration Settings

CM-7 Least Functionality

CP-6 Alternate Storage Site

CP-6(1) Separation from Primary Site

CP-7 Alternate Processing Site

CP-9 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 Monitoring and 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
Azure Cosmos DB accounts should use customer-managed keys to encrypt data at restMapped
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
PostgreSQL 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-3 Security Function Isolation

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 should use private linkMapped
Cognitive Services accounts should have public network access disabledMapped
Cognitive Services accounts should have network access restrictions configuredMapped
Disk access resources should use private linkMapped
Virtual machines should use just-in-time network access control for management portsMapped
Virtual machines should have all network ports restricted by their associated network security groupsMapped
Internet-facing virtual machines should use network security groups for protectionMapped
Container registries should not allow unrestricted network accessMapped
Container registries should use private linkMapped
Cosmos DB accounts should use private linkMapped
Azure Cosmos DB accounts should have firewall rulesMapped
Data factories should use private linkMapped
Azure Event Grid domains should use private linkMapped
Azure Event Grid topics 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
IoT Hub device provisioning service instances should use private linkMapped
Key vaults should have a firewall enabledMapped
Azure Key Vaults 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
Virtual machines should have management ports closedMapped
Subnets should have a network security group configuredMapped
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 have public network access disabledMapped
Azure Cognitive Search services 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 public network access disabledMapped
Azure SQL databases should have private endpoint connections enabledMapped
Storage accounts should prohibit public accessMapped
Storage accounts should have network access restrictions configuredMapped
Storage accounts should use virtual network rules to restrict network accessMapped
Storage accounts should use private linkMapped
Azure File Sync should use private linkMapped
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 should use private linkMapped
Cognitive Services accounts should have public network access disabledMapped
Cognitive Services accounts should have network access restrictions configuredMapped
Disk access resources should use private linkMapped
Virtual machines should use just-in-time network access control for management portsMapped
Virtual machines should have all network ports restricted by their associated network security groupsMapped
Internet-facing virtual machines should use network security groups for protectionMapped
Container registries should not allow unrestricted network accessMapped
Container registries should use private linkMapped
Cosmos DB accounts should use private linkMapped
Azure Cosmos DB accounts should have firewall rulesMapped
Data factories should use private linkMapped
Azure Event Grid domains should use private linkMapped
Azure Event Grid topics 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
IoT Hub device provisioning service instances should use private linkMapped
Key vaults should have a firewall enabledMapped
Azure Key Vaults 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
Virtual machines should have management ports closedMapped
Subnets should have a network security group configuredMapped
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 have public network access disabledMapped
Azure Cognitive Search services 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 public network access disabledMapped
Azure SQL databases should have private endpoint connections enabledMapped
Storage accounts should prohibit public accessMapped
Storage accounts should have network access restrictions configuredMapped
Storage accounts should use virtual network rules to restrict network accessMapped
Storage accounts should use private linkMapped
Azure File Sync should use private linkMapped
Azure Synapse workspaces should use private linkMapped

SC-8 Transmission Confidentiality and Integrity

SC-8(1) Cryptographic Protection

SI-16 Memory Protection

SI-2 Flaw Remediation

SI-2(6) Removal of Previous Versions of Software and Firmware

SI-3 Malicious Code Protection

SI-4 System Monitoring

ControlStatus
Linux Azure Arc machines should have the Log Analytics extension installedMapped
Windows Azure Arc machines should have the Log Analytics extension installedMapped
Virtual machines should have the Guest Configuration extension installedMapped
Virtual machines should use system-assigned managed identity with the Guest Configuration extensionMapped
Virtual machines should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Linux virtual machines should have the network traffic data collection agent installedMapped
Windows virtual machines should have the network traffic data collection agent installedMapped
Virtual machine scale sets should have the Log Analytics agent installed for Azure Security Center monitoringMapped
Azure subscriptions should have Network Watcher enabledMapped
Azure subscriptions should have auto provisioning of the Log Analytics agent enabledMapped
Azure subscriptions should have Microsoft Defender for App Service enabledMapped
Azure subscriptions should have Microsoft Defender for Containers enabledMapped
Azure subscriptions should have Azure Defender for DNS enabledMapped
Azure subscriptions should have Microsoft Defender for Key Vault enabledMapped
Azure subscriptions should have Azure Defender for Resource Manager enabledMapped
Azure subscriptions should have Microsoft Defender for Servers enabledMapped
Azure subscriptions should have Microsoft Defender for Azure SQL Database servers enabledMapped
Azure subscriptions should have Microsoft Defender for Storage enabledMapped
Unprotected Azure SQL servers should have Azure Defender for SQL enabledMapped

SI-4(12) Automated Organization-generated Alerts

FrameworkControl overlapNote
NIST SP 800-171 Rev 2High 93%
FedRAMP HighHigh 92%
FedRAMP Moderate Baseline Rev 4High 68%

Frequently asked questions

What is NIST SP 800-53 Revision 5?

It is a catalog of security and privacy controls for information systems and organizations. The controls protect organizational operations and assets, individuals, other organizations, and the Nation from threats and risks, and are implemented as part of an organization-wide process to manage risk.

When was SP 800-53 Revision 5 published and what changed recently?

It was published in September 2020, with updates as of December 10, 2020. On August 27, 2025, NIST issued a minor release (Release 5.2.0) that added `SA-15(13)`, `SA-24` and `SI-02(07)` and revised `SI-07(12)`.

How does FedRAMP relate to NIST SP 800-53?

FedRAMP was established to provide a standardized approach for assessing, monitoring, and authorizing cloud computing products and services. It is based on the NIST SP 800-53 standard, augmented by FedRAMP controls and control enhancements.

Which revision of NIST SP 800-53 replaced Revision 4?

Revision 4 of NIST SP 800-53 was withdrawn on 23 September 2021 and superseded by Revision 5.

How does Azure Policy relate to NIST SP 800-53 compliance?

Each control is associated with one or more Azure Policy definitions that may help assess compliance. Compliance in Azure Policy is only a partial view of overall compliance status.

On this page

Controls by categoryAC-16 Security and Privacy AttributesAC-17 Remote AccessAC-17(1) Monitoring and ControlAC-2 Account ManagementAC-2(1) Automated System Account ManagementAC-2(12) Account Monitoring for Atypical UsageAC-2(7) Privileged User AccountsAC-3 Access EnforcementAC-3(7) Role-based Access ControlAC-4 Information Flow EnforcementAC-4(3) Dynamic Information Flow ControlAC-5 Separation of DutiesAC-6 Least PrivilegeAC-6(7) Review of User PrivilegesAU-11 Audit Record RetentionAU-12 Audit Record GenerationAU-12(1) System-wide and Time-correlated Audit TrailAU-6 Audit Record Review, Analysis, and ReportingAU-6(4) Central Review and AnalysisAU-6(5) Integrated Analysis of Audit RecordsCM-6 Configuration SettingsCM-7 Least FunctionalityCP-6 Alternate Storage SiteCP-6(1) Separation from Primary SiteCP-7 Alternate Processing SiteCP-9 System BackupIA-2 Identification and Authentication (organizational Users)IA-4 Identifier ManagementIA-5 Authenticator ManagementIA-5(1) Password-based AuthenticationIR-4 Incident HandlingIR-5 Incident MonitoringIR-6(2) Vulnerabilities Related to IncidentsRA-5 Vulnerability Monitoring and ScanningSC-12 Cryptographic Key Establishment and ManagementSC-28 Protection of Information at RestSC-28(1) Cryptographic ProtectionSC-3 Security Function IsolationSC-5 Denial-of-service ProtectionSC-7 Boundary ProtectionSC-7(3) Access PointsSC-8 Transmission Confidentiality and IntegritySC-8(1) Cryptographic ProtectionSI-16 Memory ProtectionSI-2 Flaw RemediationSI-2(6) Removal of Previous Versions of Software and FirmwareSI-3 Malicious Code ProtectionSI-4 System MonitoringSI-4(12) Automated Organization-generated AlertsRelated frameworksFrequently asked questions

Ask AI about this

Help improve this page