| Control Domain | Control | Name | MetadataId | Category | Title | Owner | Requirements | Description | Info | Policies | Policy categories | PolicySet |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ACAT_Security_Policies | ACAT_Security_Policies | ACAT Security Policies | Guidelines for M365 Certification | Protecting systems and resources | Shared | n/a | Ensures that apps have strong security and compliance practices in place to protect customer data, security, and privacy. | link | count: 024 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service Environment should have TLS 1.0 and 1.1 disabled (d6545c6b-dd9d-4265-91e6-0b451e2f1c50), Azure Firewall Premium should configure a valid intermediate certificate to enable TLS inspection (711c24bb-7f18-4578-b192-81a6161e1f17), Azure SQL Database should be running TLS version 1.2 or newer (32e6bbec-16b6-44c2-be37-c5b672d103cf), Azure Synapse Analytics dedicated SQL pools should enable encryption (cfaf0007-99c7-4b01-b36b-4048872ac978), Bypass list of Intrusion Detection and Prevention System (IDPS) should be empty in Firewall Policy Premium (f516dc7a-4543-4d40-aad6-98f76a706b50), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Firewall Policy Premium should enable all IDPS signature rules to monitor all inbound and outbound traffic flows (610b6183-5f00-4d68-86d2-4ab4cb3a67a5), Firewall Policy Premium should enable the Intrusion Detection and Prevention System (IDPS) (6484db87-a62d-4327-9f07-80a2cbdf333a), Linux virtual machines should have Azure Monitor Agent installed (1afdc4b6-581a-45fb-b630-f1e6051e3e7a), SQL Managed Instance should have the minimal TLS version of 1.2 (a8793640-60f7-487c-b5c3-1d37215905c4), Storage accounts should have the specified minimum TLS version (fe83a0eb-a853-422d-aac2-1bffd182c5d0), Subscription should configure the Azure Firewall Premium to provide additional layer of protection (f2c2d0a6-e183-4fc8-bd8f-363c65d3bbbf), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a), Web Application Firewall (WAF) should enable all firewall rules for Application Gateway (632d3993-e2c0-44ea-a7db-2eca131f356d), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Windows machines should configure Windows Defender to update protection signatures within one day (d96163de-dbe0-45ac-b803-0e9ca0f5764e), Windows machines should enable Windows Defender Real-time protection (b3248a42-b1c1-41a4-87bc-8bad3d845589), Windows machines should schedule Windows Defender to perform a scheduled scan every day (3810e389-1d92-4f77-9267-33bdcf0bd225), Windows machines should use the default NTP server (2454bbee-dc19-442f-83fc-7f3114cafd91), Windows virtual machines should have Azure Monitor Agent installed (c02729e5-e5e7-4458-97fa-2b5ad0661f28) |
App Service, Azure Data Explorer, Guest Configuration, Monitoring, Network, SQL, Storage, Synapse | ACAT for Microsoft 365 Certification (80307b86-ab81-45ab-bf4f-4e0b93cf3dd5) | |
| AU_ISM | 1139 | AU_ISM_1139 | AU ISM 1139 | Guidelines for Cryptography - Transport Layer Security | Using Transport Layer Security - 1139 | n/a | Only the latest version of TLS is used. | link | count: 006 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Guest Configuration | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1144 | AU_ISM_1144 | AU ISM 1144 | Guidelines for System Management - System patching | When to patch security vulnerabilities - 1144 | n/a | Security vulnerabilities in applications and drivers assessed as extreme risk are patched, updated or mitigated within 48 hours of the security vulnerabilities being identified by vendors, independent third parties, system managers or users. | link | count: 007 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1173 | AU_ISM_1173 | AU ISM 1173 | Guidelines for System Hardening - Authentication hardening | Multi-factor authentication - 1173 | n/a | Multi-factor authentication is used to authenticate all privileged users and any other positions of trust. | link | count: 002 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1182 | AU_ISM_1182 | AU ISM 1182 | Guidelines for Networking - Network design and configuration | Network access controls - 1182 | n/a | Network access controls are implemented to limit traffic within and between network segments to only those that are required for business purposes. | link | count: 003 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Security Center, Storage | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1260 | AU_ISM_1260 | AU ISM 1260 | Guidelines for Database Systems - Database management system software | Database administrator accounts - 1260 | n/a | Default database administrator accounts are disabled, renamed or have their passphrases changed. | link | count: 001 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9) |
SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1261 | AU_ISM_1261 | AU ISM 1261 | Guidelines for Database Systems - Database management system software | Database administrator accounts - 1261 | n/a | Database administrator accounts are not shared across different databases. | link | count: 001 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9) |
SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1262 | AU_ISM_1262 | AU ISM 1262 | Guidelines for Database Systems - Database management system software | Database administrator accounts - 1262 | n/a | Database administrators have unique and identifiable accounts. | link | count: 001 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9) |
SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1263 | AU_ISM_1263 | AU ISM 1263 | Guidelines for Database Systems - Database management system software | Database administrator accounts - 1263 | n/a | Database administrator accounts are used exclusively for administrative tasks, with standard database accounts used for general purpose interactions with databases. | link | count: 001 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9) |
SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1264 | AU_ISM_1264 | AU ISM 1264 | Guidelines for Database Systems - Database management system software | Database administrator accounts - 1264 | n/a | Database administrator access is restricted to defined roles rather than accounts with default administrative permissions, or all permissions. | link | count: 001 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9) |
SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1277 | AU_ISM_1277 | AU ISM 1277 | Guidelines for Database Systems - Database servers | Communications between database servers and web servers - 1277 | n/a | Data communicated between database servers and web applications is encrypted. | link | count: 006 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
Cache, Guest Configuration, Storage | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1288 | AU_ISM_1288 | AU ISM 1288 | Guidelines for Gateways - Content filtering | Antivirus scanning - 1288 | n/a | Antivirus scanning, using multiple different scanning engines, is performed on all content. | link | count: 003 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Compute, Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1384 | AU_ISM_1384 | AU ISM 1384 | Guidelines for System Hardening - Authentication hardening | Multi-factor authentication - 1384 | n/a | Multi-factor authentication is used to authenticate privileged users each time they perform privileged actions. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1386 | AU_ISM_1386 | AU ISM 1386 | Guidelines for System Management - System administration | Restriction of management traffic flows - 1386 | n/a | Management traffic is only allowed to originate from network zones that are used to administer systems and applications. | link | count: 003 App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
App Service, Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1407 | AU_ISM_1407 | AU ISM 1407 | Guidelines for System Hardening - Operating system hardening | Operating system versions - 1407 | n/a | The latest version (N), or N-1 version, of an operating system is used for SOEs. | link | count: 002 System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1417 | AU_ISM_1417 | AU ISM 1417 | Guidelines for System Hardening - Operating system hardening | Antivirus software - 1417 | n/a | Antivirus software is implemented on workstations and servers and configured with: • signature-based detection enabled and set to a high level • heuristic-based detection enabled and set to a high level • detection signatures checked for currency and updated on at least a daily basis • automatic and regular scanning configured for all fixed disks and removable media. | link | count: 003 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Compute, Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1424 | AU_ISM_1424 | AU ISM 1424 | Guidelines for Software Development - Web application development | Web browser-based security controls - 1424 | n/a | Web applications implement Content-Security-Policy, HSTS and X-Frame-Options response headers. | link | count: 001 App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9) |
App Service | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1425 | AU_ISM_1425 | AU ISM 1425 | Guidelines for Database Systems - Database servers | Protecting database server contents - 1425 | n/a | Hard disks of database servers are encrypted using full disk encryption. | link | count: 002 Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Security Center, SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1431 | AU_ISM_1431 | AU ISM 1431 | Guidelines for Networking - Service continuity for online services | Denial of service strategies - 1431 | n/a | Denial-of-service attack prevention and mitigation strategies are discussed with cloud service providers, specifically: • their capacity to withstand denial-of-service attacks • any costs likely to be incurred as a result of denial-of-service attacks • thresholds for notification of denial-of-service attacks • thresholds for turning off online services during denial-of-service attacks • pre-approved actions that can be undertaken during denial-of-service attacks • denial-of-service attack prevention arrangements with upstream service providers to block malicious traffic as far upstream as possible. | link | count: 001 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1472 | AU_ISM_1472 | AU ISM 1472 | Guidelines for System Management - System patching | When to patch security vulnerabilities - 1472 | n/a | Security vulnerabilities in applications and drivers assessed as moderate or low risk are patched, updated or mitigated within one month of the security vulnerability being identified by vendors, independent third parties, system managers or users. | link | count: 007 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1490 | AU_ISM_1490 | AU ISM 1490 | Guidelines for System Hardening - Operating system hardening | Application control - 1490 | n/a | Application control is implemented on all servers to restrict the execution of executables, software libraries, scripts and installers to an approved set. | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1494 | AU_ISM_1494 | AU ISM 1494 | Guidelines for System Management - System patching | When to patch security vulnerabilities - 1494 | n/a | Security vulnerabilities in operating systems and firmware assessed as extreme risk are patched, updated or mitigated within 48 hours of the security vulnerabilities being identified by vendors, independent third parties, system managers or users. | link | count: 007 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1495 | AU_ISM_1495 | AU ISM 1495 | Guidelines for System Management - System patching | When to patch security vulnerabilities - 1495 | n/a | Security vulnerabilities in operating systems and firmware assessed as high risk are patched, updated or mitigated within two weeks of the security vulnerability being identified by vendors, independent third parties, system managers or users. | link | count: 007 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1496 | AU_ISM_1496 | AU ISM 1496 | Guidelines for System Management - System patching | When to patch security vulnerabilities - 1496 | n/a | Security vulnerabilities in operating systems and firmware assessed as moderate or low risk are patched, updated or mitigated within one month of the security vulnerability being identified by vendors, independent third parties, system managers or users. | link | count: 007 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1503 | AU_ISM_1503 | AU ISM 1503 | Guidelines for Personnel Security - Access to systems and their resources | Standard access to systems - 1503 | n/a | Standard access to systems, applications and data repositories is limited to that required for personnel to undertake their duties. | link | count: 006 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1507 | AU_ISM_1507 | AU ISM 1507 | Guidelines for Personnel Security - Access to systems and their resources | Privileged access to systems - 1507 | n/a | Privileged access to systems, applications and data repositories is validated when first requested and revalidated on an annual or more frequent basis. | link | count: 004 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1508 | AU_ISM_1508 | AU ISM 1508 | Guidelines for Personnel Security - Access to systems and their resources | Privileged access to systems - 1508 | n/a | Privileged access to systems, applications and data repositories is limited to that required for personnel to undertake their duties. | link | count: 007 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1511 | AU_ISM_1511 | AU ISM 1511 | Guidelines for System Management - Data backup and restoration | Performing backups - 1511 | n/a | Backups of important data, software and configuration settings are performed at least daily. | link | count: 001 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56) |
Compute | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1537 | AU_ISM_1537 | AU ISM 1537 | Guidelines for System Monitoring - Event logging and auditing | Events to be logged - 1537 | n/a | The following events are logged for databases: • access to particularly important data • addition of new users, especially privileged users • any query containing comments • any query containing multiple embedded queries • any query or database alerts or failures • attempts to elevate privileges • attempted access that is successful or unsuccessful • changes to the database structure • changes to user roles or database permissions • database administrator actions • database logons and logoffs • modifications to data • use of executable commands. | link | count: 003 Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
Monitoring, SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1546 | AU_ISM_1546 | AU ISM 1546 | Guidelines for System Hardening - Authentication hardening | Authenticating to systems - 1546 | n/a | Users are authenticated before they are granted access to a system and its resources. | link | count: 007 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Guest Configuration, Service Fabric, Storage | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 1552 | AU_ISM_1552 | AU ISM 1552 | Guidelines for Software Development - Web application development | Web application interactions - 1552 | n/a | All web application content is offered exclusively using HTTPS. | link | count: 003 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb) |
App Service, Cache | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 380 | AU_ISM_380 | AU ISM 380 | Guidelines for System Hardening - Operating system hardening | Operating system configuration - 380 | n/a | Unneeded operating system accounts, software, components, services and functionality are removed or disabled. | link | count: 002 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 414 | AU_ISM_414 | AU ISM 414 | Guidelines for Personnel Security - Access to systems and their resources | User identification - 414 | n/a | Personnel granted access to a system and its resources are uniquely identifiable. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 415 | AU_ISM_415 | AU ISM 415 | Guidelines for Personnel Security - Access to systems and their resources | User identification - 415 | n/a | The use of shared user accounts is strictly controlled, and personnel using such accounts are uniquely identifiable. | link | count: 004 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 421 | AU_ISM_421 | AU ISM 421 | Guidelines for System Hardening - Authentication hardening | Single-factor authentication - 421 | n/a | Passphrases used for single-factor authentication are a minimum of 14 characters with complexity, ideally as 4 random words. | link | count: 004 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Windows machines should meet requirements for 'Security Settings - Account Policies' (f2143251-70de-4e81-87a8-36cee5a2f29d) |
Guest Configuration | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 430 | AU_ISM_430 | AU ISM 430 | Guidelines for Personnel Security - Access to systems and their resources | Suspension of access to systems - 430 | n/a | Access to systems, applications and data repositories is removed or suspended on the same day personnel no longer have a legitimate requirement for access. | link | count: 002 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 441 | AU_ISM_441 | AU ISM 441 | Guidelines for Personnel Security - Access to systems and their resources | Temporary access to systems - 441 | n/a | When personnel are granted temporary access to a system, effective security controls are put in place to restrict their access to only data required for them to undertake their duties. | link | count: 004 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 445 | AU_ISM_445 | AU ISM 445 | Guidelines for Personnel Security - Access to systems and their resources | Privileged access to systems - 445 | n/a | Privileged users are assigned a dedicated privileged account to be used solely for tasks requiring privileged access. | link | count: 004 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 459 | AU_ISM_459 | AU ISM 459 | Guidelines for Cryptography - Cryptographic fundamentals | Encrypting data at rest - 459 | n/a | Encryption software used for data at rest implements full disk encryption, or partial encryption where access controls will only allow writing to the encrypted partition. | link | count: 001 Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 520 | AU_ISM_520 | AU ISM 520 | Guidelines for Networking - Network design and configuration | Network access controls - 520 | n/a | Network access controls are implemented on networks to prevent the connection of unauthorised network devices. | link | count: 001 Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Storage | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 582 | AU_ISM_582 | AU ISM 582 | Guidelines for System Monitoring - Event logging and auditing | Events to be logged - 582 | n/a | The following events are logged for operating systems: • access to important data and processes • application crashes and any error messages • attempts to use special privileges • changes to accounts • changes to security policy • changes to system configurations • Domain Name System (DNS) and Hypertext Transfer Protocol requests • failed attempts to access data and system resources • service failures and restarts • system startup and shutdown • transfer of data to and from external media • user or group management • use of special privileges. | link | count: 002 Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917) |
Monitoring | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 940 | AU_ISM_940 | AU ISM 940 | Guidelines for System Management - System patching | When to patch security vulnerabilities - 940 | n/a | Security vulnerabilities in applications and drivers assessed as high risk are patched, updated or mitigated within two weeks of the security vulnerability being identified by vendors, independent third parties, system managers or users. | link | count: 007 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| AU_ISM | 947 | AU_ISM_947 | AU ISM 947 | Guidelines for Media - Media usage | Using media for data transfers - 947 | n/a | When transferring data manually between two systems belonging to different security domains, rewritable media is sanitised after each data transfer. | link | count: 001 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4) |
Security Center | [Preview]: Australian Government ISM PROTECTED (27272c0b-c225-4cc3-b8b0-f2534b093077) | |
| Automanage Best Practices | Automanage Best Practices | 404 not found | n/a | n/a | count: 001 [Preview]: Automanage Configuration Profile Assignment should be Conformant (fd4726f4-a5fc-4540-912d-67c96fc992d5) |
Automanage | [Preview]: Audit configuration against Automanage Best Practices (c138fd1a-e08f-4318-9490-d11ef2c2f9c1) | |||||
| Azure Security Baseline | Azure Security Baseline | 404 not found | n/a | n/a | count: 004 [Preview]: A managed identity should be enabled on your machines (e4953962-5ae4-43eb-bb92-d66fd5563487), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
Automanage, Guest Configuration, Security Center | [Preview]: Audit configuration against Automanage Best Practices (c138fd1a-e08f-4318-9490-d11ef2c2f9c1) | |||||
| Azure_Security_Benchmark_v1.0 | 1.1 | Azure_Security_Benchmark_v1.0_1.1 | Azure Security Benchmark 1.1 | Network Security | Protect resources using Network Security Groups or Azure Firewall on your Virtual Network | Customer | Ensure that all Virtual Network subnet deployments have a Network Security Group applied with network access controls specific to your application's trusted ports and sources. Use Azure Services with Private Link enabled, deploy the service inside your Vnet, or connect privately using Private Endpoints. For service specific requirements, please refer to the security recommendation for that specific service. Alternatively, if you have a specific use case, requirements can be met by implementing Azure Firewall. General Information on Private Link: https://docs.microsoft.com/azure/private-link/private-link-overview How to create a Virtual Network: https://docs.microsoft.com/azure/virtual-network/quick-create-portal How to create an NSG with a security configuration: https://docs.microsoft.com/azure/virtual-network/tutorial-filter-network-traffic How to deploy and configure Azure Firewall: https://docs.microsoft.com/azure/firewall/tutorial-firewall-deploy-portal | n/a | link | count: 021 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Container Registry should use a virtual network service endpoint (c4857be7-912a-4c75-87e6-e30292bcdf78), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), App Service apps should use a virtual network service endpoint (2d21331d-a4c2-4def-a9ad-ee4e1e023beb), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Cosmos DB should use a virtual network service endpoint (e0a2b1a3-f7f9-4569-807f-2a9edebdf4d9), Event Hub should use a virtual network service endpoint (d63edb4a-c612-454d-b47d-191a724fcbf0), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Key Vault should use a virtual network service endpoint (ea4d6841-2173-4317-9747-ff522a45120f), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), SQL Server should use a virtual network service endpoint (ae5d2f14-d830-42b6-9899-df6cfe9c71a3), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage Accounts should use a virtual network service endpoint (60d21c4f-21a3-4d94-85f4-b924e6aeeda4), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3), Virtual networks should use specified virtual network gateway (f1776c76-f58c-4245-a8d0-2b207198dc8b) |
Network, Security Center, SQL, Storage | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 1.11 | Azure_Security_Benchmark_v1.0_1.11 | Azure Security Benchmark 1.11 | Network Security | Use automated tools to monitor network resource configurations and detect changes | Customer | Use Azure Policy to validate (and/or remediate) configuration for network resources. How to configure and manage Azure Policy: https://docs.microsoft.com/azure/governance/policy/tutorials/create-and-manage Azure Policy samples for networking: https://docs.microsoft.com/azure/governance/policy/samples/#network | n/a | link | count: 007 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Windows machines should meet requirements for 'Administrative Templates - Network' (67e010c1-640d-438e-a3a5-feaccb533a98), Windows machines should meet requirements for 'Security Options - Microsoft Network Server' (caf2d518-f029-4f6b-833b-d7081702f253), Windows machines should meet requirements for 'Security Options - Network Access' (3ff60f98-7fa4-410a-9f7f-0b00f5afdbdd), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 1.2 | Azure_Security_Benchmark_v1.0_1.2 | Azure Security Benchmark 1.2 | Network Security | Monitor and log the configuration and traffic of Vnets, Subnets, and NICs | Customer | Use Azure Security Center and follow network protection recommendations to help secure your network resources in Azure. Enable NSG flow logs and send logs into a Storage Account for traffic audit. How to Enable NSG Flow Logs: https://docs.microsoft.com/azure/network-watcher/network-watcher-nsg-flow-logging-portal Understand Network Security provided by Azure Security Center: https://docs.microsoft.com/azure/security-center/security-center-network-recommendations | n/a | link | count: 001 Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6) |
Network | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 1.3 | Azure_Security_Benchmark_v1.0_1.3 | Azure Security Benchmark 1.3 | Network Security | Protect critical web applications | Customer | Deploy Azure Web Application Firewall (WAF) in front of critical web applications for additional inspection of incoming traffic. Enable Diagnostic Setting for WAF and ingest logs into a Storage Account, Event Hub, or Log Analytics Workspace. How to deploy Azure WAF: https://docs.microsoft.com/azure/web-application-firewall/ag/create-waf-policy-ag | n/a | link | count: 005 App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5) |
App Service | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 1.4 | Azure_Security_Benchmark_v1.0_1.4 | Azure Security Benchmark 1.4 | Network Security | Deny communications with known malicious IP addresses | Customer | Enable DDoS Standard protection on your Azure Virtual Networks to guard against DDoS attacks. Use Azure Security Center Integrated Threat Intelligence to deny communications with known malicious IP addresses. Deploy Azure Firewall at each of the organization's network boundaries with Threat Intelligence enabled and configured to "Alert and deny" for malicious network traffic. Use Azure Security Center Just In Time Network access to configure NSGs to limit exposure of endpoints to approved IP addresses for a limited period. Use Azure Security Center Adaptive Network Hardening to recommend NSG configurations that limit ports and source IPs based on actual traffic and threat intelligence. How to configure DDoS protection: https://docs.microsoft.com/azure/virtual-network/manage-ddos-protection How to deploy Azure Firewall: https://docs.microsoft.com/azure/firewall/tutorial-firewall-deploy-portal Understand Azure Security Center Integrated Threat Intelligence: https://docs.microsoft.com/azure/security-center/security-center-alerts-service-layer Understand Azure Security Center Adaptive Network Hardening: https://docs.microsoft.com/azure/security-center/security-center-adaptive-network-hardening Understand Azure Security Center Just In Time Network Access Control: https://docs.microsoft.com/azure/security-center/security-center-just-in-time | n/a | link | count: 004 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Network, Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 1.5 | Azure_Security_Benchmark_v1.0_1.5 | Azure Security Benchmark 1.5 | Network Security | Record network packets and flow logs | Customer | Record NSG flow logs into a storage account to generate flow records. If required for investigating anomalous activity, enable Network Watcher packet capture. How to Enable NSG Flow Logs: https://docs.microsoft.com/azure/network-watcher/network-watcher-nsg-flow-logging-portal How to enable Network Watcher: https://docs.microsoft.com/azure/network-watcher/network-watcher-create | n/a | link | count: 001 Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6) |
Network | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 10.4 | Azure_Security_Benchmark_v1.0_10.4 | Azure Security Benchmark 10.4 | Incident Response | Provide security incident contact details and configure alert notifications for security incidents | Customer | Security incident contact information will be used by Microsoft to contact you if the Microsoft Security Response Center (MSRC) discovers that the customer's data has been accessed by an unlawful or unauthorized party. Review incidents after the fact to ensure that issues are resolved. How to set the Azure Security Center Security Contact: https://docs.microsoft.com/azure/security-center/security-center-provide-security-contact-details | n/a | link | count: 001 Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 2.2 | Azure_Security_Benchmark_v1.0_2.2 | Azure Security Benchmark 2.2 | Logging and Monitoring | Configure central security log management | Customer | Ingest logs via Azure Monitor to aggregate security data generated by endpoint devices, network resources, and other security systems. Within Azure Monitor, use Log Analytics Workspace(s) to query and perform analytics, and use Azure Storage Accounts for long-term/archival storage. Alternatively, you may enable and on-board data to Azure Sentinel or a third-party SIEM. How to onboard Azure Sentinel: https://docs.microsoft.com/azure/sentinel/quickstart-onboard How to collect platform logs and metrics with Azure Monitor: https://docs.microsoft.com/azure/azure-monitor/platform/diagnostic-settings How to collect Azure Virtual Machine internal host logs with Azure Monitor: https://docs.microsoft.com/azure/azure-monitor/learn/quick-collect-azurevm How to get started with Azure Monitor and third-party SIEM integration: https://azure.microsoft.com/blog/use-azure-monitor-to-integrate-with-siem-tools/ | n/a | link | count: 006 Audit Windows machines on which the Log Analytics agent is not connected as expected (6265018c-d7e2-432f-a75d-094d5f6f4465), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
Guest Configuration, Monitoring, Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 2.3 | Azure_Security_Benchmark_v1.0_2.3 | Azure Security Benchmark 2.3 | Logging and Monitoring | Enable audit logging for Azure resources | Customer | Enable Diagnostic Settings on Azure resources for access to audit, security, and diagnostic logs. Activity logs, which are automatically available, include event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. How to collect platform logs and metrics with Azure Monitor: https://docs.microsoft.com/azure/azure-monitor/platform/diagnostic-settings Understand logging and different log types in Azure: https://docs.microsoft.com/azure/azure-monitor/platform/platform-logs-overview | n/a | link | count: 015 [Deprecated]: Resource logs in Virtual Machine Scale Sets should be enabled (7c1b1214-f927-48bf-8882-84f0af6588b1), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), SQL Auditing settings should have Action-Groups configured to capture critical activities (7ff426e2-515f-405a-91c8-4f2333442eb5) |
App Service, Batch, Compute, Data Lake, Event Hub, Internet of Things, Key Vault, Logic Apps, Monitoring, Search, Service Bus, SQL, Stream Analytics | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 2.4 | Azure_Security_Benchmark_v1.0_2.4 | Azure Security Benchmark 2.4 | Logging and Monitoring | Collect security logs from operating systems | Customer | If the compute resource is owned by Microsoft, then Microsoft is responsible for monitoring it. If the compute resource is owned by your organization, it's your responsibility to monitor it. You can use Azure Security Center to monitor the OS. Data collected by Security Center from the operating system includes OS type and version, OS (Windows Event Logs), running processes, machine name, IP addresses, and logged in user. The Log Analytics Agent also collects crash dump files. How to collect Azure Virtual Machine internal host logs with Azure Monitor: https://docs.microsoft.com/azure/azure-monitor/learn/quick-collect-azurevm Understand Azure Security Center data collection: https://docs.microsoft.com/azure/security-center/security-center-enable-data-collection | n/a | link | count: 004 Audit Windows machines on which the Log Analytics agent is not connected as expected (6265018c-d7e2-432f-a75d-094d5f6f4465), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
Guest Configuration, Monitoring, Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 2.5 | Azure_Security_Benchmark_v1.0_2.5 | Azure Security Benchmark 2.5 | Logging and Monitoring | Configure security log storage retention | Customer | Within Azure Monitor, set your Log Analytics Workspace retention period according to your organization's compliance regulations. Use Azure Storage Accounts for long-term/archival storage. How to set log retention parameters for Log Analytics Workspaces: https://docs.microsoft.com/azure/azure-monitor/platform/manage-cost-storage#change-the-data-retention-period | n/a | link | count: 001 SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
SQL | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 2.7 | Azure_Security_Benchmark_v1.0_2.7 | Azure Security Benchmark 2.7 | Logging and Monitoring | Enable alerts for anomalous activity | Customer | Use Azure Security Center with Log Analytics Workspace for monitoring and alerting on anomalous activity found in security logs and events. Alternatively, you may enable and on-board data to Azure Sentinel. How to onboard Azure Sentinel: https://docs.microsoft.com/azure/sentinel/quickstart-onboard How to manage alerts in Azure Security Center: https://docs.microsoft.com/azure/security-center/security-center-managing-and-responding-alerts How to alert on log analytics log data: https://docs.microsoft.com/azure/azure-monitor/learn/tutorial-response | n/a | link | count: 002 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
SQL | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 2.8 | Azure_Security_Benchmark_v1.0_2.8 | Azure Security Benchmark 2.8 | Logging and Monitoring | Centralize anti-malware logging | Customer | Enable antimalware event collection for Azure Virtual Machines and Cloud Services. How to configure Microsoft Antimalware for Virtual Machines: https://docs.microsoft.com/powershell/module/servicemanagement/azure/set-azurevmmicrosoftantimalwareextension?view=azuresmps-4.0.0 How to configure Microsoft Antimalware for Cloud Services: https://docs.microsoft.com/powershell/module/servicemanagement/azure/set-azureserviceantimalwareextension?view=azuresmps-4.0.0 Understand Microsoft Antimalware: https://docs.microsoft.com/azure/security/fundamentals/antimalware | n/a | link | count: 003 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Compute, Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 3.1 | Azure_Security_Benchmark_v1.0_3.1 | Azure Security Benchmark 3.1 | Identity and Access Control | Maintain an inventory of administrative accounts | Customer | Microsoft Entra ID has built-in roles that must be explicitly assigned and are queryable. Use the Microsoft Entra PowerShell module to perform ad hoc queries to discover accounts that are members of administrative groups. How to get a directory role in Microsoft Entra ID with PowerShell: https://docs.microsoft.com/powershell/module/azuread/get-azureaddirectoryrole?view=azureadps-2.0 How to get members of a directory role in Microsoft Entra ID with PowerShell: https://docs.microsoft.com/powershell/module/azuread/get-azureaddirectoryrolemember?view=azureadps-2.0 | n/a | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 3.10 | Azure_Security_Benchmark_v1.0_3.10 | Azure Security Benchmark 3.10 | Identity and Access Control | Regularly review and reconcile user access | Customer | Microsoft Entra ID provides logs to help discover stale accounts. In addition, use Azure Identity Access Reviews to efficiently manage group memberships, access to enterprise applications, and role assignments. User access can be reviewed on a regular basis to make sure only the right Users have continued access. Understand Microsoft Entra reporting: https://docs.microsoft.com/azure/active-directory/reports-monitoring/ How to use Azure Identity Access Reviews: https://docs.microsoft.com/azure/active-directory/governance/access-reviews-overview | n/a | link | count: 005 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 3.3 | Azure_Security_Benchmark_v1.0_3.3 | Azure Security Benchmark 3.3 | Identity and Access Control | Use dedicated administrative accounts | Customer | Create standard operating procedures around the use of dedicated administrative accounts. Use Azure Security Center Identity and Access Management to monitor the number of administrative accounts. You can also enable a Just-In-Time / Just-Enough-Access by using Microsoft Entra Privileged Identity Management Privileged Roles for Microsoft Services, and Azure Resource Manager. Learn more: https://docs.microsoft.com/azure/active-directory/privileged-identity-management/ | n/a | link | count: 005 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7), Audit Windows machines that have extra accounts in the Administrators group (3d2a3320-2a72-4c67-ac5f-caa40fbee2b2), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 3.5 | Azure_Security_Benchmark_v1.0_3.5 | Azure Security Benchmark 3.5 | Identity and Access Control | Use multi-factor authentication for all Microsoft Entra ID based access | Customer | Enable Microsoft Entra MFA and follow Azure Security Center Identity and Access Management recommendations. How to enable MFA in Azure: https://docs.microsoft.com/azure/active-directory/authentication/howto-mfa-getstarted How to monitor identity and access within Azure Security Center: https://docs.microsoft.com/azure/security-center/security-center-identity-access | n/a | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 3.9 | Azure_Security_Benchmark_v1.0_3.9 | Azure Security Benchmark 3.9 | Identity and Access Control | Use Microsoft Entra ID | Customer | Use Microsoft Entra ID as the central authentication and authorization system. Microsoft Entra ID protects data by using strong encryption for data at rest and in transit. Microsoft Entra ID also salts, hashes, and securely stores user credentials. How to create and configure a Microsoft Entra instance: https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-access-create-new-tenant | n/a | link | count: 002 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
Service Fabric, SQL | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 4.4 | Azure_Security_Benchmark_v1.0_4.4 | Azure Security Benchmark 4.4 | Data Protection | Encrypt all sensitive information in transit | Shared | Encrypt all sensitive information in transit. Ensure that any clients connecting to your Azure resources are able to negotiate TLS 1.2 or greater. Follow Azure Security Center recommendations for encryption at rest and encryption in transit, where applicable. Understand encryption in transit with Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-overview#encryption-of-data-in-transit | n/a | link | count: 010 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
App Service, Cache, SQL, Storage | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 4.5 | Azure_Security_Benchmark_v1.0_4.5 | Azure Security Benchmark 4.5 | Data Protection | Use an active discovery tool to identify sensitive data | Customer | When no feature is available for your specific service in Azure, use a third-party active discovery tool to identify all sensitive information stored, processed, or transmitted by the organization's technology systems, including those located on-site, or at a remote service provider, and update the organization's sensitive information inventory. Use Azure Information Protection for identifying sensitive information within Office 365 documents. Use Azure SQL Information Protection to assist in the classification and labeling of information stored in Azure SQL Databases. How to implement Azure SQL Data Discovery: https://docs.microsoft.com/azure/sql-database/sql-database-data-discovery-and-classification How to implement Azure Information Protection: https://docs.microsoft.com/azure/information-protection/deployment-roadmap | n/a | link | count: 002 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
SQL | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 4.6 | Azure_Security_Benchmark_v1.0_4.6 | Azure Security Benchmark 4.6 | Data Protection | Use Azure RBAC to control access to resources | Customer | Use Microsoft Entra RBAC to control access to data and resources, otherwise use service specific access control methods. How to configure RBAC in Azure: https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal | n/a | link | count: 002 Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
General, Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 4.8 | Azure_Security_Benchmark_v1.0_4.8 | Azure Security Benchmark 4.8 | Data Protection | Encrypt sensitive information at rest | Customer | Use encryption at rest on all Azure resources. Microsoft recommends allowing Azure to manage your encryption keys, however there is the option for you to manage your own keys in some instances. Understand encryption at rest in Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-atrest How to configure customer managed encryption keys: https://docs.microsoft.com/azure/storage/common/storage-encryption-keys-portal | n/a | link | count: 007 [Deprecated]: Unattached disks should be encrypted (2c89a2e5-7285-40fe-afe0-ae8654b92fb2), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Automation, Compute, Security Center, Service Fabric, SQL | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 4.9 | Azure_Security_Benchmark_v1.0_4.9 | Azure Security Benchmark 4.9 | Data Protection | Log and alert on changes to critical Azure resources | Customer | Use Azure Monitor with the Azure Activity Log to create alerts for when changes take place to critical Azure resources. How to create alerts for Azure Activity Log events: https://docs.microsoft.com/azure/azure-monitor/platform/alerts-activity-log | n/a | link | count: 001 Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9) |
Monitoring | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 5.1 | Azure_Security_Benchmark_v1.0_5.1 | Azure Security Benchmark 5.1 | Vulnerability Management | Run automated vulnerability scanning tools | Customer | Follow recommendations from Azure Security Center on performing vulnerability assessments on your Azure virtual machines, container images, and SQL servers. Use a third-party solution for performing vulnerability assessments on network devices and web applications. When conducting remote scans, do not use a single, perpetual, administrative account. Consider implementing JIT provisioning methodology for the scan account. Credentials for the scan account should be protected, monitored, and used only for vulnerability scanning. How to implement Azure Security Center vulnerability assessment recommendations: https://docs.microsoft.com/azure/security-center/security-center-vulnerability-assessment-recommendations | n/a | link | count: 003 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 5.2 | Azure_Security_Benchmark_v1.0_5.2 | Azure Security Benchmark 5.2 | Vulnerability Management | Deploy automated operating system patch management solution | Customer | Use Azure "Update Management" to ensure the most recent security updates are installed on your Windows and Linux VMs. For Windows VMs, ensure Windows Update has been enabled and set to update automatically. How to configure Update Management for virtual machines in Azure: https://docs.microsoft.com/azure/automation/automation-update-management Understand Azure security policies monitored by Security Center: https://docs.microsoft.com/azure/security-center/security-center-policy-definitions | n/a | link | count: 002 System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 5.3 | Azure_Security_Benchmark_v1.0_5.3 | Azure Security Benchmark 5.3 | Vulnerability Management | Deploy automated third-party software patch management solution | Customer | Use a third-party patch management solution. Customers already leveraging System Center Configuration Manager in their environment may leverage System Center Updates Publisher, allowing them to publish custom updates into Windows Server Update Service. This allows Update Manager to patch machines that use System Center Configuration Manager as their update repository with third-party software. | n/a | link | count: 001 Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 5.5 | Azure_Security_Benchmark_v1.0_5.5 | Azure Security Benchmark 5.5 | Vulnerability Management | Use a risk-rating process to prioritize the remediation of discovered vulnerabilities | Customer | Use a common risk scoring program (for example, Common Vulnerability Scoring System) or the default risk ratings provided by your third-party scanning tool. | n/a | link | count: 004 SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 6.10 | Azure_Security_Benchmark_v1.0_6.10 | Azure Security Benchmark 6.10 | Inventory and Asset Management | Implement approved application list | Customer | Use Azure Security Center Adaptive Application Controls to specify which file types a rule may or may not apply to. Implement third party solution if this does not meet the requirement. How to use Azure Security Center Adaptive Application Controls: https://docs.microsoft.com/azure/security-center/security-center-adaptive-application | n/a | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 6.8 | Azure_Security_Benchmark_v1.0_6.8 | Azure Security Benchmark 6.8 | Inventory and Asset Management | Use only approved applications | Customer | Use Azure Security Center Adaptive Application Controls to ensure that only authorized software executes and all unauthorized software is blocked from executing on Azure Virtual Machines. How to use Azure Security Center Adaptive Application Controls: https://docs.microsoft.com/azure/security-center/security-center-adaptive-application | n/a | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 6.9 | Azure_Security_Benchmark_v1.0_6.9 | Azure Security Benchmark 6.9 | Inventory and Asset Management | Use only approved Azure services | Customer | Use Azure Policy to restrict which services you can provision in your environment. How to configure and manage Azure Policy: https://docs.microsoft.com/azure/governance/policy/tutorials/create-and-manage How to deny a specific resource type with Azure Policy: https://docs.microsoft.com/azure/governance/policy/samples/not-allowed-resource-types | n/a | link | count: 002 Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Storage | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 7.10 | Azure_Security_Benchmark_v1.0_7.10 | Azure Security Benchmark 7.10 | Secure Configuration | Implement automated configuration monitoring for operating systems | Customer | Use Azure Security Center to perform baseline scans for OS and Docker Settings for containers. Understand Azure Security Center container recommendations: https://docs.microsoft.com/azure/security-center/security-center-container-recommendations | n/a | link | count: 003 Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 7.11 | Azure_Security_Benchmark_v1.0_7.11 | Azure Security Benchmark 7.11 | Secure Configuration | Manage Azure secrets securely | Customer | Use Managed Service Identity in conjunction with Azure Key Vault to simplify and secure secret management for your cloud applications. How to integrate with Azure Managed Identities: https://docs.microsoft.com/azure/azure-app-configuration/howto-integrate-azure-managed-service-identity How to create a Key Vault: https://docs.microsoft.com/azure/key-vault/quick-create-portal How to provide Key Vault authentication with a managed identity: https://docs.microsoft.com/azure/key-vault/managed-identity | n/a | link | count: 001 Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53) |
Key Vault | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 7.12 | Azure_Security_Benchmark_v1.0_7.12 | Azure Security Benchmark 7.12 | Secure Configuration | Manage identities securely and automatically | Customer | Use Managed Identities to provide Azure services with an automatically managed identity in Microsoft Entra ID. Managed Identities allows you to authenticate to any service that supports Microsoft Entra authentication, including Key Vault, without any credentials in your code. How to configure Managed Identities: https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm | n/a | link | count: 002 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f) |
App Service | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 7.4 | Azure_Security_Benchmark_v1.0_7.4 | Azure Security Benchmark 7.4 | Secure Configuration | Maintain secure operating system configurations | Shared | Base operating system images are managed and maintained by Microsoft. However, you can apply security settings required by your organization using AzureResources Manager templates and/or Desired State Configuration. How to create an Azure Virtual Machine from an AzureResources Manager template: https://docs.microsoft.com/azure/virtual-machines/windows/ps-template Understand Desired State Configuration for Azure Virtual Machines: https://docs.microsoft.com/azure/virtual-machines/extensions/dsc-overview | n/a | link | count: 003 Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 8.1 | Azure_Security_Benchmark_v1.0_8.1 | Azure Security Benchmark 8.1 | Malware Defense | Use centrally managed anti-malware software | Customer | Use Microsoft Antimalware for Azure Cloud Services and Virtual Machines to continuously monitor and defend your resources. For Linux, use third party antimalware solution. How to configure Microsoft Antimalware for Cloud Services and Virtual Machines: https://docs.microsoft.com/azure/security/fundamentals/antimalware | n/a | link | count: 002 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Security Center | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 8.3 | Azure_Security_Benchmark_v1.0_8.3 | Azure Security Benchmark 8.3 | Malware Defense | Ensure anti-malware software and signatures are updated | Customer | Microsoft Antimalware will automatically install the latest signatures and engine updates by default. Follow recommendations in Azure Security Center: "Compute & Apps" to ensure all endpoints are up to date with the latest signatures. For Linux, use third party antimalware solution. How to deploy Microsoft Antimalware for Azure Cloud Services and Virtual Machines: https://docs.microsoft.com/azure/security/fundamentals/antimalware | n/a | link | count: 001 Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57) |
Compute | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 9.1 | Azure_Security_Benchmark_v1.0_9.1 | Azure Security Benchmark 9.1 | Data Recovery | Ensure regular automated back ups | Customer | Enable Azure Backup and configure the backup source (Azure VMs, SQL Server, or File Shares), as well as the desired frequency and retention period. How to enable Azure Backup: https://docs.microsoft.com/azure/backup/ | n/a | link | count: 005 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Backup, SQL | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 9.2 | Azure_Security_Benchmark_v1.0_9.2 | Azure Security Benchmark 9.2 | Data Recovery | Perform complete system backups and backup any customer managed keys | Customer | Enable Azure Backup and target VM(s), as well as the desired frequency and retention periods. Backup customer managed keys within Azure Key Vault. How to enable Azure Backup: https://docs.microsoft.com/azure/backup/ How to backup key vault keys in Azure: https://docs.microsoft.com/powershell/module/azurerm.keyvault/backup-azurekeyvaultkey?view=azurermps-6.13.0 | n/a | link | count: 005 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Backup, SQL | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v1.0 | 9.4 | Azure_Security_Benchmark_v1.0_9.4 | Azure Security Benchmark 9.4 | Data Recovery | Ensure protection of backups and customer managed keys | Customer | For on-premises backup, encryption-at-rest is provided using the passphrase you provide when backing up to Azure. For Azure VMs, data is encrypted-at-rest using Storage Service Encryption (SSE). You may enable Soft-Delete in Key Vault to protect keys against accidental or malicious deletion. How to enable Soft-Delete in Key Vault: https://docs.microsoft.com/azure/storage/blobs/storage-blob-soft-delete?tabs=azure-portal | n/a | link | count: 001 Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53) |
Key Vault | [Deprecated]: Azure Security Benchmark v1 (42a694ed-f65e-42b2-aa9e-8052e9740a92) |
| Azure_Security_Benchmark_v2.0 | AM-3 | Azure_Security_Benchmark_v2.0_AM-3 | Azure Security Benchmark AM-3 | Asset Management | Use only approved Azure services | Customer | Use Azure Policy to audit and restrict which services users can provision in your environment. Use Azure Resource Graph to query for and discover resources within their subscriptions. You can also use Azure Monitor to create rules to trigger alerts when a non-approved service is detected. Configure and manage Azure Policy: https://docs.microsoft.com/azure/governance/policy/tutorials/create-and-manage How to deny a specific resource type with Azure Policy: https://docs.microsoft.com/azure/governance/policy/samples/not-allowed-resource-types How to create queries with Azure Resource Graph Explorer: https://docs.microsoft.com/azure/governance/resource-graph/first-query-portal | n/a | link | count: 002 Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Storage | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | AM-6 | Azure_Security_Benchmark_v2.0_AM-6 | Azure Security Benchmark AM-6 | Asset Management | Use only approved applications in compute resources | Customer | Ensure that only authorized software executes, and all unauthorized software is blocked from executing on Azure Virtual Machines. Use Azure Security Center (ASC) adaptive application controls to discover and generate an application allow list. You can also use ASC adaptive application controls to ensure that only authorized software executes and all unauthorized software is blocked from executing on Azure Virtual Machines. Use Azure Automation Change Tracking and Inventory to automate the collection of inventory information from your Windows and Linux VMs. Software name, version, publisher, and refresh time are available from the Azure Portal. To get the software installation date and other information, enable guest-level diagnostics and direct the Windows Event Logs to Log Analytics workspace. Depending on the type of scripts, you can use operating system-specific configurations or third-party resources to limit users' ability to execute scripts in Azure compute resources. You can also use a third-party solution to discover and identify unapproved software. How to use Azure Security Center adaptive application controls: https://docs.microsoft.com/azure/security-center/security-center-adaptive-application Understand Azure Automation Change Tracking and Inventory: https://docs.microsoft.com/azure/automation/change-tracking How to control PowerShell script execution in Windows environments: https://docs.microsoft.com/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-6 | n/a | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | BR-1 | Azure_Security_Benchmark_v2.0_BR-1 | Azure Security Benchmark BR-1 | Backup and Recovery | Ensure regular automated backups | Customer | Ensure you are backing up systems and data to maintain business continuity after an unexpected event. This should be defined by any objectives for Recovery Point Objective (RPO) and Recovery Time Objective (RTO). Enable Azure Backup and configure the backup source (e.g. Azure VMs, SQL Server, HANA databases, or File Shares), as well as the desired frequency and retention period. For a higher level of protection, you can enable geo-redundant storage option to replicate backup data to a secondary region and recover using cross region restore. Enterprise-scale business continuity and disaster recovery: https://docs.microsoft.com/azure/cloud-adoption-framework/ready/enterprise-scale/business-continuity-and-disaster-recovery How to enable Azure Backup: https://docs.microsoft.com/azure/backup/ How to enable cross region restore: https://docs.microsoft.com/azure/backup/backup-azure-arm-restore-vms#cross-region-restore | n/a | link | count: 005 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Backup, SQL | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | BR-2 | Azure_Security_Benchmark_v2.0_BR-2 | Azure Security Benchmark BR-2 | Backup and Recovery | Encrypt backup data | Customer | Ensure your backups are protected against attacks. This should include encryption of the backups to protect against loss of confidentiality. For on-premises backups using Azure Backup, encryption-at-rest is provided using the passphrase you provide. For regular Azure service backups, backup data is automatically encrypted using Azure platform-managed keys. You can choose to encrypt the backups using customer managed key. In this case, ensure this customer-managed key in the key vault is also in the backup scope. Use role-based access control in Azure Backup, Azure Key Vault, or other resources to protect backups and customer managed keys. Additionally, you can enable advanced security features to require MFA before backups can be altered or deleted. Overview of security features in Azure Backup: https://docs.microsoft.com/azure/backup/security-overview Encryption of backup data using customer-managed keys: https://docs.microsoft.com/azure/backup/encryption-at-rest-with-cmk How to backup Key Vault keys in Azure: https://docs.microsoft.com/powershell/module/azurerm.keyvault/backup-azurekeyvaultkey?view=azurermps-6.13.0 Security features to help protect hybrid backups from attacks: https://docs.microsoft.com/azure/backup/backup-azure-security-feature#prevent-attacks | n/a | link | count: 005 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Backup, SQL | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | BR-4 | Azure_Security_Benchmark_v2.0_BR-4 | Azure Security Benchmark BR-4 | Backup and Recovery | Mitigate risk of lost keys | Customer | Ensure you have measures in place to prevent and recover from loss of keys. Enable soft delete and purge protection in Azure Key Vault to protect keys against accidental or malicious deletion. How to enable soft delete and purge protection in Key Vault: https://docs.microsoft.com/azure/storage/blobs/storage-blob-soft-delete?tabs=azure-portal | n/a | link | count: 002 Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Key Vault | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | DP-2 | Azure_Security_Benchmark_v2.0_DP-2 | Azure Security Benchmark DP-2 | Data Protection | Protect sensitive data | Shared | Protect sensitive data by restricting access using Azure Role Based Access Control (Azure RBAC), network-based access controls, and specific controls in Azure services (such as encryption in SQL and other databases). To ensure consistent access control, all types of access control should be aligned to your enterprise segmentation strategy. The enterprise segmentation strategy should also be informed by the location of sensitive or business critical data and systems. For the underlying platform, which is managed by Microsoft, Microsoft treats all customer content as sensitive and guards against customer data loss and exposure. To ensure customer data within Azure remains secure, Microsoft has implemented some default data protection controls and capabilities. Azure Role Based Access Control (RBAC): https://docs.microsoft.com/azure/role-based-access-control/overview Understand customer data protection in Azure: https://docs.microsoft.com/azure/security/fundamentals/protection-customer-data | n/a | link | count: 006 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Security Center, SQL, Storage | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | DP-3 | Azure_Security_Benchmark_v2.0_DP-3 | Azure Security Benchmark DP-3 | Data Protection | Monitor for unauthorized transfer of sensitive data | Shared | Monitor for unauthorized transfer of data to locations outside of enterprise visibility and control. This typically involves monitoring for anomalous activities (large or unusual transfers) that could indicate unauthorized data exfiltration. Azure Storage Advanced Threat Protection (ATP) and Azure SQL ATP can alert on anomalous transfer of information that might indicate unauthorized transfers of sensitive information. Azure Information protection (AIP) provides monitoring capabilities for information that has been classified and labelled. If required for compliance of data loss prevention (DLP), you can use a host-based DLP solution to enforce detective and/or preventative controls to prevent data exfiltration. Enable Azure SQL ATP: https://docs.microsoft.com/azure/azure-sql/database/threat-detection-overview Enable Azure Storage ATP: https://docs.microsoft.com/azure/storage/common/storage-advanced-threat-protection?tabs=azure-security-center | n/a | link | count: 003 Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
Security Center, SQL | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | DP-4 | Azure_Security_Benchmark_v2.0_DP-4 | Azure Security Benchmark DP-4 | Data Protection | Encrypt sensitive information in transit | Shared | To complement access controls, data in transit should be protected against ‘out of band’ attacks (e.g. traffic capture) using encryption to ensure that attackers cannot easily read or modify the data. While this is optional for traffic on private networks, this is critical for traffic on external and public networks. For HTTP traffic, ensure that any clients connecting to your Azure resources can negotiate TLS v1.2 or greater. For remote management, use SSH (for Linux) or RDP/TLS (for Windows) instead of an unencrypted protocol. Obsoleted SSL, TLS, and SSH versions and protocols, and weak ciphers should be disabled. By default, Azure provides encryption for data in transit between Azure data centers. Understand encryption in transit with Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-overview#encryption-of-data-in-transit Information on TLS Security: https://docs.microsoft.com/security/engineering/solving-tls1-problem Double encryption for Azure data in transit: https://docs.microsoft.com/azure/security/fundamentals/double-encryption#data-in-transit | n/a | link | count: 012 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, Kubernetes, SQL, Storage | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | DP-5 | Azure_Security_Benchmark_v2.0_DP-5 | Azure Security Benchmark DP-5 | Data Protection | Encrypt sensitive data at rest | Shared | To complement access controls, data at rest should be protected against ‘out of band’ attacks (such as accessing underlying storage) using encryption. This helps ensure that attackers cannot easily read or modify the data. Azure provides encryption for data at rest by default. For highly sensitive data, you have options to implement additional encryption at rest on all Azure resources where available. Azure manages your encryption keys by default, but Azure provides options to manage your own keys (customer managed keys) for certain Azure services. Understand encryption at rest in Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-atrest#encryption-at-rest-in-microsoft-cloud-services How to configure customer managed encryption keys: https://docs.microsoft.com/azure/storage/common/storage-encryption-keys-portal Encryption model and key management table: https://docs.microsoft.com/azure/security/fundamentals/encryption-models Data at rest double encryption in Azure: https://docs.microsoft.com/azure/security/fundamentals/double-encryption#data-at-rest | n/a | link | count: 013 Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Automation, Cognitive Services, Container Registry, Cosmos DB, Machine Learning, Security Center, Service Fabric, SQL, Storage | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | ES-1 | Azure_Security_Benchmark_v2.0_ES-1 | Azure Security Benchmark ES-1 | Endpoint Security | Use Endpoint Detection and Response (EDR) | Customer | Enable Endpoint Detection and Response (EDR) capabilities for servers and clients and integrate with SIEM and Security Operations processes. Microsoft Defender Advanced Threat Protection provides EDR capability as part of an enterprise endpoint security platform to prevent, detect, investigate, and respond to advanced threats. Microsoft Defender Advanced Threat Protection Overview: https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-advanced-threat-protection Microsoft Defender ATP service for Windows servers: https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-server-endpoints Microsoft Defender ATP service for non-Windows servers: https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-non-windows | n/a | link | count: 001 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | ES-2 | Azure_Security_Benchmark_v2.0_ES-2 | Azure Security Benchmark ES-2 | Endpoint Security | Use centrally managed modern anti-malware software | Customer | Use a centrally managed endpoint anti-malware solution capable of real time and periodic scanning Azure Security Center can automatically identify the use of a number of popular anti-malware solutions for your virtual machines and report the endpoint protection running status and make recommendations. Microsoft Antimalware for Azure Cloud Services is the default anti-malware for Windows virtual machines (VMs). For Linux VMs, use third-party antimalware solution. Also, you can use Azure Security Center's Threat detection for data services to detect malware uploaded to Azure Storage accounts. How to configure Microsoft Antimalware for Cloud Services and Virtual Machines: https://docs.microsoft.com/azure/security/fundamentals/antimalware Supported endpoint protection solutions: https://docs.microsoft.com/azure/security-center/security-center-services?tabs=features-windows#supported-endpoint-protection-solutions- | n/a | link | count: 003 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | ES-3 | Azure_Security_Benchmark_v2.0_ES-3 | Azure Security Benchmark ES-3 | Endpoint Security | Ensure anti-malware software and signatures are updated | Customer | Ensure anti-malware signatures are updated rapidly and consistently. Follow recommendations in Azure Security Center: "Compute & Apps" to ensure all endpoints are up to date with the latest signatures. Microsoft Antimalware will automatically install the latest signatures and engine updates by default. For Linux, use third-party antimalware solution. How to deploy Microsoft Antimalware for Azure Cloud Services and Virtual Machines: https://docs.microsoft.com/azure/security/fundamentals/antimalware Endpoint protection assessment and recommendations in Azure Security Center:https://docs.microsoft.com/azure/security-center/security-center-endpoint-protection | n/a | link | count: 002 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | IM-1 | Azure_Security_Benchmark_v2.0_IM-1 | Azure Security Benchmark IM-1 | Identity Management | Standardize Microsoft Entra ID as the central identity and authentication system | Customer | Microsoft Entra ID is Azure's default identity and access management service. You should standardize on Microsoft Entra ID to govern your organization’s identity and access management in: - Microsoft cloud resources, such as the Azure portal, Azure Storage, Azure Virtual Machines (Linux and Windows), Azure Key Vault, PaaS, and SaaS applications. - Your organization's resources, such as applications on Azure or your corporate network resources. Securing Microsoft Entra ID should be a high priority in your organization’s cloud security practice. Microsoft Entra ID provides an identity secure score to help you assess your identity security posture relative to Microsoft’s best practice recommendations. Use the score to gauge how closely your configuration matches best practice recommendations, and to make improvements in your security posture. Note: Microsoft Entra ID supports external identity providers, which allow users without a Microsoft account to sign in to their applications and resources with their external identity. Tenancy in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/develop/single-and-multi-tenant-apps How to create and configure a Microsoft Entra instance: https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-access-create-new-tenant Define Microsoft Entra tenants: https://azure.microsoft.com/resources/securing-azure-environments-with-azure-active-directory/ Use external identity providers for an application: https://docs.microsoft.com/azure/active-directory/b2b/identity-providers What is the identity secure score in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/fundamentals/identity-secure-score | n/a | link | count: 004 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Service Fabric, SQL | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | IM-2 | Azure_Security_Benchmark_v2.0_IM-2 | Azure Security Benchmark IM-2 | Identity Management | Manage application identities securely and automatically | Customer | For non-human accounts such as services or automation, use Azure managed identities, instead of creating a more powerful human account to access resources or execute code. Azure managed identities can authenticate to Azure services and resources that support Microsoft Entra authentication. Authentication is enabled through pre-defined access grant rules, avoiding hard-coded credentials in source code or configuration files. For services that do not support managed identities, use Microsoft Entra ID to create a service principal with restricted permissions at the resource level instead. It is recommended to configure service principals with certificate credentials and fall back to client secrets. In both cases, Azure Key Vault can be used in conjunction with Azure managed identities, so that the runtime environment (such as an Azure function) can retrieve the credential from the key vault. Azure managed identities: https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview Services that support managed identities for Azure resources: https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/services-support-managed-identities Azure service principal: https://docs.microsoft.com/powershell/azure/create-azure-service-principal-azureps Create a service principal with certificates: https://docs.microsoft.com/azure/active-directory/develop/howto-authenticate-service-principal-powershell Use Azure Key Vault for security principal registration: https://docs.microsoft.com/azure/key-vault/general/authentication#security-principal-registration | n/a | link | count: 002 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f) |
App Service | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | IM-4 | Azure_Security_Benchmark_v2.0_IM-4 | Azure Security Benchmark IM-4 | Identity Management | Use strong authentication controls for all Microsoft Entra ID based access | Customer | Microsoft Entra ID supports strong authentication controls through multi-factor authentication (MFA) and strong passwordless methods. - Multi-factor authentication: Enable Microsoft Entra MFA and follow Azure Security Center identity and access management recommendations for your MFA setup. MFA can be enforced on all users, select users, or at the per-user level based on sign-in conditions and risk factors. - Passwordless authentication: Three passwordless authentication options are available: Windows Hello for Business, Microsoft Authenticator app, and on-premises authentication methods such as smart cards. For administrator and privileged users, ensure the highest level of the strong authentication method is used, followed by rolling out the appropriate strong authentication policy to other users. If legacy password-based authentication is still used for Microsoft Entra ID authentication, please be aware that cloud-only accounts (user accounts created directly in Azure) have a default baseline password policy. And hybrid accounts (user accounts that come from on-premises Active Directory) follow the on-premises password policies. When using password-based authentication, Microsoft Entra ID provides a password protection capability that prevents users from setting passwords that are easy to guess. Microsoft provides a global list of banned passwords that is updated based on telemetry, and customers can augment the list based on their needs (e.g. branding, cultural references, etc.). This password protection can be used for cloud-only and hybrid accounts. Note: Authentication based on password credentials alone is susceptible to popular attack methods. For higher security, use strong authentication such as MFA and a strong password policy. For third-party applications and marketplace services that may have default passwords, you should change them during initial service setup. How to enable MFA in Azure: https://docs.microsoft.com/azure/active-directory/authentication/howto-mfa-getstarted Introduction to passwordless authentication options for Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/authentication/concept-authentication-passwordless Microsoft Entra ID default password policy: https://docs.microsoft.com/azure/active-directory/authentication/concept-sspr-policy#password-policies-that-only-apply-to-cloud-user-accounts Eliminate bad passwords using Microsoft Entra Password Protection: https://docs.microsoft.com/azure/active-directory/authentication/concept-password-ban-bad | n/a | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | IR-2 | Azure_Security_Benchmark_v2.0_IR-2 | Azure Security Benchmark IR-2 | Incident Response | Preparation - setup incident notification | Customer | Set up security incident contact information in Azure Security Center. This contact information is used by Microsoft to contact you if the Microsoft Security Response Center (MSRC) discovers that your data has been accessed by an unlawful or unauthorized party. You also have options to customize incident alert and notification in different Azure services based on your incident response needs. How to set the Azure Security Center security contact: https://docs.microsoft.com/azure/security-center/security-center-provide-security-contact-details | n/a | link | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | IR-3 | Azure_Security_Benchmark_v2.0_IR-3 | Azure Security Benchmark IR-3 | Incident Response | Detection and analysis - create incidents based on high quality alerts | Customer | Ensure you have a process to create high quality alerts and measure the quality of alerts. This allows you to learn lessons from past incidents and prioritize alerts for analysts, so they don’t waste time on false positives. High quality alerts can be built based on experience from past incidents, validated community sources, and tools designed to generate and clean up alerts by fusing and correlating diverse signal sources. Azure Security Center provides high quality alerts across many Azure assets. You can use the ASC data connector to stream the alerts to Azure Sentinel. Azure Sentinel lets you create advanced alert rules to generate incidents automatically for an investigation. Export your Azure Security Center alerts and recommendations using the export feature to help identify risks to Azure resources. Export alerts and recommendations either manually or in an ongoing, continuous fashion. How to configure export: https://docs.microsoft.com/azure/security-center/continuous-export How to stream alerts into Azure Sentinel: https://docs.microsoft.com/azure/sentinel/connect-azure-security-center | n/a | link | count: 008 [Deprecated]: Azure Defender for container registries should be enabled (c25d9a16-bc35-4e15-a7e5-9db606bf9ed4), [Deprecated]: Azure Defender for Kubernetes should be enabled (523b5cd1-3e23-492f-a539-13118b6d1e3a), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
Security Center, SQL | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | IR-5 | Azure_Security_Benchmark_v2.0_IR-5 | Azure Security Benchmark IR-5 | Incident Response | Detection and analysis - prioritize incidents | Customer | Provide context to analysts on which incidents to focus on first based on alert severity and asset sensitivity. Azure Security Center assigns a severity to each alert to help you prioritize which alerts should be investigated first. The severity is based on how confident Security Center is in the finding or the analytic used to issue the alert, as well as the confidence level that there was malicious intent behind the activity that led to the alert. Additionally, mark resources using tags and create a naming system to identify and categorize Azure resources, especially those processing sensitive data. It is your responsibility to prioritize the remediation of alerts based on the criticality of the Azure resources and environment where the incident occurred. Security alerts in Azure Security Center: https://docs.microsoft.com/azure/security-center/security-center-alerts-overview Use tags to organize your Azure resources: https://docs.microsoft.com/azure/azure-resource-manager/resource-group-using-tags | n/a | link | count: 008 [Deprecated]: Azure Defender for container registries should be enabled (c25d9a16-bc35-4e15-a7e5-9db606bf9ed4), [Deprecated]: Azure Defender for Kubernetes should be enabled (523b5cd1-3e23-492f-a539-13118b6d1e3a), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
Security Center, SQL | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | LT-1 | Azure_Security_Benchmark_v2.0_LT-1 | Azure Security Benchmark LT-1 | Logging and Threat Detection | Enable threat detection for Azure resources | Customer | Ensure you are monitoring different types of Azure assets for potential threats and anomalies. Focus on getting high quality alerts to reduce false positives for analysts to sort through. Alerts can be sourced from log data, agents, or other data. Use the Azure Security Center built-in threat detection capability, which is based on monitoring Azure service telemetry and analyzing service logs. Data is collected using the Log Analytics agent, which reads various security-related configurations and event logs from the system and copies the data to your workspace for analysis. In addition, use Azure Sentinel to build analytics rules, which hunt threats that match specific criteria across your environment. The rules generate incidents when the criteria are matched, so that you can investigate each incident. Azure Sentinel can also import third party threat intelligence to enhance its threat detection capability. Threat protection in Azure Security Center: https://docs.microsoft.com/azure/security-center/threat-protection Azure Security Center security alerts reference guide: https://docs.microsoft.com/azure/security-center/alerts-reference Create custom analytics rules to detect threats: https://docs.microsoft.com/azure/sentinel/tutorial-detect-threats-custom Cyber threat intelligence with Azure Sentinel: https://docs.microsoft.com/azure/architecture/example-scenario/data/sentinel-threat-intelligence | n/a | link | count: 008 [Deprecated]: Azure Defender for container registries should be enabled (c25d9a16-bc35-4e15-a7e5-9db606bf9ed4), [Deprecated]: Azure Defender for Kubernetes should be enabled (523b5cd1-3e23-492f-a539-13118b6d1e3a), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
Security Center, SQL | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | LT-2 | Azure_Security_Benchmark_v2.0_LT-2 | Azure Security Benchmark LT-2 | Logging and Threat Detection | Enable threat detection for Azure identity and access management | Customer | Microsoft Entra ID provides the following user logs that can be viewed in Microsoft Entra ID reporting or integrated with Azure Monitor, Azure Sentinel or other SIEM/monitoring tools for more sophisticated monitoring and analytics use cases: - Sign-ins - The sign-ins report provides information about the usage of managed applications and user sign-in activities. - Audit logs - Provides traceability through logs for all changes done by various features within Microsoft Entra ID. Examples of audit logs include changes made to any resources within Microsoft Entra ID like adding or removing users, apps, groups, roles and policies. - Risky sign-ins - A risky sign-in is an indicator for a sign-in attempt that might have been performed by someone who is not the legitimate owner of a user account. - Users flagged for risk - A risky user is an indicator for a user account that might have been compromised. Azure Security Center can also alert on certain suspicious activities such as an excessive number of failed authentication attempts, and deprecated accounts in the subscription. In addition to the basic security hygiene monitoring, Azure Security Center’s Threat Protection module can also collect more in-depth security alerts from individual Azure compute resources (such as virtual machines, containers, app service), data resources (such as SQL DB and storage), and Azure service layers. This capability allows you to see account anomalies inside the individual resources. Audit activity reports in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/reports-monitoring/concept-audit-logs Enable Azure Identity Protection: https://docs.microsoft.com/azure/active-directory/identity-protection/overview-identity-protection Threat protection in Azure Security Center: https://docs.microsoft.com/azure/security-center/threat-protection | n/a | link | count: 008 [Deprecated]: Azure Defender for container registries should be enabled (c25d9a16-bc35-4e15-a7e5-9db606bf9ed4), [Deprecated]: Azure Defender for Kubernetes should be enabled (523b5cd1-3e23-492f-a539-13118b6d1e3a), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
Security Center, SQL | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | LT-3 | Azure_Security_Benchmark_v2.0_LT-3 | Azure Security Benchmark LT-3 | Logging and Threat Detection | Enable logging for Azure network activities | Customer | Enable and collect network security group (NSG) resource logs, NSG flow logs, Azure Firewall logs, and Web Application Firewall (WAF) logs for security analysis to support incident investigations, threat hunting, and security alert generation. You can send the flow logs to an Azure Monitor Log Analytics workspace and then use Traffic Analytics to provide insights. Ensure you are collecting DNS query logs to assist in correlating other network data. How to enable network security group flow logs: https://docs.microsoft.com/azure/network-watcher/network-watcher-nsg-flow-logging-portal Azure Firewall logs and metrics: https://docs.microsoft.com/azure/firewall/logs-and-metrics How to enable and use Traffic Analytics: https://docs.microsoft.com/azure/network-watcher/traffic-analytics Monitoring with Network Watcher: https://docs.microsoft.com/azure/network-watcher/network-watcher-monitoring-overview Azure networking monitoring solutions in Azure Monitor: https://docs.microsoft.com/azure/azure-monitor/insights/azure-networking-analytics Gather insights about your DNS infrastructure with the DNS Analytics solution: https://docs.microsoft.com/azure/azure-monitor/insights/dns-analytics | n/a | link | count: 003 [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6) |
Monitoring, Network | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | LT-4 | Azure_Security_Benchmark_v2.0_LT-4 | Azure Security Benchmark LT-4 | Logging and Threat Detection | Enable logging for Azure resources | Shared | Enable logging for Azure resources to meet the requirements for compliance, threat detection, hunting, and incident investigation. You can use Azure Security Center and Azure Policy to enable resource logs and log data collecting on Azure resources for access to audit, security, and resource logs. Activity logs, which are automatically available, include event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. Understand logging and different log types in Azure: https://docs.microsoft.com/azure/azure-monitor/platform/platform-logs-overview Understand Azure Security Center data collection: https://docs.microsoft.com/azure/security-center/security-center-enable-data-collection Enable and configure antimalware monitoring: https://docs.microsoft.com/azure/security/fundamentals/antimalware#enable-and-configure-antimalware-monitoring-using-powershell-cmdlets | n/a | link | count: 013 [Deprecated]: Resource logs in Virtual Machine Scale Sets should be enabled (7c1b1214-f927-48bf-8882-84f0af6588b1), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45) |
App Service, Batch, Compute, Data Lake, Event Hub, Internet of Things, Key Vault, Logic Apps, Search, Service Bus, SQL, Stream Analytics | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | LT-5 | Azure_Security_Benchmark_v2.0_LT-5 | Azure Security Benchmark LT-5 | Logging and Threat Detection | Centralize security log management and analysis | Customer | Centralize logging storage and analysis to enable correlation. For each log source, ensure you have assigned a data owner, access guidance, storage location, what tools are used to process and access the data, and data retention requirements. Ensure you are integrating Azure activity logs into your central logging. Ingest logs via Azure Monitor to aggregate security data generated by endpoint devices, network resources, and other security systems. In Azure Monitor, use Log Analytics workspaces to query and perform analytics, and use Azure Storage accounts for long term and archival storage. In addition, enable and onboard data to Azure Sentinel or a third-party SIEM. Many organizations choose to use Azure Sentinel for “hot” data that is used frequently and Azure Storage for “cold” data that is used less frequently. How to collect platform logs and metrics with Azure Monitor: https://docs.microsoft.com/azure/azure-monitor/platform/diagnostic-settings How to onboard Azure Sentinel: https://docs.microsoft.com/azure/sentinel/quickstart-onboard | n/a | link | count: 005 [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b) |
Monitoring, Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | NS-1 | Azure_Security_Benchmark_v2.0_NS-1 | Azure Security Benchmark NS-1 | Network Security | Implement security for internal traffic | Customer | Ensure that all Azure virtual networks follow an enterprise segmentation principle that aligns to the business risks. Any system that could incur higher risk for the organization should be isolated within its own virtual network and sufficiently secured with either a network security group (NSG) and/or Azure Firewall. Based on your applications and enterprise segmentation strategy, restrict or allow traffic between internal resources based on network security group rules. For specific well-defined applications (such as a 3-tier app), this can be a highly secure "deny by default, permit by exception" approach. This might not scale well if you have many applications and endpoints interacting with each other. You can also use Azure Firewall in circumstances where central management is required over a large number of enterprise segments or spokes (in a hub/spoke topology). Use Azure Security Center Adaptive Network Hardening to recommend network security group configurations that limit ports and source IPs based with the reference to external network traffic rules. Use Azure Sentinel to discover the use of legacy insecure protocols such as SSL/TLSv1, SMBv1, LM/NTLMv1, wDigest, Unsigned LDAP Binds, and weak ciphers in Kerberos. How to create a network security group with security rules: https://docs.microsoft.com/azure/virtual-network/tutorial-filter-network-traffic How to deploy and configure Azure Firewall: https://docs.microsoft.com/azure/firewall/tutorial-firewall-deploy-portal Adaptive Network Hardening in Azure Security Center: https://docs.microsoft.com/azure/security-center/security-center-adaptive-network-hardening Azure Sentinel insecure protocols workbook:https://docs.microsoft.com/azure/sentinel/quickstart-get-visibility#use-built-in-workbooks | n/a | link | count: 019 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517) |
API Management, Azure Ai Services, Container Registry, Cosmos DB, Key Vault, Network, Security Center, SQL, Storage | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | NS-2 | Azure_Security_Benchmark_v2.0_NS-2 | Azure Security Benchmark NS-2 | Network Security | Connect private networks together | Customer | Use Azure ExpressRoute or Azure virtual private network (VPN) to create private connections between Azure datacenters and on-premises infrastructure in a colocation environment. ExpressRoute connections do not go over the public internet , and they offer more reliability, faster speeds, and lower latencies than typical internet connections. For point-to-site VPN and site-to-site VPN, you can connect on-premises devices or networks to a virtual network using any combination of these VPN options and Azure ExpressRoute. To connect two or more virtual networks in Azure together, use virtual network peering or Private Link. Network traffic between peered virtual networks is private and is kept on the Azure backbone network. What are the ExpressRoute connectivity models: https://docs.microsoft.com/azure/expressroute/expressroute-connectivity-models Azure VPN overview: https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpngateways Virtual network peering: https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview Azure Private Link: https://docs.microsoft.com/azure/private-link/private-link-service-overview | n/a | link | count: 015 [Deprecated]: Azure Cache for Redis should reside within a virtual network (7d092e0a-7acd-40d2-a975-dca21cae48c4), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
App Configuration, App Platform, Cache, Container Registry, Event Grid, Key Vault, Machine Learning, SignalR, SQL, Storage, VM Image Builder | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | NS-3 | Azure_Security_Benchmark_v2.0_NS-3 | Azure Security Benchmark NS-3 | Network Security | Establish private network access to Azure services | Customer | Use Azure Private Link to enable private access to Azure services from your virtual networks, without crossing the internet. In situations where Azure Private Link is not yet available, use Azure Virtual Network service endpoints. Azure Virtual Network service endpoints provide secure access to services via an optimized route over the Azure backbone network. Private access is an additional defense in depth measure in addition to authentication and traffic security offered by Azure services. Understand Azure Private Link: https://docs.microsoft.com/azure/private-link/private-link-overview Understand Virtual Network service endpoints: https://docs.microsoft.com/azure/virtual-network/virtual-network-service-endpoints-overview | n/a | link | count: 013 App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
App Configuration, Container Registry, Event Grid, Key Vault, Machine Learning, SignalR, SQL, Storage, VM Image Builder | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | NS-4 | Azure_Security_Benchmark_v2.0_NS-4 | Azure Security Benchmark NS-4 | Network Security | Protect applications and services from external network attacks | Customer | Protect Azure resources against attacks from external networks, including distributed denial of service (DDoS) Attacks, application specific attacks, and unsolicited and potentially malicious internet traffic. Azure includes native capabilities for this: - Use Azure Firewall to protect applications and services against potentially malicious traffic from the internet and other external locations. - Use Web Application Firewall (WAF) capabilities in Azure Application Gateway, Azure Front Door, and Azure Content Delivery Network (CDN) to protect your applications, services, and APIs against application layer attacks. - Protect your assets against DDoS attacks by enabling DDoS protection on your Azure virtual networks. - Use Azure Security Center to detect misconfiguration risks related to the above. Azure Firewall Documentation: https://docs.microsoft.com/azure/firewall/ How to deploy Azure WAF: https://docs.microsoft.com/azure/web-application-firewall/overview Manage Azure DDoS Protection using the Azure portal: https://docs.microsoft.com/azure/virtual-network/manage-ddos-protection | n/a | link | count: 015 [Deprecated]: RDP access from the Internet should be blocked (e372f825-a257-4fb8-9175-797a8a8627d6), [Deprecated]: SSH access from the Internet should be blocked (2c89a2e5-7285-40fe-afe0-ae8654b92fab), [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Cosmos DB, Key Vault, Network, Security Center, Storage | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | NS-5 | Azure_Security_Benchmark_v2.0_NS-5 | Azure Security Benchmark NS-5 | Network Security | Deploy intrusion detection/intrusion prevention systems (IDS/IPS) | Customer | Use Azure Firewall threat intelligence-based filtering to alert on and/or block traffic to and from known malicious IP addresses and domains. The IP addresses and domains are sourced from the Microsoft Threat Intelligence feed. When payload inspection is required, you can deploy a third-party intrusion detection/intrusion prevent system (IDS/IPS) from Azure Marketplace with payload inspection capabilities. Alternately you can use host-based IDS/IPS or a host-based endpoint detection and response (EDR) solution in conjunction with or instead of network-based IDS/IPS. Note: If you have a regulatory or other requirement for IDS/IPS use, ensure that it is always tuned to provide high quality alerts to your SIEM solution. How to deploy Azure Firewall: https://docs.microsoft.com/azure/firewall/tutorial-firewall-deploy-portal Azure Marketplace includes third party IDS capabilities: https://azuremarketplace.microsoft.com/marketplace?search=IDS Microsoft Defender ATP EDR capability: https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/overview-endpoint-detection-response | n/a | link | count: 001 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c) |
Network | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | PA-1 | Azure_Security_Benchmark_v2.0_PA-1 | Azure Security Benchmark PA-1 | Privileged Access | Protect and limit highly privileged users | Customer | Limit the number of highly privileged user accounts, and protect these accounts at an elevated level. The most critical built-in roles in Microsoft Entra ID are Global Administrator and the Privileged Role Administrator, because users assigned to these two roles can delegate administrator roles. With these privileges, users can directly or indirectly read and modify every resource in your Azure environment: - Global Administrator / Company Administrator: Users with this role have access to all administrative features in Microsoft Entra ID, as well as services that use Microsoft Entra identities. - Privileged Role Administrator: Users with this role can manage role assignments in Microsoft Entra ID, as well as within Microsoft Entra Privileged Identity Management (PIM). In addition, this role allows management of all aspects of PIM and administrative units. Note: You may have other critical roles that need to be governed if you use custom roles with certain privileged permissions assigned. And you may also want to apply similar controls to the administrator account of critical business assets. You can enable just-in-time (JIT) privileged access to Azure resources and Microsoft Entra ID using Microsoft Entra Privileged Identity Management (PIM). JIT grants temporary permissions to perform privileged tasks only when users need it. PIM can also generate security alerts when there is suspicious or unsafe activity in your Microsoft Entra organization. Administrator role permissions in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles Use Azure Privileged Identity Management security alerts: https://docs.microsoft.com/azure/active-directory/privileged-identity-management/pim-how-to-configure-security-alerts Securing privileged access for hybrid and cloud deployments in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-admin-roles-secure | n/a | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | PA-3 | Azure_Security_Benchmark_v2.0_PA-3 | Azure Security Benchmark PA-3 | Privileged Access | Review and reconcile user access regularly | Customer | Review user accounts and access assignment regularly to ensure the accounts and their level of access are valid. You can use Microsoft Entra access reviews to review group memberships, access to enterprise applications, and role assignments. Microsoft Entra reporting can provide logs to help discover stale accounts. You can also use Microsoft Entra Privileged Identity Management to create an access review report workflow that facilitates the review process. In addition, Azure Privileged Identity Management can be configured to alert when an excessive number of administrator accounts are created, and to identify administrator accounts that are stale or improperly configured. Note: Some Azure services support local users and roles that aren't managed through Microsoft Entra ID. You must manage these users separately. Create an access review of Azure resource roles in Privileged Identity Management(PIM): https://docs.microsoft.com/azure/active-directory/privileged-identity-management/pim-resource-roles-start-access-review How to use Microsoft Entra identity and access reviews: https://docs.microsoft.com/azure/active-directory/governance/access-reviews-overview | n/a | link | count: 005 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | PA-7 | Azure_Security_Benchmark_v2.0_PA-7 | Azure Security Benchmark PA-7 | Privileged Access | Follow just enough administration (least privilege principle) | Customer | Azure role-based access control (Azure RBAC) allows you to manage Azure resource access through role assignments. You can assign these roles to users, group service principals, and managed identities. There are pre-defined built-in roles for certain resources, and these roles can be inventoried or queried through tools such as Azure CLI, Azure PowerShell, and the Azure portal. The privileges you assign to resources through Azure RBAC should always be limited to what's required by the roles. Limited privileges complement the just in time (JIT) approach of Microsoft Entra Privileged Identity Management (PIM), and those privileges should be reviewed periodically. Use built-in roles to allocate permission and only create custom role when required. What is Azure role-based access control (Azure RBAC): https://docs.microsoft.com/azure/role-based-access-control/overview How to configure Azure RBAC: https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal How to use Microsoft Entra identity and access reviews: https://docs.microsoft.com/azure/active-directory/governance/access-reviews-overview | n/a | link | count: 003 [Deprecated]: Custom subscription owner roles should not exist (10ee2ea2-fb4d-45b8-a7e9-a2e770044cd9), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
General, Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | PV-2 | Azure_Security_Benchmark_v2.0_PV-2 | Azure Security Benchmark PV-2 | Posture and Vulnerability Management | Sustain secure configurations for Azure services | Customer | Use Azure Security Center to monitor your configuration baseline and use Azure Policy [deny] and [deploy if not exist] rule to enforce secure configuration across Azure compute resources, including VMs, containers, and others. Understand Azure Policy effects: https://docs.microsoft.com/azure/governance/policy/concepts/effects Create and manage policies to enforce compliance: https://docs.microsoft.com/azure/governance/policy/tutorials/create-and-manage | n/a | link | count: 019 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99) |
App Service, Kubernetes | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | PV-4 | Azure_Security_Benchmark_v2.0_PV-4 | Azure Security Benchmark PV-4 | Posture and Vulnerability Management | Sustain secure configurations for compute resources | Shared | Use Azure Security Center and Azure Policy to regularly assess and remediate configuration risks on your Azure compute resources, including VMs, containers, and others. In addition, you can use Azure Resource Manager templates, custom operating system images, or Azure Automation State Configuration to maintain the security configuration of the operating system required by your organization. Microsoft VM templates in conjunction with Azure Automation State Configuration can assist in meeting and maintaining security requirements. Also, note that Azure Marketplace VM images published by Microsoft are managed and maintained by Microsoft. Azure Security Center can also scan vulnerabilities in container images and perform continuous monitoring of your Docker configuration in containers, based on the CIS Docker Benchmark. You can use the Azure Security Center recommendations page to view recommendations and remediate issues. How to implement Azure Security Center vulnerability assessment recommendations: https://docs.microsoft.com/azure/security-center/security-center-vulnerability-assessment-recommendations How to create an Azure virtual machine from an ARM template: https://docs.microsoft.com/azure/virtual-machines/windows/ps-template Azure Automation State Configuration overview: https://docs.microsoft.com/azure/automation/automation-dsc-overview Create a Windows virtual machine in the Azure portal: https://docs.microsoft.com/azure/virtual-machines/windows/quick-create-portal Information on how to download template for a VM: https://docs.microsoft.com/azure/virtual-machines/windows/download-template Sample script to upload a VHD to Azure and create a new VM: https://docs.microsoft.com/azure/virtual-machines/scripts/virtual-machines-windows-powershell-upload-generalized-script Container security in Azure Security Center: https://docs.microsoft.com/azure/security-center/container-security | n/a | link | count: 003 Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | PV-6 | Azure_Security_Benchmark_v2.0_PV-6 | Azure Security Benchmark PV-6 | Posture and Vulnerability Management | Perform software vulnerability assessments | Customer | Follow recommendations from Azure Security Center for performing vulnerability assessments on your Azure virtual machines, container images, and SQL servers. Azure Security Center has a built-in vulnerability scanner for virtual machine scan. Use a third-party solution for performing vulnerability assessments on network devices and web applications. When conducting remote scans, do not use a single, perpetual, administrative account. Consider implementing JIT (Just In Time) provisioning methodology for the scan account. Credentials for the scan account should be protected, monitored, and used only for vulnerability scanning. Export scan results at consistent intervals and compare the results with previous scans to verify that vulnerabilities have been remediated. When using vulnerability management recommendations suggested by Azure Security Center, you can pivot into the selected scan solution's portal to view historical scan data. How to implement Azure Security Center vulnerability assessment recommendations: https://docs.microsoft.com/azure/security-center/security-center-vulnerability-assessment-recommendations Integrated vulnerability scanner for virtual machines: https://docs.microsoft.com/azure/security-center/built-in-vulnerability-assessment SQL vulnerability assessment: https://docs.microsoft.com/azure/azure-sql/database/sql-vulnerability-assessment Exporting Azure Security Center vulnerability scan results: https://docs.microsoft.com/azure/security-center/built-in-vulnerability-assessment#exporting-results | n/a | link | count: 005 [Deprecated]: Azure registry container images should have vulnerabilities resolved (powered by Qualys) (5f0f936f-2f01-4bf5-b6be-d423792fa562), A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v2.0 | PV-7 | Azure_Security_Benchmark_v2.0_PV-7 | Azure Security Benchmark PV-7 | Posture and Vulnerability Management | Rapidly and automatically remediate software vulnerabilities | Customer | Rapidly deploy software updates to remediate software vulnerabilities in operating systems and applications. Use a common risk scoring program (for example, Common Vulnerability Scoring System) or the default risk ratings provided by your third-party scanning tool and tailor to your environment, taking into account which applications present a high security risk and which ones require high uptime. Use Azure Automation Update Management or a third-party solution to ensure that the most recent security updates are installed on your Windows and Linux VMs. For Windows VMs, ensure Windows Update has been enabled and set to update automatically. For third-party software, use a third-party patch management solution or System Center Updates Publisher for Configuration Manager. How to configure Update Management for virtual machines in Azure: https://docs.microsoft.com/azure/automation/automation-update-management Manage updates and patches for your Azure VMs: https://docs.microsoft.com/azure/automation/automation-tutorial-update-management | n/a | link | count: 003 Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Security Center | [Deprecated]: Azure Security Benchmark v2 (bb522ac1-bc39-4957-b194-429bcd3bcb0b) |
| Azure_Security_Benchmark_v3.0 | AM-2 | Azure_Security_Benchmark_v3.0_AM-2 | Microsoft cloud security benchmark AM-2 | Asset Management | Use only approved services | Shared | **Security Principle:** Ensure that only approved cloud services can be used, by auditing and restricting which services users can provision in the environment. **Azure Guidance:** Use Azure Policy to audit and restrict which services users can provision in your environment. Use Azure Resource Graph to query for and discover resources within their subscriptions. You can also use Azure Monitor to create rules to trigger alerts when a non-approved service is detected. **Implementation and additional context:** Configure and manage Azure Policy: https://docs.microsoft.com/azure/governance/policy/tutorials/create-and-manage How to deny a specific resource type with Azure Policy: https://docs.microsoft.com/azure/governance/policy/samples/not-allowed-resource-types How to create queries with Azure Resource Graph Explorer: https://docs.microsoft.com/azure/governance/resource-graph/first-query-portal | n/a | link | count: 003 Azure API Management platform version should be stv2 (1dc2fc00-2245-4143-99f4-874c937f13ef), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
API Management, Compute, Storage | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | AM-3 | Azure_Security_Benchmark_v3.0_AM-3 | Microsoft cloud security benchmark AM-3 | Asset Management | Ensure security of asset lifecycle management | Shared | **Security Principle:** Ensure security attributes or configurations of the assets are always updated during the asset lifecycle. **Azure Guidance:** Establish or update security policies/process that address asset lifecycle management processes for potentially high impact modifications. These modifications include changes to identity providers and access, data sensitivity, network configuration, and administrative privilege assignment. Remove Azure resources when they are no longer needed. **Implementation and additional context:** Delete Azure resource group and resource: https://docs.microsoft.com/azure/azure-resource-manager/management/delete-resource-group | n/a | link | count: 001 API endpoints that are unused should be disabled and removed from the Azure API Management service (c8acafaf-3d23-44d1-9624-978ef0f8652c) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | AM-5 | Azure_Security_Benchmark_v3.0_AM-5 | Microsoft cloud security benchmark AM-5 | Asset Management | Use only approved applications in virtual machine | Shared | **Security Principle:** Ensure that only authorized software executes by creating an allow list and block the unauthorized software from executing in your environment. **Azure Guidance:** Use Microsoft Defender for Cloud adaptive application controls to discover and generate an application allow list. You can also use ASC adaptive application controls to ensure that only authorized software executes and all unauthorized software is blocked from executing on Azure Virtual Machines. Use Azure Automation Change Tracking and Inventory to automate the collection of inventory information from your Windows and Linux VMs. Software name, version, publisher, and refresh time are available from the Azure portal. To get the software installation date and other information, enable guest-level diagnostics and direct the Windows Event Logs to Log Analytics workspace. Depending on the type of scripts, you can use operating system-specific configurations or third-party resources to limit users' ability to execute scripts in Azure compute resources. You can also use a third-party solution to discover and identify unapproved software. **Implementation and additional context:** How to use Microsoft Defender for Cloud adaptive application controls: https://docs.microsoft.com/azure/security-center/security-center-adaptive-application Understand Azure Automation Change Tracking and Inventory: https://docs.microsoft.com/azure/automation/change-tracking How to control PowerShell script execution in Windows environments: https://docs.microsoft.com/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-6 | n/a | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | BR-1 | Azure_Security_Benchmark_v3.0_BR-1 | Microsoft cloud security benchmark BR-1 | Backup and Recovery | Ensure regular automated backups | Shared | **Security Principle:** Ensure backup of business-critical resources, either during resource creation or enforced through policy for existing resources. **Azure Guidance:** For Azure Backup supported resources, enable Azure Backup and configure the backup source (such as Azure VMs, SQL Server, HANA databases, or File Shares) on the desired frequency and retention period. For Azure VM, you can use Azure Policy to have backup automatically enabled using Azure Policy. For resources not supported by Azure Backup, enable the backup as part of its resource creation. Where applicable, use built-in policies (Azure Policy) to ensure that your Azure resources are configured for backup. **Implementation and additional context:** How to enable Azure Backup: https://docs.microsoft.com/azure/backup/ Auto-Enable Backup on VM Creation using Azure Policy: https://docs.microsoft.com/azure/backup/backup-azure-auto-enable-backup | n/a | link | count: 004 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430) |
Backup, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | BR-2 | Azure_Security_Benchmark_v3.0_BR-2 | Microsoft cloud security benchmark BR-2 | Backup and Recovery | Protect backup and recovery data | Shared | **Security Principle:** Ensure backup data and operations are protected from data exfiltration, data compromise, ransomware/malware and malicious insiders. The security controls that should be applied include user and network access control, data encryption at-rest and in-transit. **Azure Guidance:** Use Azure RBAC and multi-factor-authentication to secure the critical Azure Backup operations (such as delete, change retention, updates to backup config). For Azure Backup supported resources, use Azure RBAC to segregate duties and enable fine grained access, and create private endpoints within your Azure Virtual Network to securely backup and restore data from your Recovery Services vaults. For Azure Backup supported resources, backup data is automatically encrypted using Azure platform-managed keys with 256-bit AES encryption. You can also choose to encrypt the backups using customer managed key. In this case, ensure this customer-managed key in the Azure Key Vault is also in the backup scope. If you use customer-managed key options, use soft delete and purge protection in Azure Key Vault to protect keys from accidental or malicious deletion. For on-premises backups using Azure Backup, encryption-at-rest is provided using the passphrase you provide. Safeguard backup data from accidental or malicious deletion (such as ransomware attacks/attempts to encrypt or tamper backup data. For Azure Backup supported resources, enable soft delete to ensure recovery of items with no data loss for up to 14 days after an unauthorized deletion, and enable multifactor authentication using a PIN generated in the Azure portal. Also enable cross-region restore to ensure backup data is restorable when there is a disaster in primary region. Note: If you use resource's native backup feature or backup services other than Azure Backup, refer to the Azure Security Benchmark (and service baselines) to implement the above controls. **Implementation and additional context:** Overview of security features in Azure Backup: https://docs.microsoft.com/azure/backup/security-overview Encryption of backup data using customer-managed keys: https://docs.microsoft.com/azure/backup/encryption-at-rest-with-cmk Security features to help protect hybrid backups from attacks: https://docs.microsoft.com/azure/backup/backup-azure-security-feature#prevent-attacks Azure Backup - set cross region restore https://docs.microsoft.com/azure/backup/backup-create-rs-vault#set-cross-region-restore | n/a | link | count: 004 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430) |
Backup, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | DP-1 | Azure_Security_Benchmark_v3.0_DP-1 | Microsoft cloud security benchmark DP-1 | Data Protection | Discover, classify, and label sensitive data | Shared | **Security Principle:** Establish and maintain an inventory of the sensitive data, based on the defined sensitive data scope. Use tools to discover, classify and label the in- scope sensitive data. **Azure Guidance:** Use tools such as Azure Purview, Azure Information Protection and Azure SQL Data Discovery and Classification to centrally scan, classify and label the sensitive data that reside in the Azure, on-premises, Microsoft 365, and other locations. **Implementation and additional context:** Data classification overview: https://docs.microsoft.com/azure/cloud-adoption-framework/govern/policy-compliance/data-classification Label your sensitive data using Azure Purview: https://docs.microsoft.com/azure/purview/create-sensitivity-label Tag sensitive information using Azure Information Protection: https://docs.microsoft.com/azure/information-protection/what-is-information-protection How to implement Azure SQL Data Discovery: https://docs.microsoft.com/azure/sql-database/sql-database-data-discovery-and-classification Azure Purview data sources: https://docs.microsoft.com/azure/purview/purview-connector-overview#purview-data-sources | n/a | link | count: 001 Microsoft Defender for APIs should be enabled (7926a6d1-b268-4586-8197-e8ae90c877d7) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | DP-2 | Azure_Security_Benchmark_v3.0_DP-2 | Microsoft cloud security benchmark DP-2 | Data Protection | Monitor anomalies and threats targeting sensitive data | Shared | **Security Principle:** Monitor for anomalies around sensitive data, such as unauthorized transfer of data to locations outside of enterprise visibility and control. This typically involves monitoring for anomalous activities (large or unusual transfers) that could indicate unauthorized data exfiltration. **Azure Guidance:** Use Azure Information protection (AIP) to monitor the data that has been classified and labeled. Use Azure Defender for Storage, Azure Defender for SQL and Azure Cosmos DB to alert on anomalous transfer of information that might indicate unauthorized transfers of sensitive data information. Note: If required for compliance of data loss prevention (DLP), you can use a host based DLP solution from Azure Marketplace or a Microsoft 365 DLP solution to enforce detective and/or preventative controls to prevent data exfiltration. **Implementation and additional context:** Enable Azure Defender for SQL: https://docs.microsoft.com/azure/azure-sql/database/azure-defender-for-sql Enable Azure Defender for Storage: https://docs.microsoft.com/azure/storage/common/storage-advanced-threat-protection?tabs=azure-security-center | n/a | link | count: 006 Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for APIs should be enabled (7926a6d1-b268-4586-8197-e8ae90c877d7), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4) |
Security Center, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | DP-3 | Azure_Security_Benchmark_v3.0_DP-3 | Microsoft cloud security benchmark DP-3 | Data Protection | Encrypt sensitive data in transit | Shared | **Security Principle:** Protect the data in transit against 'out of band' attacks (such as traffic capture) using encryption to ensure that attackers cannot easily read or modify the data. Set the network boundary and service scope where data in transit encryption is mandatory inside and outside of the network. While this is optional for traffic on private networks, this is critical for traffic on external and public networks. **Azure Guidance:** Enforce secure transfer in services such as Azure Storage, where a native data in transit encryption feature is built in. Enforce HTTPS for workload web application and services by ensuring that any clients connecting to your Azure resources use transportation layer security (TLS) v1.2 or later. For remote management of VMs, use SSH (for Linux) or RDP/TLS (for Windows) instead of an unencrypted protocol. Note: Data in transit encryption is enabled for all Azure traffic traveling between Azure datacenters. TLS v1.2 or later is enabled on most Azure PaaS services by default. **Implementation and additional context:** Double encryption for Azure data in transit: https://docs.microsoft.com/azure/security/fundamentals/double-encryption#data-in-transit Understand encryption in transit with Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-overview#encryption-of-data-in-transit Information on TLS Security: https://docs.microsoft.com/security/engineering/solving-tls1-problem Enforce secure transfer in Azure storage: https://docs.microsoft.com/azure/storage/common/storage-require-secure-transfer?toc=/azure/storage/blobs/toc.json#require-secure-transfer-for-a-new-storage-account | n/a | link | count: 015 [Preview]: Host and VM networking should be protected on Azure Stack HCI systems (36f0d6bc-a253-4df8-b25b-c3a5023ff443), API Management APIs should use only encrypted protocols (ee7495e7-3ba7-40b6-bfee-c29e22cc75d4), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure SQL Database should be running TLS version 1.2 or newer (32e6bbec-16b6-44c2-be37-c5b672d103cf), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
API Management, App Service, Cache, Guest Configuration, Kubernetes, SQL, Stack HCI, Storage | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | DP-4 | Azure_Security_Benchmark_v3.0_DP-4 | Microsoft cloud security benchmark DP-4 | Data Protection | Enable data at rest encryption by default | Shared | **Security Principle:** To complement access controls, data at rest should be protected against 'out of band' attacks (such as accessing underlying storage) using encryption. This helps ensure that attackers cannot easily read or modify the data. **Azure Guidance:** Many Azure services have data at rest encryption enabled by default at the infrastructure layer using a service-managed key. Where technically feasible and not enabled by default, you can enable data at rest encryption in the Azure services, or in your VMs for storage level, file level, or database level encryption. **Implementation and additional context:** Understand encryption at rest in Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-atrest#encryption-at-rest-in-microsoft-cloud-services Data at rest double encryption in Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-models Encryption model and key management table: https://docs.microsoft.com/azure/security/fundamentals/encryption-models | n/a | link | count: 009 A Microsoft Entra administrator should be provisioned for MySQL servers (146412e9-005c-472b-9e48-c87b72ac229e), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure MySQL flexible server should have Microsoft Entra Only Authentication enabled (40e85574-ef33-47e8-a854-7a65c7500560), Linux virtual machines should enable Azure Disk Encryption or EncryptionAtHost. (ca88aadc-6e2b-416c-9de2-5a0f01d1693f), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d), Windows virtual machines should enable Azure Disk Encryption or EncryptionAtHost. (3dc5edcd-002d-444c-b216-e123bbfa37c0) |
Automation, Compute, Guest Configuration, Security Center, Service Fabric, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | DP-5 | Azure_Security_Benchmark_v3.0_DP-5 | Microsoft cloud security benchmark DP-5 | Data Protection | Use customer-managed key option in data at rest encryption when required | Shared | **Security Principle:** If required for regulatory compliance, define the use case and service scope where customer-managed key option is needed. Enable and implement data at rest encryption using customer-managed key in services. **Azure Guidance:** Azure also provides encryption option using keys managed by yourself (customer-managed keys) for certain services. However, using customer-managed key option requires additional operational efforts to manage the key lifecycle. This may include encryption key generation, rotation, revoke and access control, etc. **Implementation and additional context:** Encryption model and key management table: https://docs.microsoft.com/azure/security/fundamentals/encryption-models Services that support encryption using customer-managed key: https://docs.microsoft.com/azure/security/fundamentals/encryption-models#supporting-services How to configure customer managed encryption keys in Azure Storage: https://docs.microsoft.com/azure/storage/common/storage-encryption-keys-portal | n/a | link | count: 010 [Preview]: Azure Stack HCI systems should have encrypted volumes (ee8ca833-1583-4d24-837e-96c2af9488a4), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
Cognitive Services, Container Registry, Cosmos DB, Machine Learning, SQL, Stack HCI, Storage | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | DP-6 | Azure_Security_Benchmark_v3.0_DP-6 | Microsoft cloud security benchmark DP-6 | Data Protection | Use a secure key management process | Shared | **Security Principle:** Document and implement an enterprise cryptographic key management standard, processes, and procedures to control your key lifecycle. When there is a need to use customer-managed key in the services, use a secured key vault service for key generation, distribution, and storage. Rotate and revoke your keys based on the defined schedule and when there is a key retirement or compromise. **Azure Guidance:** Use Azure Key Vault to create and control your encryption keys life cycle, including key generation, distribution, and storage. Rotate and revoke your keys in Azure Key Vault and your service based on the defined schedule and when there is a key retirement or compromise. When there is a need to use customer-managed key (CMK) in the workload services or applications, ensure you follow the best practices: - Use a key hierarchy to generate a separate data encryption key (DEK) with your key encryption key (KEK) in your key vault. - Ensure keys are registered with Azure Key Vault and implement via key IDs in each service or application. If you need to bring your own key (BYOK) to the services (i.e., importing HSM-protected keys from your on-premises HSMs into Azure Key Vault), follow the recommended guideline to perform the key generation and key transfer. Note: Refer to the below for the FIPS 140-2 level for Azure Key Vault types and FIPS compliance level. - Software-protected keys in vaults (Premium & Standard SKUs): FIPS 140-2 Level 1 - HSM-protected keys in vaults (Premium SKU): FIPS 140-2 Level 2 - HSM-protected keys in Managed HSM: FIPS 140-2 Level 3 **Implementation and additional context:** Azure Key Vault overview: https://docs.microsoft.com/azure/key-vault/general/overview Azure data encryption at rest--Key Hierarchy: https://docs.microsoft.com/azure/security/fundamentals/encryption-atrest#key-hierarchy BYOK(Bring Your Own Key) specification: https://docs.microsoft.com/azure/key-vault/keys/byok-specification | n/a | link | count: 003 API Management secret named values should be stored in Azure Key Vault (f1cc7827-022c-473e-836e-5a51cae0b249), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37) |
API Management, Key Vault | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | DP-7 | Azure_Security_Benchmark_v3.0_DP-7 | Microsoft cloud security benchmark DP-7 | Data Protection | Use a secure certificate management process | Shared | **Security Principle:** Document and implement an enterprise certificate management standard, processes and procedures which includes the certificate lifecycle control, and certificate policies (if a public key infrastructure is needed). Ensure certificates used by the critical services in your organization are inventoried, tracked, monitored, and renewed timely using automated mechanism to avoid service disruption. **Azure Guidance:** Use Azure Key Vault to create and control the certificate lifecycle, including creation/import, rotation, revocation, storage, and purge of the certificate. Ensure the certificate generation follows the defined standard without using any insecure properties, such as insufficient key size, overly long validity period, insecure cryptography and so on. Setup automatic rotation of the certificate in Azure Key Vault and Azure service (if supported) based on the defined schedule and when there is a certificate expiration. If automatic rotation is not supported in the front application, use a manual rotation in Azure Key Vault. Avoid using self-signed certificate and wildcard certificate in your critical services due to the limited security assurance. Instead, you can create public signed certificate in Azure Key Vault. The following CAs are the current partnered providers with Azure Key Vault. - DigiCert: Azure Key Vault offers OV TLS/SSL certificates with DigiCert. - GlobalSign: Azure Key Vault offers OV TLS/SSL certificates with GlobalSign. Note: Use only approved Certificate Authority (CA) and ensure the known bad CA root/intermediate certificates and certificates issued by these CAs are disabled. **Implementation and additional context:** Get started with Key Vault certificates: https://docs.microsoft.com/azure/key-vault/certificates/certificate-scenarios Certificate Access Control in Azure Key Vault: https://docs.microsoft.com/azure/key-vault/certificates/certificate-access-control | n/a | link | count: 001 Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560) |
Key Vault | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | DP-8 | Azure_Security_Benchmark_v3.0_DP-8 | Microsoft cloud security benchmark DP-8 | Data Protection | Ensure security of key and certificate repository | Shared | **Security Principle:** Ensure the security of the key vault service used for the cryptographic key and certificate lifecycle management. Harden your key vault service through access control, network security, logging and monitoring and backup to ensure keys and certificates are always protected using the maximum security. **Azure Guidance:** Secure your cryptographic keys and certificates by hardening your Azure Key Vault service through the following controls: - Restrict the access to keys and certificates in Azure Key Vault using built-in access policies or Azure RBAC to ensure the least privileges principle are in place for management plane access and data plane access. - Secure the Azure Key Vault using Private Link and Azure Firewall to ensure the minimal exposure of the service - Ensure separation of duties is place for users who manages encryption keys not have the ability to access encrypted data, and vice versa. - Use managed identity to access keys stored in the Azure Key Vault in your workload applications. - Never have the keys stored in plaintext format outside of the Azure Key Vault. - When purging data, ensure your keys are not deleted before the actual data, backups and archives are purged. - Backup your keys and certificates using the Azure Key Vault. Enable soft delete and purge protection to avoid accidental deletion of keys. - Turn on Azure Key Vault logging to ensure the critical management plane and data plane activities are logged. **Implementation and additional context:** Azure Key Vault overview: https://docs.microsoft.com/azure/key-vault/general/overview Azure Key Vault security best practices: https://docs.microsoft.com/azure/key-vault/general/best-practices Use managed identity to access Azure Key Vault: https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-nonaad | n/a | link | count: 006 Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21) |
Key Vault, Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | DS-6 | Azure_Security_Benchmark_v3.0_DS-6 | Microsoft cloud security benchmark DS-6 | DevOps Security | Enforce security of workload throughout DevOps lifecycle | Shared | **Security Principle:** Ensure the workload is secured throughout the entire lifecycle in development, testing, and deployment stage. Use Azure Security Benchmark to evaluate the controls (such as network security, identity management, privileged access and so on) that can be set as guardrails by default or shift left prior to the deployment stage. In particular, ensure the following controls are in place in your DevOps process: - Automate the deployment by using Azure or third-party tooling in the CI/CD workflow, infrastructure management (infrastructure as code), and testing to reduce human error and attack surface. - Ensure VMs, container images and other artifacts are secure from malicious manipulation. - Scan the workload artifacts (in other words, container images, dependencies, SAST and DAST scans) prior to the deployment in the CI/CD workflow - Deploy vulnerability assessment and threat detection capability into the production environment and continuously use these capabilities in the run-time. **Azure Guidance:** Guidance for Azure VMs: - Use Azure Shared Image Gallery to share and control access to your images by different users, service principals, or AD groups within your organization. Use Azure role-based access control (Azure RBAC) to ensure that only authorized users can access your custom images. - Define the secure configuration baselines for the VMs to eliminate unnecessary credentials, permissions, and packages. Through custom images, Azure Resource Manager template, and/or Azure Policy guest configuration to deploy and enforce these the configuration baseline. Guidance for Azure container services: - Use Azure Container Registry (ACR) to create your private container registry where a granular access can be restricted through Azure RBAC, so only authorized services and accounts can access the containers in the private registry. - Use Defender for Azure Container Registry for vulnerability assessment of the images in your private Azure Container Registry. In addition, you can use Microsoft Defender for Cloud to ingrate container images scan as part of your CI/CD workflows. For Azure serverless services, adopt the similar controls to ensure security controls are shift left to the stage prior to the deployment. **Implementation and additional context:** Shared Image Gallery overview: https://docs.microsoft.com/azure/virtual-machines/windows/shared-image-galleries How to implement Microsoft Defender for Cloud vulnerability assessment recommendations: https://docs.microsoft.com/azure/security-center/security-center-vulnerability-assessment-recommendations Security considerations for Azure Container: https://docs.microsoft.com/azure/container-instances/container-instances-image-security Azure Defender for container registries: https://docs.microsoft.com/azure/security-center/defender-for-container-registries-introduction | n/a | link | count: 003 Azure registry container images should have vulnerabilities resolved (powered by Microsoft Defender Vulnerability Management) (090c7b07-b4ed-4561-ad20-e9075f3ccaff), Azure running container images should have vulnerabilities resolved (powered by Microsoft Defender Vulnerability Management) (17f4b1cc-c55c-4d94-b1f9-2978f6ac2957), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | ES-1 | Azure_Security_Benchmark_v3.0_ES-1 | Microsoft cloud security benchmark ES-1 | Endpoint Security | Use Endpoint Detection and Response (EDR) | Shared | **Security Principle:** Enable Endpoint Detection and Response (EDR) capabilities for VMs and integrate with SIEM and security operations processes. **Azure Guidance:** Azure Defender for servers (with Microsoft Defender for Endpoint integrated) provides EDR capability to prevent, detect, investigate, and respond to advanced threats. Use Microsoft Defender for Cloud to deploy Azure Defender for servers for your endpoint and integrate the alerts to your SIEM solution such as Azure Sentinel. **Implementation and additional context:** Azure Defender for servers introduction: https://docs.microsoft.com/azure/security-center/defender-for-servers-introduction Microsoft Defender for Endpoint overview: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/microsoft-defender-endpoint?view=o365-worldwide Microsoft Defender for Cloud feature coverage for machines: https://docs.microsoft.com/azure/security-center/security-center-services?tabs=features-windows Connector for Defender for servers integration into SIEM: https://docs.microsoft.com/azure/security-center/security-center-wdatp?WT.mc_id=Portal-Microsoft_Azure_Security_CloudNativeCompute&tabs=windows | n/a | link | count: 001 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | ES-2 | Azure_Security_Benchmark_v3.0_ES-2 | Microsoft cloud security benchmark ES-2 | Endpoint Security | Use modern anti-malware software | Shared | **Security Principle:** Use anti-malware solutions capable of real-time protection and periodic scanning. **Azure Guidance:** Microsoft Defender for Cloud can automatically identify the use of a number of popular anti-malware solutions for your virtual machines and on-premises machines with Azure Arc configured, and report the endpoint protection running status and make recommendations. Microsoft Defender Antivirus is the default anti-malware solution for Windows server 2016 and above. For Windows server 2012 R2, use Microsoft Antimalware extension to enable SCEP (System Center Endpoint Protection), and Microsoft Defender for Cloud to discover and assess the health status. For Linux VMs, use Microsoft Defender for Endpoint on Linux. Note: You can also use Microsoft Defender for Cloud's Defender for Storage to detect malware uploaded to Azure Storage accounts. **Implementation and additional context:** Supported endpoint protection solutions: https://docs.microsoft.com/azure/security-center/security-center-services?tabs=features-windows#supported-endpoint-protection-solutions- How to configure Microsoft Antimalware for Cloud Services and virtual machines: https://docs.microsoft.com/azure/security/fundamentals/antimalware | n/a | link | count: 005 Endpoint protection health issues should be resolved on your machines (8e42c1f2-a2ab-49bc-994a-12bcd0dc4ac2), Endpoint protection should be installed on your machines (1f7c564c-0a90-4d44-b7e1-9d456cffaee8), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | ES-3 | Azure_Security_Benchmark_v3.0_ES-3 | Microsoft cloud security benchmark ES-3 | Endpoint Security | Ensure anti-malware software and signatures are updated | Shared | **Security Principle:** Ensure anti-malware signatures are updated rapidly and consistently for the anti-malware solution. **Azure Guidance:** Follow recommendations in Microsoft Defender for Cloud: "Compute & Apps" to keep all endpoints up to date with the latest signatures. Microsoft Antimalware will automatically install the latest signatures and engine updates by default. For Linux, ensure the signatures are updated in the third-party anti-malware solution. **Implementation and additional context:** How to deploy Microsoft Antimalware for Cloud Services and virtual machine: https://docs.microsoft.com/azure/security/fundamentals/antimalware Endpoint protection assessment and recommendations in Microsoft Defender for Cloud: https://docs.microsoft.com/azure/security-center/security-center-endpoint-protection | n/a | link | count: 001 Endpoint protection health issues should be resolved on your machines (8e42c1f2-a2ab-49bc-994a-12bcd0dc4ac2) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | IM-1 | Azure_Security_Benchmark_v3.0_IM-1 | Microsoft cloud security benchmark IM-1 | Identity Management | Use centralized identity and authentication system | Shared | **Security Principle:** Use a centralized identity and authentication system to govern your organization's identities and authentications for cloud and non-cloud resources. **Azure Guidance:** Microsoft Entra ID is Azure's identity and authentication management service. You should standardize on Microsoft Entra ID to govern your organization's identity and authentication in: - Microsoft cloud resources, such as the Azure Storage, Azure Virtual Machines (Linux and Windows), Azure Key Vault, PaaS, and SaaS applications. - Your organization's resources, such as applications on Azure, third-party applications running on your corporate network resources, and third-party SaaS applications. - Your enterprise identities in Active Directory by synchronization to Microsoft Entra ID to ensure a consistent and centrally managed identity strategy. Note: As soon as it is technically feasible, you should migrate on-premises Active Directory based applications to Microsoft Entra ID. This could be a Microsoft Entra Enterprise Directory, Business to Business configuration, or Business to consumer configuration. **Implementation and additional context:** Tenancy in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/develop/single-and-multi-tenant-apps How to create and configure a Microsoft Entra instance: https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-access-create-new-tenant Define Microsoft Entra ID tenants: https://azure.microsoft.com/resources/securing-azure-environments-with-azure-active-directory/ Use external identity providers for an application: https://docs.microsoft.com/azure/active-directory/b2b/identity-providers | n/a | link | count: 014 A Microsoft Entra administrator should be provisioned for PostgreSQL servers (b4dec045-250a-48c2-b5cc-e0c4eec8b5b4), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Azure Machine Learning Computes should have local authentication methods disabled (e96a9a5f-07ca-471b-9bc5-6a0f33cbd68f), Azure SQL Database should have Microsoft Entra-only authentication enabled (b3a22bc9-66de-45fb-98fa-00f5df42f41a), Azure SQL Database should have Microsoft Entra-only authentication enabled during creation (abda6d70-9778-44e7-84a8-06713e6db027), Azure SQL Managed Instance should have Microsoft Entra-only authentication enabled (0c28c3fb-c244-42d5-a9bf-f35f2999577b), Azure SQL Managed Instances should have Microsoft Entra-only authentication enabled during creation (78215662-041e-49ed-a9dd-5385911b3a1f), Cosmos DB database accounts should have local authentication methods disabled (5450f5bd-9c72-4390-a9c4-a7aba4edfdd2), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should prevent shared key access (8c6a50c6-9ffd-4ae7-986f-5fa6111f9a54), Synapse Workspaces should have Microsoft Entra-only authentication enabled (6ea81a52-5ca7-4575-9669-eaa910b7edf8), Synapse Workspaces should use only Microsoft Entra identities for authentication during workspace creation (2158ddbe-fefa-408e-b43f-d4faef8ff3b8), VPN gateways should use only Azure Active Directory (Azure AD) authentication for point-to-site users (21a6bc25-125e-4d13-b82d-2e19b7208ab7) |
Azure Ai Services, Cosmos DB, Machine Learning, Network, Service Fabric, SQL, Storage, Synapse | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | IM-3 | Azure_Security_Benchmark_v3.0_IM-3 | Microsoft cloud security benchmark IM-3 | Identity Management | Manage application identities securely and automatically | Shared | **Security Principle:** Use managed application identities instead of creating human accounts for applications to access resources and execute code. Managed application identities provide benefits such as reducing the exposure of credentials. Automate the rotation of credential to ensure the security of the identities. **Azure Guidance:** Use Azure managed identities, which can authenticate to Azure services and resources that support Microsoft Entra ID authentication. Managed identity credentials are fully managed, rotated, and protected by the platform, avoiding hard-coded credentials in source code or configuration files. For services that don't support managed identities, use Microsoft Entra ID to create a service principal with restricted permissions at the resource level. It is recommended to configure service principals with certificate credentials and fall back to client secrets for authentication. **Implementation and additional context:** Azure managed identities: https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview Services that support managed identities for Azure resources: https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/services-support-managed-identities Azure service principal: https://docs.microsoft.com/powershell/azure/create-azure-service-principal-azureps Create a service principal with certificates: https://docs.microsoft.com/azure/active-directory/develop/howto-authenticate-service-principal-powershell | n/a | link | count: 003 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | IM-4 | Azure_Security_Benchmark_v3.0_IM-4 | Microsoft cloud security benchmark IM-4 | Identity Management | Authenticate server and services | Shared | **Security Principle:** Authenticate remote servers and services from your client side to ensure you are connecting to trusted server and services. The most common server authentication protocol is Transport Layer Security (TLS), where the client-side (often a browser or client device) verifies the server by verifying the server’s certificate was issued by a trusted certificate authority. Note: Mutual authentication can be used when both the server and the client authenticate one-another. **Azure Guidance:** Many Azure services support TLS authentication by default. For the services supporting TLS enable/disable switch by the user, ensure it's always enabled to support the server/service authentication. Your client application should also be designed to verify server/service identity (by verifying the server’s certificate issued by a trusted certificate authority) in the handshake stage. **Implementation and additional context:** Enforce Transport Layer Security (TLS) for a storage account: https://docs.microsoft.com/azure/storage/common/transport-layer-security-configure-minimum-version?tabs=portal#use-azure-policy-to-enforce-the-minimum-tls-version | n/a | link | count: 004 API endpoints in Azure API Management should be authenticated (8ac833bd-f505-48d5-887e-c993a1d3eea0), API Management calls to API backends should be authenticated (c15dcc82-b93c-4dcb-9332-fbf121685b54), API Management calls to API backends should not bypass certificate thumbprint or name validation (92bb331d-ac71-416a-8c91-02f2cb734ce4), Azure SQL Database should be running TLS version 1.2 or newer (32e6bbec-16b6-44c2-be37-c5b672d103cf) |
API Management, Security Center, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | IM-6 | Azure_Security_Benchmark_v3.0_IM-6 | Microsoft cloud security benchmark IM-6 | Identity Management | Use strong authentication controls | Shared | **Security Principle:** Enforce strong authentication controls (strong passwordless authentication or multi-factor authentication) with your centralized identity and authentication management system for all access to resources. Authentication based on password credentials alone is considered legacy, as it is insecure and does not stand up to popular attack methods. When deploying strong authentication, configure administrators and privileged users first, to ensure the highest level of the strong authentication method, quickly followed by rolling out the appropriate strong authentication policy to all users. Note: If legacy password-based authentication is required for legacy applications and scenarios, ensure password security best practices such as complexity requirements, are followed. **Azure Guidance:** Microsoft Entra ID supports strong authentication controls through passwordless methods and multi-factor authentication (MFA). - Passwordless authentication: Use passwordless authentication as your default authentication method. There are three options available in passwordless authentication: Windows Hello for Business, Microsoft Authenticator app phone sign-in, and FIDO 2Keys. In addition, customers can use on-premises authentication methods such as smart cards. - Multi-factor authentication: Azure MFA can be enforced on all users, select users, or at the per-user level based on sign-in conditions and risk factors. Enable Azure MFA and follow Microsoft Defender for Cloud identity and access management recommendations for your MFA setup. If legacy password-based authentication is still used for Microsoft Entra ID authentication, be aware that cloud-only accounts (user accounts created directly in Azure) have a default baseline password policy. And hybrid accounts (user accounts that come from on-premises Active Directory) follow the on-premises password policies. For third-party applications and services that may have default IDs and passwords, you should disable or change them during initial service setup. **Implementation and additional context:** How to enable MFA in Azure: https://docs.microsoft.com/azure/active-directory/authentication/howto-mfa-getstarted Introduction to passwordless authentication options for Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/authentication/concept-authentication-passwordless Microsoft Entra ID default password policy: https://docs.microsoft.com/azure/active-directory/authentication/concept-sspr-policy#password-policies-that-only-apply-to-cloud-user-accounts Eliminate bad passwords using Microsoft Entra Password Protection: https://docs.microsoft.com/azure/active-directory/authentication/concept-password-ban-bad Block legacy authentication: https://docs.microsoft.com/azure/active-directory/conditional-access/block-legacy-authentication | n/a | link | count: 004 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6) |
Guest Configuration, Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | IM-8 | Azure_Security_Benchmark_v3.0_IM-8 | Microsoft cloud security benchmark IM-8 | Identity Management | Restrict the exposure of credential and secrets | Shared | **Security Principle:** Ensure that application developers securely handle credentials and secrets: - Avoid embedding the credentials and secrets into the code and configuration files - Use key vault or a secure key store service to store the credentials and secrets - Scan for credentials in source code. Note: This is often governed and enforced through a secure software development lifecycle (SDLC) and DevOps security process **Azure Guidance:** Ensure that secrets and credentials are stored in secure locations such as Azure Key Vault, instead of embedding them into the code and configuration files. - Implement Azure DevOps Credential Scanner to identify credentials within the code. - For GitHub, use the native secret scanning feature to identify credentials or other form of secrets within the code. Clients such as Azure Functions, Azure Apps services, and VMs can use managed identities to access Azure Key Vault securely. See Data Protection controls related to the use of Azure Key Vault for secrets management. **Implementation and additional context:** How to setup Credential Scanner: https://secdevtools.azurewebsites.net/helpcredscan.html GitHub secret scanning: https://docs.github.com/github/administering-a-repository/about-secret-scanning | n/a | link | count: 003 API Management minimum API version should be set to 2019-12-01 or higher (549814b6-3212-4203-bdc8-1548d342fb67), API Management secret named values should be stored in Azure Key Vault (f1cc7827-022c-473e-836e-5a51cae0b249), Machines should have secret findings resolved (3ac7c827-eea2-4bde-acc7-9568cd320efa) |
API Management, Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | IR-2 | Azure_Security_Benchmark_v3.0_IR-2 | Microsoft cloud security benchmark IR-2 | Incident Response | Preparation - setup incident notification | Shared | **Security Principle:** Ensure the security alerts and incident notification from the cloud service provider's platform and your environments can be received by correct contact in your incident response organization. **Azure Guidance:** Set up security incident contact information in Microsoft Defender for Cloud. This contact information is used by Microsoft to contact you if the Microsoft Security Response Center (MSRC) discovers that your data has been accessed by an unlawful or unauthorized party. You also have options to customize incident alert and notification in different Azure services based on your incident response needs. **Implementation and additional context:** How to set the Microsoft Defender for Cloud security contact: https://docs.microsoft.com/azure/security-center/security-center-provide-security-contact-details | n/a | link | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | IR-3 | Azure_Security_Benchmark_v3.0_IR-3 | Microsoft cloud security benchmark IR-3 | Incident Response | Detection and analysis - create incidents based on high-quality alerts | Shared | **Security Principle:** Ensure you have a process to create high-quality alerts and measure the quality of alerts. This allows you to learn lessons from past incidents and prioritize alerts for analysts, so they don't waste time on false positives. High-quality alerts can be built based on experience from past incidents, validated community sources, and tools designed to generate and clean up alerts by fusing and correlating diverse signal sources. **Azure Guidance:** Microsoft Defender for Cloud provides high-quality alerts across many Azure assets. You can use the Microsoft Defender for Cloud data connector to stream the alerts to Azure Sentinel. Azure Sentinel lets you create advanced alert rules to generate incidents automatically for an investigation. Export your Microsoft Defender for Cloud alerts and recommendations using the export feature to help identify risks to Azure resources. Export alerts and recommendations either manually or in an ongoing, continuous fashion. **Implementation and additional context:** How to configure export: https://docs.microsoft.com/azure/security-center/continuous-export How to stream alerts into Azure Sentinel: https://docs.microsoft.com/azure/sentinel/connect-azure-security-center | n/a | link | count: 017 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected PostgreSQL flexible servers (d38668f5-d155-42c7-ab3d-9b57b50f8fbf), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender CSPM should be enabled (1f90fc71-a595-4066-8974-d4d0802e8ef0), Microsoft Defender for APIs should be enabled (7926a6d1-b268-4586-8197-e8ae90c877d7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for SQL should be enabled for unprotected Synapse workspaces (d31e5c31-63b2-4f12-887b-e49456834fa1), Microsoft Defender for SQL status should be protected for Arc-enabled SQL Servers (938c4981-c2c9-4168-9cd6-972b8675f906), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), SQL server-targeted autoprovisioning should be enabled for SQL servers on machines plan (c6283572-73bb-4deb-bf2c-7a2b8f7462cb) |
Security Center, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | IR-4 | Azure_Security_Benchmark_v3.0_IR-4 | Microsoft cloud security benchmark IR-4 | Incident Response | Detection and analysis - investigate an incident | Shared | **Security Principle:** Ensure security operation team can query and use diverse data sources as they investigate potential incidents, to build a full view of what happened. Diverse logs should be collected to track the activities of a potential attacker across the kill chain to avoid blind spots. You should also ensure insights and learnings are captured for other analysts and for future historical reference. **Azure Guidance:** The data sources for investigation are the centralized logging sources that are already being collected from the in-scope services and running systems, but can also include: - Network data: Use network security groups' flow logs, Azure Network Watcher, and Azure Monitor to capture network flow logs and other analytics information. - Snapshots of running systems: a) Azure virtual machine's snapshot capability, to create a snapshot of the running system's disk. b) The operating system's native memory dump capability, to create a snapshot of the running system's memory. c) The snapshot feature of the Azure services or your software's own capability, to create snapshots of the running systems. Azure Sentinel provides extensive data analytics across virtually any log source and a case management portal to manage the full lifecycle of incidents. Intelligence information during an investigation can be associated with an incident for tracking and reporting purposes. **Implementation and additional context:** Snapshot a Windows machine's disk: https://docs.microsoft.com/azure/virtual-machines/windows/snapshot-copy-managed-disk Snapshot a Linux machine's disk: https://docs.microsoft.com/azure/virtual-machines/linux/snapshot-copy-managed-disk Microsoft Azure Support diagnostic information and memory dump collection: https://azure.microsoft.com/support/legal/support-diagnostic-information-collection/ Investigate incidents with Azure Sentinel: https://docs.microsoft.com/azure/sentinel/tutorial-investigate-cases | n/a | link | count: 001 Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6) |
Network | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | IR-5 | Azure_Security_Benchmark_v3.0_IR-5 | AMicrosoft cloud security benchmark IR-5 | Incident Response | Detection and analysis - prioritize incidents | Shared | **Security Principle:** Provide context to security operations teams to help them determine which incidents ought to first be focused on, based on alert severity and asset sensitivity defined in your organization’s incident response plan. **Azure Guidance:** Microsoft Defender for Cloud assigns a severity to each alert to help you prioritize which alerts should be investigated first. The severity is based on how confident Microsoft Defender for Cloud is in the finding or the analytics used to issue the alert, as well as the confidence level that there was malicious intent behind the activity that led to the alert. Additionally, mark resources using tags and create a naming system to identify and categorize Azure resources, especially those processing sensitive data. It is your responsibility to prioritize the remediation of alerts based on the criticality of the Azure resources and environment where the incident occurred. **Implementation and additional context:** Security alerts in Microsoft Defender for Cloud: https://docs.microsoft.com/azure/security-center/security-center-alerts-overview Use tags to organize your Azure resources: https://docs.microsoft.com/azure/azure-resource-manager/resource-group-using-tags | n/a | link | count: 017 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected PostgreSQL flexible servers (d38668f5-d155-42c7-ab3d-9b57b50f8fbf), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender CSPM should be enabled (1f90fc71-a595-4066-8974-d4d0802e8ef0), Microsoft Defender for APIs should be enabled (7926a6d1-b268-4586-8197-e8ae90c877d7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for SQL should be enabled for unprotected Synapse workspaces (d31e5c31-63b2-4f12-887b-e49456834fa1), Microsoft Defender for SQL status should be protected for Arc-enabled SQL Servers (938c4981-c2c9-4168-9cd6-972b8675f906), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), SQL server-targeted autoprovisioning should be enabled for SQL servers on machines plan (c6283572-73bb-4deb-bf2c-7a2b8f7462cb) |
Security Center, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | LT-1 | Azure_Security_Benchmark_v3.0_LT-1 | Microsoft cloud security benchmark LT-1 | Logging and Threat Detection | Enable threat detection capabilities | Shared | **Security Principle:** To support threat detection scenarios, monitor all known resource types for known and expected threats and anomalies. Configure your alert filtering and analytics rules to extract high-quality alerts from log data, agents, or other data sources to reduce false positives. **Azure Guidance:** Use the threat detection capability of Azure Defender services in Microsoft Defender for Cloud for the respective Azure services. For threat detection not included in Azure Defender services, refer to the Azure Security Benchmark service baselines for the respective services to enable the threat detection or security alert capabilities within the service. Extract the alerts to your Azure Monitor or Azure Sentinel to build analytics rules, which hunt threats that match specific criteria across your environment. For Operational Technology (OT) environments that include computers that control or monitor Industrial Control System (ICS) or Supervisory Control and Data Acquisition (SCADA) resources, use Defender for IoT to inventory assets and detect threats and vulnerabilities. For services that do not have a native threat detection capability, consider collecting the data plane logs and analyze the threats through Azure Sentinel. **Implementation and additional context:** Introduction to Azure Defender: https://docs.microsoft.com/azure/security-center/azure-defender Microsoft Defender for Cloud security alerts reference guide: https://docs.microsoft.com/azure/security-center/alerts-reference Create custom analytics rules to detect threats: https://docs.microsoft.com/azure/sentinel/tutorial-detect-threats-custom Cyber threat intelligence with Azure Sentinel: https://docs.microsoft.com/azure/architecture/example-scenario/data/sentinel-threat-intelligence | n/a | link | count: 020 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected PostgreSQL flexible servers (d38668f5-d155-42c7-ab3d-9b57b50f8fbf), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Kubernetes Service clusters should have Defender profile enabled (a1840de2-8088-4ea8-b153-b4c723e9cb01), Microsoft Defender CSPM should be enabled (1f90fc71-a595-4066-8974-d4d0802e8ef0), Microsoft Defender for APIs should be enabled (7926a6d1-b268-4586-8197-e8ae90c877d7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for SQL should be enabled for unprotected Synapse workspaces (d31e5c31-63b2-4f12-887b-e49456834fa1), Microsoft Defender for SQL status should be protected for Arc-enabled SQL Servers (938c4981-c2c9-4168-9cd6-972b8675f906), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), SQL server-targeted autoprovisioning should be enabled for SQL servers on machines plan (c6283572-73bb-4deb-bf2c-7a2b8f7462cb), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Kubernetes, Security Center, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | LT-2 | Azure_Security_Benchmark_v3.0_LT-2 | Microsoft cloud security benchmark LT-2 | Logging and Threat Detection | Enable threat detection for identity and access management | Shared | **Security Principle:** Detect threats for identities and access management by monitoring the user and application sign-in and access anomalies. Behavioral patterns such as excessive number of failed login attempts, and deprecated accounts in the subscription, should be alerted. **Azure Guidance:** Microsoft Entra ID provides the following logs that can be viewed in Microsoft Entra reporting or integrated with Azure Monitor, Azure Sentinel or other SIEM/monitoring tools for more sophisticated monitoring and analytics use cases: - Sign-ins: The sign-ins report provides information about the usage of managed applications and user sign-in activities. - Audit logs: Provides traceability through logs for all changes done by various features within Microsoft Entra ID. Examples of audit logs include changes made to any resources within Microsoft Entra ID like adding or removing users, apps, groups, roles and policies. - Risky sign-ins: A risky sign-in is an indicator for a sign-in attempt that might have been performed by someone who is not the legitimate owner of a user account. - Users flagged for risk: A risky user is an indicator for a user account that might have been compromised. Microsoft Entra ID also provides an Identity Protection module to detect, and remediate risks related to user accounts and sign-in behaviors. Examples risks include leaked credentials, sign-in from anonymous or malware linked IP addresses, password spray. The policies in the Microsoft Entra Identity Protection allow you to enforce risk-based MFA authentication in conjunction with Azure Conditional Access on user accounts. In addition, Microsoft Defender for Cloud can be configured to alert on deprecated accounts in the subscription and suspicious activities such as an excessive number of failed authentication attempts. In addition to the basic security hygiene monitoring, Microsoft Defender for Cloud's Threat Protection module can also collect more in-depth security alerts from individual Azure compute resources (such as virtual machines, containers, app service), data resources (such as SQL DB and storage), and Azure service layers. This capability allows you to see account anomalies inside the individual resources. Note: If you are connecting your on-premises Active Directory for synchronization, use the Microsoft Defender for Identity solution to consume your on-premises Active Directory signals to identify, detect, and investigate advanced threats, compromised identities, and malicious insider actions directed at your organization. **Implementation and additional context:** Audit activity reports in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/reports-monitoring/concept-audit-logs Enable Azure Identity Protection: https://docs.microsoft.com/azure/active-directory/identity-protection/overview-identity-protection Threat protection in Microsoft Defender for Cloud: https://docs.microsoft.com/azure/security-center/threat-protection | n/a | link | count: 019 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected PostgreSQL flexible servers (d38668f5-d155-42c7-ab3d-9b57b50f8fbf), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Kubernetes Service clusters should have Defender profile enabled (a1840de2-8088-4ea8-b153-b4c723e9cb01), Microsoft Defender CSPM should be enabled (1f90fc71-a595-4066-8974-d4d0802e8ef0), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for SQL should be enabled for unprotected Synapse workspaces (d31e5c31-63b2-4f12-887b-e49456834fa1), Microsoft Defender for SQL status should be protected for Arc-enabled SQL Servers (938c4981-c2c9-4168-9cd6-972b8675f906), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), SQL server-targeted autoprovisioning should be enabled for SQL servers on machines plan (c6283572-73bb-4deb-bf2c-7a2b8f7462cb), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Kubernetes, Security Center, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | LT-3 | Azure_Security_Benchmark_v3.0_LT-3 | Microsoft cloud security benchmark LT-3 | Logging and Threat Detection | Enable logging for security investigation | Shared | **Security Principle:** Enable logging for your cloud resources to meet the requirements for security incident investigations and security response and compliance purposes. **Azure Guidance:** Enable logging capability for resources at the different tiers, such as logs for Azure resources, operating systems and applications inside in your VMs and other log types. Be mindful about different type of logs for security, audit, and other operation logs at the management/control plane and data plane tiers. There are three types of the logs available at the Azure platform: - Azure resource log: Logging of operations that are performed within an Azure resource (the data plane). For example, getting a secret from a key vault or making a request to a database. The content of resource logs varies by the Azure service and resource type. - Azure activity log: Logging of operations on each Azure resource at the subscription layer, from the outside (the management plane). You can use the Activity Log to determine the what, who, and when for any write operations (PUT, POST, DELETE) taken on the resources in your subscription. There is a single Activity log for each Azure subscription. - Microsoft Entra logs: Logs of the history of sign-in activity and audit trail of changes made in the Microsoft Entra ID for a particular tenant. You can also use Microsoft Defender for Cloud and Azure Policy to enable resource logs and log data collecting on Azure resources. **Implementation and additional context:** Understand logging and different log types in Azure: https://docs.microsoft.com/azure/azure-monitor/platform/platform-logs-overview Understand Microsoft Defender for Cloud data collection: https://docs.microsoft.com/azure/security-center/security-center-enable-data-collection Enable and configure antimalware monitoring: https://docs.microsoft.com/azure/security/fundamentals/antimalware#enable-and-configure-antimalware-monitoring-using-powershell-cmdlets Operating systems and application logs inside in your compute resources: https://docs.microsoft.com/azure/azure-monitor/agents/data-sources#operating-system-guest | n/a | link | count: 015 App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Databricks Workspaces should be enabled (138ff14d-b687-4faa-a81c-898c91a87fa2), Resource logs in Azure Kubernetes Service should be enabled (245fc9df-fa96-4414-9a0b-3738c2f7341c), Resource logs in Azure Machine Learning Workspaces should be enabled (afe0c3be-ba3b-4544-ba52-0c99672a8ad6), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45) |
App Service, Azure Databricks, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Machine Learning, Search, Service Bus, SQL, Stream Analytics | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | LT-4 | Azure_Security_Benchmark_v3.0_LT-4 | Microsoft cloud security benchmark LT-4 | Logging and Threat Detection | Enable network logging for security investigation | Shared | **Security Principle:** Enable logging for your network services to support network-related incident investigations, threat hunting, and security alert generation. The network logs may include logs from network services such as IP filtering, network and application firewall, DNS, flow monitoring and so on. **Azure Guidance:** Enable and collect network security group (NSG) resource logs, NSG flow logs, Azure Firewall logs, and Web Application Firewall (WAF) logs for security analysis to support incident investigations, and security alert generation. You can send the flow logs to an Azure Monitor Log Analytics workspace and then use Traffic Analytics to provide insights. Collect DNS query logs to assist in correlating other network data. **Implementation and additional context:** How to enable network security group flow logs: https://docs.microsoft.com/azure/network-watcher/network-watcher-nsg-flow-logging-portal Azure Firewall logs and metrics: https://docs.microsoft.com/azure/firewall/logs-and-metrics Azure networking monitoring solutions in Azure Monitor: https://docs.microsoft.com/azure/azure-monitor/insights/azure-networking-analytics Gather insights about your DNS infrastructure with the DNS Analytics solution: https://docs.microsoft.com/azure/azure-monitor/insights/dns-analytics | n/a | link | count: 002 [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d) |
Monitoring | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | LT-5 | Azure_Security_Benchmark_v3.0_LT-5 | Microsoft cloud security benchmark LT-5 | Logging and Threat Detection | Centralize security log management and analysis | Shared | **Security Principle:** Centralize logging storage and analysis to enable correlation across log data. For each log source, ensure that you have assigned a data owner, access guidance, storage location, what tools are used to process and access the data, and data retention requirements. **Azure Guidance:** Ensure that you are integrating Azure activity logs into a centralized Log Analytics workspace. Use Azure Monitor to query and perform analytics and create alert rules using the logs aggregated from Azure services, endpoint devices, network resources, and other security systems. In addition, enable and onboard data to Azure Sentinel which provides the security information event management (SIEM) and security orchestration automated response (SOAR) capability. **Implementation and additional context:** How to collect platform logs and metrics with Azure Monitor: https://docs.microsoft.com/azure/azure-monitor/platform/diagnostic-settings How to onboard Azure Sentinel: https://docs.microsoft.com/azure/sentinel/quickstart-onboard | n/a | link | count: 007 [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Linux machines should have Log Analytics agent installed on Azure Arc (1e7fed80-8321-4605-b42c-65fc300f23a3), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Windows machines should have Log Analytics agent installed on Azure Arc (4078e558-bda6-41fb-9b3c-361e8875200d) |
Guest Configuration, Monitoring, Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | LT-6 | Azure_Security_Benchmark_v3.0_LT-6 | Microsoft cloud security benchmark LT-6 | Logging and Threat Detection | Configure log storage retention | Shared | **Security Principle:** Plan your log retention strategy according to your compliance, regulation, and business requirements. Configure the log retention policy at the individual logging services to ensure the logs are archived appropriately. **Azure Guidance:** Logs such as Azure Activity Logs events are retained for 90 days then deleted. You should create a diagnostic setting and route the log entries to another location (such as Azure Monitor Log Analytics workspace, Event Hubs or Azure Storage) based on your needs. This strategy also applies to the other resource logs and resources managed by yourself such as logs in the operating systems and applications inside the VMs. You have the log retention option as below: - Use Azure Monitor Log Analytics workspace for a log retention period of up to 1 year or per your response team requirements. - Use Azure Storage, Data Explorer or Data Lake for long-term and archival storage for greater than 1 year and to meet your security compliance requirements. - Use Azure Event Hubs to forward logs to outside of Azure. Note: Azure Sentinel uses Log Analytics workspace as its backend for log storage. You should consider a long-term storage strategy if you plan to retain SIEM logs for longer time. **Implementation and additional context:** Change the data retention period in Log Analytics: https://docs.microsoft.com/azure/azure-monitor/platform/manage-cost-storage#change-the-data-retention-period How to configure retention policy for Azure Storage account logs: https://docs.microsoft.com/azure/storage/common/storage-monitor-storage-account#configure-logging Microsoft Defender for Cloud alerts and recommendations export: https://docs.microsoft.com/azure/security-center/continuous-export | n/a | link | count: 001 SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | NS-1 | Azure_Security_Benchmark_v3.0_NS-1 | Microsoft cloud security benchmark NS-1 | Network Security | Establish network segmentation boundaries | Shared | **Security Principle:** Ensure that your virtual network deployment aligns to your enterprise segmentation strategy defined in the GS-2 security control. Any workload that could incur higher risk for the organization should be in isolated virtual networks. Examples of high-risk workload include: - An application storing or processing highly sensitive data. - An external network-facing application accessible by the public or users outside of your organization. - An application using insecure architecture or containing vulnerabilities that cannot be easily remediated. To enhance your enterprise segmentation strategy, restrict or monitor traffic between internal resources using network controls. For specific, well-defined applications (such as a 3-tier app), this can be a highly secure "deny by default, permit by exception" approach by restricting the ports, protocols, source, and destination IPs of the network traffic. If you have many applications and endpoints interacting with each other, blocking traffic may not scale well, and you may only be able to monitor traffic. **Azure Guidance:** Create a virtual network (VNet) as a fundamental segmentation approach in your Azure network, so resources such as VMs can be deployed into the VNet within a network boundary. To further segment the network, you can create subnets inside VNet for smaller sub-networks. Use network security groups (NSG) as a network layer control to restrict or monitor traffic by port, protocol, source IP address, or destination IP address. You can also use application security groups (ASGs) to simplify complex configuration. Instead of defining policy based on explicit IP addresses in network security groups, ASGs enable you to configure network security as a natural extension of an application's structure, allowing you to group virtual machines and define network security policies based on those groups. **Implementation and additional context:** Azure Virtual Network concepts and best practices: https://docs.microsoft.com/azure/virtual-network/concepts-and-best-practices Add, change, or delete a virtual network subnet: https://docs.microsoft.com/azure/virtual-network/virtual-network-manage-subnet How to create a network security group with security rules: https://docs.microsoft.com/azure/virtual-network/tutorial-filter-network-traffic Understand and use application security groups: https://docs.microsoft.com/azure/virtual-network/network-security-groups-overview#application-security-groups | n/a | link | count: 005 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | NS-2 | Azure_Security_Benchmark_v3.0_NS-2 | Microsoft cloud security benchmark NS-2 | Network Security | Secure cloud services with network controls | Shared | **Security Principle:** Secure cloud services by establishing a private access point for the resources. You should also disable or restrict access from public network when possible. **Azure Guidance:** Deploy private endpoints for all Azure resources that support the Private Link feature, to establish a private access point for the resources. You should also disable or restrict public network access to services where feasible. For certain services, you also have the option to deploy VNet integration for the service where you can restrict the VNET to establish a private access point for the service. **Implementation and additional context:** Understand Azure Private Link: https://docs.microsoft.com/azure/private-link/private-link-overview | n/a | link | count: 039 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), API Management should disable public network access to the service configuration endpoints (df73bd95-24da-4a4f-96b9-4e8b94b402bd), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Cosmos DB should disable public network access (797b37f7-06b8-444c-b1ad-fc62867f335a), Azure Databricks Clusters should disable public IP (51c1490f-3319-459c-bbbc-7f391bbed753), Azure Databricks Workspaces should be in a virtual network (9c25c9e4-ee12-4882-afd2-11fb9d87893f), Azure Databricks Workspaces should disable public network access (0e7849de-b939-4c50-ab48-fc6b0f5eeba2), Azure Databricks Workspaces should use private link (258823f2-4595-4b52-b333-cc96192710d8), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning Computes should be in a virtual network (7804b5c7-01dc-4723-969b-ae300cc07ff1), Azure Machine Learning Workspaces should disable public network access (438c38d2-3772-465a-a9cc-7a6666a275ce), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure SQL Managed Instances should disable public network access (9dfea752-dd46-4766-aed1-c355fa93fb91), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API Management, App Configuration, App Platform, Azure Ai Services, Azure Databricks, Cache, Cognitive Services, Container Registry, Cosmos DB, Event Grid, Key Vault, Machine Learning, Security Center, SignalR, SQL, Storage, VM Image Builder | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | NS-3 | Azure_Security_Benchmark_v3.0_NS-3 | Microsoft cloud security benchmark NS-3 | Network Security | Deploy firewall at the edge of enterprise network | Shared | **Security Principle:** Deploy a firewall to perform advanced filtering on network traffic to and from external networks. You can also use firewalls between internal segments to support a segmentation strategy. If required, use custom routes for your subnet to override the system route when you need to force the network traffic to go through a network appliance for security control purpose. At a minimum, block known bad IP addresses and high-risk protocols, such as remote management (for example, RDP and SSH) and intranet protocols (for example, SMB and Kerberos). **Azure Guidance:** Use Azure Firewall to provide fully stateful application layer traffic restriction (such as URL filtering) and/or central management over a large number of enterprise segments or spokes (in a hub/spoke topology). If you have a complex network topology, such as a hub/spoke setup, you may need to create user-defined routes (UDR) to ensure the traffic goes through the desired route. For example, you have option to use an UDR to redirect egress internet traffic through a specific Azure Firewall or a network virtual appliance. **Implementation and additional context:** How to deploy Azure Firewall: https://docs.microsoft.com/azure/firewall/tutorial-firewall-deploy-portal Virtual network traffic routing: https://docs.microsoft.com/azure/virtual-network/virtual-networks-udr-overview | n/a | link | count: 004 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917) |
Network, Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | NS-5 | Azure_Security_Benchmark_v3.0_NS-5 | Microsoft cloud security benchmark NS-5 | Network Security | Deploy DDOS protection | Shared | **Security Principle:** Deploy distributed denial of service (DDoS) protection to protect your network and applications from attacks. **Azure Guidance:** Enable DDoS protection plan on your VNet to protect resources that are exposed to the public networks. **Implementation and additional context:** Manage Azure DDoS Protection using the Azure portal: https://docs.microsoft.com/azure/virtual-network/manage-ddos-protection | n/a | link | count: 001 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | NS-6 | Azure_Security_Benchmark_v3.0_NS-6 | Microsoft cloud security benchmark NS-6 | Network Security | Deploy web application firewall | Shared | **Security Principle:** Deploy a web application firewall (WAF) and configure the appropriate rules to protect your web applications and APIs from application-specific attacks. **Azure Guidance:** Use web application firewall (WAF) capabilities in Azure Application Gateway, Azure Front Door, and Azure Content Delivery Network (CDN) to protect your applications, services and APIs against application layer attacks at the edge of your network. Set your WAF in "detection" or "prevention mode," depending on your needs and threat landscape. Choose a built-in ruleset, such as OWASP Top 10 vulnerabilities, and tune it to your application. **Implementation and additional context:** How to deploy Azure WAF: https://docs.microsoft.com/azure/web-application-firewall/overview | n/a | link | count: 002 Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Network | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | NS-7 | Azure_Security_Benchmark_v3.0_NS-7 | Microsoft cloud security benchmark NS-7 | Network Security | Simplify network security configuration | Shared | **Security Principle:** When managing a complex network environment, use tools to simplify, centralize and enhance the network security management. **Azure Guidance:** Use the following features to simplify the implementation and management of the NSG and Azure Firewall rules: - Use Microsoft Defender for Cloud Adaptive Network Hardening to recommend NSG hardening rules that further limit ports, protocols and source IPs based on threat intelligence and traffic analysis result. - Use Azure Firewall Manager to centralize the firewall policy and route management of the virtual network. To simplify the firewall rules and network security groups implementation, you can also use the Azure Firewall Manager ARM (Azure Resource Manager) template. **Implementation and additional context:** Adaptive Network Hardening in Microsoft Defender for Cloud: https://docs.microsoft.com/azure/security-center/security-center-adaptive-network-hardening Azure Firewall Manager: https://docs.microsoft.com/azure/firewall-manager/overview Create an Azure Firewall and a firewall policy - ARM template https://docs.microsoft.com/azure/firewall-manager/quick-firewall-policy | n/a | link | count: 001 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | NS-8 | Azure_Security_Benchmark_v3.0_NS-8 | Microsoft cloud security benchmark NS-8 | Network Security | Detect and disable insecure services and protocols | Shared | **Security Principle:** Detect and disable insecure services and protocols at the OS, application, or software package layer. Deploy compensating controls if disabling insecure services and protocols are not possible. **Azure Guidance:** Use Azure Sentinel’s built-in Insecure Protocol Workbook to discover the use of insecure services and protocols such as SSL/TLSv1, SSHv1, SMBv1, LM/NTLMv1, wDigest, Unsigned LDAP Binds, and weak ciphers in Kerberos. Disable insecure services and protocols that do not meet the appropriate security standard. Note: If disabling insecure services or protocols is not possible, use compensating controls such as blocking access to the resources through network security group, Azure Firewall, or Azure Web Application Firewall to reduce the attack surface. **Implementation and additional context:** Azure Sentinel insecure protocols workbook: https://docs.microsoft.com/azure/sentinel/quickstart-get-visibility#use-built-in-workbooks | n/a | link | count: 002 App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193) |
App Service | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | PA-1 | Azure_Security_Benchmark_v3.0_PA-1 | Microsoft cloud security benchmark PA-1 | Privileged Access | Separate and limit highly privileged/administrative users | Shared | **Security Principle:** Ensure you are identifying all high business impact accounts. Limit the number of privileged/administrative accounts in your cloud's control plane, management plane and data/workload plane. **Azure Guidance:** Microsoft Entra ID is Azure's default identity and access management service. The most critical built-in roles in Microsoft Entra ID are Global Administrator and Privileged Role Administrator, because users assigned to these two roles can delegate administrator roles. With these privileges, users can directly or indirectly read and modify every resource in your Azure environment: - Global Administrator / Company Administrator: Users with this role have access to all administrative features in Microsoft Entra ID, as well as services that use Microsoft Entra identities. - Privileged Role Administrator: Users with this role can manage role assignments in Microsoft Entra ID, as well as within Microsoft Entra Privileged Identity Management (PIM). In addition, this role allows management of all aspects of PIM and administrative units. Outside of the Microsoft Entra ID, Azure has built-in roles that can be critical for privileged access at the resource level. - Owner: Grants full access to manage all resources, including the ability to assign roles in Azure RBAC. - Contributor: Grants full access to manage all resources, but does not allow you to assign roles in Azure RBAC, manage assignments in Azure Blueprints, or share image galleries. - User Access Administrator: Lets you manage user access to Azure resources. Note: You may have other critical roles that need to be governed if you use custom roles in the Microsoft Entra ID level or resource level with certain privileged permissions assigned. Ensure that you also restrict privileged accounts in other management, identity, and security systems that have administrative access to your business-critical assets, such as Active Directory Domain Controllers (DCs), security tools, and system management tools with agents installed on business critical systems. Attackers who compromise these management and security systems can immediately weaponize them to compromise business critical assets. **Implementation and additional context:** Administrator role permissions in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles Use Azure Privileged Identity Management security alerts: https://docs.microsoft.com/azure/active-directory/privileged-identity-management/pim-how-to-configure-security-alerts Securing privileged access for hybrid and cloud deployments in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-admin-roles-secure | n/a | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | PA-2 | Azure_Security_Benchmark_v3.0_PA-2 | Microsoft cloud security benchmark PA-2 | Privileged Access | Avoid standing access for accounts and permissions | Shared | **Security Principle:** Instead of creating standing privileges, use just-in-time (JIT) mechanism to assign privileged access to the different resource tiers. **Azure Guidance:** Enable just-in-time (JIT) privileged access to Azure resources and Microsoft Entra ID using Microsoft Entra Privileged Identity Management (PIM). JIT is a model in which users receive temporary permissions to perform privileged tasks, which prevents malicious or unauthorized users from gaining access after the permissions have expired. Access is granted only when users need it. PIM can also generate security alerts when there is suspicious or unsafe activity in your Microsoft Entra ID organization. Restrict inbound traffic to your sensitive virtual machines (VM) management ports with Microsoft Defender for Cloud's just-in-time (JIT) for VM access feature. This ensures the privileged access to the VM are granted only when users need it. **Implementation and additional context:** Azure PIM just-in-time access deployment: https://docs.microsoft.com/azure/active-directory/privileged-identity-management/pim-deployment-plan | n/a | link | count: 001 Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | PA-4 | Azure_Security_Benchmark_v3.0_PA-4 | Microsoft cloud security benchmark PA-4 | Privileged Access | Review and reconcile user access regularly | Shared | **Security Principle:** Conduct regular review of privileged account entitlements. Ensure the access granted to the accounts are valid for administration of control plane, management plane, and workloads. **Azure Guidance:** Review all privileged accounts and the access entitlements in Azure including such as Azure tenant, Azure services, VM/IaaS, CI/CD processes, and enterprise management and security tools. Use Microsoft Entra access reviews to review Microsoft Entra roles and Azure resource access roles, group memberships, access to enterprise applications. Microsoft Entra reporting can also provide logs to help discover stale accounts, accounts not being used for certain amount of time. In addition, Microsoft Entra Privileged Identity Management can be configured to alert when an excessive number of administrator accounts are created for a specific role, and to identify administrator accounts that are stale or improperly configured. **Implementation and additional context:** Create an access review of Azure resource roles in Privileged Identity Management (PIM): https://docs.microsoft.com/azure/active-directory/privileged-identity-management/pim-resource-roles-start-access-review How to use Microsoft Entra identity and access reviews: https://docs.microsoft.com/azure/active-directory/governance/access-reviews-overview | n/a | link | count: 005 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | PA-7 | Azure_Security_Benchmark_v3.0_PA-7 | Microsoft cloud security benchmark PA-7 | Privileged Access | Follow just enough administration (least privilege) principle | Shared | **Security Principle:** Follow the just enough administration (least privilege) principle to manage permissions at fine-grained level. Use features such as role-based access control (RBAC) to manage resource access through role assignments. **Azure Guidance:** Use Azure role-based access control (Azure RBAC) to manage Azure resource access through role assignments. Through RBAC, you can assign roles to users, group service principals, and managed identities. There are pre-defined built-in roles for certain resources, and these roles can be inventoried or queried through tools such as Azure CLI, Azure PowerShell, and the Azure portal. The privileges you assign to resources through Azure RBAC should always be limited to what's required by the roles. Limited privileges will complement the just-in-time (JIT) approach of Microsoft Entra Privileged Identity Management (PIM), and those privileges should be reviewed periodically. If required, you can also use PIM to define the time-length (time-bound-assignment) condition in role assignment where a user can activate or use the role only within start and end dates. Note: Use Azure built-in roles to allocate permissions and only create custom roles when required. **Implementation and additional context:** What is Azure role-based access control (Azure RBAC): https://docs.microsoft.com/azure/role-based-access-control/overview How to configure RBAC in Azure: https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal How to use Microsoft Entra identity and access reviews: https://docs.microsoft.com/azure/active-directory/governance/access-reviews-overview Microsoft Entra Privileged Identity Management - Time-bound assignment: https://docs.microsoft.com/azure/active-directory/privileged-identity-management/pim-configure#what-does-it-do | n/a | link | count: 003 API Management subscriptions should not be scoped to all APIs (3aa03346-d8c5-4994-a5bc-7652c2a2aef1), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
API Management, General, Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | PV-2 | Azure_Security_Benchmark_v3.0_PV-2 | Microsoft cloud security benchmark PV-2 | Posture and Vulnerability Management | Audit and enforce secure configurations | Shared | **Security Principle:** Continuously monitor and alert when there is a deviation from the defined configuration baseline. Enforce the desired configuration according to the baseline configuration by denying the non-compliant configuration or deploy a configuration. **Azure Guidance:** Use Microsoft Defender for Cloud to configure Azure Policy to audit and enforce configurations of your Azure resources. Use Azure Monitor to create alerts when there is a configuration deviation detected on the resources. Use Azure Policy [deny] and [deploy if not exist] rule to enforce secure configuration across Azure resources. For resource configuration audit and enforcement not supported by Azure Policy, you may need to write your own scripts or use third-party tooling to implement the configuration audit and enforcement. **Implementation and additional context:** Understand Azure Policy effects: https://docs.microsoft.com/azure/governance/policy/concepts/effects Create and manage policies to enforce compliance: https://docs.microsoft.com/azure/governance/policy/tutorials/create-and-manage Get compliance data of Azure resources: https://docs.microsoft.com/azure/governance/policy/how-to/get-compliance-data | n/a | link | count: 027 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), API Management direct management endpoint should not be enabled (b741306c-968e-4b67-b916-5675e5c709f4), API Management minimum API version should be set to 2019-12-01 or higher (549814b6-3212-4203-bdc8-1548d342fb67), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure API Management platform version should be stv2 (1dc2fc00-2245-4143-99f4-874c937f13ef), Azure Arc enabled Kubernetes clusters should have the Azure Policy extension installed (6b2122c1-8120-4ff5-801b-17625a355590), Azure Machine Learning compute instances should be recreated to get the latest software updates (f110a506-2dcb-422e-bcea-d533fc8c35e2), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should disable automounting API credentials (423dd1ba-798e-40e4-9c4d-b6902674b423), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Kubernetes clusters should not grant CAP_SYS_ADMIN security capabilities (d2e7ea85-6b44-4317-a0be-1b951587f626), Kubernetes clusters should not use the default namespace (9f061a12-e40d-4183-a00e-171812443373) |
API Management, App Service, Kubernetes, Machine Learning | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | PV-4 | Azure_Security_Benchmark_v3.0_PV-4 | Microsoft cloud security benchmark PV-4 | Posture and Vulnerability Management | Audit and enforce secure configurations for compute resources | Shared | **Security Principle:** Continuously monitor and alert when there is a deviation from the defined configuration baseline in your compute resources. Enforce the desired configuration according to the baseline configuration by denying the non-compliant configuration or deploy a configuration in compute resources. **Azure Guidance:** Use Microsoft Defender for Cloud and Azure Policy guest configuration agent to regularly assess and remediate configuration deviations on your Azure compute resources, including VMs, containers, and others. In addition, you can use Azure Resource Manager templates, custom operating system images, or Azure Automation State Configuration to maintain the security configuration of the operating system. Microsoft VM templates in conjunction with Azure Automation State Configuration can assist in meeting and maintaining security requirements. Note: Azure Marketplace VM images published by Microsoft are managed and maintained by Microsoft. **Implementation and additional context:** How to implement Microsoft Defender for Cloud vulnerability assessment recommendations: https://docs.microsoft.com/azure/security-center/security-center-vulnerability-assessment-recommendations How to create an Azure virtual machine from an ARM template: https://docs.microsoft.com/azure/virtual-machines/windows/ps-template Azure Automation State Configuration overview: https://docs.microsoft.com/azure/automation/automation-dsc-overview Create a Windows virtual machine in the Azure portal: https://docs.microsoft.com/azure/virtual-machines/windows/quick-create-portal Container security in Microsoft Defender for Cloud: https://docs.microsoft.com/azure/security-center/container-security | n/a | link | count: 013 [Preview]: Azure Stack HCI servers should have consistently enforced application control policies (dad3a6b9-4451-492f-a95c-69efc6f3fada), [Preview]: Azure Stack HCI servers should meet Secured-core requirements (5e6bf724-0154-49bc-985f-27b2e07e636b), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines (672fe5a1-2fcd-42d7-b85d-902b6e28c6ff), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines scale sets (a21f8c92-9e22-4f09-b759-50500d1d2dda), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines (1cb4d9c2-f88f-4069-bee0-dba239a57b09), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines scale sets (f655e522-adff-494d-95c2-52d4f6d56a42), [Preview]: Linux virtual machines should use only signed and trusted boot components (13a6c84f-49a5-410a-b5df-5b880c3fe009), [Preview]: Secure Boot should be enabled on supported Windows virtual machines (97566dd7-78ae-4997-8b36-1c7bfe0d8121), [Preview]: vTPM should be enabled on supported virtual machines (1c30f9cd-b84c-49cc-aa2c-9288447cc3b3), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
Guest Configuration, Security Center, Stack HCI | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | PV-5 | Azure_Security_Benchmark_v3.0_PV-5 | Microsoft cloud security benchmark PV-5 | Posture and Vulnerability Management | Perform vulnerability assessments | Shared | **Security Principle:** Perform vulnerabilities assessment for your cloud resources at all tiers in a fixed schedule or on-demand. Track and compare the scan results to verify the vulnerabilities are remediated. The assessment should include all type of vulnerabilities, such as vulnerabilities in Azure services, network, web, operating systems, misconfigurations, and so on. Be aware of the potential risks associated with the privileged access used by the vulnerability scanners. Follow the privileged access security best practice to secure any administrative accounts used for the scanning. **Azure Guidance:** Follow recommendations from Microsoft Defender for Cloud for performing vulnerability assessments on your Azure virtual machines, container images, and SQL servers. Microsoft Defender for Cloud has a built-in vulnerability scanner for virtual machine scan. Use a third-party solution for performing vulnerability assessments on network devices and applications (e.g., web applications) Export scan results at consistent intervals and compare the results with previous scans to verify that vulnerabilities have been remediated. When using vulnerability management recommendations suggested by Microsoft Defender for Cloud, you can pivot into the selected scan solution's portal to view historical scan data. When conducting remote scans, do not use a single, perpetual, administrative account. Consider implementing JIT (Just In Time) provisioning methodology for the scan account. Credentials for the scan account should be protected, monitored, and used only for vulnerability scanning. Note: Azure Defender services (including Defender for server, container registry, App Service, SQL, and DNS) embed certain vulnerability assessment capabilities. The alerts generated from Azure Defender services should be monitored and reviewed together with the result from Microsoft Defender for Cloud vulnerability scanning tool. Note: Ensure your setup email notifications in Microsoft Defender for Cloud. **Implementation and additional context:** How to implement Microsoft Defender for Cloud vulnerability assessment recommendations: https://docs.microsoft.com/azure/security-center/security-center-vulnerability-assessment-recommendations Integrated vulnerability scanner for virtual machines: https://docs.microsoft.com/azure/security-center/built-in-vulnerability-assessment SQL vulnerability assessment: https://docs.microsoft.com/azure/azure-sql/database/sql-vulnerability-assessment Exporting Microsoft Defender for Cloud vulnerability scan results: https://docs.microsoft.com/azure/security-center/built-in-vulnerability-assessment#exporting-results | n/a | link | count: 004 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Machines should have secret findings resolved (3ac7c827-eea2-4bde-acc7-9568cd320efa), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| Azure_Security_Benchmark_v3.0 | PV-6 | Azure_Security_Benchmark_v3.0_PV-6 | Microsoft cloud security benchmark PV-6 | Posture and Vulnerability Management | Rapidly and automatically remediate vulnerabilities | Shared | **Security Principle:** Rapidly and automatically deploy patches and updates to remediate vulnerabilities in your cloud resources. Use the appropriate risk-based approach to prioritize the remediation of the vulnerabilities. For example, more severe vulnerabilities in a higher value asset should be addressed as a higher priority. **Azure Guidance:** Use Azure Automation Update Management or a third-party solution to ensure that the most recent security updates are installed on your Windows and Linux VMs. For Windows VMs, ensure Windows Update has been enabled and set to update automatically. For third-party software, use a third-party patch management solution or System Center Updates Publisher for Configuration Manager. Prioritize which updates to deploy first using a common risk scoring program (such as Common Vulnerability Scoring System) or the default risk ratings provided by your third-party scanning tool and tailor to your environment. You should also consider which applications present a high security risk and which ones require high uptime. **Implementation and additional context:** How to configure Update Management for virtual machines in Azure: https://docs.microsoft.com/azure/automation/update-management/overview Manage updates and patches for your Azure VMs: https://docs.microsoft.com/azure/automation/update-management/manage-updates-for-vm | n/a | link | count: 011 [Preview]: System updates should be installed on your machines (powered by Update Center) (f85bf3e0-d513-442e-89c3-1784ad63382b), Azure registry container images should have vulnerabilities resolved (powered by Microsoft Defender Vulnerability Management) (090c7b07-b4ed-4561-ad20-e9075f3ccaff), Azure running container images should have vulnerabilities resolved (powered by Microsoft Defender Vulnerability Management) (17f4b1cc-c55c-4d94-b1f9-2978f6ac2957), Machines should be configured to periodically check for missing system updates (bd876905-5b84-4f73-ab2d-2e7a7c4568d9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Azure Update Manager, Security Center | Microsoft cloud security benchmark (1f3afdf9-d0c9-4c3d-847f-89da613e70a8) |
| B.01.3 - Legal, statutory, regulatory requirements | B.01.3 - Legal, statutory, regulatory requirements | 404 not found | n/a | n/a | count: 002 Allowed locations (e56962a6-4747-49cd-b67b-bf8b01975c4c), Allowed locations for resource groups (e765b5de-1225-4ba3-bd56-1ac6695af988) |
General | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| B.09.1 - Security aspects and stages | B.09.1 - Security aspects and stages | 404 not found | n/a | n/a | count: 002 Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
Cache, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| B.10.2 - Security function | B.10.2 - Security function | 404 not found | n/a | n/a | count: 002 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| B.10.3 - Organisational position | B.10.3 - Organisational position | 404 not found | n/a | n/a | count: 002 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| B.10.4 - Tasks, responsibilities and powers | B.10.4 - Tasks, responsibilities and powers | 404 not found | n/a | n/a | count: 002 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| Boot Diagnostics | Boot Diagnostics | 404 not found | n/a | n/a | count: 001 [Preview]: Boot Diagnostics should be enabled on virtual machines (fb97d6e1-5c98-4743-a439-23e0977bad9e) |
Automanage | [Preview]: Audit configuration against Automanage Best Practices (c138fd1a-e08f-4318-9490-d11ef2c2f9c1) | |||||
| C.04.3 - Timelines | C.04.3 - Timelines | 404 not found | n/a | n/a | count: 026 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), App Service apps that use Java should use a specified 'Java version' (496223c3-ad65-4ecd-878a-bae78737e9ed), App Service apps that use PHP should use a specified 'PHP version' (7261b898-8a84-4db8-9e04-18527132abb3), App Service apps that use Python should use a specified 'Python version' (7008174a-fd10-4ef0-817e-fc820a951d73), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Function apps that use Java should use a specified 'Java version' (9d0b6ea4-93e2-4578-bf2f-6bb17d22b4bc), Function apps that use Python should use a specified 'Python version' (7238174a-fd10-4ef0-817e-fc820a951d73), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
App Service, Guest Configuration, Security Center, Synapse | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| C.04.6 - Timelines | C.04.6 - Timelines | 404 not found | n/a | n/a | count: 026 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), App Service apps that use Java should use a specified 'Java version' (496223c3-ad65-4ecd-878a-bae78737e9ed), App Service apps that use PHP should use a specified 'PHP version' (7261b898-8a84-4db8-9e04-18527132abb3), App Service apps that use Python should use a specified 'Python version' (7008174a-fd10-4ef0-817e-fc820a951d73), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Machine Learning compute instances should be recreated to get the latest software updates (f110a506-2dcb-422e-bcea-d533fc8c35e2), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Function apps that use Java should use a specified 'Java version' (9d0b6ea4-93e2-4578-bf2f-6bb17d22b4bc), Function apps that use Python should use a specified 'Python version' (7238174a-fd10-4ef0-817e-fc820a951d73), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
App Service, Guest Configuration, Machine Learning, Security Center | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| C.04.7 - Evaluated | C.04.7 - Evaluated | 404 not found | n/a | n/a | count: 045 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), App Service apps that use Java should use a specified 'Java version' (496223c3-ad65-4ecd-878a-bae78737e9ed), App Service apps that use PHP should use a specified 'PHP version' (7261b898-8a84-4db8-9e04-18527132abb3), App Service apps that use Python should use a specified 'Python version' (7008174a-fd10-4ef0-817e-fc820a951d73), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Function apps that use Java should use a specified 'Java version' (9d0b6ea4-93e2-4578-bf2f-6bb17d22b4bc), Function apps that use Python should use a specified 'Python version' (7238174a-fd10-4ef0-817e-fc820a951d73), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should disable automounting API credentials (423dd1ba-798e-40e4-9c4d-b6902674b423), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Kubernetes clusters should not grant CAP_SYS_ADMIN security capabilities (d2e7ea85-6b44-4317-a0be-1b951587f626), Kubernetes clusters should not use the default namespace (9f061a12-e40d-4183-a00e-171812443373), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
App Service, Guest Configuration, Kubernetes, Security Center | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| C.04.8 - Evaluated | C.04.8 - Evaluated | 404 not found | n/a | n/a | count: 005 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Security Center | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| C.05.5 - Monitored and reported | C.05.5 - Monitored and reported | 404 not found | n/a | n/a | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| CCCS | AC-17(1) | CCCS_AC-17(1) | CCCS AC-17(1) | Access Control | Remote Access | Automated Monitoring / Control | n/a | The information system monitors and controls remote access methods. | link | count: 007 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
App Service, Guest Configuration, Storage | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | AC-2 | CCCS_AC-2 | CCCS AC-2 | Access Control | Account Management | n/a | (A) The organization identifies and selects which types of information system accounts support organizational missions/business functions. (B) The organization assigns account managers for information system accounts. (C) The organization establishes conditions for group and role membership. (D) The organization specifies authorized users of the information system, group and role membership, and access authorizations (i.e., privileges) and other attributes (as required) for each account. (E) The organization requires approvals by responsible managers for requests to create information system accounts. (F) The organization creates, enables, modifies, disables, and removes information system accounts in accordance with information system account management procedures. (G) The organization monitors the use of information system accounts. (H) The organization notifies account managers: (a) When accounts are no longer required; (b) When users are terminated or transferred; and (c) When individual information system usage or need-to-know changes. (I) The organization authorizes access to the information system based on: (a) A valid access authorization; (b) Intended system usage; and (c) Other attributes as required by the organization or associated missions/business functions. (J) The organization reviews accounts for compliance with account management requirements at least annually. (K) The organization establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group. | link | count: 005 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | AC-2(7) | CCCS_AC-2(7) | CCCS AC-2(7) | Access Control | Account Management | Role-Based Schemes | n/a | (a) The organization establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles; (b) The organization monitors privileged role assignments; and (c) The organization disables (or revokes) privileged user assignments within 24 hours or sooner when privileged role assignments are no longer appropriate. | link | count: 002 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
Service Fabric, SQL | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | AC-4 | CCCS_AC-4 | CCCS AC-4 | Access Control | Information Flow Enforcement | n/a | (A) The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems based on deny all, approve by exception information flow policies. | link | count: 001 App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9) |
App Service | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | AC-5 | CCCS_AC-5 | CCCS AC-5 | Access Control | Separation of Duties | n/a | (A) The organization: (a) Separate organization-defined duties of individuals including at least separation of operational, development, security monitoring, and management functions; (b) Documents separation of duties of individuals; and (c) Defines information system access authorizations to support separation of duties. | link | count: 007 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | AC-6 | CCCS_AC-6 | CCCS AC-6 | Access Control | Least Privilege | n/a | (A) The organization employs the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions. | link | count: 007 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | AU-12 | CCCS_AU-12 | CCCS AU-12 | Audit and Accountability | Audit Generation | n/a | (A) The information system provides audit record generation capability for the auditable events defined in AU-2 a. of all information system and network components where audit capability is deployed/available. (B) The information system allows organization-defined personnel or roles to select which auditable events are to be audited by specific components of the information system. (C) The information system generates audit records for the events defined in AU-2 d. with the content defined in AU-3. | link | count: 007 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917) |
Monitoring, SQL | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | AU-3 | CCCS_AU-3 | CCCS AU-3 | Audit and Accountability | Content of Audit Records | n/a | (A) The information system generates audit records containing information that establishes what type of event occurred, when the event occurred, where the event occurred, the source of the event, the outcome of the event, and the identity of any individuals or subjects associated with the event. | link | count: 003 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917) |
Monitoring | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | AU-5 | CCCS_AU-5 | CCCS AU-5 | Audit and Accountability | Response to Audit Processing Failures | n/a | (A) The information system alerts organization-defined personnel or roles in the event of an audit processing failure; and (B) The information system overwrites the oldest audit records. | link | count: 004 Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
Monitoring, SQL | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | CM-11 | CCCS_CM-11 | CCCS CM-11 | Configuration Management | User-Installed Software | n/a | (A) The organization establishes organization-defined policies governing the installation of software by users. (B) The organization enforces software installation policies through organization-defined methods. (C) The organization monitors policy compliance continuously via 7(5). | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | CM-7(5) | CCCS_CM-7(5) | CCCS CM-7(5) | Configuration Management | Least Functionality | Authorized Software / Whitelisting | n/a | (a) The organization identifie authorized software programs in baseline configuration and information system component inventory; (b) The organization employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the information system; and (c) The organization reviews and updates the list of authorized software programs at least annually or when there is a change. | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | CP-7 | CCCS_CP-7 | CCCS CP-7 | Contingency Planning | Alternative Processing Site | n/a | (A) The organization establishes an alternate processing site including necessary agreements to permit the transfer and resumption of organization-defined information system operations for essential missions/business functions within organization-defined time period consistent with recovery time and recovery point objectives when the primary processing capabilities are unavailable. (B) The organization ensures that equipment and supplies required to transfer and resume operations are available at the alternate processing site or contracts are in place to support delivery to the site within the organization-defined time period for transfer/resumption. (C) The organization ensures that the alternate processing site provides information security safeguards equivalent to that of the primary site. | link | count: 001 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56) |
Compute | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | IA-2(1) | CCCS_IA-2(1) | CCCS IA-2(1) | Identification and Authentication | Identification and Authentication (Organizational Users) | Network Access to Privileged Accounts | n/a | The information system implements multifactor authentication for network access to privileged accounts. | link | count: 002 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | IA-5 | CCCS_IA-5 | CCCS IA-5 | Identification and Authentication | Authenticator Management | n/a | (A) The organization manages information system authenticators by verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, or device receiving the authenticator. (B) The organization manages information system authenticators by establishing initial authenticator content for authenticators defined by the organization. (C) The organization manages information system authenticators by ensuring that authenticators have sufficient strength of mechanism for their intended use. (D) The organization manages information system authenticators by establishing and implementing administrative procedures for initial authenticator distribution, for lost/compromised or damaged authenticators, and for revoking authenticators. (E) The organization manages information system authenticators by changing the default content of authenticators prior to information system installation. (F) The organization manages information system authenticators by establishing minimum and maximum lifetime restrictions and reuse conditions for authenticators. (G) The organization manages information system authenticators by changing/refreshing authenticators in accordance with CCCS’s ITSP.30.031. (H) The organization manages information system authenticators by protecting authenticator content from unauthorized disclosure and modification. (I) The organization manages information system authenticators by requiring individuals to take, and having devices implement, specific security safeguards to protect authenticators. (J) The organization manages information system authenticators by changing authenticators for group/role accounts when membership to those accounts changes. | link | count: 005 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da) |
Guest Configuration | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | IA-5(1) | CCCS_IA-5(1) | CCCS IA-5(1) | Identification and Authentication | Authenticator Management | Password-Based Authentication | n/a | (a) The information system, for password-based authentication, enforces minimum password complexity of case sensitive, minimum of eight characters, and at least one each of upper-case letters, lower-case letters, numbers, and special characters; (b) The information system, for password-based authentication, enforces that at least one of the characters are changed when new passwords are created; (c) The information system, for password-based authentication, stores and transmits only cryptographically-protected passwords; (d) The information system, for password-based authentication, enforces password minimum and maximum lifetime restrictions of one-day minimum, sixty-day maximum; (e) The information system, for password-based authentication prohibits password reuse for 24 generations; and (f) The information system, for password-based authentication allows the use of a temporary password for system logons with an immediate change to a permanent password. | link | count: 008 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | RA-5 | CCCS_RA-5 | CCCS RA-5 | Risk Assessment | Vulnerability Scanning | n/a | (A) The organization scans for vulnerabilities in the information system and hosted applications monthly for operating systems/infrastructure, web applications, and database management systems and when new vulnerabilities potentially affecting the system/applications are identified and reported. (B) The organization employs vulnerability scanning tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: (a) Enumerating platforms, software flaws, and improper configurations; (b) Formatting checklists and test procedures; and (c) Measuring vulnerability impact. (C) The organization analyzes vulnerability scan reports and results from security control assessments. (D) The organization remediates legitimate vulnerabilities within 30 days for high-risk vulnerabilities and 90 days for moderate-risk vulnerabilities from the date of discovery in accordance with an organizational assessment of risk. (E) The organization shares information obtained from the vulnerability scanning process and security control assessments with organization-defined personnel or roles to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies). | link | count: 006 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center, SQL | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SC-28 | CCCS_SC-28 | CCCS SC-28 | System and Communications Protection | Protection of Information at Rest | n/a | (A) The information system protects the confidentiality and integrity ofall information not cleared for public release and all data with a higher than low integrity requirement. | link | count: 004 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Security Center, SQL | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SC-5 | CCCS_SC-5 | CCCS SC-5 | System and Communications Protection | Denial of Service Protection | n/a | (A) The information system protects against or limits the effects of the following denial of service attempts that attack bandwidth, transactional capacity and storage by employing geo-replication, IP address blocking, and network-based DDoS protections. | link | count: 001 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SC-7 | CCCS_SC-7 | CCCS SC-7 | System and Communications Protection | Boundary Protection | n/a | (A) The information system monitors and controls communications at the external boundary of the system and at key internal boundaries within the system. (B) The information system implements sub-networks for publicly accessible system components that are physically or logically separated from internal organizational networks. (C) The information system connects to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture. | link | count: 003 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Security Center, Storage | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SC-7(3) | CCCS_SC-7(3) | CCCS SC-7(3) | System and Communications Protection | Boundary Protection | Access Points | n/a | The organization limits the number of external network connections to the information system. | link | count: 001 Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SC-7(4) | CCCS_SC-7(4) | CCCS SC-7(4) | System and Communications Protection | Boundary Protection | External Telecommunications Services | n/a | (a) The organization implements a managed interface for each external telecommunication service; (b) The organization establishes a traffic flow policy for each managed interface; (c) The organization protects the confidentiality and integrity of the information being transmitted across each interface; (d) The organization documents each exception to the traffic flow policy with a supporting mission/business need and duration of that need; and (e) The organization reviews exceptions to the traffic flow policy at least annually and removes exceptions that are no longer supported by an explicit mission/business need. | link | count: 001 Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SC-8(1) | CCCS_SC-8(1) | CCCS SC-8(1) | System and Communications Protection | Transmission Confidentiality and Integrity | Cryptographic or Alternate Physical Protection | n/a | The information system implements cryptographic mechanisms to prevent unauthorized disclosure of information and detect changes to information during transmission unless otherwise protected by physical security safeguards applied in applied in accordance with, or uses an adequate risk-based approach aligned with the practices specified in TBS and RCMP physical security standards and any related provisions of the Industrial Security Program. The cryptography must be compliant with the requirements of control SC-13. | link | count: 005 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, Storage | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SI-2 | CCCS_SI-2 | CCCS SI-2 | System and Information Integrity | Flaw Remediation | n/a | (A) The organization identifies, reports, and corrects information system flaws. (B) The organization tests software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation. (C) The organization installs security-relevant software and firmware updates within 30 days of release of the release of the updates. (D) The organization incorporates flaw remediation into the organizational configuration management process. | link | count: 005 SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SI-3 | CCCS_SI-3 | CCCS SI-3 | System and Information Integrity | Malicious Code Protection | n/a | (A) The organization employs malicious code protection mechanisms at information system entry and exit points to detect and eradicate malicious code. (B) The organization updates malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures. (C) The organization configures malicious code protection mechanisms to: (a) Perform periodic scans of the information system at least weekly and real-time scans of files from external sources at endpoints and network entry/exit points as the files are downloaded, opened, or executed in accordance with organizational security policy; and (b) Block and quarantine malicious code; send alert to the key role as defined in the system and information integrity policy in response to malicious code detection. (D) The organization addresses the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the information system. | link | count: 002 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SI-3(1) | CCCS_SI-3(1) | CCCS SI-3(1) | System and Information Integrity | Malicious Code Protection | Central Management | n/a | The organization centrally manages malicious code protection mechanisms. | link | count: 002 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Security Center | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CCCS | SI-4 | CCCS_SI-4 | CCCS SI-4 | System and Information Integrity | Information System Monitoring | n/a | (A) The organization monitors the information system to detect: (a) Attacks and indicators of potential attacks in accordance with organization-defined monitoring objectives; and (b) Unauthorized local, network, and remote connections; (B) The organization identifies unauthorized use of the information system through organization-defined techniques and methods. (C) The organization deploys monitoring devices: (i) strategically within the information system to collect organization-determined essential information; and (ii) at ad hoc locations within the system to track specific types of transactions of interest to the organization. (D) The organization protects information obtained from intrusion-monitoring tools from unauthorized access, modification, and deletion. (E) The organization heightens the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or Canada based on law enforcement information, intelligence information, or other credible sources of information. (F) The organization obtains legal opinion with regard to information system monitoring activities in accordance with orgnanizational policies, directives and standards. (G) The organization provides organization-defined information system monitoring information to organization-defined personnel or roles at an organization-defined frequency. | link | count: 005 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917) |
Monitoring, SQL | Canada Federal PBMM (4c4a5f27-de81-430b-b4e5-9cbd50595a87) | |
| CIS_Azure_1.1.0 | 1.1 | CIS_Azure_1.1.0_1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 1.1 | 1 Identity and Access Management | Ensure that multi-factor authentication is enabled for all privileged users | Shared | The customer is responsible for implementing this recommendation. | Enable multi-factor authentication for all user credentials who have write access to Azure resources. These include roles like - Service Co-Administrators - Subscription Owners - Contributors | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.10 | CIS_Azure_1.1.0_1.10 | CIS Microsoft Azure Foundations Benchmark recommendation 1.10 | 1 Identity and Access Management | Ensure that 'Users can add gallery apps to their Access Panel' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Require administrators to provide consent for the apps before use. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.11 | CIS_Azure_1.1.0_1.11 | CIS Microsoft Azure Foundations Benchmark recommendation 1.11 | 1 Identity and Access Management | Ensure that 'Users can register applications' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Require administrators to register third-party applications. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.12 | CIS_Azure_1.1.0_1.12 | CIS Microsoft Azure Foundations Benchmark recommendation 1.12 | 1 Identity and Access Management | Ensure that 'Guest user permissions are limited' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Limit guest user permissions. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.13 | CIS_Azure_1.1.0_1.13 | CIS Microsoft Azure Foundations Benchmark recommendation 1.13 | 1 Identity and Access Management | Ensure that 'Members can invite' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict invitations to administrators only. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.14 | CIS_Azure_1.1.0_1.14 | CIS Microsoft Azure Foundations Benchmark recommendation 1.14 | 1 Identity and Access Management | Ensure that 'Guests can invite' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict guest invitations. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.15 | CIS_Azure_1.1.0_1.15 | CIS Microsoft Azure Foundations Benchmark recommendation 1.15 | 1 Identity and Access Management | Ensure that 'Restrict access to Azure AD administration portal' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Restrict access to the Azure AD administration portal to administrators only. | link | count: 007 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.16 | CIS_Azure_1.1.0_1.16 | CIS Microsoft Azure Foundations Benchmark recommendation 1.16 | 1 Identity and Access Management | Ensure that 'Self-service group management enabled' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict group creation to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.17 | CIS_Azure_1.1.0_1.17 | CIS Microsoft Azure Foundations Benchmark recommendation 1.17 | 1 Identity and Access Management | Ensure that 'Users can create security groups' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict security group creation to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.18 | CIS_Azure_1.1.0_1.18 | CIS Microsoft Azure Foundations Benchmark recommendation 1.18 | 1 Identity and Access Management | Ensure that 'Users who can manage security groups' is set to 'None' | Shared | The customer is responsible for implementing this recommendation. | Restrict security group management to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.19 | CIS_Azure_1.1.0_1.19 | CIS Microsoft Azure Foundations Benchmark recommendation 1.19 | 1 Identity and Access Management | Ensure that 'Users can create Office 365 groups' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict Office 365 group creation to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.2 | CIS_Azure_1.1.0_1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 1.2 | 1 Identity and Access Management | Ensure that multi-factor authentication is enabled for all non-privileged users | Shared | The customer is responsible for implementing this recommendation. | Enable multi-factor authentication for all non-privileged users. | link | count: 002 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.20 | CIS_Azure_1.1.0_1.20 | CIS Microsoft Azure Foundations Benchmark recommendation 1.20 | 1 Identity and Access Management | Ensure that 'Users who can manage Office 365 groups' is set to 'None' | Shared | The customer is responsible for implementing this recommendation. | Restrict Office 365 group management to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.22 | CIS_Azure_1.1.0_1.22 | CIS Microsoft Azure Foundations Benchmark recommendation 1.22 | 1 Identity and Access Management | Ensure that 'Require Multi-Factor Auth to join devices' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Joining devices to the active directory should require Multi-factor authentication. | link | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.23 | CIS_Azure_1.1.0_1.23 | CIS Microsoft Azure Foundations Benchmark recommendation 1.23 | 1 Identity and Access Management | Ensure that no custom subscription owner roles are created | Shared | The customer is responsible for implementing this recommendation. | Subscription ownership should not include permission to create custom owner roles. The principle of least privilege should be followed and only necessary privileges should be assigned instead of allowing full administrative access. | link | count: 006 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.3 | CIS_Azure_1.1.0_1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 1.3 | 1 Identity and Access Management | Ensure that there are no guest users | Shared | The customer is responsible for implementing this recommendation. | Do not add guest users if not needed. | link | count: 008 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.4 | CIS_Azure_1.1.0_1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 1.4 | 1 Identity and Access Management | Ensure that 'Allow users to remember multi-factor authentication on devices they trust' is 'Disabled' | Shared | The customer is responsible for implementing this recommendation. | Do not allow users to remember multi-factor authentication on devices. | link | count: 003 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.6 | CIS_Azure_1.1.0_1.6 | CIS Microsoft Azure Foundations Benchmark recommendation 1.6 | 1 Identity and Access Management | Ensure that 'Number of days before users are asked to re-confirm their authentication information' is not set to '0' | Shared | The customer is responsible for implementing this recommendation. | Ensure that the number of days before users are asked to re-confirm their authentication information is not set to 0. | link | count: 004 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.7 | CIS_Azure_1.1.0_1.7 | CIS Microsoft Azure Foundations Benchmark recommendation 1.7 | 1 Identity and Access Management | Ensure that 'Notify users on password resets?' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Ensure that users are notified on their primary and secondary emails on password resets. | link | count: 005 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.8 | CIS_Azure_1.1.0_1.8 | CIS Microsoft Azure Foundations Benchmark recommendation 1.8 | 1 Identity and Access Management | Ensure that 'Notify all admins when other admins reset their password?' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Ensure that all administrators are notified if any other administrator resets their password. | link | count: 010 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 1.9 | CIS_Azure_1.1.0_1.9 | CIS Microsoft Azure Foundations Benchmark recommendation 1.9 | 1 Identity and Access Management | Ensure that 'Users can consent to apps accessing company data on their behalf' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Require administrators to provide consent for the apps before use. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.1 | CIS_Azure_1.1.0_2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1 | 2 Security Center | Ensure that standard pricing tier is selected | Shared | The customer is responsible for implementing this recommendation. | The standard pricing tier enables threat detection for networks and virtual machines, providing threat intelligence, anomaly detection, and behavior analytics in the Azure Security Center. | link | count: 015 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.10 | CIS_Azure_1.1.0_2.10 | CIS Microsoft Azure Foundations Benchmark recommendation 2.10 | 2 Security Center | Ensure ASC Default policy setting "Monitor Vulnerability Assessment" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable vulnerability assessment recommendations for virtual machines. | link | count: 001 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9) |
Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.11 | CIS_Azure_1.1.0_2.11 | CIS Microsoft Azure Foundations Benchmark recommendation 2.11 | 2 Security Center | Ensure ASC Default policy setting "Monitor Storage Blob Encryption" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable storage encryption recommendations. | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.12 | CIS_Azure_1.1.0_2.12 | CIS Microsoft Azure Foundations Benchmark recommendation 2.12 | 2 Security Center | Ensure ASC Default policy setting "Monitor JIT Network Access" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable JIT Network Access for virtual machines. | link | count: 002 Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.13 | CIS_Azure_1.1.0_2.13 | CIS Microsoft Azure Foundations Benchmark recommendation 2.13 | 2 Security Center | Ensure ASC Default policy setting "Monitor Adaptive Application Whitelisting" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable adaptive application controls. | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.14 | CIS_Azure_1.1.0_2.14 | CIS Microsoft Azure Foundations Benchmark recommendation 2.14 | 2 Security Center | Ensure ASC Default policy setting "Monitor SQL Auditing" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable SQL auditing recommendations. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.15 | CIS_Azure_1.1.0_2.15 | CIS Microsoft Azure Foundations Benchmark recommendation 2.15 | 2 Security Center | Ensure ASC Default policy setting "Monitor SQL Encryption" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable SQL encryption recommendations. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.16 | CIS_Azure_1.1.0_2.16 | CIS Microsoft Azure Foundations Benchmark recommendation 2.16 | 2 Security Center | Ensure that 'Security contact emails' is set | Shared | The customer is responsible for implementing this recommendation. | Provide a security contact email address. | link | count: 001 Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.18 | CIS_Azure_1.1.0_2.18 | CIS Microsoft Azure Foundations Benchmark recommendation 2.18 | 2 Security Center | Ensure that 'Send email notification for high severity alerts' is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Enable emailing security alerts to the security contact. | link | count: 001 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899) |
Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.19 | CIS_Azure_1.1.0_2.19 | CIS Microsoft Azure Foundations Benchmark recommendation 2.19 | 2 Security Center | Ensure that 'Send email also to subscription owners' is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Enable security alert emails to subscription owners. | link | count: 001 Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d) |
Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.2 | CIS_Azure_1.1.0_2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 2.2 | 2 Security Center | Ensure that 'Automatic provisioning of monitoring agent' is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Enable automatic provisioning of the monitoring agent to collect security data. | link | count: 003 Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.3 | CIS_Azure_1.1.0_2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 2.3 | 2 Security Center | Ensure ASC Default policy setting "Monitor System Updates" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable system updates recommendations for virtual machines. | link | count: 002 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.4 | CIS_Azure_1.1.0_2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 2.4 | 2 Security Center | Ensure ASC Default policy setting "Monitor OS Vulnerabilities" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable Monitor OS vulnerability recommendations for virtual machines. | link | count: 003 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.5 | CIS_Azure_1.1.0_2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 2.5 | 2 Security Center | Ensure ASC Default policy setting "Monitor Endpoint Protection" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable Endpoint protection recommendations for virtual machines. | link | count: 008 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.6 | CIS_Azure_1.1.0_2.6 | CIS Microsoft Azure Foundations Benchmark recommendation 2.6 | 2 Security Center | Ensure ASC Default policy setting "Monitor Disk Encryption" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable Disk encryption recommendations for virtual machines. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.7 | CIS_Azure_1.1.0_2.7 | CIS Microsoft Azure Foundations Benchmark recommendation 2.7 | 2 Security Center | Ensure ASC Default policy setting "Monitor Network Security Groups" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable Network security group recommendations for virtual machines. | link | count: 003 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.8 | CIS_Azure_1.1.0_2.8 | CIS Microsoft Azure Foundations Benchmark recommendation 2.8 | 2 Security Center | Ensure ASC Default policy setting "Monitor Web Application Firewall" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable Web application firewall recommendations for virtual machines. | link | count: 002 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 2.9 | CIS_Azure_1.1.0_2.9 | CIS Microsoft Azure Foundations Benchmark recommendation 2.9 | 2 Security Center | Ensure ASC Default policy setting "Enable Next Generation Firewall(NGFW) Monitoring" is not "Disabled" | Shared | The customer is responsible for implementing this recommendation. | Enable next generation firewall recommendations for virtual machines. | link | count: 004 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 3.1 | CIS_Azure_1.1.0_3.1 | CIS Microsoft Azure Foundations Benchmark recommendation 3.1 | 3 Storage Accounts | Ensure that 'Secure transfer required' is set to 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable data encryption in transit. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 3.2 | CIS_Azure_1.1.0_3.2 | CIS Microsoft Azure Foundations Benchmark recommendation 3.2 | 3 Storage Accounts | Ensure that storage account access keys are periodically regenerated | Shared | The customer is responsible for implementing this recommendation. | Regenerate storage account access keys periodically. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 3.3 | CIS_Azure_1.1.0_3.3 | CIS Microsoft Azure Foundations Benchmark recommendation 3.3 | 3 Storage Accounts | Ensure Storage logging is enabled for Queue service for read, write, and delete requests | Shared | The customer is responsible for implementing this recommendation. | The Storage Queue service stores messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size using version 2011-08-18 or newer. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the queues. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 3.4 | CIS_Azure_1.1.0_3.4 | CIS Microsoft Azure Foundations Benchmark recommendation 3.4 | 3 Storage Accounts | Ensure that shared access signature tokens expire within an hour | Shared | The customer is responsible for implementing this recommendation. | Expire shared access signature tokens within an hour. | link | count: 003 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 3.5 | CIS_Azure_1.1.0_3.5 | CIS Microsoft Azure Foundations Benchmark recommendation 3.5 | 3 Storage Accounts | Ensure that shared access signature tokens are allowed only over https | Shared | The customer is responsible for implementing this recommendation. | Shared access signature tokens should be allowed only over HTTPS protocol. | link | count: 003 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 3.6 | CIS_Azure_1.1.0_3.6 | CIS Microsoft Azure Foundations Benchmark recommendation 3.6 | 3 Storage Accounts | Ensure that 'Public access level' is set to Private for blob containers | Shared | The customer is responsible for implementing this recommendation. | Disable anonymous access to blob containers. | link | count: 007 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 3.7 | CIS_Azure_1.1.0_3.7 | CIS Microsoft Azure Foundations Benchmark recommendation 3.7 | 3 Storage Accounts | Ensure default network access rule for Storage Accounts is set to deny | Shared | The customer is responsible for implementing this recommendation. | Restricting default network access helps to provide a new layer of security, since storage accounts accept connections from clients on any network. To limit access to selected networks, the default action must be changed. | link | count: 001 Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Storage | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 3.8 | CIS_Azure_1.1.0_3.8 | CIS Microsoft Azure Foundations Benchmark recommendation 3.8 | 3 Storage Accounts | Ensure 'Trusted Microsoft Services' is enabled for Storage Account access | Shared | The customer is responsible for implementing this recommendation. | Some Microsoft services that interact with storage accounts operate from networks that can't be granted access through network rules. To help this type of service work as intended, allow the set of trusted Microsoft services to bypass the network rules. These services will then use strong authentication to access the storage account. If the Allow trusted Microsoft services exception is enabled, the following services: Azure Backup, Azure Site Recovery, Azure DevTest Labs, Azure Event Grid, Azure Event Hubs, Azure Networking, Azure Monitor and Azure SQL Data Warehouse (when registered in the subscription), are granted access to the storage account. | link | count: 006 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.1 | CIS_Azure_1.1.0_4.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1 | 4 Database Services | Ensure that 'Auditing' is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Enable auditing on SQL Servers. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.10 | CIS_Azure_1.1.0_4.10 | CIS Microsoft Azure Foundations Benchmark recommendation 4.10 | 4 Database Services | Ensure SQL server's TDE protector is encrypted with BYOK (Use your own key) | Shared | The customer is responsible for implementing this recommendation. | TDE with BYOK support provides increased transparency and control over the TDE Protector, increased security with an HSM-backed external service, and promotion of separation of duties. With TDE, data is encrypted at rest with a symmetric key (called the database encryption key) stored in the database or data warehouse distribution. To protect this data encryption key (DEK) in the past, only a certificate that the Azure SQL Service managed could be used. Now, with BYOK support for TDE, the DEK can be protected with an asymmetric key that is stored in the Key Vault. Key Vault is a highly available and scalable cloud-based key store which offers central key management, leverages FIPS 140-2 Level 2 validated hardware security modules (HSMs), and allows separation of management of keys and data, for additional security. Based on business needs or criticality of data/databases hosted a SQL server, it is recommended that the TDE protector is encrypted by a key that is managed by the data owner (BYOK). | link | count: 006 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.11 | CIS_Azure_1.1.0_4.11 | CIS Microsoft Azure Foundations Benchmark recommendation 4.11 | 4 Database Services | Ensure 'Enforce SSL connection' is set to 'ENABLED' for MySQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'SSL connection' on 'MYSQL' Servers. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.12 | CIS_Azure_1.1.0_4.12 | CIS Microsoft Azure Foundations Benchmark recommendation 4.12 | 4 Database Services | Ensure server parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_checkpoints' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Log checkpoints should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e43d), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.13 | CIS_Azure_1.1.0_4.13 | CIS Microsoft Azure Foundations Benchmark recommendation 4.13 | 4 Database Services | Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'SSL connection' on 'PostgreSQL' Servers. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.14 | CIS_Azure_1.1.0_4.14 | CIS Microsoft Azure Foundations Benchmark recommendation 4.14 | 4 Database Services | Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_connections' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Log connections should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e442), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.15 | CIS_Azure_1.1.0_4.15 | CIS Microsoft Azure Foundations Benchmark recommendation 4.15 | 4 Database Services | Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_disconnections' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Disconnections should be logged for PostgreSQL database servers. (eb6f77b9-bd53-4e35-a23d-7f65d5f0e446), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.16 | CIS_Azure_1.1.0_4.16 | CIS Microsoft Azure Foundations Benchmark recommendation 4.16 | 4 Database Services | Ensure server parameter 'log_duration' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_duration' on 'PostgreSQL Servers'. | link | count: 004 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.17 | CIS_Azure_1.1.0_4.17 | CIS Microsoft Azure Foundations Benchmark recommendation 4.17 | 4 Database Services | Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'connection_throttling' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Connection throttling should be enabled for PostgreSQL database servers (5345bb39-67dc-4960-a1bf-427e16b9a0bd), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.18 | CIS_Azure_1.1.0_4.18 | CIS Microsoft Azure Foundations Benchmark recommendation 4.18 | 4 Database Services | Ensure server parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_retention_days' on 'PostgreSQL Servers'. | link | count: 004 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.19 | CIS_Azure_1.1.0_4.19 | CIS Microsoft Azure Foundations Benchmark recommendation 4.19 | 4 Database Services | Ensure that Azure Active Directory Admin is configured | Shared | The customer is responsible for implementing this recommendation. | Use Azure Active Directory Authentication for authentication with SQL Database. | link | count: 004 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.2 | CIS_Azure_1.1.0_4.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2 | 4 Database Services | Ensure that 'AuditActionGroups' in 'auditing' policy for a SQL server is set properly | Shared | The customer is responsible for implementing this recommendation. | Configure the 'AuditActionGroups' property to appropriate groups to capture all the critical activities on the SQL Server and all the SQL databases hosted on the SQL server. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), SQL Auditing settings should have Action-Groups configured to capture critical activities (7ff426e2-515f-405a-91c8-4f2333442eb5) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.3 | CIS_Azure_1.1.0_4.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3 | 4 Database Services | Ensure that 'Auditing' Retention is 'greater than 90 days' | Shared | The customer is responsible for implementing this recommendation. | SQL Server Audit Retention should be configured to be greater than 90 days. | link | count: 005 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.4 | CIS_Azure_1.1.0_4.4 | CIS Microsoft Azure Foundations Benchmark recommendation 4.4 | 4 Database Services | Ensure that 'Advanced Data Security' on a SQL server is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Enable "Advanced Data Security" on critical SQL Servers. | link | count: 003 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.5 | CIS_Azure_1.1.0_4.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.5 | 4 Database Services | Ensure that 'Threat Detection types' is set to 'All' | Shared | The customer is responsible for implementing this recommendation. | Enable all types of threat detection on SQL servers. | link | count: 001 Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.6 | CIS_Azure_1.1.0_4.6 | CIS Microsoft Azure Foundations Benchmark recommendation 4.6 | 4 Database Services | Ensure that 'Send alerts to' is set | Shared | The customer is responsible for implementing this recommendation. | Provide the email address where alerts will be sent when anomalous activities are detected on SQL servers. | link | count: 003 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.7 | CIS_Azure_1.1.0_4.7 | CIS Microsoft Azure Foundations Benchmark recommendation 4.7 | 4 Database Services | Ensure that 'Email service and co-administrators' is 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable service and co-administrators to receive security alerts from the SQL server. | link | count: 003 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.8 | CIS_Azure_1.1.0_4.8 | CIS Microsoft Azure Foundations Benchmark recommendation 4.8 | 4 Database Services | Ensure that Azure Active Directory Admin is configured | Shared | The customer is responsible for implementing this recommendation. | Use Azure Active Directory Authentication for authentication with SQL Database. | link | count: 005 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 4.9 | CIS_Azure_1.1.0_4.9 | CIS Microsoft Azure Foundations Benchmark recommendation 4.9 | 4 Database Services | Ensure that 'Data encryption' is set to 'On' on a SQL Database | Shared | The customer is responsible for implementing this recommendation. | Enable Transparent Data Encryption on every SQL server. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.1.1 | CIS_Azure_1.1.0_5.1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.1 | 5 Logging and Monitoring | Ensure that a Log Profile exists | Shared | The customer is responsible for implementing this recommendation. | Enable log profile for exporting activity logs. | link | count: 005 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.1.2 | CIS_Azure_1.1.0_5.1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.2 | 5 Logging and Monitoring | Ensure that Activity Log Retention is set 365 days or greater | Shared | The customer is responsible for implementing this recommendation. | Ensure activity log retention is set for 365 days or greater. | link | count: 004 Activity log should be retained for at least one year (b02aacc0-b073-424e-8298-42b22829ee0a), Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.1.3 | CIS_Azure_1.1.0_5.1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.3 | 5 Logging and Monitoring | Ensure audit profile captures all the activities | Shared | The customer is responsible for implementing this recommendation. | The log profile should be configured to export all activities from the control/management plane. | link | count: 005 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.1.4 | CIS_Azure_1.1.0_5.1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.4 | 5 Logging and Monitoring | Ensure the log profile captures activity logs for all regions including global | Shared | The customer is responsible for implementing this recommendation. | Configure the log profile to export activities from all Azure supported regions/locations including global. | link | count: 005 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.1.5 | CIS_Azure_1.1.0_5.1.5 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.5 | 5 Logging and Monitoring | Ensure the storage container storing the activity logs is not publicly accessible | Shared | The customer is responsible for implementing this recommendation. | The storage account container containing the activity log export should not be publicly accessible. | link | count: 003 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.1.6 | CIS_Azure_1.1.0_5.1.6 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.6 | 5 Logging and Monitoring | Ensure the storage account containing the container with activity logs is encrypted with BYOK (Use Your Own Key) | Shared | The customer is responsible for implementing this recommendation. | The storage account with the activity log export container is configured to use BYOK (Use Your Own Key). | link | count: 004 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Maintain integrity of audit system (c0559109-6a27-a217-6821-5a6d44f92897), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Storage account containing the container with activity logs must be encrypted with BYOK (fbb99e8e-e444-4da0-9ff1-75c92f5a85b2) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.1.7 | CIS_Azure_1.1.0_5.1.7 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.7 | 5 Logging and Monitoring | Ensure that logging for Azure KeyVault is 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable AuditEvent logging for key vault instances to ensure interactions with key vaults are logged and available. | link | count: 006 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Resource logs in Azure Key Vault Managed HSM should be enabled (a2a5b911-5617-447e-a49e-59dbe0e0434b), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.2.1 | CIS_Azure_1.1.0_5.2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.1 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create Policy Assignment | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create Policy Assignment event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.2.2 | CIS_Azure_1.1.0_5.2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.2 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update Network Security Group | Shared | The customer is responsible for implementing this recommendation. | Create an Activity Log Alert for the "Create" or "Update Network Security Group" event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.2.3 | CIS_Azure_1.1.0_5.2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.3 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Delete Network Security Group | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Network Security Group event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.2.4 | CIS_Azure_1.1.0_5.2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.4 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update Network Security Group Rule | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create or Update Network Security Group Rule event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.2.5 | CIS_Azure_1.1.0_5.2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.5 | 5 Logging and Monitoring | Ensure that activity log alert exists for the Delete Network Security Group Rule | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Network Security Group Rule event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.2.6 | CIS_Azure_1.1.0_5.2.6 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.6 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update Security Solution | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create or Update Security Solution event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.2.7 | CIS_Azure_1.1.0_5.2.7 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.7 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Delete Security Solution | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Security Solution event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.2.8 | CIS_Azure_1.1.0_5.2.8 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.8 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update or Delete SQL Server Firewall Rule | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create or Update or Delete SQL Server Firewall Rule event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 5.2.9 | CIS_Azure_1.1.0_5.2.9 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.9 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Update Security Policy | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Update Security Policy event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 6.3 | CIS_Azure_1.1.0_6.3 | CIS Microsoft Azure Foundations Benchmark recommendation 6.3 | 6 Networking | Ensure no SQL Databases allow ingress 0.0.0.0/0 (ANY IP) | Shared | The customer is responsible for implementing this recommendation. | Ensure that no SQL Databases allow ingress from 0.0.0.0/0 (ANY IP). | link | count: 002 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 6.4 | CIS_Azure_1.1.0_6.4 | CIS Microsoft Azure Foundations Benchmark recommendation 6.4 | 6 Networking | Ensure that Network Security Group Flow Log retention period is 'greater than 90 days' | Shared | The customer is responsible for implementing this recommendation. | Network Security Group Flow Logs should be enabled and the retention period is set to greater than or equal to 90 days. | link | count: 003 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 6.5 | CIS_Azure_1.1.0_6.5 | CIS Microsoft Azure Foundations Benchmark recommendation 6.5 | 6 Networking | Ensure that Network Watcher is 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable Network Watcher for Azure subscriptions. | link | count: 002 Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Network, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 7.1 | CIS_Azure_1.1.0_7.1 | CIS Microsoft Azure Foundations Benchmark recommendation 7.1 | 7 Virtual Machines | Ensure that 'OS disk' are encrypted | Shared | The customer is responsible for implementing this recommendation. | Ensure that OS disks (boot volumes) are encrypted, where possible. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 7.2 | CIS_Azure_1.1.0_7.2 | CIS Microsoft Azure Foundations Benchmark recommendation 7.2 | 7 Virtual Machines | Ensure that 'Data disks' are encrypted | Shared | The customer is responsible for implementing this recommendation. | Ensure that data disks (non-boot volumes) are encrypted, where possible. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 7.3 | CIS_Azure_1.1.0_7.3 | CIS Microsoft Azure Foundations Benchmark recommendation 7.3 | 7 Virtual Machines | Ensure that 'Unattached disks' are encrypted | Shared | The customer is responsible for implementing this recommendation. | Ensure that unattached disks in a subscription are encrypted. | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 7.4 | CIS_Azure_1.1.0_7.4 | CIS Microsoft Azure Foundations Benchmark recommendation 7.4 | 7 Virtual Machines | Ensure that only approved extensions are installed | Shared | The customer is responsible for implementing this recommendation. | Only install organization-approved extensions on VMs. | link | count: 001 Only approved VM extensions should be installed (c0e996f8-39cf-4af9-9f45-83fbde810432) |
Compute | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 7.5 | CIS_Azure_1.1.0_7.5 | CIS Microsoft Azure Foundations Benchmark recommendation 7.5 | 7 Virtual Machines | Ensure that the latest OS Patches for all Virtual Machines are applied | Shared | The customer is responsible for implementing this recommendation. | Ensure that the latest OS patches for all virtual machines are applied. | link | count: 002 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 7.6 | CIS_Azure_1.1.0_7.6 | CIS Microsoft Azure Foundations Benchmark recommendation 7.6 | 7 Virtual Machines | Ensure that the endpoint protection for all Virtual Machines is installed | Shared | The customer is responsible for implementing this recommendation. | Install endpoint protection for all virtual machines. | link | count: 011 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 8.1 | CIS_Azure_1.1.0_8.1 | CIS Microsoft Azure Foundations Benchmark recommendation 8.1 | 8 Other Security Considerations | Ensure that the expiration date is set on all keys | Shared | The customer is responsible for implementing this recommendation. | Ensure that all keys in Azure Key Vault have an expiration time set. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 8.2 | CIS_Azure_1.1.0_8.2 | CIS Microsoft Azure Foundations Benchmark recommendation 8.2 | 8 Other Security Considerations | Ensure that the expiration date is set on all Secrets | Shared | The customer is responsible for implementing this recommendation. | Ensure that all Secrets in the Azure Key Vault have an expiration time set. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 8.3 | CIS_Azure_1.1.0_8.3 | CIS Microsoft Azure Foundations Benchmark recommendation 8.3 | 8 Other Security Considerations | Ensure that Resource Locks are set for mission critical Azure resources | Shared | The customer is responsible for implementing this recommendation. | Resource Manager Locks provide a way for administrators to lock down Azure resources to prevent deletion of, or modifications to, a resource. These locks sit outside of the Role Based Access Controls (RBAC) hierarchy and, when applied, will place restrictions on the resource for all users. These are very useful when there is have an important resource in a subscription that users should not be able to delete or change and can help prevent accidental and malicious changes or deletion. | link | count: 001 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 8.4 | CIS_Azure_1.1.0_8.4 | CIS Microsoft Azure Foundations Benchmark recommendation 8.4 | 8 Other Security Considerations | Ensure the key vault is recoverable | Shared | The customer is responsible for implementing this recommendation. | The key vault contains object keys, secrets and certificates. Accidental unavailability of a key vault can cause immediate data loss or loss of security functions (authentication, validation, verification, non-repudiation, etc.) supported by the key vault objects. It is recommended the key vault be made recoverable by enabling the "Do Not Purge" and "Soft Delete" functions. This is in order to prevent loss of encrypted data including storage accounts, SQL databases, and/or dependent services provided by key vault objects (Keys, Secrets, Certificates) etc., as may happen in the case of accidental deletion by a user or from disruptive activity by a malicious user. | link | count: 003 Azure Key Vault Managed HSM should have purge protection enabled (c39ba22d-4428-4149-b981-70acb31fc383), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 8.5 | CIS_Azure_1.1.0_8.5 | CIS Microsoft Azure Foundations Benchmark recommendation 8.5 | 8 Other Security Considerations | Enable role-based access control (RBAC) within Azure Kubernetes Services | Shared | The customer is responsible for implementing this recommendation. | Ensure that RBAC is enabled on all Azure Kubernetes Services Instances | link | count: 007 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.1 | CIS_Azure_1.1.0_9.1 | CIS Microsoft Azure Foundations Benchmark recommendation 9.1 | 9 AppService | Ensure App Service Authentication is set on Azure App Service | Shared | The customer is responsible for implementing this recommendation. | Azure App Service Authentication is a feature that can prevent anonymous HTTP requests from reaching the API app, or authenticate those that have tokens before they reach the API app. If an anonymous request is received from a browser, App Service will redirect to a logon page. To handle the logon process, a choice from a set of identity providers can be made, or a custom authentication mechanism can be implemented. | link | count: 005 App Service apps should have authentication enabled (95bccee9-a7f8-4bec-9ee9-62c3473701fc), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Function apps should have authentication enabled (c75248c1-ea1d-4a9c-8fc9-29a6aabd5da8), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.10 | CIS_Azure_1.1.0_9.10 | CIS Microsoft Azure Foundations Benchmark recommendation 9.10 | 9 AppService | Ensure that 'HTTP Version' is the latest, if used to run the web app | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for HTTP either due to security flaws or to include additional functionality. Using the latest HTTP version for web apps to take advantage of security fixes, if any, and/or new functionalities of the newer version. | link | count: 003 App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.2 | CIS_Azure_1.1.0_9.2 | CIS Microsoft Azure Foundations Benchmark recommendation 9.2 | 9 AppService | Ensure web app redirects all HTTP traffic to HTTPS in Azure App Service | Shared | The customer is responsible for implementing this recommendation. | Azure Web Apps allows sites to run under both HTTP and HTTPS by default. Web apps can be accessed by anyone using non-secure HTTP links by default. Non-secure HTTP requests can be restricted and all HTTP requests redirected to the secure HTTPS port. It is recommended to enforce HTTPS-only traffic. | link | count: 004 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.3 | CIS_Azure_1.1.0_9.3 | CIS Microsoft Azure Foundations Benchmark recommendation 9.3 | 9 AppService | Ensure web app is using the latest version of TLS encryption | Shared | The customer is responsible for implementing this recommendation. | The TLS(Transport Layer Security) protocol secures transmission of data over the internet using standard encryption technology. Encryption should be set with the latest version of TLS. App service allows TLS 1.2 by default, which is the recommended TLS level by industry standards, such as PCI DSS. | link | count: 005 App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.4 | CIS_Azure_1.1.0_9.4 | CIS Microsoft Azure Foundations Benchmark recommendation 9.4 | 9 AppService | Ensure the web app has 'Client Certificates (Incoming client certificates)' set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Client certificates allow for the app to request a certificate for incoming requests. Only clients that have a valid certificate will be able to reach the app. | link | count: 003 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.5 | CIS_Azure_1.1.0_9.5 | CIS Microsoft Azure Foundations Benchmark recommendation 9.5 | 9 AppService | Ensure that Register with Azure Active Directory is enabled on App Service | Shared | The customer is responsible for implementing this recommendation. | Managed service identity in App Service makes the app more secure by eliminating secrets from the app, such as credentials in the connection strings. When registering with Azure Active Directory in the app service, the app will connect to other Azure services securely without the need of username and passwords. | link | count: 006 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.6 | CIS_Azure_1.1.0_9.6 | CIS Microsoft Azure Foundations Benchmark recommendation 9.6 | 9 AppService | Ensure that '.Net Framework' version is the latest, if used as a part of the web app | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for .Net Framework software either due to security flaws or to include additional functionality. Using the latest .Net framework version for web apps is recommended in order to to take advantage of security fixes, if any, and/or new functionalities of the latest version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.7 | CIS_Azure_1.1.0_9.7 | CIS Microsoft Azure Foundations Benchmark recommendation 9.7 | 9 AppService | Ensure that 'PHP version' is the latest, if used to run the web app | Shared | The customer is responsible for implementing this recommendation. | Periodically newer versions are released for PHP software either due to security flaws or to include additional functionality. Using the latest PHP version for web apps is recommended in order to take advantage of security fixes, if any, and/or additional functionalities of the newer version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.8 | CIS_Azure_1.1.0_9.8 | CIS Microsoft Azure Foundations Benchmark recommendation 9.8 | 9 AppService | Ensure that 'Python version' is the latest, if used to run the web app | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for Python software either due to security flaws or to include additional functionality. Using the latest Python version for web apps is recommended in order to take advantage of security fixes, if any, and/or additional functionalities of the newer version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.1.0 | 9.9 | CIS_Azure_1.1.0_9.9 | CIS Microsoft Azure Foundations Benchmark recommendation 9.9 | 9 AppService | Ensure that 'Java version' is the latest, if used to run the web app | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for Java software either due to security flaws or to include additional functionality. Using the latest Java version for web apps is recommended in order to take advantage of security fixes, if any, and/or new functionalities of the newer version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.1.0 (1a5bb27d-173f-493e-9568-eb56638dde4d) |
| CIS_Azure_1.3.0 | 1.1 | CIS_Azure_1.3.0_1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 1.1 | 1 Identity and Access Management | Ensure that multi-factor authentication is enabled for all privileged users | Shared | The customer is responsible for implementing this recommendation. | Enable multi-factor authentication for all user credentials who have write access to Azure resources. These include roles like - Service Co-Administrators - Subscription Owners - Contributors | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.10 | CIS_Azure_1.3.0_1.10 | CIS Microsoft Azure Foundations Benchmark recommendation 1.10 | 1 Identity and Access Management | Ensure that 'Users can add gallery apps to their Access Panel' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Require administrators to provide consent for the apps before use. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.11 | CIS_Azure_1.3.0_1.11 | CIS Microsoft Azure Foundations Benchmark recommendation 1.11 | 1 Identity and Access Management | Ensure that 'Users can register applications' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Require administrators to register third-party applications. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.12 | CIS_Azure_1.3.0_1.12 | CIS Microsoft Azure Foundations Benchmark recommendation 1.12 | 1 Identity and Access Management | Ensure that 'Guest user permissions are limited' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Limit guest user permissions. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.13 | CIS_Azure_1.3.0_1.13 | CIS Microsoft Azure Foundations Benchmark recommendation 1.13 | 1 Identity and Access Management | Ensure that 'Members can invite' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict invitations to administrators only. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.14 | CIS_Azure_1.3.0_1.14 | CIS Microsoft Azure Foundations Benchmark recommendation 1.14 | 1 Identity and Access Management | Ensure that 'Guests can invite' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict guest being able to invite other guests to collaborate with your organization. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.15 | CIS_Azure_1.3.0_1.15 | CIS Microsoft Azure Foundations Benchmark recommendation 1.15 | 1 Identity and Access Management | Ensure that 'Restrict access to Azure AD administration portal' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Restrict access to the Azure AD administration portal to administrators only. | link | count: 006 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.16 | CIS_Azure_1.3.0_1.16 | CIS Microsoft Azure Foundations Benchmark recommendation 1.16 | 1 Identity and Access Management | Ensure that 'Restrict user ability to access groups features in the Access Pane' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict group creation to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.17 | CIS_Azure_1.3.0_1.17 | CIS Microsoft Azure Foundations Benchmark recommendation 1.17 | 1 Identity and Access Management | Ensure that 'Users can create security groups in Azure Portals' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict security group creation to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.18 | CIS_Azure_1.3.0_1.18 | CIS Microsoft Azure Foundations Benchmark recommendation 1.18 | 1 Identity and Access Management | Ensure that 'Owners can manage group membership requests in the Access Panel' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict security group management to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.19 | CIS_Azure_1.3.0_1.19 | CIS Microsoft Azure Foundations Benchmark recommendation 1.19 | 1 Identity and Access Management | Ensure that 'Users can create Microsoft 365 groups in Azure Portals' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict Microsoft 365 group creation to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.2 | CIS_Azure_1.3.0_1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 1.2 | 1 Identity and Access Management | Ensure that multi-factor authentication is enabled for all non-privileged users | Shared | The customer is responsible for implementing this recommendation. | Enable multi-factor authentication for all non-privileged users. | link | count: 002 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.20 | CIS_Azure_1.3.0_1.20 | CIS Microsoft Azure Foundations Benchmark recommendation 1.20 | 1 Identity and Access Management | Ensure that 'Require Multi-Factor Auth to join devices' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Joining devices to the active directory should require Multi-factor authentication. | link | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.21 | CIS_Azure_1.3.0_1.21 | CIS Microsoft Azure Foundations Benchmark recommendation 1.21 | 1 Identity and Access Management | Ensure that no custom subscription owner roles are created | Shared | The customer is responsible for implementing this recommendation. | Subscription ownership should not include permission to create custom owner roles. The principle of least privilege should be followed and only necessary privileges should be assigned instead of allowing full administrative access. | link | count: 006 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.22 | CIS_Azure_1.3.0_1.22 | CIS Microsoft Azure Foundations Benchmark recommendation 1.22 | 1 Identity and Access Management | Ensure Security Defaults is enabled on Azure Active Directory | Shared | The customer is responsible for implementing this recommendation. | Security defaults in Azure Active Directory (Azure AD) make it easier to be secure and help protect your organization. Security defaults contain preconfigured security settings for common attacks. Microsoft is making security defaults available to everyone. The goal is to ensure that all organizations have a basic level of security-enabled at no extra cost. You turn on security defaults in the Azure portal. | link | count: 009 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.23 | CIS_Azure_1.3.0_1.23 | CIS Microsoft Azure Foundations Benchmark recommendation 1.23 | 1 Identity and Access Management | Ensure Custom Role is assigned for Administering Resource Locks | Shared | The customer is responsible for implementing this recommendation. | Resource locking is a powerful protection mechanism that can prevent inadvertent modification/deletion of resources within Azure subscriptions/Resource Groups and is a recommended NIST configuration. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.3 | CIS_Azure_1.3.0_1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 1.3 | 1 Identity and Access Management | Ensure guest users are reviewed on a monthly basis | Shared | The customer is responsible for implementing this recommendation. | Azure AD is extended to include Azure AD B2B collaboration, allowing you to invite people from outside your organization to be guest users in your cloud account and sign in with their own work, school, or social identities. Guest users allow you to share your company's applications and services with users from any other organization, while maintaining control over your own corporate data. Work with external partners, large or small, even if they don't have Azure AD or an IT department. A simple invitation and redemption process lets partners use their own credentials to access your company's resources a a guest user. | link | count: 008 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.4 | CIS_Azure_1.3.0_1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 1.4 | 1 Identity and Access Management | Ensure that 'Allow users to remember multi-factor authentication on devices they trust' is 'Disabled' | Shared | The customer is responsible for implementing this recommendation. | Do not allow users to remember multi-factor authentication on devices. | link | count: 003 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.6 | CIS_Azure_1.3.0_1.6 | CIS Microsoft Azure Foundations Benchmark recommendation 1.6 | 1 Identity and Access Management | Ensure that 'Number of days before users are asked to re-confirm their authentication information' is not set to "0" | Shared | The customer is responsible for implementing this recommendation. | Ensure that the number of days before users are asked to re-confirm their authentication information is not set to 0. | link | count: 004 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.7 | CIS_Azure_1.3.0_1.7 | CIS Microsoft Azure Foundations Benchmark recommendation 1.7 | 1 Identity and Access Management | Ensure that 'Notify users on password resets?' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Ensure that users are notified on their primary and secondary emails on password resets. | link | count: 005 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.8 | CIS_Azure_1.3.0_1.8 | CIS Microsoft Azure Foundations Benchmark recommendation 1.8 | 1 Identity and Access Management | Ensure that 'Notify all admins when other admins reset their password?' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Ensure that all administrators are notified if any other administrator resets their password. | link | count: 010 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 1.9 | CIS_Azure_1.3.0_1.9 | CIS Microsoft Azure Foundations Benchmark recommendation 1.9 | 1 Identity and Access Management | Ensure that 'Users can consent to apps accessing company data on their behalf' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Require administrators to provide consent for the apps before use. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.1 | CIS_Azure_1.3.0_2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1 | 2 Security Center | Ensure that Azure Defender is set to On for Servers | Shared | The customer is responsible for implementing this recommendation. | Turning on Azure Defender enables threat detection for Server, providing threat intelligence, anomaly detection, and behavior analytics in the Azure Security Center. | link | count: 009 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.10 | CIS_Azure_1.3.0_2.10 | CIS Microsoft Azure Foundations Benchmark recommendation 2.10 | 2 Security Center | Ensure that Microsoft Cloud App Security (MCAS) integration with Security Center is selected | Shared | The customer is responsible for implementing this recommendation. | This setting enables Microsoft Cloud App Security (MCAS) integration with Security Center. | link | count: 008 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.11 | CIS_Azure_1.3.0_2.11 | CIS Microsoft Azure Foundations Benchmark recommendation 2.11 | 2 Security Center | Ensure that 'Automatic provisioning of monitoring agent' is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Enable automatic provisioning of the monitoring agent to collect security data. | link | count: 003 Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.12 | CIS_Azure_1.3.0_2.12 | CIS Microsoft Azure Foundations Benchmark recommendation 2.12 | 2 Security Center | Ensure any of the ASC Default policy setting is not set to "Disabled" | Shared | The customer is responsible for implementing this recommendation. | None of the settings offered by ASC Default policy should be set to effect "Disabled". | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.13 | CIS_Azure_1.3.0_2.13 | CIS Microsoft Azure Foundations Benchmark recommendation 2.13 | 2 Security Center | Ensure 'Additional email addresses' is configured with a security contact email | Shared | The customer is responsible for implementing this recommendation. | Security Center emails the subscription owners whenever a high-severity alert is triggered for their subscription. You should provide a security contact email address as an additional email address. | link | count: 001 Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.14 | CIS_Azure_1.3.0_2.14 | CIS Microsoft Azure Foundations Benchmark recommendation 2.14 | 2 Security Center | Ensure that 'Notify about alerts with the following severity' is set to 'High' | Shared | The customer is responsible for implementing this recommendation. | Enables emailing security alerts to the subscription owner or other designated security contact. | link | count: 001 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899) |
Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.2 | CIS_Azure_1.3.0_2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 2.2 | 2 Security Center | Ensure that Azure Defender is set to On for App Service | Shared | The customer is responsible for implementing this recommendation. | Turning on Azure Defender enables threat detection for App Service, providing threat intelligence, anomaly detection, and behavior analytics in the Azure Security Center. | link | count: 009 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.3 | CIS_Azure_1.3.0_2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 2.3 | 2 Security Center | Ensure that Azure Defender is set to On for Azure SQL database servers | Shared | The customer is responsible for implementing this recommendation. | Turning on Azure Defender enables threat detection for Azure SQL database servers, providing threat intelligence, anomaly detection, and behavior analytics in the Azure Security Center. | link | count: 009 Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.4 | CIS_Azure_1.3.0_2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 2.4 | 2 Security Center | Ensure that Azure Defender is set to On for SQL servers on machines | Shared | The customer is responsible for implementing this recommendation. | Turning on Azure Defender enables threat detection for SQL servers on machines, providing threat intelligence, anomaly detection, and behavior analytics in the Azure Security Center. | link | count: 009 Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.5 | CIS_Azure_1.3.0_2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 2.5 | 2 Security Center | Ensure that Azure Defender is set to On for Storage | Shared | The customer is responsible for implementing this recommendation. | Turning on Azure Defender enables threat detection for Storage, providing threat intelligence, anomaly detection, and behavior analytics in the Azure Security Center. | link | count: 009 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.6 | CIS_Azure_1.3.0_2.6 | CIS Microsoft Azure Foundations Benchmark recommendation 2.6 | 2 Security Center | Ensure that Azure Defender is set to On for Kubernetes | Shared | The customer is responsible for implementing this recommendation. | Turning on Azure Defender enables threat detection for Kubernetes, providing threat intelligence, anomaly detection, and behavior analytics in the Azure Security Center. | link | count: 009 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.7 | CIS_Azure_1.3.0_2.7 | CIS Microsoft Azure Foundations Benchmark recommendation 2.7 | 2 Security Center | Ensure that Azure Defender is set to On for Container Registries | Shared | The customer is responsible for implementing this recommendation. | Turning on Azure Defender enables threat detection for Container Registries, providing threat intelligence, anomaly detection, and behavior analytics in the Azure Security Center. | link | count: 009 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.8 | CIS_Azure_1.3.0_2.8 | CIS Microsoft Azure Foundations Benchmark recommendation 2.8 | 2 Security Center | Ensure that Azure Defender is set to On for Key Vault | Shared | The customer is responsible for implementing this recommendation. | Turning on Azure Defender enables threat detection for Key Vault, providing threat intelligence, anomaly detection, and behavior analytics in the Azure Security Center. | link | count: 009 Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 2.9 | CIS_Azure_1.3.0_2.9 | CIS Microsoft Azure Foundations Benchmark recommendation 2.9 | 2 Security Center | Ensure that Windows Defender ATP (WDATP) integration with Security Center is selected | Shared | The customer is responsible for implementing this recommendation. | This setting enables Windows Defender ATP (WDATP) integration with Security Center. | link | count: 008 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.1 | CIS_Azure_1.3.0_3.1 | CIS Microsoft Azure Foundations Benchmark recommendation 3.1 | 3 Storage Accounts | Ensure that 'Secure transfer required' is set to 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable data encryption in transit. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.10 | CIS_Azure_1.3.0_3.10 | CIS Microsoft Azure Foundations Benchmark recommendation 3.10 | 3 Storage Accounts | Ensure Storage logging is enabled for Blob service for read, write, and delete requests | Shared | The customer is responsible for implementing this recommendation. | The Storage Blob service provides scalable, cost-efficient objective storage in the cloud. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the blobs. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.11 | CIS_Azure_1.3.0_3.11 | CIS Microsoft Azure Foundations Benchmark recommendation 3.11 | 3 Storage Accounts | Ensure Storage logging is enabled for Table service for read, write, and delete requests | Shared | The customer is responsible for implementing this recommendation. | The Storage Table storage is a service that stores structure NoSQL data in the cloud, providing a key/attribute store with a schema less design. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the tables. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.2 | CIS_Azure_1.3.0_3.2 | CIS Microsoft Azure Foundations Benchmark recommendation 3.2 | 3 Storage Accounts | Ensure that storage account access keys are periodically regenerated | Shared | The customer is responsible for implementing this recommendation. | Regenerate storage account access keys periodically. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.3 | CIS_Azure_1.3.0_3.3 | CIS Microsoft Azure Foundations Benchmark recommendation 3.3 | 3 Storage Accounts | Ensure Storage logging is enabled for Queue service for read, write, and delete requests | Shared | The customer is responsible for implementing this recommendation. | The Storage Queue service stores messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size using version 2011-08-18 or newer. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the queues. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.4 | CIS_Azure_1.3.0_3.4 | CIS Microsoft Azure Foundations Benchmark recommendation 3.4 | 3 Storage Accounts | Ensure that shared access signature tokens expire within an hour | Shared | The customer is responsible for implementing this recommendation. | Expire shared access signature tokens within an hour. | link | count: 003 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.5 | CIS_Azure_1.3.0_3.5 | CIS Microsoft Azure Foundations Benchmark recommendation 3.5 | 3 Storage Accounts | Ensure that 'Public access level' is set to Private for blob containers | Shared | The customer is responsible for implementing this recommendation. | Disable anonymous access to blob containers and disallow blob public access on storage account. | link | count: 007 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.6 | CIS_Azure_1.3.0_3.6 | CIS Microsoft Azure Foundations Benchmark recommendation 3.6 | 3 Storage Accounts | Ensure default network access rule for Storage Accounts is set to deny | Shared | The customer is responsible for implementing this recommendation. | Restricting default network access helps to provide a new layer of security, since storage accounts accept connections from clients on any network. To limit access to selected networks, the default action must be changed. | link | count: 002 Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f) |
Storage | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.7 | CIS_Azure_1.3.0_3.7 | CIS Microsoft Azure Foundations Benchmark recommendation 3.7 | 3 Storage Accounts | Ensure 'Trusted Microsoft Services' is enabled for Storage Account access | Shared | The customer is responsible for implementing this recommendation. | Some Microsoft services that interact with storage accounts operate from networks that can't be granted access through network rules. To help this type of service work as intended, allow the set of trusted Microsoft services to bypass the network rules. These services will then use strong authentication to access the storage account. If the Allow trusted Microsoft services exception is enabled, the following services: Azure Backup, Azure Site Recovery, Azure DevTest Labs, Azure Event Grid, Azure Event Hubs, Azure Networking, Azure Monitor and Azure SQL Data Warehouse (when registered in the subscription), are granted access to the storage account. | link | count: 006 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 3.9 | CIS_Azure_1.3.0_3.9 | CIS Microsoft Azure Foundations Benchmark recommendation 3.9 | 3 Storage Accounts | Ensure storage for critical data are encrypted with Customer Managed Key | Shared | The customer is responsible for implementing this recommendation. | Enable sensitive data encryption at rest using Customer Managed Keys rather than Microsoft Managed keys | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.1.1 | CIS_Azure_1.3.0_4.1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.1 | 4 Database Services | Ensure that 'Auditing' is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Enable auditing on SQL Servers. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.1.2 | CIS_Azure_1.3.0_4.1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.2 | 4 Database Services | Ensure that 'Data encryption' is set to 'On' on a SQL Database | Shared | The customer is responsible for implementing this recommendation. | Enable Transparent Data Encryption on every SQL server. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.1.3 | CIS_Azure_1.3.0_4.1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.3 | 4 Database Services | Ensure that 'Auditing' Retention is 'greater than 90 days' | Shared | The customer is responsible for implementing this recommendation. | SQL Server Audit Retention should be configured to be greater than 90 days. | link | count: 005 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.2.1 | CIS_Azure_1.3.0_4.2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.1 | 4 Database Services | Ensure that Advanced Threat Protection (ATP) on a SQL server is set to 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable "Azure Defender for SQL" on critical SQL Servers. | link | count: 003 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.2.2 | CIS_Azure_1.3.0_4.2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.2 | 4 Database Services | Ensure that Vulnerability Assessment (VA) is enabled on a SQL server by setting a Storage Account | Shared | The customer is responsible for implementing this recommendation. | Enable Vulnerability Assessment (VA) service scans for critical SQL servers and corresponding SQL databases. | link | count: 004 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.2.3 | CIS_Azure_1.3.0_4.2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.3 | 4 Database Services | Ensure that VA setting Periodic Recurring Scans is enabled on a SQL server | Shared | The customer is responsible for implementing this recommendation. | Enable Vulnerability Assessment (VA) Periodic recurring scans for critical SQL servers and corresponding SQL databases. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.2.4 | CIS_Azure_1.3.0_4.2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.4 | 4 Database Services | Ensure that VA setting Send scan reports to is configured for a SQL server | Shared | The customer is responsible for implementing this recommendation. | Configure 'Send scan reports to' with email ids of concerned data owners/stakeholders for a critical SQL servers. | link | count: 003 Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.2.5 | CIS_Azure_1.3.0_4.2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.5 | 4 Database Services | Ensure that VA setting 'Also send email notifications to admins and subscription owners' is set for a SQL server | Shared | The customer is responsible for implementing this recommendation. | Enable Vulnerability Assessment (VA) setting 'Also send email notifications to admins and subscription owners'. | link | count: 003 Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.3.1 | CIS_Azure_1.3.0_4.3.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.1 | 4 Database Services | Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'SSL connection' on 'PostgreSQL' Servers. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.3.2 | CIS_Azure_1.3.0_4.3.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.2 | 4 Database Services | Ensure 'Enforce SSL connection' is set to 'ENABLED' for MySQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'SSL connection' on 'MYSQL' Servers. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.3.3 | CIS_Azure_1.3.0_4.3.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.3 | 4 Database Services | Ensure server parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_checkpoints' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Log checkpoints should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e43d), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.3.4 | CIS_Azure_1.3.0_4.3.4 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.4 | 4 Database Services | Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_connections' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Log connections should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e442), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.3.5 | CIS_Azure_1.3.0_4.3.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.5 | 4 Database Services | Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_disconnections' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Disconnections should be logged for PostgreSQL database servers. (eb6f77b9-bd53-4e35-a23d-7f65d5f0e446), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.3.6 | CIS_Azure_1.3.0_4.3.6 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.6 | 4 Database Services | Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'connection_throttling' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Connection throttling should be enabled for PostgreSQL database servers (5345bb39-67dc-4960-a1bf-427e16b9a0bd), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.3.7 | CIS_Azure_1.3.0_4.3.7 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.7 | 4 Database Services | Ensure server parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_retention_days' on 'PostgreSQL Servers'. | link | count: 004 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.3.8 | CIS_Azure_1.3.0_4.3.8 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.8 | 4 Database Services | Ensure 'Allow access to Azure services' for PostgreSQL Database Server is disabled | Shared | The customer is responsible for implementing this recommendation. | Disable access from Azure services to PostgreSQL Database Server | link | count: 005 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.4 | CIS_Azure_1.3.0_4.4 | CIS Microsoft Azure Foundations Benchmark recommendation 4.4 | 4 Database Services | Ensure that Azure Active Directory Admin is configured | Shared | The customer is responsible for implementing this recommendation. | Use Azure Active Directory Authentication for authentication with SQL Database. | link | count: 005 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 4.5 | CIS_Azure_1.3.0_4.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.5 | 4 Database Services | Ensure SQL server's TDE protector is encrypted with Customer-managed key | Shared | The customer is responsible for implementing this recommendation. | TDE with Customer-managed key support provides increased transparency and control over the TDE Protector, increased security with an HSM-backed external service, and promotion of separation of duties. With TDE, data is encrypted at rest with a symmetric key (called the database encryption key) stored in the database or data warehouse distribution. To protect this data encryption key (DEK) in the past, only a certificate that the Azure SQL Service managed could be used. Now, with Customer-managed key support for TDE, the DEK can be protected with an asymmetric key that is stored in the Key Vault. Key Vault is a highly available and scalable cloud-based key store which offers central key management, leverages FIPS 140-2 Level 2 validated hardware security modules (HSMs), and allows separation of management of keys and data, for additional security. Based on business needs or criticality of data/databases hosted a SQL server, it is recommended that the TDE protector is encrypted by a key that is managed by the data owner (Customer-managed key). | link | count: 006 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.1.1 | CIS_Azure_1.3.0_5.1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.1 | 5 Logging and Monitoring | Ensure that a 'Diagnostics Setting' exists | Shared | The customer is responsible for implementing this recommendation. | Enable Diagnostic settings for exporting activity logs. Diagnostic setting are available for each individual resources within a subscription. Settings should be configured for all appropriate resources for your environment. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.1.2 | CIS_Azure_1.3.0_5.1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.2 | 5 Logging and Monitoring | Ensure Diagnostic Setting captures appropriate categories | Shared | The customer is responsible for implementing this recommendation. | The diagnostic setting should be configured to log the appropriate activities from the control/management plane. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.1.3 | CIS_Azure_1.3.0_5.1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.3 | 5 Logging and Monitoring | Ensure the storage container storing the activity logs is not publicly accessible | Shared | The customer is responsible for implementing this recommendation. | The storage account container containing the activity log export should not be publicly accessible. | link | count: 003 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.1.4 | CIS_Azure_1.3.0_5.1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.4 | 5 Logging and Monitoring | Ensure the storage account containing the container with activity logs is encrypted with BYOK (Use Your Own Key) | Shared | The customer is responsible for implementing this recommendation. | The storage account with the activity log export container is configured to use BYOK (Use Your Own Key). | link | count: 004 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Maintain integrity of audit system (c0559109-6a27-a217-6821-5a6d44f92897), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Storage account containing the container with activity logs must be encrypted with BYOK (fbb99e8e-e444-4da0-9ff1-75c92f5a85b2) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.1.5 | CIS_Azure_1.3.0_5.1.5 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.5 | 5 Logging and Monitoring | Ensure that logging for Azure KeyVault is 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable AuditEvent logging for key vault instances to ensure interactions with key vaults are logged and available. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.2.1 | CIS_Azure_1.3.0_5.2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.1 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create Policy Assignment | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create Policy Assignment event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.2.2 | CIS_Azure_1.3.0_5.2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.2 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Delete Policy Assignment | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Policy Assignment event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.2.3 | CIS_Azure_1.3.0_5.2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.3 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update Network Security Group | Shared | The customer is responsible for implementing this recommendation. | Create an Activity Log Alert for the "Create" or "Update Network Security Group" event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.2.4 | CIS_Azure_1.3.0_5.2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.4 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Delete Network Security Group | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Network Security Group event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.2.5 | CIS_Azure_1.3.0_5.2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.5 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update Network Security Group Rule | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create or Update Network Security Group Rule event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.2.6 | CIS_Azure_1.3.0_5.2.6 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.6 | 5 Logging and Monitoring | Ensure that activity log alert exists for the Delete Network Security Group Rule | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Network Security Group Rule event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.2.7 | CIS_Azure_1.3.0_5.2.7 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.7 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update Security Solution | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create or Update Security Solution event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.2.8 | CIS_Azure_1.3.0_5.2.8 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.8 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Delete Security Solution | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Security Solution event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.2.9 | CIS_Azure_1.3.0_5.2.9 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.9 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update or Delete SQL Server Firewall Rule | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create or Update or Delete SQL Server Firewall Rule event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 5.3 | CIS_Azure_1.3.0_5.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | 5 Logging and Monitoring | Ensure that Diagnostic Logs are enabled for all services which support it. | Shared | The customer is responsible for implementing this recommendation. | Diagnostic Logs capture activity to the data access plane while the Activity log is a subscription-level log for the control plane. Resource-level diagnostic logs provide insight into operations that were performed within that resource itself, for example, getting a secret from a Key Vault. Currently, 32 Azure resources support Diagnostic Logging (See the references section for a complete list), including Network Security Groups, Load Balancers, Key Vault, AD, Logic Apps and CosmosDB. The content of these logs varies by resource type. For example, Windows event system logs are a category of diagnostics logs for VMs, and blob, table, and queue logs are categories of diagnostics logs for storage accounts. A number of back-end services were not configured to log and store Diagnostic Logs for certain activities or for a sufficient length. It is crucial that logging systems are correctly configured to log all relevant activities and retain those logs for a sufficient length of time. By default, Diagnostic Logs are not enabled. Given that the mean time to detection in an enterprise is 240 days, a minimum retention period of two years is recommended. Note: The CIS Benchmark covers some specific Diagnostic Logs separately. ''' 3.3 - Ensure Storage logging is enabled for Queue service for read, write, and delete requests 6.4 Ensure that Network Security Group Flow Log retention period is 'greater than 90 days' ''' | link | count: 020 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Logic Apps, Regulatory Compliance, Search, Service Bus, Stream Analytics | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 6.3 | CIS_Azure_1.3.0_6.3 | CIS Microsoft Azure Foundations Benchmark recommendation 6.3 | 6 Networking | Ensure no SQL Databases allow ingress 0.0.0.0/0 (ANY IP) | Shared | The customer is responsible for implementing this recommendation. | Ensure that no SQL Databases allow ingress from 0.0.0.0/0 (ANY IP). | link | count: 002 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 6.4 | CIS_Azure_1.3.0_6.4 | CIS Microsoft Azure Foundations Benchmark recommendation 6.4 | 6 Networking | Ensure that Network Security Group Flow Log retention period is 'greater than 90 days' | Shared | The customer is responsible for implementing this recommendation. | Network Security Group Flow Logs should be enabled and the retention period is set to greater than or equal to 90 days. | link | count: 003 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 6.5 | CIS_Azure_1.3.0_6.5 | CIS Microsoft Azure Foundations Benchmark recommendation 6.5 | 6 Networking | Ensure that Network Watcher is 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable Network Watcher for Azure subscriptions. | link | count: 002 Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Network, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 7.1 | CIS_Azure_1.3.0_7.1 | CIS Microsoft Azure Foundations Benchmark recommendation 7.1 | 7 Virtual Machines | Ensure Virtual Machines are utilizing Managed Disks | Shared | The customer is responsible for implementing this recommendation. | Migrate BLOB based VHD's to Managed Disks on Virtual Machines to exploit the default features of this configuration. The features include 1) Default Disk Encryption 2) Resilience as Microsoft will managed the disk storage and move around if underlying hardware goes faulty 3) Reduction of costs over storage accounts | link | count: 004 Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Compute, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 7.2 | CIS_Azure_1.3.0_7.2 | CIS Microsoft Azure Foundations Benchmark recommendation 7.2 | 7 Virtual Machines | Ensure that 'OS and Data' disks are encrypted with CMK | Shared | The customer is responsible for implementing this recommendation. | Ensure that OS disks (boot volumes) and data disks (non-boot volumes) are encrypted with CMK. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 7.3 | CIS_Azure_1.3.0_7.3 | CIS Microsoft Azure Foundations Benchmark recommendation 7.3 | 7 Virtual Machines | Ensure that 'Unattached disks' are encrypted with CMK | Shared | The customer is responsible for implementing this recommendation. | Ensure that unattached disks in a subscription are encrypted with a Customer Managed Key (CMK). | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 7.4 | CIS_Azure_1.3.0_7.4 | CIS Microsoft Azure Foundations Benchmark recommendation 7.4 | 7 Virtual Machines | Ensure that only approved extensions are installed | Shared | The customer is responsible for implementing this recommendation. | Only install organization-approved extensions on VMs. | link | count: 001 Only approved VM extensions should be installed (c0e996f8-39cf-4af9-9f45-83fbde810432) |
Compute | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 7.5 | CIS_Azure_1.3.0_7.5 | CIS Microsoft Azure Foundations Benchmark recommendation 7.5 | 7 Virtual Machines | Ensure that the latest OS Patches for all Virtual Machines are applied | Shared | The customer is responsible for implementing this recommendation. | Ensure that the latest OS patches for all virtual machines are applied. | link | count: 002 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 7.6 | CIS_Azure_1.3.0_7.6 | CIS Microsoft Azure Foundations Benchmark recommendation 7.6 | 7 Virtual Machines | Ensure that the endpoint protection for all Virtual Machines is installed | Shared | The customer is responsible for implementing this recommendation. | Install endpoint protection for all virtual machines. | link | count: 011 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 7.7 | CIS_Azure_1.3.0_7.7 | CIS Microsoft Azure Foundations Benchmark recommendation 7.7 | 7 Virtual Machines | Ensure that VHD's are encrypted | Shared | The customer is responsible for implementing this recommendation. | VHD (Virtual Hard Disks) are stored in BLOB storage and are the old style disks that were attached to Virtual Machines, and the BLOB VHD was then leased to the VM. By Default storage accounts are not encrypted, and Azure Defender(Security Centre) would then recommend that the OS disks should be encrypted. Storage accounts can be encrypted as a whole using PMK or CMK and this should be turned on for storage accounts containing VHD's. | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 8.1 | CIS_Azure_1.3.0_8.1 | CIS Microsoft Azure Foundations Benchmark recommendation 8.1 | 8 Other Security Considerations | Ensure that the expiration date is set on all keys | Shared | The customer is responsible for implementing this recommendation. | Ensure that all keys in Azure Key Vault have an expiration time set. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 8.2 | CIS_Azure_1.3.0_8.2 | CIS Microsoft Azure Foundations Benchmark recommendation 8.2 | 8 Other Security Considerations | Ensure that the expiration date is set on all Secrets | Shared | The customer is responsible for implementing this recommendation. | Ensure that all Secrets in the Azure Key Vault have an expiration time set. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 8.3 | CIS_Azure_1.3.0_8.3 | CIS Microsoft Azure Foundations Benchmark recommendation 8.3 | 8 Other Security Considerations | Ensure that Resource Locks are set for mission critical Azure resources | Shared | The customer is responsible for implementing this recommendation. | Resource Manager Locks provide a way for administrators to lock down Azure resources to prevent deletion of, or modifications to, a resource. These locks sit outside of the Role Based Access Controls (RBAC) hierarchy and, when applied, will place restrictions on the resource for all users. These locks are very useful when there is an important resource in a subscription that users should not be able to delete or change. Locks can help prevent accidental and malicious changes or deletion. | link | count: 001 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 8.4 | CIS_Azure_1.3.0_8.4 | CIS Microsoft Azure Foundations Benchmark recommendation 8.4 | 8 Other Security Considerations | Ensure the key vault is recoverable | Shared | The customer is responsible for implementing this recommendation. | The key vault contains object keys, secrets and certificates. Accidental unavailability of a key vault can cause immediate data loss or loss of security functions (authentication, validation, verification, non-repudiation, etc.) supported by the key vault objects. It is recommended the key vault be made recoverable by enabling the "Do Not Purge" and "Soft Delete" functions. This is in order to prevent loss of encrypted data including storage accounts, SQL databases, and/or dependent services provided by key vault objects (Keys, Secrets, Certificates) etc., as may happen in the case of accidental deletion by a user or from disruptive activity by a malicious user. | link | count: 002 Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 8.5 | CIS_Azure_1.3.0_8.5 | CIS Microsoft Azure Foundations Benchmark recommendation 8.5 | 8 Other Security Considerations | Enable role-based access control (RBAC) within Azure Kubernetes Services | Shared | The customer is responsible for implementing this recommendation. | Ensure that RBAC is enabled on all Azure Kubernetes Services Instances | link | count: 007 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.1 | CIS_Azure_1.3.0_9.1 | CIS Microsoft Azure Foundations Benchmark recommendation 9.1 | 9 AppService | Ensure App Service Authentication is set on Azure App Service | Shared | The customer is responsible for implementing this recommendation. | Azure App Service Authentication is a feature that can prevent anonymous HTTP requests from reaching the API app, or authenticate those that have tokens before they reach the API app. If an anonymous request is received from a browser, App Service will redirect to a logon page. To handle the logon process, a choice from a set of identity providers can be made, or a custom authentication mechanism can be implemented. | link | count: 005 App Service apps should have authentication enabled (95bccee9-a7f8-4bec-9ee9-62c3473701fc), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Function apps should have authentication enabled (c75248c1-ea1d-4a9c-8fc9-29a6aabd5da8), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.10 | CIS_Azure_1.3.0_9.10 | CIS Microsoft Azure Foundations Benchmark recommendation 9.10 | 9 AppService | Ensure FTP deployments are disabled | Shared | The customer is responsible for implementing this recommendation. | By default, Azure Functions, Web and API Services can be deployed over FTP. If FTP is required for an essential deployment workflow, FTPS should be required for FTP login for all App Service Apps and Functions. | link | count: 005 App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.11 | CIS_Azure_1.3.0_9.11 | CIS Microsoft Azure Foundations Benchmark recommendation 9.11 | 9 AppService | Ensure Azure Keyvaults are used to store secrets | Shared | The customer is responsible for implementing this recommendation. | Encryption keys ,Certificate thumbprints and Managed Identity Credentials can be coded into the APP service, this renders them visible as part of the configuration, to maintain security of these keys it is better to store in an Azure Keyvault and reference them from the Keyvault. | link | count: 009 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Ensure cryptographic mechanisms are under configuration management (b8dad106-6444-5f55-307e-1e1cc9723e39), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.2 | CIS_Azure_1.3.0_9.2 | CIS Microsoft Azure Foundations Benchmark recommendation 9.2 | 9 AppService | Ensure web app redirects all HTTP traffic to HTTPS in Azure App Service | Shared | The customer is responsible for implementing this recommendation. | Azure Web Apps allows sites to run under both HTTP and HTTPS by default. Web apps can be accessed by anyone using non-secure HTTP links by default. Non-secure HTTP requests can be restricted and all HTTP requests redirected to the secure HTTPS port. It is recommended to enforce HTTPS-only traffic. | link | count: 004 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.3 | CIS_Azure_1.3.0_9.3 | CIS Microsoft Azure Foundations Benchmark recommendation 9.3 | 9 AppService | Ensure web app is using the latest version of TLS encryption | Shared | The customer is responsible for implementing this recommendation. | The TLS(Transport Layer Security) protocol secures transmission of data over the internet using standard encryption technology. Encryption should be set with the latest version of TLS. App service allows TLS 1.2 by default, which is the recommended TLS level by industry standards, such as PCI DSS. | link | count: 005 App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.4 | CIS_Azure_1.3.0_9.4 | CIS Microsoft Azure Foundations Benchmark recommendation 9.4 | 9 AppService | Ensure the web app has 'Client Certificates (Incoming client certificates)' set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Client certificates allow for the app to request a certificate for incoming requests. Only clients that have a valid certificate will be able to reach the app. | link | count: 003 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.5 | CIS_Azure_1.3.0_9.5 | CIS Microsoft Azure Foundations Benchmark recommendation 9.5 | 9 AppService | Ensure that Register with Azure Active Directory is enabled on App Service | Shared | The customer is responsible for implementing this recommendation. | Managed service identity in App Service makes the app more secure by eliminating secrets from the app, such as credentials in the connection strings. When registering with Azure Active Directory in the app service, the app will connect to other Azure services securely without the need of username and passwords. | link | count: 006 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.6 | CIS_Azure_1.3.0_9.6 | CIS Microsoft Azure Foundations Benchmark recommendation 9.6 | 9 AppService | Ensure that 'PHP version' is the latest, if used to run the web app | Shared | The customer is responsible for implementing this recommendation. | Periodically newer versions are released for PHP software either due to security flaws or to include additional functionality. Using the latest PHP version for web apps is recommended in order to take advantage of security fixes, if any, and/or additional functionalities of the newer version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.7 | CIS_Azure_1.3.0_9.7 | CIS Microsoft Azure Foundations Benchmark recommendation 9.7 | 9 AppService | Ensure that 'Python version' is the latest, if used to run the web app | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for Python software either due to security flaws or to include additional functionality. Using the latest Python version for web apps is recommended in order to take advantage of security fixes, if any, and/or additional functionalities of the newer version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.8 | CIS_Azure_1.3.0_9.8 | CIS Microsoft Azure Foundations Benchmark recommendation 9.8 | 9 AppService | Ensure that 'Java version' is the latest, if used to run the web app | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for Java software either due to security flaws or to include additional functionality. Using the latest Java version for web apps is recommended in order to take advantage of security fixes, if any, and/or new functionalities of the newer version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.3.0 | 9.9 | CIS_Azure_1.3.0_9.9 | CIS Microsoft Azure Foundations Benchmark recommendation 9.9 | 9 AppService | Ensure that 'HTTP Version' is the latest, if used to run the web app | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for HTTP either due to security flaws or to include additional functionality. Using the latest HTTP version for web apps to take advantage of security fixes, if any, and/or new functionalities of the newer version. | link | count: 003 App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.3.0 (612b5213-9160-4969-8578-1518bd2a000c) |
| CIS_Azure_1.4.0 | 1.1 | CIS_Azure_1.4.0_1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 1.1 | 1 Identity and Access Management | Ensure that 'Multi-Factor Auth Status' is 'Enabled' for all Privileged Users | Shared | The customer is responsible for implementing this recommendation. | Enable multi-factor authentication for all roles, groups, and users that have write access or permissions to Azure resources. These include custom created objects or built-in roles such as; - Service Co-Administrators - Subscription Owners - Contributors | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.10 | CIS_Azure_1.4.0_1.10 | CIS Microsoft Azure Foundations Benchmark recommendation 1.10 | 1 Identity and Access Management | Ensure that 'Users can add gallery apps to My Apps' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Require administrators to provide consent for the apps before use. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.11 | CIS_Azure_1.4.0_1.11 | CIS Microsoft Azure Foundations Benchmark recommendation 1.11 | 1 Identity and Access Management | Ensure that 'Users can register applications' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Require administrators to register third-party applications. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.12 | CIS_Azure_1.4.0_1.12 | CIS Microsoft Azure Foundations Benchmark recommendation 1.12 | 1 Identity and Access Management | Ensure That 'Guest users access restrictions' is set to 'Guest user access is restricted to properties and memberships of their own directory objects'' | Shared | The customer is responsible for implementing this recommendation. | Limit guest user permissions. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.13 | CIS_Azure_1.4.0_1.13 | CIS Microsoft Azure Foundations Benchmark recommendation 1.13 | 1 Identity and Access Management | Ensure that 'Guest invite restrictions' is set to "Only users assigned to specific admin roles can invite guest users" | Shared | The customer is responsible for implementing this recommendation. | Restrict invitations to users with specific admin roles only. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.14 | CIS_Azure_1.4.0_1.14 | CIS Microsoft Azure Foundations Benchmark recommendation 1.14 | 1 Identity and Access Management | Ensure That 'Restrict access to Azure AD administration portal' is Set to "Yes" | Shared | The customer is responsible for implementing this recommendation. | Restrict access to the Azure AD administration portal to administrators only. | link | count: 006 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.15 | CIS_Azure_1.4.0_1.15 | CIS Microsoft Azure Foundations Benchmark recommendation 1.15 | 1 Identity and Access Management | Ensure that 'Restrict user ability to access groups features in the Access Pane' is Set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Restricts group creation to administrators with permissions only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.16 | CIS_Azure_1.4.0_1.16 | CIS Microsoft Azure Foundations Benchmark recommendation 1.16 | 1 Identity and Access Management | Ensure that 'Users can create security groups in Azure portals, API or PowerShell' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict security group creation to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.17 | CIS_Azure_1.4.0_1.17 | CIS Microsoft Azure Foundations Benchmark recommendation 1.17 | 1 Identity and Access Management | Ensure that 'Owners can manage group membership requests in the Access Panel' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict security group management to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.18 | CIS_Azure_1.4.0_1.18 | CIS Microsoft Azure Foundations Benchmark recommendation 1.18 | 1 Identity and Access Management | Ensure that 'Users can create Microsoft 365 groups in Azure portals, API or PowerShell' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Restrict Microsoft 365 group creation to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.19 | CIS_Azure_1.4.0_1.19 | CIS Microsoft Azure Foundations Benchmark recommendation 1.19 | 1 Identity and Access Management | Ensure that 'Require Multi-Factor Authentication to register or join devices with Azure AD' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Joining or registering devices to the active directory should require Multi-factor authentication. | link | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.2 | CIS_Azure_1.4.0_1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 1.2 | 1 Identity and Access Management | Ensure that 'Multi-Factor Auth Status' is 'Enabled' for all Non-Privileged Users | Shared | The customer is responsible for implementing this recommendation. | Enable multi-factor authentication for all non-privileged users. | link | count: 002 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.20 | CIS_Azure_1.4.0_1.20 | CIS Microsoft Azure Foundations Benchmark recommendation 1.20 | 1 Identity and Access Management | Ensure That No Custom Subscription Owner Roles Are Created | Shared | The customer is responsible for implementing this recommendation. | Subscription ownership should not include permission to create custom owner roles. The principle of least privilege should be followed and only necessary privileges should be assigned instead of allowing full administrative access. | link | count: 006 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.21 | CIS_Azure_1.4.0_1.21 | CIS Microsoft Azure Foundations Benchmark recommendation 1.21 | 1 Identity and Access Management | Ensure Security Defaults is enabled on Azure Active Directory | Shared | The customer is responsible for implementing this recommendation. | Security defaults in Azure Active Directory (Azure AD) make it easier to be secure and help protect your organization. Security defaults contain preconfigured security settings for common attacks. Microsoft is making security defaults available to everyone. The goal is to ensure that all organizations have a basic level of security-enabled at no extra cost. You turn on security defaults in the Azure portal. | link | count: 009 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.22 | CIS_Azure_1.4.0_1.22 | CIS Microsoft Azure Foundations Benchmark recommendation 1.22 | 1 Identity and Access Management | Ensure a Custom Role is Assigned Permissions for Administering Resource Locks | Shared | The customer is responsible for implementing this recommendation. | Resource locking is a powerful protection mechanism that can prevent inadvertent modification/deletion of resources within Azure subscriptions/Resource Groups and is a recommended NIST configuration. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.3 | CIS_Azure_1.4.0_1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 1.3 | 1 Identity and Access Management | Ensure guest users are reviewed on a monthly basis | Shared | The customer is responsible for implementing this recommendation. | Azure AD is extended to include Azure AD B2B collaboration, allowing you to invite people from outside your organization to be guest users in your cloud account and sign in with their own work, school, or social identities. Guest users allow you to share your company's applications and services with users from any other organization, while maintaining control over your own corporate data. Work with external partners, large or small, even if they don't have Azure AD or an IT department. A simple invitation and redemption process lets partners use their own credentials to access your company's resources a a guest user. | link | count: 008 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.4 | CIS_Azure_1.4.0_1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 1.4 | 1 Identity and Access Management | Ensure that 'Restore multi-factor authentication on all remembered devices' is Enabled | Shared | The customer is responsible for implementing this recommendation. | Do not allow users to remember multi-factor authentication on devices. | link | count: 003 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.6 | CIS_Azure_1.4.0_1.6 | CIS Microsoft Azure Foundations Benchmark recommendation 1.6 | 1 Identity and Access Management | Ensure that 'Number of days before users are asked to re-confirm their authentication information' is not set to '0' | Shared | The customer is responsible for implementing this recommendation. | Ensure that the number of days before users are asked to re-confirm their authentication information is not set to 0. | link | count: 004 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.7 | CIS_Azure_1.4.0_1.7 | CIS Microsoft Azure Foundations Benchmark recommendation 1.7 | 1 Identity and Access Management | Ensure that 'Notify users on password resets?' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Ensure that users are notified on their primary and secondary emails on password resets. | link | count: 005 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.8 | CIS_Azure_1.4.0_1.8 | CIS Microsoft Azure Foundations Benchmark recommendation 1.8 | 1 Identity and Access Management | Ensure That 'Notify all admins when other admins reset their password?' is set to 'Yes' | Shared | The customer is responsible for implementing this recommendation. | Ensure that all administrators are notified if any other administrator resets their password. | link | count: 010 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 1.9 | CIS_Azure_1.4.0_1.9 | CIS Microsoft Azure Foundations Benchmark recommendation 1.9 | 1 Identity and Access Management | Ensure that 'Users can consent to apps accessing company data on their behalf' is set to 'No' | Shared | The customer is responsible for implementing this recommendation. | Require administrators to provide consent for the apps before use. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.1 | CIS_Azure_1.4.0_2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for Servers is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Turning on Microsoft Defender for Servers enables threat detection for Servers, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. | link | count: 009 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.10 | CIS_Azure_1.4.0_2.10 | CIS Microsoft Azure Foundations Benchmark recommendation 2.10 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for Cloud Apps (MCAS) Integration with Microsoft Defender for Cloud is Selected | Shared | The customer is responsible for implementing this recommendation. | This setting enables Microsoft Defender for Cloud Apps (MCAS) integration with Microsoft Defender for Cloud. | link | count: 008 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.11 | CIS_Azure_1.4.0_2.11 | CIS Microsoft Azure Foundations Benchmark recommendation 2.11 | 2 Microsoft Defender for Cloud | Ensure That Auto provisioning of 'Log Analytics agent for Azure VMs' is Set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Enable automatic provisioning of the monitoring agent to collect security data. | link | count: 003 Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.12 | CIS_Azure_1.4.0_2.12 | CIS Microsoft Azure Foundations Benchmark recommendation 2.12 | 2 Microsoft Defender for Cloud | Ensure Any of the ASC Default Policy Setting is Not Set to 'Disabled' | Shared | The customer is responsible for implementing this recommendation. | None of the settings offered by ASC Default policy should be set to effect "Disabled". | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.13 | CIS_Azure_1.4.0_2.13 | CIS Microsoft Azure Foundations Benchmark recommendation 2.13 | 2 Microsoft Defender for Cloud | Ensure 'Additional email addresses' is Configured with a Security Contact Email | Shared | The customer is responsible for implementing this recommendation. | Microsoft Defender for Cloud emails the subscription owners whenever a high-severity alert is triggered for their subscription. You should provide a security contact email address as an additional email address. | link | count: 001 Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.14 | CIS_Azure_1.4.0_2.14 | CIS Microsoft Azure Foundations Benchmark recommendation 2.14 | 2 Microsoft Defender for Cloud | Ensure That 'Notify about alerts with the following severity' is Set to 'High' | Shared | The customer is responsible for implementing this recommendation. | Enables emailing security alerts to the subscription owner or other designated security contact. | link | count: 001 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899) |
Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.2 | CIS_Azure_1.4.0_2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 2.2 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for App Service is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Turning on Microsoft Defender for App Service enables threat detection for App Service, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. | link | count: 009 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.3 | CIS_Azure_1.4.0_2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 2.3 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for Azure SQL Databases is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Turning on Microsoft Defender for Azure SQL Databases enables threat detection for Azure SQL database servers, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. | link | count: 009 Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.4 | CIS_Azure_1.4.0_2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 2.4 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for SQL servers on machines is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Turning on Microsoft Defender for SQL servers on machines enables threat detection for SQL servers on machines, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. | link | count: 009 Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.5 | CIS_Azure_1.4.0_2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 2.5 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for Storage is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Turning on Microsoft Defender for Storage enables threat detection for Storage, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. | link | count: 009 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.6 | CIS_Azure_1.4.0_2.6 | CIS Microsoft Azure Foundations Benchmark recommendation 2.6 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for Kubernetes is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Turning on Microsoft Defender for Kubernetes enables threat detection for Kubernetes, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. | link | count: 009 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.7 | CIS_Azure_1.4.0_2.7 | CIS Microsoft Azure Foundations Benchmark recommendation 2.7 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for Container Registries is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Turning on Microsoft Defender for Container Registries enables threat detection for Container Registries, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. | link | count: 009 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.8 | CIS_Azure_1.4.0_2.8 | CIS Microsoft Azure Foundations Benchmark recommendation 2.8 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for Key Vault is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Turning on Microsoft Defender for Key Vault enables threat detection for Key Vault, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. | link | count: 009 Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 2.9 | CIS_Azure_1.4.0_2.9 | CIS Microsoft Azure Foundations Benchmark recommendation 2.9 | 2 Microsoft Defender for Cloud | Ensure that Microsoft Defender for Endpoint (WDATP) integration with Microsoft Defender for Cloud is selected | Shared | The customer is responsible for implementing this recommendation. | This setting enables Microsoft Defender for Endpoint integration with Microsoft Defender for Cloud. | link | count: 008 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.1 | CIS_Azure_1.4.0_3.1 | CIS Microsoft Azure Foundations Benchmark recommendation 3.1 | 3 Storage Accounts | Ensure that 'Secure transfer required' is set to 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable data encryption in transit. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.10 | CIS_Azure_1.4.0_3.10 | CIS Microsoft Azure Foundations Benchmark recommendation 3.10 | 3 Storage Accounts | Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests | Shared | The customer is responsible for implementing this recommendation. | The Storage Blob service provides scalable, cost-efficient objective storage in the cloud. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the blobs. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.11 | CIS_Azure_1.4.0_3.11 | CIS Microsoft Azure Foundations Benchmark recommendation 3.11 | 3 Storage Accounts | Ensure Storage Logging is Enabled for Table Service for 'Read', 'Write', and 'Delete' Requests | Shared | The customer is responsible for implementing this recommendation. | The Storage Table storage is a service that stores structure NoSQL data in the cloud, providing a key/attribute store with a schema less design. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the tables. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.12 | CIS_Azure_1.4.0_3.12 | CIS Microsoft Azure Foundations Benchmark recommendation 3.12 | 3 Storage Accounts | Ensure the "Minimum TLS version" is set to "Version 1.2" | Shared | The customer is responsible for implementing this recommendation. | Azure Storage sets the minimum TLS version to be version 1.0 by default. TLS 1.0 is a legacy version and has known vulnerabilities. This minimum TLS version can be configured to be later protocols such as TLS 1.2. | link | count: 003 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.2 | CIS_Azure_1.4.0_3.2 | CIS Microsoft Azure Foundations Benchmark recommendation 3.2 | 3 Storage Accounts | Ensure That Storage Account Access Keys are Periodically Regenerated | Shared | The customer is responsible for implementing this recommendation. | Regenerate storage account access keys periodically. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.3 | CIS_Azure_1.4.0_3.3 | CIS Microsoft Azure Foundations Benchmark recommendation 3.3 | 3 Storage Accounts | Ensure Storage Logging is Enabled for Queue Service for 'Read', 'Write', and 'Delete' requests | Shared | The customer is responsible for implementing this recommendation. | The Storage Queue service stores messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size using version 2011-08-18 or newer. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the queues. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.4 | CIS_Azure_1.4.0_3.4 | CIS Microsoft Azure Foundations Benchmark recommendation 3.4 | 3 Storage Accounts | Ensure that Shared Access Signature Tokens Expire Within an Hour | Shared | The customer is responsible for implementing this recommendation. | Expire shared access signature tokens within an hour. | link | count: 003 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.5 | CIS_Azure_1.4.0_3.5 | CIS Microsoft Azure Foundations Benchmark recommendation 3.5 | 3 Storage Accounts | Ensure that 'Public access level' is set to Private for blob containers | Shared | The customer is responsible for implementing this recommendation. | Disable anonymous access to blob containers and disallow blob public access on storage account. | link | count: 007 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.6 | CIS_Azure_1.4.0_3.6 | CIS Microsoft Azure Foundations Benchmark recommendation 3.6 | 3 Storage Accounts | Ensure Default Network Access Rule for Storage Accounts is Set to Deny | Shared | The customer is responsible for implementing this recommendation. | Restricting default network access helps to provide a new layer of security, since storage accounts accept connections from clients on any network. To limit access to selected networks, the default action must be changed. | link | count: 002 Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f) |
Storage | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.7 | CIS_Azure_1.4.0_3.7 | CIS Microsoft Azure Foundations Benchmark recommendation 3.7 | 3 Storage Accounts | Ensure 'Trusted Microsoft Services' are Enabled for Storage Account Access | Shared | The customer is responsible for implementing this recommendation. | Some Microsoft services that interact with storage accounts operate from networks that can't be granted access through network rules. To help this type of service work as intended, allow the set of trusted Microsoft services to bypass the network rules. These services will then use strong authentication to access the storage account. If the Allow trusted Microsoft services exception is enabled, the following services: Azure Backup, Azure Site Recovery, Azure DevTest Labs, Azure Event Grid, Azure Event Hubs, Azure Networking, Azure Monitor and Azure SQL Data Warehouse (when registered in the subscription), are granted access to the storage account. | link | count: 006 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 3.9 | CIS_Azure_1.4.0_3.9 | CIS Microsoft Azure Foundations Benchmark recommendation 3.9 | 3 Storage Accounts | Ensure Storage for Critical Data are Encrypted with Customer Managed Keys | Shared | The customer is responsible for implementing this recommendation. | Enable sensitive data encryption at rest using Customer Managed Keys rather than Microsoft Managed keys | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.1.1 | CIS_Azure_1.4.0_4.1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.1 | 4 Database Services | Ensure that 'Auditing' is set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Enable auditing on SQL Servers. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.1.2 | CIS_Azure_1.4.0_4.1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.2 | 4 Database Services | Ensure that 'Data encryption' is set to 'On' on a SQL Database | Shared | The customer is responsible for implementing this recommendation. | Enable Transparent Data Encryption on every SQL server. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.1.3 | CIS_Azure_1.4.0_4.1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.3 | 4 Database Services | Ensure that 'Auditing' Retention is 'greater than 90 days' | Shared | The customer is responsible for implementing this recommendation. | SQL Server Audit Retention should be configured to be greater than 90 days. | link | count: 005 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.2.1 | CIS_Azure_1.4.0_4.2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.1 | 4 Database Services | Ensure that Advanced Threat Protection (ATP) on a SQL Server is Set to 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable "Azure Defender for SQL" on critical SQL Servers. | link | count: 003 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.2.2 | CIS_Azure_1.4.0_4.2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.2 | 4 Database Services | Ensure that Vulnerability Assessment (VA) is enabled on a SQL server by setting a Storage Account | Shared | The customer is responsible for implementing this recommendation. | Enable Vulnerability Assessment (VA) service scans for critical SQL servers and corresponding SQL databases. | link | count: 004 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.2.3 | CIS_Azure_1.4.0_4.2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.3 | 4 Database Services | Ensure that VA setting 'Periodic recurring scans' to 'on' for each SQL server | Shared | The customer is responsible for implementing this recommendation. | Enable Vulnerability Assessment (VA) Periodic recurring scans for critical SQL servers and corresponding SQL databases. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.2.4 | CIS_Azure_1.4.0_4.2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.4 | 4 Database Services | Ensure that VA setting 'Send scan reports to' is configured for a SQL server | Shared | The customer is responsible for implementing this recommendation. | Configure 'Send scan reports to' with email ids of concerned data owners/stakeholders for a critical SQL servers. | link | count: 003 Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.2.5 | CIS_Azure_1.4.0_4.2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.5 | 4 Database Services | Ensure that Vulnerability Assessment Setting 'Also send email notifications to admins and subscription owners' is Set for Each SQL Server | Shared | The customer is responsible for implementing this recommendation. | Enable Vulnerability Assessment (VA) setting 'Also send email notifications to admins and subscription owners'. | link | count: 003 Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.3.1 | CIS_Azure_1.4.0_4.3.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.1 | 4 Database Services | Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'SSL connection' on 'PostgreSQL' Servers. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.3.2 | CIS_Azure_1.4.0_4.3.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.2 | 4 Database Services | Ensure Server Parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_checkpoints' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Log checkpoints should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e43d), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.3.3 | CIS_Azure_1.4.0_4.3.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.3 | 4 Database Services | Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_connections' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Log connections should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e442), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.3.4 | CIS_Azure_1.4.0_4.3.4 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.4 | 4 Database Services | Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_disconnections' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Disconnections should be logged for PostgreSQL database servers. (eb6f77b9-bd53-4e35-a23d-7f65d5f0e446), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.3.5 | CIS_Azure_1.4.0_4.3.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.5 | 4 Database Services | Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'connection_throttling' on 'PostgreSQL Servers'. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Connection throttling should be enabled for PostgreSQL database servers (5345bb39-67dc-4960-a1bf-427e16b9a0bd), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.3.6 | CIS_Azure_1.4.0_4.3.6 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.6 | 4 Database Services | Ensure server parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'log_retention_days' on 'PostgreSQL Servers'. | link | count: 004 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.3.7 | CIS_Azure_1.4.0_4.3.7 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.7 | 4 Database Services | Ensure 'Allow access to Azure services' for PostgreSQL Database Server is disabled | Shared | The customer is responsible for implementing this recommendation. | Disable access from Azure services to PostgreSQL Database Server | link | count: 005 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.3.8 | CIS_Azure_1.4.0_4.3.8 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.8 | 4 Database Services | Ensure 'Infrastructure double encryption' for PostgreSQL Database Server is 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable encryption at rest for PostgreSQL Databases. | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.4.1 | CIS_Azure_1.4.0_4.4.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.4.1 | 4 Database Services | Ensure 'Enforce SSL connection' is set to 'Enabled' for Standard MySQL Database Server | Shared | The customer is responsible for implementing this recommendation. | Enable 'SSL connection' on 'MYSQL' Servers. | link | count: 003 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.4.2 | CIS_Azure_1.4.0_4.4.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.4.2 | 4 Database Services | Ensure 'TLS Version' is set to 'TLSV1.2' for MySQL flexible Database Server | Shared | The customer is responsible for implementing this recommendation. | Ensure 'TLS version' on 'MySQL flexible' servers is set to the default value. | link | count: 003 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.5 | CIS_Azure_1.4.0_4.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.5 | 4 Database Services | Ensure that Azure Active Directory Admin is configured | Shared | The customer is responsible for implementing this recommendation. | Use Azure Active Directory Authentication for authentication with SQL Database to manage credentials in a single place. | link | count: 005 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 4.6 | CIS_Azure_1.4.0_4.6 | CIS Microsoft Azure Foundations Benchmark recommendation 4.6 | 4 Database Services | Ensure SQL server's TDE protector is encrypted with Customer-managed key | Shared | The customer is responsible for implementing this recommendation. | TDE with Customer-managed key support provides increased transparency and control over the TDE Protector, increased security with an HSM-backed external service, and promotion of separation of duties. With TDE, data is encrypted at rest with a symmetric key (called the database encryption key) stored in the database or data warehouse distribution. To protect this data encryption key (DEK) in the past, only a certificate that the Azure SQL Service managed could be used. Now, with Customer-managed key support for TDE, the DEK can be protected with an asymmetric key that is stored in the Key Vault. Key Vault is a highly available and scalable cloud-based key store which offers central key management, leverages FIPS 140-2 Level 2 validated hardware security modules (HSMs), and allows separation of management of keys and data, for additional security. Based on business needs or criticality of data/databases hosted a SQL server, it is recommended that the TDE protector is encrypted by a key that is managed by the data owner (Customer-managed key). | link | count: 006 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.1.1 | CIS_Azure_1.4.0_5.1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.1 | 5 Logging and Monitoring | Ensure that a 'Diagnostics Setting' exists | Shared | The customer is responsible for implementing this recommendation. | Enable Diagnostic settings for exporting activity logs. Diagnostic setting are available for each individual resources within a subscription. Settings should be configured for all appropriate resources for your environment. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.1.2 | CIS_Azure_1.4.0_5.1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.2 | 5 Logging and Monitoring | Ensure Diagnostic Setting captures appropriate categories | Shared | The customer is responsible for implementing this recommendation. | The diagnostic setting should be configured to log the appropriate activities from the control/management plane. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.1.3 | CIS_Azure_1.4.0_5.1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.3 | 5 Logging and Monitoring | Ensure the storage container storing the activity logs is not publicly accessible | Shared | The customer is responsible for implementing this recommendation. | The storage account container containing the activity log export should not be publicly accessible. | link | count: 003 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.1.4 | CIS_Azure_1.4.0_5.1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.4 | 5 Logging and Monitoring | Ensure the storage account containing the container with activity logs is encrypted with BYOK (Use Your Own Key) | Shared | The customer is responsible for implementing this recommendation. | The storage account with the activity log export container is configured to use BYOK (Use Your Own Key). | link | count: 004 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Maintain integrity of audit system (c0559109-6a27-a217-6821-5a6d44f92897), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Storage account containing the container with activity logs must be encrypted with BYOK (fbb99e8e-e444-4da0-9ff1-75c92f5a85b2) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.1.5 | CIS_Azure_1.4.0_5.1.5 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.5 | 5 Logging and Monitoring | Ensure that logging for Azure KeyVault is 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable AuditEvent logging for key vault instances to ensure interactions with key vaults are logged and available. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.2.1 | CIS_Azure_1.4.0_5.2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.1 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create Policy Assignment | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create Policy Assignment event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.2.2 | CIS_Azure_1.4.0_5.2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.2 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Delete Policy Assignment | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Policy Assignment event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.2.3 | CIS_Azure_1.4.0_5.2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.3 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update Network Security Group | Shared | The customer is responsible for implementing this recommendation. | Create an Activity Log Alert for the "Create" or "Update Network Security Group" event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.2.4 | CIS_Azure_1.4.0_5.2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.4 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Delete Network Security Group | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Network Security Group event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.2.5 | CIS_Azure_1.4.0_5.2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.5 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update Network Security Group | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create or Update Network Security Group Rule event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.2.6 | CIS_Azure_1.4.0_5.2.6 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.6 | 5 Logging and Monitoring | Ensure that activity log alert exists for the Delete Network Security Group Rule | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Network Security Group Rule event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.2.7 | CIS_Azure_1.4.0_5.2.7 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.7 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update Security Solution | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create or Update Security Solution event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.2.8 | CIS_Azure_1.4.0_5.2.8 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.8 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Delete Security Solution | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Delete Security Solution event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.2.9 | CIS_Azure_1.4.0_5.2.9 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.9 | 5 Logging and Monitoring | Ensure that Activity Log Alert exists for Create or Update or Delete SQL Server Firewall Rule | Shared | The customer is responsible for implementing this recommendation. | Create an activity log alert for the Create or Update or Delete SQL Server Firewall Rule event. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 5.3 | CIS_Azure_1.4.0_5.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | 5 Logging and Monitoring | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Shared | The customer is responsible for implementing this recommendation. | Diagnostic Logs capture activity to the data access plane while the Activity log is a subscription-level log for the control plane. Resource-level diagnostic logs provide insight into operations that were performed within that resource itself, for example, getting a secret from a Key Vault. Currently, 32 Azure resources support Diagnostic Logging (See the references section for a complete list), including Network Security Groups, Load Balancers, Key Vault, AD, Logic Apps and CosmosDB. The content of these logs varies by resource type. For example, Windows event system logs are a category of diagnostics logs for VMs, and blob, table, and queue logs are categories of diagnostics logs for storage accounts. A number of back-end services were not configured to log and store Diagnostic Logs for certain activities or for a sufficient length. It is crucial that logging systems are correctly configured to log all relevant activities and retain those logs for a sufficient length of time. By default, Diagnostic Logs are not enabled. Given that the mean time to detection in an enterprise is 240 days, a minimum retention period of two years is recommended. Note: The CIS Benchmark covers some specific Diagnostic Logs separately. ''' 3.3 - Ensure Storage logging is enabled for Queue service for read, write, and delete requests 6.4 Ensure that Network Security Group Flow Log retention period is 'greater than 90 days' ''' | link | count: 020 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Logic Apps, Regulatory Compliance, Search, Service Bus, Stream Analytics | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 6.3 | CIS_Azure_1.4.0_6.3 | CIS Microsoft Azure Foundations Benchmark recommendation 6.3 | 6 Networking | Ensure no SQL Databases allow ingress 0.0.0.0/0 (ANY IP) | Shared | The customer is responsible for implementing this recommendation. | Ensure that no SQL Databases allow ingress from 0.0.0.0/0 (ANY IP). | link | count: 002 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 6.4 | CIS_Azure_1.4.0_6.4 | CIS Microsoft Azure Foundations Benchmark recommendation 6.4 | 6 Networking | Ensure that Network Security Group Flow Log retention period is 'greater than 90 days' | Shared | The customer is responsible for implementing this recommendation. | Network Security Group Flow Logs should be enabled and the retention period is set to greater than or equal to 90 days. | link | count: 003 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 6.5 | CIS_Azure_1.4.0_6.5 | CIS Microsoft Azure Foundations Benchmark recommendation 6.5 | 6 Networking | Ensure that Network Watcher is 'Enabled' | Shared | The customer is responsible for implementing this recommendation. | Enable Network Watcher for Azure subscriptions. | link | count: 002 Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Network, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 7.1 | CIS_Azure_1.4.0_7.1 | CIS Microsoft Azure Foundations Benchmark recommendation 7.1 | 7 Virtual Machines | Ensure Virtual Machines are utilizing Managed Disks | Shared | The customer is responsible for implementing this recommendation. | Migrate BLOB based VHD's to Managed Disks on Virtual Machines to exploit the default features of this configuration. The features include 1) Default Disk Encryption 2) Resilience as Microsoft will managed the disk storage and move around if underlying hardware goes faulty 3) Reduction of costs over storage accounts | link | count: 004 Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Compute, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 7.2 | CIS_Azure_1.4.0_7.2 | CIS Microsoft Azure Foundations Benchmark recommendation 7.2 | 7 Virtual Machines | Ensure that 'OS and Data' disks are encrypted with Customer Managed Key (CMK) | Shared | The customer is responsible for implementing this recommendation. | Ensure that OS disks (boot volumes) and data disks (non-boot volumes) are encrypted with CMK (Customer Managed Keys). Customer Managed keys can be either ADE or Server Side Encryption(SSE) | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 7.3 | CIS_Azure_1.4.0_7.3 | CIS Microsoft Azure Foundations Benchmark recommendation 7.3 | 7 Virtual Machines | Ensure that 'Unattached disks' are encrypted with CMK | Shared | The customer is responsible for implementing this recommendation. | Ensure that unattached disks in a subscription are encrypted with a Customer Managed Key (CMK). | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 7.4 | CIS_Azure_1.4.0_7.4 | CIS Microsoft Azure Foundations Benchmark recommendation 7.4 | 7 Virtual Machines | Ensure that Only Approved Extensions Are Installed | Shared | The customer is responsible for implementing this recommendation. | For added security only install organization-approved extensions on VMs. | link | count: 001 Only approved VM extensions should be installed (c0e996f8-39cf-4af9-9f45-83fbde810432) |
Compute | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 7.5 | CIS_Azure_1.4.0_7.5 | CIS Microsoft Azure Foundations Benchmark recommendation 7.5 | 7 Virtual Machines | Ensure that the latest OS Patches for all Virtual Machines are applied | Shared | The customer is responsible for implementing this recommendation. | Ensure that the latest OS patches for all virtual machines are applied. | link | count: 002 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 7.6 | CIS_Azure_1.4.0_7.6 | CIS Microsoft Azure Foundations Benchmark recommendation 7.6 | 7 Virtual Machines | Ensure that the endpoint protection for all Virtual Machines is installed | Shared | The customer is responsible for implementing this recommendation. | Install endpoint protection for all virtual machines. | link | count: 011 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 7.7 | CIS_Azure_1.4.0_7.7 | CIS Microsoft Azure Foundations Benchmark recommendation 7.7 | 7 Virtual Machines | Ensure that VHD's are Encrypted | Shared | The customer is responsible for implementing this recommendation. | VHD (Virtual Hard Disks) are stored in BLOB storage and are the old style disks that were attached to Virtual Machines, and the BLOB VHD was then leased to the VM. By Default storage accounts are not encrypted, and Azure Defender(Security Centre) would then recommend that the OS disks should be encrypted. Storage accounts can be encrypted as a whole using PMK or CMK and this should be turned on for storage accounts containing VHD's. | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 8.1 | CIS_Azure_1.4.0_8.1 | CIS Microsoft Azure Foundations Benchmark recommendation 8.1 | 8 Other Security Considerations | Ensure that the Expiration Date is set for all Keys in RBAC Key Vaults | Shared | The customer is responsible for implementing this recommendation. | Ensure that all Keys in Role Based Access Control (RBAC) Azure Key Vaults have an expiration time set. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 8.2 | CIS_Azure_1.4.0_8.2 | CIS Microsoft Azure Foundations Benchmark recommendation 8.2 | 8 Other Security Considerations | Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults. | Shared | The customer is responsible for implementing this recommendation. | Ensure that all Keys in Non Role Based Access Control (RBAC) Azure Key Vaults have an expiration time set. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 8.3 | CIS_Azure_1.4.0_8.3 | CIS Microsoft Azure Foundations Benchmark recommendation 8.3 | 8 Other Security Considerations | Ensure that the Expiration Date is set for all Secrets in RBAC Key Vaults | Shared | The customer is responsible for implementing this recommendation. | Ensure that all Secrets in Role Based Access Control (RBAC) Azure Key Vaults have an expiration time set. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 8.4 | CIS_Azure_1.4.0_8.4 | CIS Microsoft Azure Foundations Benchmark recommendation 8.4 | 8 Other Security Considerations | Ensure that the Expiration Date is set for all Secrets in Non-RBAC Key Vaults | Shared | The customer is responsible for implementing this recommendation. | Ensure that all Secrets in Non Role Based Access Control (RBAC) Azure Key Vaults have an expiration time set. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 8.5 | CIS_Azure_1.4.0_8.5 | CIS Microsoft Azure Foundations Benchmark recommendation 8.5 | 8 Other Security Considerations | Ensure that Resource Locks are set for Mission Critical Azure Resources | Shared | The customer is responsible for implementing this recommendation. | Resource Manager Locks provide a way for administrators to lock down Azure resources to prevent deletion of, or modifications to, a resource. These locks sit outside of the Role Based Access Controls (RBAC) hierarchy and, when applied, will place restrictions on the resource for all users. These locks are very useful when there is an important resource in a subscription that users should not be able to delete or change. Locks can help prevent accidental and malicious changes or deletion. | link | count: 001 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 8.6 | CIS_Azure_1.4.0_8.6 | CIS Microsoft Azure Foundations Benchmark recommendation 8.6 | 8 Other Security Considerations | Ensure the key vault is recoverable | Shared | The customer is responsible for implementing this recommendation. | The key vault contains object keys, secrets and certificates. Accidental unavailability of a key vault can cause immediate data loss or loss of security functions (authentication, validation, verification, non-repudiation, etc.) supported by the key vault objects. It is recommended the key vault be made recoverable by enabling the "Do Not Purge" and "Soft Delete" functions. This is in order to prevent loss of encrypted data including storage accounts, SQL databases, and/or dependent services provided by key vault objects (Keys, Secrets, Certificates) etc., as may happen in the case of accidental deletion by a user or from disruptive activity by a malicious user. | link | count: 002 Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 8.7 | CIS_Azure_1.4.0_8.7 | CIS Microsoft Azure Foundations Benchmark recommendation 8.7 | 8 Other Security Considerations | Enable role-based access control (RBAC) within Azure Kubernetes Services | Shared | The customer is responsible for implementing this recommendation. | Ensure that RBAC is enabled on all Azure Kubernetes Services Instances | link | count: 007 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.1 | CIS_Azure_1.4.0_9.1 | CIS Microsoft Azure Foundations Benchmark recommendation 9.1 | 9 AppService | Ensure App Service Authentication is set up for apps in Azure App Service | Shared | The customer is responsible for implementing this recommendation. | Azure App Service Authentication is a feature that can prevent anonymous HTTP requests from reaching the API app, or authenticate those that have tokens before they reach the API app. If an anonymous request is received from a browser, App Service will redirect to a logon page. To handle the logon process, a choice from a set of identity providers can be made, or a custom authentication mechanism can be implemented. | link | count: 005 App Service apps should have authentication enabled (95bccee9-a7f8-4bec-9ee9-62c3473701fc), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Function apps should have authentication enabled (c75248c1-ea1d-4a9c-8fc9-29a6aabd5da8), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.10 | CIS_Azure_1.4.0_9.10 | CIS Microsoft Azure Foundations Benchmark recommendation 9.10 | 9 AppService | Ensure FTP deployments are Disabled | Shared | The customer is responsible for implementing this recommendation. | By default, Azure Functions, Web and API Services can be deployed over FTP. If FTP is required for an essential deployment workflow, FTPS should be required for FTP login for all App Service Apps and Functions. | link | count: 005 App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.11 | CIS_Azure_1.4.0_9.11 | CIS Microsoft Azure Foundations Benchmark recommendation 9.11 | 9 AppService | Ensure Azure Keyvaults are Used to Store Secrets | Shared | The customer is responsible for implementing this recommendation. | Encryption keys ,Certificate thumbprints and Managed Identity Credentials can be coded into the APP service, this renders them visible as part of the configuration, to maintain security of these keys it is better to store in an Azure Keyvault and reference them from the Keyvault. | link | count: 009 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Ensure cryptographic mechanisms are under configuration management (b8dad106-6444-5f55-307e-1e1cc9723e39), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.2 | CIS_Azure_1.4.0_9.2 | CIS Microsoft Azure Foundations Benchmark recommendation 9.2 | 9 AppService | Ensure Web App Redirects All HTTP traffic to HTTPS in Azure App Service | Shared | The customer is responsible for implementing this recommendation. | Azure Web Apps allows sites to run under both HTTP and HTTPS by default. Web apps can be accessed by anyone using non-secure HTTP links by default. Non-secure HTTP requests can be restricted and all HTTP requests redirected to the secure HTTPS port. It is recommended to enforce HTTPS-only traffic. | link | count: 004 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.3 | CIS_Azure_1.4.0_9.3 | CIS Microsoft Azure Foundations Benchmark recommendation 9.3 | 9 AppService | Ensure Web App is using the latest version of TLS encryption | Shared | The customer is responsible for implementing this recommendation. | The TLS(Transport Layer Security) protocol secures transmission of data over the internet using standard encryption technology. Encryption should be set with the latest version of TLS. App service allows TLS 1.2 by default, which is the recommended TLS level by industry standards, such as PCI DSS. | link | count: 005 App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.4 | CIS_Azure_1.4.0_9.4 | CIS Microsoft Azure Foundations Benchmark recommendation 9.4 | 9 AppService | Ensure the web app has 'Client Certificates (Incoming client certificates)' set to 'On' | Shared | The customer is responsible for implementing this recommendation. | Client certificates allow for the app to request a certificate for incoming requests. Only clients that have a valid certificate will be able to reach the app. | link | count: 003 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.5 | CIS_Azure_1.4.0_9.5 | CIS Microsoft Azure Foundations Benchmark recommendation 9.5 | 9 AppService | Ensure that Register with Azure Active Directory is enabled on App Service | Shared | The customer is responsible for implementing this recommendation. | Managed service identity in App Service makes the app more secure by eliminating secrets from the app, such as credentials in the connection strings. When registering with Azure Active Directory in the app service, the app will connect to other Azure services securely without the need of username and passwords. | link | count: 006 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.6 | CIS_Azure_1.4.0_9.6 | CIS Microsoft Azure Foundations Benchmark recommendation 9.6 | 9 AppService | Ensure That 'PHP version' is the Latest, If Used to Run the Web App | Shared | The customer is responsible for implementing this recommendation. | Periodically newer versions are released for PHP software either due to security flaws or to include additional functionality. Using the latest PHP version for web apps is recommended in order to take advantage of security fixes, if any, and/or additional functionalities of the newer version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.7 | CIS_Azure_1.4.0_9.7 | CIS Microsoft Azure Foundations Benchmark recommendation 9.7 | 9 AppService | Ensure that 'Python version' is the Latest Stable Version, if Used to Run the Web App | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for Python software either due to security flaws or to include additional functionality. Using the latest full Python version for web apps is recommended in order to take advantage of security fixes, if any, and/or additional functionalities of the newer version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.8 | CIS_Azure_1.4.0_9.8 | CIS Microsoft Azure Foundations Benchmark recommendation 9.8 | 9 AppService | Ensure that 'Java version' is the latest, if used to run the Web App | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for Java software either due to security flaws or to include additional functionality. Using the latest Java version for web apps is recommended in order to take advantage of security fixes, if any, and/or new functionalities of the newer version. | link | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_1.4.0 | 9.9 | CIS_Azure_1.4.0_9.9 | CIS Microsoft Azure Foundations Benchmark recommendation 9.9 | 9 AppService | Ensure that 'HTTP Version' is the Latest, if Used to Run the Web App | Shared | The customer is responsible for implementing this recommendation. | Periodically, newer versions are released for HTTP either due to security flaws or to include additional functionality. Using the latest HTTP version for web apps to take advantage of security fixes, if any, and/or new functionalities of the newer version. | link | count: 003 App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v1.4.0 (c3f5c4d9-9a1d-4a99-85c0-7f93e384d5c5) |
| CIS_Azure_2.0.0 | 1.1.1 | CIS_Azure_2.0.0_1.1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 1.1.1 | 1.1 | Ensure Security Defaults is enabled on Azure Active Directory | Shared | This recommendation should be implemented initially and then may be overridden by other service/product specific CIS Benchmarks. Administrators should also be aware that certain configurations in Azure Active Directory may impact other Microsoft services such as Microsoft 365. | Security defaults in Azure Active Directory (Azure AD) make it easier to be secure and help protect your organization. Security defaults contain preconfigured security settings for common attacks. Security defaults is available to everyone. The goal is to ensure that all organizations have a basic level of security enabled at no extra cost. You may turn on security defaults in the Azure portal. Security defaults provide secure default settings that we manage on behalf of organizations to keep customers safe until they are ready to manage their own identity security settings. For example, doing the following: - Requiring all users and admins to register for MFA. - Challenging users with MFA - when necessary, based on factors such as location, device, role, and task. - Disabling authentication from legacy authentication clients, which can’t do MFA. | link | count: 009 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.1.2 | CIS_Azure_2.0.0_1.1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 1.1.2 | 1.1 | Ensure that 'Multi-Factor Auth Status' is 'Enabled' for all Privileged Users | Shared | Users would require two forms of authentication before any access is granted. Additional administrative time will be required for managing dual forms of authentication when enabling multi-factor authentication. | Enable multi-factor authentication for all roles, groups, and users that have write access or permissions to Azure resources. These include custom created objects or built-in roles such as; - Service Co-Administrators - Subscription Owners - Contributors Multi-factor authentication requires an individual to present a minimum of two separate forms of authentication before access is granted. Multi-factor authentication provides additional assurance that the individual attempting to gain access is who they claim to be. With multi-factor authentication, an attacker would need to compromise at least two different authentication mechanisms, increasing the difficulty of compromise and thus reducing the risk. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.1.3 | CIS_Azure_2.0.0_1.1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 1.1.3 | 1.1 | Ensure that 'Multi-Factor Auth Status' is 'Enabled' for all Non-Privileged Users | Shared | Users would require two forms of authentication before any access is granted. Also, this requires an overhead for managing dual forms of authentication. | Enable multi-factor authentication for all non-privileged users. Multi-factor authentication requires an individual to present a minimum of two separate forms of authentication before access is granted. Multi-factor authentication provides additional assurance that the individual attempting to gain access is who they claim to be. With multi-factor authentication, an attacker would need to compromise at least two different authentication mechanisms, increasing the difficulty of compromise and thus reducing the risk. | link | count: 002 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.1.4 | CIS_Azure_2.0.0_1.1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 1.1.4 | 1.1 | Ensure that 'Allow users to remember multi-factor authentication on devices they trust' is Disabled | Shared | For every login attempt, the user will be required to perform multi-factor authentication. | Do not allow users to remember multi-factor authentication on devices. Remembering Multi-Factor Authentication (MFA) for devices and browsers allows users to have the option to bypass MFA for a set number of days after performing a successful sign-in using MFA. This can enhance usability by minimizing the number of times a user may need to perform two-step verification on the same device. However, if an account or device is compromised, remembering MFA for trusted devices may affect security. Hence, it is recommended that users not be allowed to bypass MFA. | link | count: 003 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.10 | CIS_Azure_2.0.0_1.10 | CIS Microsoft Azure Foundations Benchmark recommendation 1.10 | 1 | Ensure That 'Notify all admins when other admins reset their password?' is set to 'Yes' | Shared | All Global Administrators will receive a notification from Azure every time a password is reset. This is useful for auditing procedures to confirm that there are no out of the ordinary password resets for Global Administrators. There is additional overhead, however, in the time required for Global Administrators to audit the notifications. This setting is only useful if all Global Administrators pay attention to the notifications, and audit each one. | Ensure that all Global Administrators are notified if any other administrator resets their password. Global Administrator accounts are sensitive. Any password reset activity notification, when sent to all Global Administrators, ensures that all Global administrators can passively confirm if such a reset is a common pattern within their group. For example, if all Global Administrators change their password every 30 days, any password reset activity before that may require administrator(s) to evaluate any unusual activity and confirm its origin. | link | count: 010 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.11 | CIS_Azure_2.0.0_1.11 | CIS Microsoft Azure Foundations Benchmark recommendation 1.11 | 1 | Ensure `User consent for applications` is set to `Do not allow user consent` | Shared | Enforcing this setting may create additional requests that administrators need to review. | Require administrators to provide consent for applications before use. If Azure Active Directory is running as an identity provider for third-party applications, permissions and consent should be limited to administrators or pre-approved. Malicious applications may attempt to exfiltrate data or abuse privileged user accounts. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.13 | CIS_Azure_2.0.0_1.13 | CIS Microsoft Azure Foundations Benchmark recommendation 1.13 | 1 | Ensure that 'Users can add gallery apps to My Apps' is set to 'No' | Shared | Can cause additional requests to administrators that need to be fulfilled quite often. | Require administrators to provide consent for the apps before use. Unless Azure Active Directory is running as an identity provider for third-party applications, do not allow users to use their identity outside of your cloud environment. User profiles contain private information such as phone numbers and email addresses which could then be sold off to other third parties without requiring any further consent from the user. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.14 | CIS_Azure_2.0.0_1.14 | CIS Microsoft Azure Foundations Benchmark recommendation 1.14 | 1 | Ensure That 'Users Can Register Applications' Is Set to 'No' | Shared | Enforcing this setting will create additional requests for approval that will need to be addressed by an administrator. If permissions are delegated, a user may approve a malevolent third party application, potentially giving it access to your data. | Require administrators or appropriately delegated users to register third-party applications. It is recommended to only allow an administrator to register custom-developed applications. This ensures that the application undergoes a formal security review and approval process prior to exposing Azure Active Directory data. Certain users like developers or other high-request users may also be delegated permissions to prevent them from waiting on an administrative user. Your organization should review your policies and decide your needs. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.15 | CIS_Azure_2.0.0_1.15 | CIS Microsoft Azure Foundations Benchmark recommendation 1.15 | 1 | Ensure That 'Guest users access restrictions' is set to 'Guest user access is restricted to properties and memberships of their own directory objects' | Shared | This may create additional requests for permissions to access resources that administrators will need to approve. | Limit guest user permissions. Limiting guest access ensures that guest accounts do not have permission for certain directory tasks, such as enumerating users, groups or other directory resources, and cannot be assigned to administrative roles in your directory. Guest access has three levels of restriction. 1. Guest users have the same access as members (most inclusive), 2. Guest users have limited access to properties and memberships of directory objects (default value), 3. Guest user access is restricted to properties and memberships of their own directory objects (most restrictive). The recommended option is the 3rd, most restrictive: "Guest user access is restricted to their own directory object". | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.16 | CIS_Azure_2.0.0_1.16 | CIS Microsoft Azure Foundations Benchmark recommendation 1.16 | 1 | Ensure that 'Guest invite restrictions' is set to "Only users assigned to specific admin roles can invite guest users" | Shared | With the option of `Only users assigned to specific admin roles can invite guest users` selected, users with specific admin roles will be in charge of sending invitations to the external users, requiring additional overhead by them to manage user accounts. This will mean coordinating with other departments as they are onboarding new users. | Restrict invitations to users with specific administrative roles only. Restricting invitations to users with specific administrator roles ensures that only authorized accounts have access to cloud resources. This helps to maintain "Need to Know" permissions and prevents inadvertent access to data. By default the setting `Guest invite restrictions` is set to `Anyone in the organization can invite guest users including guests and non-admins`. This would allow anyone within the organization to invite guests and non-admins to the tenant, posing a security risk. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.17 | CIS_Azure_2.0.0_1.17 | CIS Microsoft Azure Foundations Benchmark recommendation 1.17 | 1 | Ensure That 'Restrict access to Azure AD administration portal' is Set to 'Yes' | Shared | All administrative tasks will need to be done by Administrators, causing additional overhead in management of users and resources. | Restrict access to the Azure AD administration portal to administrators only. **NOTE**: This only affects access to the Azure AD administrator's web portal. This setting does not prohibit privileged users from using other methods such as Rest API or Powershell to obtain sensitive information from Azure AD. The Azure AD administrative portal has sensitive data and permission settings. All non-administrators should be prohibited from accessing any Azure AD data in the administration portal to avoid exposure. | link | count: 006 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.18 | CIS_Azure_2.0.0_1.18 | CIS Microsoft Azure Foundations Benchmark recommendation 1.18 | 1 | Ensure that 'Restrict user ability to access groups features in the Access Pane' is Set to 'Yes' | Shared | Setting to `Yes` could create administrative overhead by customers seeking certain group memberships that will have to be manually managed by administrators with appropriate permissions. | Restricts group creation to administrators with permissions only. Self-service group management enables users to create and manage security groups or Office 365 groups in Azure Active Directory (Azure AD). Unless a business requires this day-to-day delegation for some users, self-service group management should be disabled. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.19 | CIS_Azure_2.0.0_1.19 | CIS Microsoft Azure Foundations Benchmark recommendation 1.19 | 1 | Ensure that 'Users can create security groups in Azure portals, API or PowerShell' is set to 'No' | Shared | Enabling this setting could create a number of requests that would need to be managed by an administrator. | Restrict security group creation to administrators only. When creating security groups is enabled, all users in the directory are allowed to create new security groups and add members to those groups. Unless a business requires this day-to-day delegation, security group creation should be restricted to administrators only. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.20 | CIS_Azure_2.0.0_1.20 | CIS Microsoft Azure Foundations Benchmark recommendation 1.20 | 1 | Ensure that 'Owners can manage group membership requests in the Access Panel' is set to 'No' | Shared | Group Membership for user accounts will need to be handled by Admins and cause administrative overhead. | Restrict security group management to administrators only. Restricting security group management to administrators only prohibits users from making changes to security groups. This ensures that security groups are appropriately managed and their management is not delegated to non-administrators. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.21 | CIS_Azure_2.0.0_1.21 | CIS Microsoft Azure Foundations Benchmark recommendation 1.21 | 1 | Ensure that 'Users can create Microsoft 365 groups in Azure portals, API or PowerShell' is set to 'No' | Shared | Enabling this setting could create a number of requests that would need to be managed by an administrator. | Restrict Microsoft 365 group creation to administrators only. Restricting Microsoft 365 group creation to administrators only ensures that creation of Microsoft 365 groups is controlled by the administrator. Appropriate groups should be created and managed by the administrator and group creation rights should not be delegated to any other user. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.22 | CIS_Azure_2.0.0_1.22 | CIS Microsoft Azure Foundations Benchmark recommendation 1.22 | 1 | Ensure that 'Require Multi-Factor Authentication to register or join devices with Azure AD' is set to 'Yes' | Shared | A slight impact of additional overhead, as Administrators will now have to approve every access to the domain. | Joining or registering devices to the active directory should require Multi-factor authentication. Multi-factor authentication is recommended when adding devices to Azure AD. When set to `Yes`, users who are adding devices from the internet must first use the second method of authentication before their device is successfully added to the directory. This ensures that rogue devices are not added to the domain using a compromised user account. _Note:_ Some Microsoft documentation suggests to use conditional access policies for joining a domain from certain whitelisted networks or devices. Even with these in place, using Multi-Factor Authentication is still recommended, as it creates a process for review before joining the domain. | link | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.23 | CIS_Azure_2.0.0_1.23 | CIS Microsoft Azure Foundations Benchmark recommendation 1.23 | 1 | Ensure That No Custom Subscription Administrator Roles Exist | Shared | Subscriptions will need to be handled by Administrators with permissions. | The principle of least privilege should be followed and only necessary privileges should be assigned instead of allowing full administrative access. Classic subscription admin roles offer basic access management and include Account Administrator, Service Administrator, and Co-Administrators. It is recommended the least necessary permissions be given initially. Permissions can be added as needed by the account holder. This ensures the account holder cannot perform actions which were not intended. | link | count: 007 Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
General, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.24 | CIS_Azure_2.0.0_1.24 | CIS Microsoft Azure Foundations Benchmark recommendation 1.24 | 1 | Ensure a Custom Role is Assigned Permissions for Administering Resource Locks | Shared | By adding this role, specific permissions may be granted for managing just resource locks rather than needing to provide the wide Owner or User Access Administrator role, reducing the risk of the user being able to do unintentional damage. | Resource locking is a powerful protection mechanism that can prevent inadvertent modification/deletion of resources within Azure subscriptions/Resource Groups and is a recommended NIST configuration. Given the resource lock functionality is outside of standard Role Based Access Control(RBAC), it would be prudent to create a resource lock administrator role to prevent inadvertent unlocking of resources. | link | count: 004 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.5 | CIS_Azure_2.0.0_1.5 | CIS Microsoft Azure Foundations Benchmark recommendation 1.5 | 1 | Ensure Guest Users Are Reviewed on a Regular Basis | Shared | Before removing guest users, determine their use and scope. Like removing any user, there may be unforeseen consequences to systems if it is deleted. | Azure AD is extended to include Azure AD B2B collaboration, allowing you to invite people from outside your organization to be guest users in your cloud account and sign in with their own work, school, or social identities. Guest users allow you to share your company's applications and services with users from any other organization, while maintaining control over your own corporate data. Work with external partners, large or small, even if they don't have Azure AD or an IT department. A simple invitation and redemption process lets partners use their own credentials to access your company's resources as a guest user. Guest users in every subscription should be review on a regular basis to ensure that inactive and unneeded accounts are removed. Guest users in the Azure AD are generally required for collaboration purposes in Office 365, and may also be required for Azure functions in enterprises with multiple Azure tenants. Guest users are typically added outside your employee on-boarding/off-boarding process and could potentially be overlooked indefinitely, leading to a potential vulnerability. To prevent this, guest users should be reviewed on a regular basis. During this audit, guest users should also be determined to not have administrative privileges. | link | count: 008 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.8 | CIS_Azure_2.0.0_1.8 | CIS Microsoft Azure Foundations Benchmark recommendation 1.8 | 1 | Ensure that 'Number of days before users are asked to re-confirm their authentication information' is not set to '0' | Shared | Users will be prompted for their multifactor authentication at the duration set here. | Ensure that the number of days before users are asked to re-confirm their authentication information is not set to 0. This setting is necessary if you have setup 'Require users to register when signing in option'. If authentication re-confirmation is disabled, registered users will never be prompted to re-confirm their existing authentication information. If the authentication information for a user changes, such as a phone number or email, then the password reset information for that user reverts to the previously registered authentication information. | link | count: 004 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 1.9 | CIS_Azure_2.0.0_1.9 | CIS Microsoft Azure Foundations Benchmark recommendation 1.9 | 1 | Ensure that 'Notify users on password resets?' is set to 'Yes' | Shared | Users will receive emails alerting them to password changes to both their primary and secondary emails. | Ensure that users are notified on their primary and secondary emails on password resets. User notification on password reset is a proactive way of confirming password reset activity. It helps the user to recognize unauthorized password reset activities. | link | count: 005 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 10.1 | CIS_Azure_2.0.0_10.1 | CIS Microsoft Azure Foundations Benchmark recommendation 10.1 | 10 | Ensure that Resource Locks are set for Mission-Critical Azure Resources | Shared | There can be unintended outcomes of locking a resource. Applying a lock to a parent service will cause it to be inherited by all resources within. Conversely, applying a lock to a resource may not apply to connected storage, leaving it unlocked. Please see the documentation for further information. | Resource Manager Locks provide a way for administrators to lock down Azure resources to prevent deletion of, or modifications to, a resource. These locks sit outside of the Role Based Access Controls (RBAC) hierarchy and, when applied, will place restrictions on the resource for all users. These locks are very useful when there is an important resource in a subscription that users should not be able to delete or change. Locks can help prevent accidental and malicious changes or deletion. As an administrator, it may be necessary to lock a subscription, resource group, or resource to prevent other users in the organization from accidentally deleting or modifying critical resources. The lock level can be set to to `CanNotDelete` or `ReadOnly` to achieve this purpose. - `CanNotDelete` means authorized users can still read and modify a resource, but they cannot delete the resource. - `ReadOnly` means authorized users can read a resource, but they cannot delete or update the resource. Applying this lock is similar to restricting all authorized users to the permissions granted by the Reader role. | link | count: 001 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.1 | CIS_Azure_2.0.0_2.1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.1 | 2.1 | Ensure That Microsoft Defender for Servers Is Set to 'On' | Shared | Turning on Microsoft Defender for Servers in Microsoft Defender for Cloud incurs an additional cost per resource. | Turning on Microsoft Defender for Servers enables threat detection for Servers, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. Enabling Microsoft Defender for Servers allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC). | link | count: 009 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.10 | CIS_Azure_2.0.0_2.1.10 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.10 | 2.1 | Ensure That Microsoft Defender for Key Vault Is Set To 'On' | Shared | Turning on Microsoft Defender for Key Vault incurs an additional cost per resource. | Turning on Microsoft Defender for Key Vault enables threat detection for Key Vault, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. Enabling Microsoft Defender for Key Vault allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC). | link | count: 009 Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.11 | CIS_Azure_2.0.0_2.1.11 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.11 | 2.1 | Ensure That Microsoft Defender for DNS Is Set To 'On' | Shared | Enabling Microsoft Defender for DNS requires enabling Microsoft Defender for your subscription. Both will incur additional charges, with Defender for DNS being a small amount per million queries. | Microsoft Defender for DNS scans all network traffic exiting from within a subscription. DNS lookups within a subscription are scanned and compared to a dynamic list of websites that might be potential security threats. These threats could be a result of a security breach within your services, thus scanning for them could prevent a potential security threat from being introduced. | link | count: 001 [Deprecated]: Azure Defender for DNS should be enabled (bdc59948-5574-49b3-bb91-76b7c986428d) |
Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.12 | CIS_Azure_2.0.0_2.1.12 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.12 | 2.1 | Ensure That Microsoft Defender for Resource Manager Is Set To 'On' | Shared | Enabling Microsoft Defender for Resource Manager requires enabling Microsoft Defender for your subscription. Both will incur additional charges. | Microsoft Defender for Resource Manager scans incoming administrative requests to change your infrastructure from both CLI and the Azure portal. Scanning resource requests lets you be alerted every time there is suspicious activity in order to prevent a security threat from being introduced. | link | count: 001 Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99) |
Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.13 | CIS_Azure_2.0.0_2.1.13 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.13 | 2.1 | Ensure that Microsoft Defender Recommendation for 'Apply system updates' status is 'Completed' | Shared | Running Microsoft Defender for Cloud incurs additional charges for each resource monitored. Please see attached reference for exact charges per hour. | Ensure that the latest OS patches for all virtual machines are applied. Windows and Linux virtual machines should be kept updated to: - Address a specific bug or flaw - Improve an OS or application’s general stability - Fix a security vulnerability The Azure Security Center retrieves a list of available security and critical updates from Windows Update or Windows Server Update Services (WSUS), depending on which service is configured on a Windows VM. The security center also checks for the latest updates in Linux systems. If a VM is missing a system update, the security center will recommend system updates be applied. | link | count: 001 Machines should be configured to periodically check for missing system updates (bd876905-5b84-4f73-ab2d-2e7a7c4568d9) |
Azure Update Manager | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.14 | CIS_Azure_2.0.0_2.1.14 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.14 | 2.1 | Ensure Any of the ASC Default Policy Settings are Not Set to 'Disabled' | Shared | n/a | None of the settings offered by ASC Default policy should be set to effect `Disabled`. A security policy defines the desired configuration of your workloads and helps ensure compliance with company or regulatory security requirements. ASC Default policy is associated with every subscription by default. ASC default policy assignment is a set of security recommendations based on best practices. Enabling recommendations in ASC default policy ensures that Azure security center provides the ability to monitor all of the supported recommendations and optionally allow automated action for a few of the supported recommendations. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.15 | CIS_Azure_2.0.0_2.1.15 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.15 | 2.1 | Ensure that Auto provisioning of 'Log Analytics agent for Azure VMs' is Set to 'On' | Shared | n/a | Enable automatic provisioning of the monitoring agent to collect security data. When `Log Analytics agent for Azure VMs` is turned on, Microsoft Defender for Cloud provisions the Microsoft Monitoring Agent on all existing supported Azure virtual machines and any new ones that are created. The Microsoft Monitoring Agent scans for various security-related configurations and events such as system updates, OS vulnerabilities, endpoint protection, and provides alerts. | link | count: 003 Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.17 | CIS_Azure_2.0.0_2.1.17 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.17 | 2.1 | Ensure that Auto provisioning of 'Microsoft Defender for Containers components' is Set to 'On' | Shared | Microsoft Defender for Containers will require additional licensing. | Enable automatic provisioning of the Microsoft Defender for Containers components. As with any compute resource, Container environments require hardening and run-time protection to ensure safe operations and detection of threats and vulnerabilities. | link | count: 009 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.19 | CIS_Azure_2.0.0_2.1.19 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.19 | 2.1 | Ensure 'Additional email addresses' is Configured with a Security Contact Email | Shared | n/a | Microsoft Defender for Cloud emails the subscription owners whenever a high-severity alert is triggered for their subscription. You should provide a security contact email address as an additional email address. Microsoft Defender for Cloud emails the Subscription Owner to notify them about security alerts. Adding your Security Contact's email address to the 'Additional email addresses' field ensures that your organization's Security Team is included in these alerts. This ensures that the proper people are aware of any potential compromise in order to mitigate the risk in a timely fashion. | link | count: 001 Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.2 | CIS_Azure_2.0.0_2.1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.2 | 2.1 | Ensure That Microsoft Defender for App Services Is Set To 'On' | Shared | Turning on Microsoft Defender for App Service incurs an additional cost per resource. | Turning on Microsoft Defender for App Service enables threat detection for App Service, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. Enabling Microsoft Defender for App Service allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC). | link | count: 009 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.20 | CIS_Azure_2.0.0_2.1.20 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.20 | 2.1 | Ensure That 'Notify about alerts with the following severity' is Set to 'High' | Shared | n/a | Enables emailing security alerts to the subscription owner or other designated security contact. Enabling security alert emails ensures that security alert emails are received from Microsoft. This ensures that the right people are aware of any potential security issues and are able to mitigate the risk. | link | count: 001 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899) |
Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.21 | CIS_Azure_2.0.0_2.1.21 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.21 | 2.1 | Ensure that Microsoft Defender for Cloud Apps integration with Microsoft Defender for Cloud is Selected | Shared | Microsoft Defender for Cloud Apps works with Standard pricing tier Subscription. Choosing the Standard pricing tier of Microsoft Defender for Cloud incurs an additional cost per resource. | This integration setting enables Microsoft Defender for Cloud Apps (formerly 'Microsoft Cloud App Security' or 'MCAS' - see additional info) to communicate with Microsoft Defender for Cloud. Microsoft Defender for Cloud offers an additional layer of protection by using Azure Resource Manager events, which is considered to be the control plane for Azure. By analyzing the Azure Resource Manager records, Microsoft Defender for Cloud detects unusual or potentially harmful operations in the Azure subscription environment. Several of the preceding analytics are powered by Microsoft Defender for Cloud Apps. To benefit from these analytics, subscription must have a Cloud App Security license. Microsoft Defender for Cloud Apps works only with Standard Tier subscriptions. | link | count: 008 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.22 | CIS_Azure_2.0.0_2.1.22 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.22 | 2.1 | Ensure that Microsoft Defender for Endpoint integration with Microsoft Defender for Cloud is selected | Shared | Microsoft Defender for Endpoint works with Standard pricing tier Subscription. Choosing the Standard pricing tier of Microsoft Defender for Cloud incurs an additional cost per resource. | This integration setting enables Microsoft Defender for Endpoint (formerly 'Advanced Threat Protection' or 'ATP' or 'WDATP' - see additional info) to communicate with Microsoft Defender for Cloud. **IMPORTANT:** When enabling integration between DfE & DfC it needs to be taken into account that this will have some side effects that may be undesirable. 1. For server 2019 & above if defender is installed (default for these server SKU's) this will trigger a deployment of the new unified agent and link to any of the extended configuration in the Defender portal. 1. If the new unified agent is required for server SKU's of Win 2016 or Linux and lower there is additional integration that needs to be switched on and agents need to be aligned. Microsoft Defender for Endpoint integration brings comprehensive Endpoint Detection and Response (EDR) capabilities within Microsoft Defender for Cloud. This integration helps to spot abnormalities, as well as detect and respond to advanced attacks on endpoints monitored by Microsoft Defender for Cloud. MDE works only with Standard Tier subscriptions. | link | count: 008 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.3 | CIS_Azure_2.0.0_2.1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.3 | 2.1 | Ensure That Microsoft Defender for Databases Is Set To 'On' | Shared | Running Defender on Infrastructure as a service (IaaS) may incur increased costs associated with running the service and the instance it is on. Similarly, you will need qualified personnel to maintain the operating system and software updates. If it is not maintained, security patches will not be applied and it may be open to vulnerabilities. | Turning on Microsoft Defender for Databases enables threat detection for the instances running your database software. This provides threat intelligence, anomaly detection, and behavior analytics in the Azure Microsoft Defender for Cloud. Instead of being enabled on services like Platform as a Service (PaaS), this implementation will run within your instances as Infrastructure as a Service (IaaS) on the Operating Systems hosting your databases. Enabling Microsoft Defender for Azure SQL Databases allows your organization more granular control of the infrastructure running your database software. Instead of waiting on Microsoft release updates or other similar processes, you can manage them yourself. Threat detection is provided by the Microsoft Security Response Center (MSRC). | link | count: 004 Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Microsoft Defender for Azure Cosmos DB should be enabled (adbe85b5-83e6-4350-ab58-bf3a4f736e5e) |
Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.4 | CIS_Azure_2.0.0_2.1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.4 | 2.1 | Ensure That Microsoft Defender for Azure SQL Databases Is Set To 'On' | Shared | Turning on Microsoft Defender for Azure SQL Databases incurs an additional cost per resource. | Turning on Microsoft Defender for Azure SQL Databases enables threat detection for Azure SQL database servers, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. Enabling Microsoft Defender for Azure SQL Databases allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC). | link | count: 009 Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.5 | CIS_Azure_2.0.0_2.1.5 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.5 | 2.1 | Ensure That Microsoft Defender for SQL Servers on Machines Is Set To 'On' | Shared | Turning on Microsoft Defender for SQL servers on machines incurs an additional cost per resource. | Turning on Microsoft Defender for SQL servers on machines enables threat detection for SQL servers on machines, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. Enabling Microsoft Defender for SQL servers on machines allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC). | link | count: 009 Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.6 | CIS_Azure_2.0.0_2.1.6 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.6 | 2.1 | Ensure That Microsoft Defender for Open-Source Relational Databases Is Set To 'On' | Shared | Turning on Microsoft Defender for Open-source relational databases incurs an additional cost per resource. | Turning on Microsoft Defender for Open-source relational databases enables threat detection for Open-source relational databases, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. Enabling Microsoft Defender for Open-source relational databases allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC). | link | count: 001 Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835) |
Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.7 | CIS_Azure_2.0.0_2.1.7 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.7 | 2.1 | Ensure That Microsoft Defender for Storage Is Set To 'On' | Shared | Turning on Microsoft Defender for Storage incurs an additional cost per resource. | Turning on Microsoft Defender for Storage enables threat detection for Storage, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. Enabling Microsoft Defender for Storage allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC). | link | count: 009 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.8 | CIS_Azure_2.0.0_2.1.8 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.8 | 2.1 | Ensure That Microsoft Defender for Containers Is Set To 'On' | Shared | Turning on Microsoft Defender for Containers incurs an additional cost per resource. | Turning on Microsoft Defender for Containers enables threat detection for Container Registries including Kubernetes, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud. Enabling Microsoft Defender for Container Registries allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC). | link | count: 009 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 2.1.9 | CIS_Azure_2.0.0_2.1.9 | CIS Microsoft Azure Foundations Benchmark recommendation 2.1.9 | 2.1 | Ensure That Microsoft Defender for Azure Cosmos DB Is Set To 'On' | Shared | Enabling Microsoft Defender for Azure Cosmos DB requires enabling Microsoft Defender for your subscription. Both will incur additional charges. | Microsoft Defender for Azure Cosmos DB scans all incoming network requests for threats to your Azure Cosmos DB resources. In scanning Azure Cosmos DB requests within a subscription, requests are compared to a heuristic list of potential security threats. These threats could be a result of a security breach within your services, thus scanning for them could prevent a potential security threat from being introduced. | link | count: 001 Microsoft Defender for Azure Cosmos DB should be enabled (adbe85b5-83e6-4350-ab58-bf3a4f736e5e) |
Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.1 | CIS_Azure_2.0.0_3.1 | CIS Microsoft Azure Foundations Benchmark recommendation 3.1 | 3 | Ensure that 'Secure transfer required' is set to 'Enabled' | Shared | n/a | Enable data encryption in transit. The secure transfer option enhances the security of a storage account by only allowing requests to the storage account by a secure connection. For example, when calling REST APIs to access storage accounts, the connection must use HTTPS. Any requests using HTTP will be rejected when 'secure transfer required' is enabled. When using the Azure files service, connection without encryption will fail, including scenarios using SMB 2.1, SMB 3.0 without encryption, and some flavors of the Linux SMB client. Because Azure storage doesn’t support HTTPS for custom domain names, this option is not applied when using a custom domain name. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.10 | CIS_Azure_2.0.0_3.10 | CIS Microsoft Azure Foundations Benchmark recommendation 3.10 | 3 | Ensure Private Endpoints are used to access Storage Accounts | Shared | There is no cost in deploying VNets between Azure resources. If improperly implemented, it may result in loss of critical network traffic. | Use private endpoints for your Azure Storage accounts to allow clients and services to securely access data located over a network via an encrypted Private Link. To do this, the private endpoint uses an IP address from the VNet for each service. Network traffic between disparate services securely traverses encrypted over the VNet. This VNet can also link addressing space, extending your network and accessing resources on it. Similarly, it can be a tunnel through public networks to connect remote infrastructures together. This creates further security through segmenting network traffic and preventing outside sources from accessing it. Securing traffic between services through encryption protects the data from easy interception and reading. | link | count: 001 Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9) |
Storage | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.12 | CIS_Azure_2.0.0_3.12 | CIS Microsoft Azure Foundations Benchmark recommendation 3.12 | 3 | Ensure Storage for Critical Data are Encrypted with Customer Managed Keys | Shared | If the key expires by setting the 'activation date' and 'expiration date', the user must rotate the key manually. Using Customer Managed Keys may also incur additional man-hour requirements to create, store, manage, and protect the keys as needed. | Enable sensitive data encryption at rest using Customer Managed Keys rather than Microsoft Managed keys. By default, data in the storage account is encrypted using Microsoft Managed Keys at rest. All Azure Storage resources are encrypted, including blobs, disks, files, queues, and tables. All object metadata is also encrypted. If you want to control and manage this encryption key yourself, however, you can specify a customer-managed key. That key is used to protect and control access to the key that encrypts your data. You can also choose to automatically update the key version used for Azure Storage encryption whenever a new version is available in the associated Key Vault. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.13 | CIS_Azure_2.0.0_3.13 | CIS Microsoft Azure Foundations Benchmark recommendation 3.13 | 3 | Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests | Shared | Being a level 2, enabling this setting can have a high impact on the cost of data storage used for logging more data per each request. Do not enable this without determining your need for this level of logging or forget to check in on data usage and projected cost. | The Storage Blob service provides scalable, cost-efficient object storage in the cloud. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the blobs. Storage Logging log entries contain the following information about individual requests: timing information such as start time, end-to-end latency, and server latency; authentication details; concurrency information; and the sizes of the request and response messages. Storage Analytics logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor each individual request to a storage service for increased security or diagnostics. Requests are logged on a best-effort basis. Storage Analytics logging is not enabled by default for your storage account. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.14 | CIS_Azure_2.0.0_3.14 | CIS Microsoft Azure Foundations Benchmark recommendation 3.14 | 3 | Ensure Storage Logging is Enabled for Table Service for 'Read', 'Write', and 'Delete' Requests | Shared | Being a level 2, enabling this setting can have a high impact on the cost of data storage used for logging more data per each request. Do not enable this without determining your need for this level of logging or forget to check in on data usage and projected cost. | Azure Table storage is a service that stores structured NoSQL data in the cloud, providing a key/attribute store with a schema-less design. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the tables. Storage Logging log entries contain the following information about individual requests: timing information such as start time, end-to-end latency, and server latency; authentication details; concurrency information; and the sizes of the request and response messages. Storage Analytics logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor each individual request to a storage service for increased security or diagnostics. Requests are logged on a best-effort basis. Storage Analytics logging is not enabled by default for your storage account. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.15 | CIS_Azure_2.0.0_3.15 | CIS Microsoft Azure Foundations Benchmark recommendation 3.15 | 3 | Ensure the "Minimum TLS version" for storage accounts is set to "Version 1.2" | Shared | When set to TLS 1.2 all requests must leverage this version of the protocol. Applications leveraging legacy versions of the protocol will fail. | In some cases, Azure Storage sets the minimum TLS version to be version 1.0 by default. TLS 1.0 is a legacy version and has known vulnerabilities. This minimum TLS version can be configured to be later protocols such as TLS 1.2. TLS 1.0 has known vulnerabilities and has been replaced by later versions of the TLS protocol. Continued use of this legacy protocol affects the security of data in transit. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Storage accounts should have the specified minimum TLS version (fe83a0eb-a853-422d-aac2-1bffd182c5d0) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.2 | CIS_Azure_2.0.0_3.2 | CIS Microsoft Azure Foundations Benchmark recommendation 3.2 | 3 | Ensure that ‘Enable Infrastructure Encryption’ for Each Storage Account in Azure Storage is Set to ‘enabled’ | Shared | The read and write speeds to the storage will be impacted if both default encryption and Infrastructure Encryption are checked, as a secondary form of encryption requires more resource overhead for the cryptography of information. This performance impact should be considered in an analysis for justifying use of the feature in your environment. Customer-managed keys are recommended for the most secure implementation, leading to overhead of key management. The key will also need to be backed up in a secure location, as loss of the key will mean loss of the information in the storage. | Enabling encryption at the hardware level on top of the default software encryption for Storage Accounts accessing Azure storage solutions. Azure Storage automatically encrypts all data in a storage account at the network level using 256-bit AES encryption, which is one of the strongest, FIPS 140-2-compliant block ciphers available. Customers who require higher levels of assurance that their data is secure can also enable 256-bit AES encryption at the Azure Storage infrastructure level for double encryption. Double encryption of Azure Storage data protects against a scenario where one of the encryption algorithms or keys may be compromised. Similarly, data is encrypted even before network transmission and in all backups. In this scenario, the additional layer of encryption continues to protect your data. For the most secure implementation of key based encryption, it is recommended to use a Customer Managed asymmetric RSA 2048 Key in Azure Key Vault. | link | count: 001 Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a) |
Storage | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.4 | CIS_Azure_2.0.0_3.4 | CIS Microsoft Azure Foundations Benchmark recommendation 3.4 | 3 | Ensure that Storage Account Access Keys are Periodically Regenerated | Shared | Regenerating access keys can affect services in Azure as well as the organization's applications that are dependent on the storage account. All clients who use the access key to access the storage account must be updated to use the new key. | For increased security, regenerate storage account access keys periodically. When a storage account is created, Azure generates two 512-bit storage access keys which are used for authentication when the storage account is accessed. Rotating these keys periodically ensures that any inadvertent access or exposure does not result from the compromise of these keys. Cryptographic key rotation periods will vary depending on your organization's security requirements and the type of data which is being stored in the Storage Account. For example, PCI DSS mandates that cryptographic keys be replaced or rotated 'regularly,' and advises that keys for static data stores be rotated every 'few months.' For the purposes of this recommendation, 90 days will prescribed for the reminder. Review and adjustment of the 90 day period is recommended, and may even be necessary. Your organization's security requirements should dictate the appropriate setting. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.5 | CIS_Azure_2.0.0_3.5 | CIS Microsoft Azure Foundations Benchmark recommendation 3.5 | 3 | Ensure Storage Logging is Enabled for Queue Service for 'Read', 'Write', and 'Delete' requests | Shared | Enabling this setting can have a high impact on the cost of the log analytics service and data storage used by logging more data per each request. Do not enable this without determining your need for this level of logging, and do not forget to check in on data usage and projected cost. Some users have seen their logging costs increase from $10 per month to $10,000 per month. | The Storage Queue service stores messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size using version 2011-08-18 or newer. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the queues. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details, concurrency information, and the sizes of the request and response messages. Storage Analytics logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor individual requests and to diagnose issues with a storage service. Requests are logged on a best-effort basis. Storage Analytics logging is not enabled by default for your storage account. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.6 | CIS_Azure_2.0.0_3.6 | CIS Microsoft Azure Foundations Benchmark recommendation 3.6 | 3 | Ensure that Shared Access Signature Tokens Expire Within an Hour | Shared | n/a | Expire shared access signature tokens within an hour. A shared access signature (SAS) is a URI that grants restricted access rights to Azure Storage resources. A shared access signature can be provided to clients who should not be trusted with the storage account key but for whom it may be necessary to delegate access to certain storage account resources. Providing a shared access signature URI to these clients allows them access to a resource for a specified period of time. This time should be set as low as possible and preferably no longer than an hour. | link | count: 003 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.7 | CIS_Azure_2.0.0_3.7 | CIS Microsoft Azure Foundations Benchmark recommendation 3.7 | 3 | Ensure that 'Public access level' is disabled for storage accounts with blob containers | Shared | Access will have to be managed using shared access signatures or via Azure AD RBAC. | Disallowing public access for a storage account overrides the public access settings for individual containers in that storage account. The default configuration for a storage account permits a user with appropriate permissions to configure public (anonymous) access to containers and blobs in a storage account. Keep in mind that public access to a container is always turned off by default and must be explicitly configured to permit anonymous requests. It grants read-only access to these resources without sharing the account key, and without requiring a shared access signature. It is recommended not to provide anonymous access to blob containers until, and unless, it is strongly desired. A shared access signature token or Azure AD RBAC should be used for providing controlled and timed access to blob containers. If no anonymous access is needed on any container in the storage account, it’s recommended to set allowBlobPublicAccess false at the account level, which forbids any container to accept anonymous access in the future. | link | count: 007 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.8 | CIS_Azure_2.0.0_3.8 | CIS Microsoft Azure Foundations Benchmark recommendation 3.8 | 3 | Ensure Default Network Access Rule for Storage Accounts is Set to Deny | Shared | All allowed networks will need to be whitelisted on each specific network, creating administrative overhead. This may result in loss of network connectivity, so do not turn on for critical resources during business hours. | Restricting default network access helps to provide a new layer of security, since storage accounts accept connections from clients on any network. To limit access to selected networks, the default action must be changed. Storage accounts should be configured to deny access to traffic from all networks (including internet traffic). Access can be granted to traffic from specific Azure Virtual networks, allowing a secure network boundary for specific applications to be built. Access can also be granted to public internet IP address ranges to enable connections from specific internet or on-premises clients. When network rules are configured, only applications from allowed networks can access a storage account. When calling from an allowed network, applications continue to require proper authorization (a valid access key or SAS token) to access the storage account. | link | count: 002 Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f) |
Storage | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 3.9 | CIS_Azure_2.0.0_3.9 | CIS Microsoft Azure Foundations Benchmark recommendation 3.9 | 3 | Ensure 'Allow Azure services on the trusted services list to access this storage account' is Enabled for Storage Account Access | Shared | This creates authentication credentials for services that need access to storage resources so that services will no longer need to communicate via network request. There may be a temporary loss of communication as you set each Storage Account. It is recommended to not do this on mission-critical resources during business hours. | Some Azure services that interact with storage accounts operate from networks that can't be granted access through network rules. To help this type of service work as intended, allow the set of trusted Azure services to bypass the network rules. These services will then use strong authentication to access the storage account. If the Allow trusted Azure services exception is enabled, the following services are granted access to the storage account: Azure Backup, Azure Site Recovery, Azure DevTest Labs, Azure Event Grid, Azure Event Hubs, Azure Networking, Azure Monitor, and Azure SQL Data Warehouse (when registered in the subscription). Turning on firewall rules for storage account will block access to incoming requests for data, including from other Azure services. We can re-enable this functionality by enabling `"Trusted Azure Services"` through networking exceptions. | link | count: 006 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.1.1 | CIS_Azure_2.0.0_4.1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.1 | 4.1 | Ensure that 'Auditing' is set to 'On' | Shared | n/a | Enable auditing on SQL Servers. The Azure platform allows a SQL server to be created as a service. Enabling auditing at the server level ensures that all existing and newly created databases on the SQL server instance are audited. Auditing policy applied on the SQL database does not override auditing policy and settings applied on the particular SQL server where the database is hosted. Auditing tracks database events and writes them to an audit log in the Azure storage account. It also helps to maintain regulatory compliance, understand database activity, and gain insight into discrepancies and anomalies that could indicate business concerns or suspected security violations. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.1.2 | CIS_Azure_2.0.0_4.1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.2 | 4.1 | Ensure no Azure SQL Databases allow ingress from 0.0.0.0/0 (ANY IP) | Shared | Disabling `Allow Azure services and resources to access this server` will break all connections to SQL server and Hosted Databases unless custom IP specific rules are added in Firewall Policy. | Ensure that no SQL Databases allow ingress from 0.0.0.0/0 (ANY IP). Azure SQL Server includes a firewall to block access to unauthorized connections. More granular IP addresses can be defined by referencing the range of addresses available from specific datacenters. By default, for a SQL server, a Firewall exists with StartIp of 0.0.0.0 and EndIP of 0.0.0.0 allowing access to all the Azure services. Additionally, a custom rule can be set up with StartIp of 0.0.0.0 and EndIP of 255.255.255.255 allowing access from ANY IP over the Internet. In order to reduce the potential attack surface for a SQL server, firewall rules should be defined with more granular IP addresses by referencing the range of addresses available from specific datacenters. | link | count: 003 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.1.3 | CIS_Azure_2.0.0_4.1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.3 | 4.1 | Ensure SQL server's Transparent Data Encryption (TDE) protector is encrypted with Customer-managed key | Shared | Once TDE protector is encrypted with a Customer-managed key, it transfers entire responsibility of respective key management on to you, and hence you should be more careful about doing any operations on the particular key in order to keep data from corresponding SQL server and Databases hosted accessible. When deploying Customer Managed Keys, it is prudent to ensure that you also deploy an automated toolset for managing these keys (this should include discovery and key rotation), and Keys should be stored in an HSM or hardware backed keystore, such as Azure Key Vault. As far as toolsets go, check with your cryptographic key provider, as they may well provide one as an add-on to their service. | Transparent Data Encryption (TDE) with Customer-managed key support provides increased transparency and control over the TDE Protector, increased security with an HSM-backed external service, and promotion of separation of duties. With TDE, data is encrypted at rest with a symmetric key (called the database encryption key) stored in the database or data warehouse distribution. To protect this data encryption key (DEK) in the past, only a certificate that the Azure SQL Service managed could be used. Now, with Customer-managed key support for TDE, the DEK can be protected with an asymmetric key that is stored in the Azure Key Vault. The Azure Key Vault is a highly available and scalable cloud-based key store which offers central key management, leverages FIPS 140-2 Level 2 validated hardware security modules (HSMs), and allows separation of management of keys and data for additional security. Based on business needs or criticality of data/databases hosted on a SQL server, it is recommended that the TDE protector is encrypted by a key that is managed by the data owner (Customer-managed key). Customer-managed key support for Transparent Data Encryption (TDE) allows user control of TDE encryption keys and restricts who can access them and when. Azure Key Vault, Azure’s cloud-based external key management system, is the first key management service where TDE has integrated support for Customer-managed keys. With Customer-managed key support, the database encryption key is protected by an asymmetric key stored in the Key Vault. The asymmetric key is set at the server level and inherited by all databases under that server. | link | count: 006 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.1.4 | CIS_Azure_2.0.0_4.1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.4 | 4.1 | Ensure that Azure Active Directory Admin is Configured for SQL Servers | Shared | This will create administrative overhead with user account and permission management. For further security on these administrative accounts, you may want to consider higher tiers of AAD which support features like Multi Factor Authentication, that will cost more. | Use Azure Active Directory Authentication for authentication with SQL Database to manage credentials in a single place. Azure Active Directory authentication is a mechanism to connect to Microsoft Azure SQL Database and SQL Data Warehouse by using identities in Azure Active Directory (Azure AD). With Azure AD authentication, identities of database users and other Microsoft services can be managed in one central location. Central ID management provides a single place to manage database users and simplifies permission management. - It provides an alternative to SQL Server authentication. - Helps stop the proliferation of user identities across database servers. - Allows password rotation in a single place. - Customers can manage database permissions using external (AAD) groups. - It can eliminate storing passwords by enabling integrated Windows authentication and other forms of authentication supported by Azure Active Directory. - Azure AD authentication uses contained database users to authenticate identities at the database level. - Azure AD supports token-based authentication for applications connecting to SQL Database. - Azure AD authentication supports ADFS (domain federation) or native user/password authentication for a local Azure Active Directory without domain synchronization. - Azure AD supports connections from SQL Server Management Studio that use Active Directory Universal Authentication, which includes Multi-Factor Authentication (MFA). MFA includes strong authentication with a range of easy verification options — phone call, text message, smart cards with pin, or mobile app notification. | link | count: 005 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.1.5 | CIS_Azure_2.0.0_4.1.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.5 | 4.1 | Ensure that 'Data encryption' is set to 'On' on a SQL Database | Shared | n/a | Enable Transparent Data Encryption on every SQL server. Azure SQL Database transparent data encryption helps protect against the threat of malicious activity by performing real-time encryption and decryption of the database, associated backups, and transaction log files at rest without requiring changes to the application. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.1.6 | CIS_Azure_2.0.0_4.1.6 | CIS Microsoft Azure Foundations Benchmark recommendation 4.1.6 | 4.1 | Ensure that 'Auditing' Retention is 'greater than 90 days' | Shared | n/a | SQL Server Audit Retention should be configured to be greater than 90 days. Audit Logs can be used to check for anomalies and give insight into suspected breaches or misuse of information and access. | link | count: 005 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.2.1 | CIS_Azure_2.0.0_4.2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.1 | 4.2 | Ensure that Microsoft Defender for SQL is set to 'On' for critical SQL Servers | Shared | Microsoft Defender for SQL is a paid feature and will incur additional cost for each SQL server. | Enable "Microsoft Defender for SQL" on critical SQL Servers. Microsoft Defender for SQL is a unified package for advanced SQL security capabilities. Microsoft Defender is available for Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics. It includes functionality for discovering and classifying sensitive data, surfacing and mitigating potential database vulnerabilities, and detecting anomalous activities that could indicate a threat to your database. It provides a single go-to location for enabling and managing these capabilities. | link | count: 003 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.2.2 | CIS_Azure_2.0.0_4.2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.2 | 4.2 | Ensure that Vulnerability Assessment (VA) is enabled on a SQL server by setting a Storage Account | Shared | Enabling the `Microsoft Defender for SQL` features will incur additional costs for each SQL server. | Enable Vulnerability Assessment (VA) service scans for critical SQL servers and corresponding SQL databases. Enabling Microsoft Defender for SQL server does not enables Vulnerability Assessment capability for individual SQL databases unless storage account is set to store the scanning data and reports. The Vulnerability Assessment service scans databases for known security vulnerabilities and highlights deviations from best practices, such as misconfigurations, excessive permissions, and unprotected sensitive data. Results of the scan include actionable steps to resolve each issue and provide customized remediation scripts where applicable. Additionally, an assessment report can be customized by setting an acceptable baseline for permission configurations, feature configurations, and database settings. | link | count: 004 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.2.3 | CIS_Azure_2.0.0_4.2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.3 | 4.2 | Ensure that Vulnerability Assessment (VA) setting 'Periodic recurring scans' is set to 'on' for each SQL server | Shared | Enabling the `Azure Defender for SQL` feature will incur additional costs for each SQL server. | Enable Vulnerability Assessment (VA) Periodic recurring scans for critical SQL servers and corresponding SQL databases. VA setting 'Periodic recurring scans' schedules periodic (weekly) vulnerability scanning for the SQL server and corresponding Databases. Periodic and regular vulnerability scanning provides risk visibility based on updated known vulnerability signatures and best practices. | link | count: 003 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.2.4 | CIS_Azure_2.0.0_4.2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.4 | 4.2 | Ensure that Vulnerability Assessment (VA) setting 'Send scan reports to' is configured for a SQL server | Shared | Enabling the `Microsoft Defender for SQL` features will incur additional costs for each SQL server. | Configure 'Send scan reports to' with email addresses of concerned data owners/stakeholders for a critical SQL servers. Vulnerability Assessment (VA) scan reports and alerts will be sent to email addresses configured at 'Send scan reports to'. This may help in reducing time required for identifying risks and taking corrective measures. | link | count: 004 Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.2.5 | CIS_Azure_2.0.0_4.2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.2.5 | 4.2 | Ensure that Vulnerability Assessment (VA) setting 'Also send email notifications to admins and subscription owners' is set for each SQL Server | Shared | Enabling the `Microsoft Defender for SQL` features will incur additional costs for each SQL server. | Enable Vulnerability Assessment (VA) setting 'Also send email notifications to admins and subscription owners'. VA scan reports and alerts will be sent to admins and subscription owners by enabling setting 'Also send email notifications to admins and subscription owners'. This may help in reducing time required for identifying risks and taking corrective measures. | link | count: 005 Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Regulatory Compliance, Security Center, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.3.1 | CIS_Azure_2.0.0_4.3.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.1 | 4.3 | Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server | Shared | n/a | Enable `SSL connection` on `PostgreSQL` Servers. `SSL connectivity` helps to provide a new layer of security by connecting database server to client applications using Secure Sockets Layer (SSL). Enforcing SSL connections between database server and client applications helps protect against "man in the middle" attacks by encrypting the data stream between the server and application. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.3.2 | CIS_Azure_2.0.0_4.3.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.2 | 4.3 | Ensure Server Parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server | Shared | n/a | Enable `log_checkpoints` on `PostgreSQL Servers`. Enabling `log_checkpoints` helps the PostgreSQL Database to `Log each checkpoint` in turn generates query and error logs. However, access to transaction logs is not supported. Query and error logs can be used to identify, troubleshoot, and repair configuration errors and sub-optimal performance. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Log checkpoints should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e43d), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.3.3 | CIS_Azure_2.0.0_4.3.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.3 | 4.3 | Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server | Shared | n/a | Enable `log_connections` on `PostgreSQL Servers`. Enabling `log_connections` helps PostgreSQL Database to log attempted connection to the server, as well as successful completion of client authentication. Log data can be used to identify, troubleshoot, and repair configuration errors and suboptimal performance. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Log connections should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e442), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.3.4 | CIS_Azure_2.0.0_4.3.4 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.4 | 4.3 | Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server | Shared | Enabling this setting will enable a log of all disconnections. If this is enabled for a high traffic server, the log may grow exponentially. | Enable `log_disconnections` on `PostgreSQL Servers`. Enabling `log_disconnections` helps PostgreSQL Database to `Logs end of a session`, including duration, which in turn generates query and error logs. Query and error logs can be used to identify, troubleshoot, and repair configuration errors and sub-optimal performance. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Disconnections should be logged for PostgreSQL database servers. (eb6f77b9-bd53-4e35-a23d-7f65d5f0e446), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.3.5 | CIS_Azure_2.0.0_4.3.5 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.5 | 4.3 | Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server | Shared | n/a | Enable `connection_throttling` on `PostgreSQL Servers`. Enabling `connection_throttling` helps the PostgreSQL Database to `Set the verbosity of logged messages`. This in turn generates query and error logs with respect to concurrent connections that could lead to a successful Denial of Service (DoS) attack by exhausting connection resources. A system can also fail or be degraded by an overload of legitimate users. Query and error logs can be used to identify, troubleshoot, and repair configuration errors and sub-optimal performance. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Connection throttling should be enabled for PostgreSQL database servers (5345bb39-67dc-4960-a1bf-427e16b9a0bd), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.3.6 | CIS_Azure_2.0.0_4.3.6 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.6 | 4.3 | Ensure Server Parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server | Shared | Configuring this setting will result in logs being retained for the specified number of days. If this is configured on a high traffic server, the log may grow quickly to occupy a large amount of disk space. In this case you may want to set this to a lower number. | Ensure `log_retention_days` on `PostgreSQL Servers` is set to an appropriate value. Configuring `log_retention_days` determines the duration in days that `Azure Database for PostgreSQL` retains log files. Query and error logs can be used to identify, troubleshoot, and repair configuration errors and sub-optimal performance. | link | count: 004 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.3.7 | CIS_Azure_2.0.0_4.3.7 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.7 | 4.3 | Ensure 'Allow access to Azure services' for PostgreSQL Database Server is disabled | Shared | n/a | Disable access from Azure services to PostgreSQL Database Server. If access from Azure services is enabled, the server's firewall will accept connections from all Azure resources, including resources not in your subscription. This is usually not a desired configuration. Instead, set up firewall rules to allow access from specific network ranges or VNET rules to allow access from specific virtual networks. | link | count: 007 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.3.8 | CIS_Azure_2.0.0_4.3.8 | CIS Microsoft Azure Foundations Benchmark recommendation 4.3.8 | 4.3 | Ensure 'Infrastructure double encryption' for PostgreSQL Database Server is 'Enabled' | Shared | The read and write speeds to the database will be impacted if both default encryption and Infrastructure Encryption are checked, as a secondary form of encryption requires more resource overhead for the cryptography of information. This cost is justified for information security. Customer managed keys are recommended for the most secure implementation, leading to overhead of key management. The key will also need to be backed up in a secure location, as loss of the key will mean loss of the information in the database. | Azure Database for PostgreSQL servers should be created with 'infrastructure double encryption' enabled. If Double Encryption is enabled, another layer of encryption is implemented at the hardware level before the storage or network level. Information will be encrypted before it is even accessed, preventing both interception of data in motion if the network layer encryption is broken and data at rest in system resources such as memory or processor cache. Encryption will also be in place for any backups taken of the database, so the key will secure access the data in all forms. For the most secure implementation of key based encryption, it is recommended to use a Customer Managed asymmetric RSA 2048 Key in Azure Key Vault. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.4.1 | CIS_Azure_2.0.0_4.4.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.4.1 | 4.4 | Ensure 'Enforce SSL connection' is set to 'Enabled' for Standard MySQL Database Server | Shared | n/a | Enable `SSL connection` on `MYSQL` Servers. SSL connectivity helps to provide a new layer of security by connecting database server to client applications using Secure Sockets Layer (SSL). Enforcing SSL connections between database server and client applications helps protect against "man in the middle" attacks by encrypting the data stream between the server and application. | link | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance, SQL | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.4.2 | CIS_Azure_2.0.0_4.4.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.4.2 | 4.4 | Ensure 'TLS Version' is set to 'TLSV1.2' for MySQL flexible Database Server | Shared | n/a | Ensure `TLS version` on `MySQL flexible` servers is set to the default value. TLS connectivity helps to provide a new layer of security by connecting database server to client applications using Transport Layer Security (TLS). Enforcing TLS connections between database server and client applications helps protect against "man in the middle" attacks by encrypting the data stream between the server and application. | link | count: 003 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.5.1 | CIS_Azure_2.0.0_4.5.1 | CIS Microsoft Azure Foundations Benchmark recommendation 4.5.1 | 4.5 | Ensure That 'Firewalls & Networks' Is Limited to Use Selected Networks Instead of All Networks | Shared | Failure to whitelist the correct networks will result in a connection loss. | Limiting your Cosmos DB to only communicate on whitelisted networks lowers its attack footprint. Selecting certain networks for your Cosmos DB to communicate restricts the number of networks including the internet that can interact with what is stored within the database. | link | count: 001 Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb) |
Cosmos DB | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.5.2 | CIS_Azure_2.0.0_4.5.2 | CIS Microsoft Azure Foundations Benchmark recommendation 4.5.2 | 4.5 | Ensure That Private Endpoints Are Used Where Possible | Shared | Only whitelisted services will have access to communicate with the Cosmos DB. | Private endpoints limit network traffic to approved sources. For sensitive data, private endpoints allow granular control of which services can communicate with Cosmos DB and ensure that this network traffic is private. You set this up on a case by case basis for each service you wish to be connected. | link | count: 001 CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7) |
Cosmos DB | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 4.5.3 | CIS_Azure_2.0.0_4.5.3 | CIS Microsoft Azure Foundations Benchmark recommendation 4.5.3 | 4.5 | Use Azure Active Directory (AAD) Client Authentication and Azure RBAC where possible. | Shared | n/a | Cosmos DB can use tokens or AAD for client authentication which in turn will use Azure RBAC for authorization. Using AAD is significantly more secure because AAD handles the credentials and allows for MFA and centralized management, and the Azure RBAC better integrated with the rest of Azure. AAD client authentication is considerably more secure than token-based authentication because the tokens must be persistent at the client. AAD does not require this. | link | count: 001 Cosmos DB database accounts should have local authentication methods disabled (5450f5bd-9c72-4390-a9c4-a7aba4edfdd2) |
Cosmos DB | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.1.1 | CIS_Azure_2.0.0_5.1.1 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.1 | 5.1 | Ensure that a 'Diagnostic Setting' exists | Shared | n/a | Enable Diagnostic settings for exporting activity logs. Diagnostic settings are available for each individual resource within a subscription. Settings should be configured for all appropriate resources for your environment. A diagnostic setting controls how a diagnostic log is exported. By default, logs are retained only for 90 days. Diagnostic settings should be defined so that logs can be exported and stored for a longer duration in order to analyze security activities within an Azure subscription. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.1.2 | CIS_Azure_2.0.0_5.1.2 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.2 | 5.1 | Ensure Diagnostic Setting captures appropriate categories | Shared | n/a | **Prerequisite**: A Diagnostic Setting must exist. If a Diagnostic Setting does not exist, the navigation and options within this recommendation will not be available. Please review the recommendation at the beginning of this subsection titled: "Ensure that a 'Diagnostic Setting' exists." The diagnostic setting should be configured to log the appropriate activities from the control/management plane. A diagnostic setting controls how the diagnostic log is exported. Capturing the diagnostic setting categories for appropriate control/management plane activities allows proper alerting. | link | count: 008 An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.1.3 | CIS_Azure_2.0.0_5.1.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.3 | 5.1 | Ensure the Storage Container Storing the Activity Logs is not Publicly Accessible | Shared | Configuring container `Access policy` to `private` will remove access from the container for everyone except owners of the storage account. Access policy needs to be set explicitly in order to allow access to other desired users. | The storage account container containing the activity log export should not be publicly accessible. Allowing public access to activity log content may aid an adversary in identifying weaknesses in the affected account's use or configuration. | link | count: 003 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance, Storage | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.1.4 | CIS_Azure_2.0.0_5.1.4 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.4 | 5.1 | Ensure the storage account containing the container with activity logs is encrypted with Customer Managed Key | Shared | **NOTE:** You must have your key vault setup to utilize this. All Audit Logs will be encrypted with a key you provide. You will need to set up customer managed keys separately, and you will select which key to use via the instructions here. You will be responsible for the lifecycle of the keys, and will need to manually replace them at your own determined intervals to keep the data secure. | Storage accounts with the activity log exports can be configured to use Customer Managed Keys (CMK). Configuring the storage account with the activity log export container to use CMKs provides additional confidentiality controls on log data, as a given user must have read permission on the corresponding storage account and must be granted decrypt permission by the CMK. | link | count: 004 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Maintain integrity of audit system (c0559109-6a27-a217-6821-5a6d44f92897), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Storage account containing the container with activity logs must be encrypted with BYOK (fbb99e8e-e444-4da0-9ff1-75c92f5a85b2) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.1.5 | CIS_Azure_2.0.0_5.1.5 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.5 | 5.1 | Ensure that logging for Azure Key Vault is 'Enabled' | Shared | n/a | Enable AuditEvent logging for key vault instances to ensure interactions with key vaults are logged and available. Monitoring how and when key vaults are accessed, and by whom, enables an audit trail of interactions with confidential information, keys, and certificates managed by Azure Keyvault. Enabling logging for Key Vault saves information in an Azure storage account which the user provides. This creates a new container named insights-logs-auditevent automatically for the specified storage account. This same storage account can be used for collecting logs for multiple key vaults. | link | count: 005 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.1.6 | CIS_Azure_2.0.0_5.1.6 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.6 | 5.1 | Ensure that Network Security Group Flow logs are captured and sent to Log Analytics | Shared | The impact of configuring NSG Flow logs is primarily one of cost and configuration. If deployed, it will create storage accounts that hold minimal amounts of data on a 5-day lifecycle before feeding to Log Analytics Workspace. This will increase the amount of data stored and used by Azure Monitor. | Ensure that network flow logs are captured and fed into a central log analytics workspace. Network Flow Logs provide valuable insight into the flow of traffic around your network and feed into both Azure Monitor and Azure Sentinel (if in use), permitting the generation of visual flow diagrams to aid with analyzing for lateral movement, etc. | link | count: 003 All flow log resources should be in enabled state (27960feb-a23c-4577-8d36-ef8b5f35e0be), Audit flow logs configuration for every virtual network (4c3c6c5f-0d47-4402-99b8-aa543dd8bcee), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41) |
Network | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.2.1 | CIS_Azure_2.0.0_5.2.1 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.1 | 5.2 | Ensure that Activity Log Alert exists for Create Policy Assignment | Shared | n/a | Create an activity log alert for the Create Policy Assignment event. Monitoring for create policy assignment events gives insight into changes done in "Azure policy - assignments" and can reduce the time it takes to detect unsolicited changes. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.2.2 | CIS_Azure_2.0.0_5.2.2 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.2 | 5.2 | Ensure that Activity Log Alert exists for Delete Policy Assignment | Shared | n/a | Create an activity log alert for the Delete Policy Assignment event. Monitoring for delete policy assignment events gives insight into changes done in "azure policy - assignments" and can reduce the time it takes to detect unsolicited changes. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.2.3 | CIS_Azure_2.0.0_5.2.3 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.3 | 5.2 | Ensure that Activity Log Alert exists for Create or Update Network Security Group | Shared | n/a | Create an Activity Log Alert for the Create or Update Network Security Group event. Monitoring for Create or Update Network Security Group events gives insight into network access changes and may reduce the time it takes to detect suspicious activity. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.2.4 | CIS_Azure_2.0.0_5.2.4 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.4 | 5.2 | Ensure that Activity Log Alert exists for Delete Network Security Group | Shared | n/a | Create an activity log alert for the Delete Network Security Group event. Monitoring for "Delete Network Security Group" events gives insight into network access changes and may reduce the time it takes to detect suspicious activity. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.2.5 | CIS_Azure_2.0.0_5.2.5 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.5 | 5.2 | Ensure that Activity Log Alert exists for Create or Update Security Solution | Shared | n/a | Create an activity log alert for the Create or Update Security Solution event. Monitoring for Create or Update Security Solution events gives insight into changes to the active security solutions and may reduce the time it takes to detect suspicious activity. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.2.6 | CIS_Azure_2.0.0_5.2.6 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.6 | 5.2 | Ensure that Activity Log Alert exists for Delete Security Solution | Shared | n/a | Create an activity log alert for the Delete Security Solution event. Monitoring for Delete Security Solution events gives insight into changes to the active security solutions and may reduce the time it takes to detect suspicious activity. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.2.7 | CIS_Azure_2.0.0_5.2.7 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.7 | 5.2 | Ensure that Activity Log Alert exists for Create or Update SQL Server Firewall Rule | Shared | There will be a substantial increase in log size if there are a large number of administrative actions on a server. | Create an activity log alert for the Create or Update SQL Server Firewall Rule event. Monitoring for Create or Update SQL Server Firewall Rule events gives insight into network access changes and may reduce the time it takes to detect suspicious activity. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.2.8 | CIS_Azure_2.0.0_5.2.8 | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.8 | 5.2 | Ensure that Activity Log Alert exists for Delete SQL Server Firewall Rule | Shared | There will be a substantial increase in log size if there are a large number of administrative actions on a server. | Create an activity log alert for the "Delete SQL Server Firewall Rule." Monitoring for Delete SQL Server Firewall Rule events gives insight into SQL network access changes and may reduce the time it takes to detect suspicious activity. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Monitoring, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 5.4 | CIS_Azure_2.0.0_5.4 | CIS Microsoft Azure Foundations Benchmark recommendation 5.4 | 5 | Ensure that Azure Monitor Resource Logging is Enabled for All Services that Support it | Shared | Costs for monitoring varies with Log Volume. Not every resource needs to have logging enabled. It is important to determine the security classification of the data being processed by the given resource and adjust the logging based on which events need to be tracked. This is typically determined by governance and compliance requirements. | Resource Logs capture activity to the data access plane while the Activity log is a subscription-level log for the control plane. Resource-level diagnostic logs provide insight into operations that were performed within that resource itself; for example, reading or updating a secret from a Key Vault. Currently, 95 Azure resources support Azure Monitoring (See the more information section for a complete list), including Network Security Groups, Load Balancers, Key Vault, AD, Logic Apps, and CosmosDB. The content of these logs varies by resource type. A number of back-end services were not configured to log and store Resource Logs for certain activities or for a sufficient length. It is crucial that monitoring is correctly configured to log all relevant activities and retain those logs for a sufficient length of time. Given that the mean time to detection in an enterprise is 240 days, a minimum retention period of two years is recommended. A lack of monitoring reduces the visibility into the data plane, and therefore an organization's ability to detect reconnaissance, authorization attempts or other malicious activity. Unlike Activity Logs, Resource Logs are not enabled by default. Specifically, without monitoring it would be impossible to tell which entities had accessed a data store that was breached. In addition, alerts for failed attempts to access APIs for Web Services or Databases are only possible when logging is enabled. | link | count: 020 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Logic Apps, Regulatory Compliance, Search, Service Bus, Stream Analytics | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 6.1 | CIS_Azure_2.0.0_6.1 | CIS Microsoft Azure Foundations Benchmark recommendation 6.1 | 6 | Ensure that RDP access from the Internet is evaluated and restricted | Shared | n/a | Network security groups should be periodically evaluated for port misconfigurations. Where certain ports and protocols may be exposed to the Internet, they should be evaluated for necessity and restricted wherever they are not explicitly required. The potential security problem with using RDP over the Internet is that attackers can use various brute force techniques to gain access to Azure Virtual Machines. Once the attackers gain access, they can use a virtual machine as a launch point for compromising other machines on an Azure Virtual Network or even attack networked devices outside of Azure. | link | count: 001 Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917) |
Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 6.2 | CIS_Azure_2.0.0_6.2 | CIS Microsoft Azure Foundations Benchmark recommendation 6.2 | 6 | Ensure that SSH access from the Internet is evaluated and restricted | Shared | n/a | Network security groups should be periodically evaluated for port misconfigurations. Where certain ports and protocols may be exposed to the Internet, they should be evaluated for necessity and restricted wherever they are not explicitly required. The potential security problem with using SSH over the Internet is that attackers can use various brute force techniques to gain access to Azure Virtual Machines. Once the attackers gain access, they can use a virtual machine as a launch point for compromising other machines on the Azure Virtual Network or even attack networked devices outside of Azure. | link | count: 001 Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917) |
Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 6.5 | CIS_Azure_2.0.0_6.5 | CIS Microsoft Azure Foundations Benchmark recommendation 6.5 | 6 | Ensure that Network Security Group Flow Log retention period is 'greater than 90 days' | Shared | This will keep IP traffic logs for longer than 90 days. As a level 2, first determine your need to retain data, then apply your selection here. As this is data stored for longer, your monthly storage costs will increase depending on your data use. | Network Security Group Flow Logs should be enabled and the retention period set to greater than or equal to 90 days. Flow logs enable capturing information about IP traffic flowing in and out of network security groups. Logs can be used to check for anomalies and give insight into suspected breaches. | link | count: 003 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 6.6 | CIS_Azure_2.0.0_6.6 | CIS Microsoft Azure Foundations Benchmark recommendation 6.6 | 6 | Ensure that Network Watcher is 'Enabled' | Shared | There are additional costs per transaction to run and store network data. For high-volume networks these charges will add up quickly. | Enable Network Watcher for Azure subscriptions. Network diagnostic and visualization tools available with Network Watcher help users understand, diagnose, and gain insights to the network in Azure. | link | count: 002 Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Network, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 7.2 | CIS_Azure_2.0.0_7.2 | CIS Microsoft Azure Foundations Benchmark recommendation 7.2 | 7 | Ensure Virtual Machines are utilizing Managed Disks | Shared | There are additional costs for managed disks based off of disk space allocated. When converting to managed disks, VMs will be powered off and back on. | Migrate blob-based VHDs to Managed Disks on Virtual Machines to exploit the default features of this configuration. The features include: 1) Default Disk Encryption 2) Resilience, as Microsoft will managed the disk storage and move around if underlying hardware goes faulty 3) Reduction of costs over storage accounts Managed disks are by default encrypted on the underlying hardware, so no additional encryption is required for basic protection. It is available if additional encryption is required. Managed disks are by design more resilient that storage accounts. For ARM-deployed Virtual Machines, Azure Adviser will at some point recommend moving VHDs to managed disks both from a security and cost management perspective. | link | count: 004 Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Compute, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 7.3 | CIS_Azure_2.0.0_7.3 | CIS Microsoft Azure Foundations Benchmark recommendation 7.3 | 7 | Ensure that 'OS and Data' disks are encrypted with Customer Managed Key (CMK) | Shared | Using CMK/BYOK will entail additional management of keys. **NOTE:** You must have your key vault set up to utilize this. | Ensure that OS disks (boot volumes) and data disks (non-boot volumes) are encrypted with CMK (Customer Managed Keys). Customer Managed keys can be either ADE or Server Side Encryption (SSE). Encrypting the IaaS VM's OS disk (boot volume) and Data disks (non-boot volume) ensures that the entire content is fully unrecoverable without a key, thus protecting the volume from unwanted reads. PMK (Platform Managed Keys) are enabled by default in Azure-managed disks and allow encryption at rest. CMK is recommended because it gives the customer the option to control which specific keys are used for the encryption and decryption of the disk. The customer can then change keys and increase security by disabling them instead of relying on the PMK key that remains unchanging. There is also the option to increase security further by using automatically rotating keys so that access to disk is ensured to be limited. Organizations should evaluate what their security requirements are, however, for the data stored on the disk. For high-risk data using CMK is a must, as it provides extra steps of security. If the data is low risk, PMK is enabled by default and provides sufficient data security. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 7.4 | CIS_Azure_2.0.0_7.4 | CIS Microsoft Azure Foundations Benchmark recommendation 7.4 | 7 | Ensure that 'Unattached disks' are encrypted with 'Customer Managed Key' (CMK) | Shared | **NOTE:** You must have your key vault set up to utilize this. Encryption is available only on Standard tier VMs. This might cost you more. Utilizing and maintaining Customer-managed keys will require additional work to create, protect, and rotate keys. | Ensure that unattached disks in a subscription are encrypted with a Customer Managed Key (CMK). Managed disks are encrypted by default with Platform-managed keys. Using Customer-managed keys may provide an additional level of security or meet an organization's regulatory requirements. Encrypting managed disks ensures that its entire content is fully unrecoverable without a key and thus protects the volume from unwarranted reads. Even if the disk is not attached to any of the VMs, there is always a risk where a compromised user account with administrative access to VM service can mount/attach these data disks, which may lead to sensitive information disclosure and tampering. | link | count: 005 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Compute, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 7.5 | CIS_Azure_2.0.0_7.5 | CIS Microsoft Azure Foundations Benchmark recommendation 7.5 | 7 | Ensure that Only Approved Extensions Are Installed | Shared | Functionality by unsupported extensions will be disabled. | For added security, only install organization-approved extensions on VMs. Azure virtual machine extensions are small applications that provide post-deployment configuration and automation tasks on Azure virtual machines. These extensions run with administrative privileges and could potentially access anything on a virtual machine. The Azure Portal and community provide several such extensions. Each organization should carefully evaluate these extensions and ensure that only those that are approved for use are actually implemented. | link | count: 001 Only approved VM extensions should be installed (c0e996f8-39cf-4af9-9f45-83fbde810432) |
Compute | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 7.6 | CIS_Azure_2.0.0_7.6 | CIS Microsoft Azure Foundations Benchmark recommendation 7.6 | 7 | Ensure that Endpoint Protection for all Virtual Machines is installed | Shared | Endpoint protection will incur an additional cost to you. | Install endpoint protection for all virtual machines. Installing endpoint protection systems (like anti-malware for Azure) provides for real-time protection capability that helps identify and remove viruses, spyware, and other malicious software. These also offer configurable alerts when known-malicious or unwanted software attempts to install itself or run on Azure systems. | link | count: 011 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Endpoint protection should be installed on your machines (1f7c564c-0a90-4d44-b7e1-9d456cffaee8), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance, Security Center | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 7.7 | CIS_Azure_2.0.0_7.7 | CIS Microsoft Azure Foundations Benchmark recommendation 7.7 | 7 | [Legacy] Ensure that VHDs are Encrypted | Shared | Depending on how the encryption is implemented will change the size of the impact. If provider-managed keys(PMK) are utilized, the impact is relatively low, but processes need to be put in place to regularly rotate the keys. If Customer-managed keys(CMK) are utilized, a key management process needs to be implemented to store and manage key rotation, thus the impact is medium to high depending on user maturity with key management. | **NOTE: This is a legacy recommendation. Managed Disks are encrypted by default and recommended for all new VM implementations.** VHD (Virtual Hard Disks) are stored in blob storage and are the old-style disks that were attached to Virtual Machines. The blob VHD was then leased to the VM. By default, storage accounts are not encrypted, and Microsoft Defender will then recommend that the OS disks should be encrypted. Storage accounts can be encrypted as a whole using PMK or CMK. This should be turned on for storage accounts containing VHDs. While it is recommended to use Managed Disks which are encrypted by default, "legacy" VHDs may exist for a variety of reasons and may need to remain in VHD format. VHDs are not encrypted by default, so this recommendation intends to address the security of these disks. In these niche cases, VHDs should be encrypted using the procedures in this recommendation to encrypt and protect the data content. If a virtual machine is using a VHD and can be converted to a managed disk, instructions for this procedure can be found in the resources section of this recommendation under the title "Convert VHD to Managed Disk." | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 8.1 | CIS_Azure_2.0.0_8.1 | CIS Microsoft Azure Foundations Benchmark recommendation 8.1 | 8 | Ensure that the Expiration Date is set for all Keys in RBAC Key Vaults | Shared | Keys cannot be used beyond their assigned expiration dates respectively. Keys need to be rotated periodically wherever they are used. | Ensure that all Keys in Role Based Access Control (RBAC) Azure Key Vaults have an expiration date set. Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. The `exp` (expiration date) attribute identifies the expiration date on or after which the key MUST NOT be used for encryption of new data, wrapping of new keys, and signing. By default, keys never expire. It is thus recommended that keys be rotated in the key vault and set an explicit expiration date for all keys to help enforce the key rotation. This ensures that the keys cannot be used beyond their assigned lifetimes. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 8.2 | CIS_Azure_2.0.0_8.2 | CIS Microsoft Azure Foundations Benchmark recommendation 8.2 | 8 | Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults. | Shared | Keys cannot be used beyond their assigned expiration dates respectively. Keys need to be rotated periodically wherever they are used. | Ensure that all Keys in Non Role Based Access Control (RBAC) Azure Key Vaults have an expiration date set. Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. The `exp` (expiration date) attribute identifies the expiration date on or after which the key MUST NOT be used for a cryptographic operation. By default, keys never expire. It is thus recommended that keys be rotated in the key vault and set an explicit expiration date for all keys. This ensures that the keys cannot be used beyond their assigned lifetimes. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 8.3 | CIS_Azure_2.0.0_8.3 | CIS Microsoft Azure Foundations Benchmark recommendation 8.3 | 8 | Ensure that the Expiration Date is set for all Secrets in RBAC Key Vaults | Shared | Secrets cannot be used beyond their assigned expiry date respectively. Secrets need to be rotated periodically wherever they are used. | Ensure that all Secrets in Role Based Access Control (RBAC) Azure Key Vaults have an expiration date set. The Azure Key Vault enables users to store and keep secrets within the Microsoft Azure environment. Secrets in the Azure Key Vault are octet sequences with a maximum size of 25k bytes each. The `exp` (expiration date) attribute identifies the expiration date on or after which the secret MUST NOT be used. By default, secrets never expire. It is thus recommended to rotate secrets in the key vault and set an explicit expiration date for all secrets. This ensures that the secrets cannot be used beyond their assigned lifetimes. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 8.4 | CIS_Azure_2.0.0_8.4 | CIS Microsoft Azure Foundations Benchmark recommendation 8.4 | 8 | Ensure that the Expiration Date is set for all Secrets in Non-RBAC Key Vaults | Shared | Secrets cannot be used beyond their assigned expiry date respectively. Secrets need to be rotated periodically wherever they are used. | Ensure that all Secrets in Non Role Based Access Control (RBAC) Azure Key Vaults have an expiration date set. The Azure Key Vault enables users to store and keep secrets within the Microsoft Azure environment. Secrets in the Azure Key Vault are octet sequences with a maximum size of 25k bytes each. The `exp` (expiration date) attribute identifies the expiration date on or after which the secret MUST NOT be used. By default, secrets never expire. It is thus recommended to rotate secrets in the key vault and set an explicit expiration date for all secrets. This ensures that the secrets cannot be used beyond their assigned lifetimes. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Key Vault, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 8.5 | CIS_Azure_2.0.0_8.5 | CIS Microsoft Azure Foundations Benchmark recommendation 8.5 | 8 | Ensure the Key Vault is Recoverable | Shared | Once purge-protection and soft-delete are enabled for a Key Vault, the action is irreversible. | The Key Vault contains object keys, secrets, and certificates. Accidental unavailability of a Key Vault can cause immediate data loss or loss of security functions (authentication, validation, verification, non-repudiation, etc.) supported by the Key Vault objects. It is recommended the Key Vault be made recoverable by enabling the "Do Not Purge" and "Soft Delete" functions. This is in order to prevent loss of encrypted data, including storage accounts, SQL databases, and/or dependent services provided by Key Vault objects (Keys, Secrets, Certificates) etc. This may happen in the case of accidental deletion by a user or from disruptive activity by a malicious user. WARNING: A current limitation of the soft-delete feature across all Azure services is role assignments disappearing when Key Vault is deleted. All role assignments will need to be recreated after recovery. There could be scenarios where users accidentally run delete/purge commands on Key Vault or an attacker/malicious user deliberately does so in order to cause disruption. Deleting or purging a Key Vault leads to immediate data loss, as keys encrypting data and secrets/certificates allowing access/services will become non-accessible. There are 2 Key Vault properties that play a role in permanent unavailability of a Key Vault: 1. `enableSoftDelete`: Setting this parameter to "true" for a Key Vault ensures that even if Key Vault is deleted, Key Vault itself or its objects remain recoverable for the next 90 days. Key Vault/objects can either be recovered or purged (permanent deletion) during those 90 days. If no action is taken, key vault and its objects will subsequently be purged. 2. `enablePurgeProtection`: enableSoftDelete only ensures that Key Vault is not deleted permanently and will be recoverable for 90 days from date of deletion. However, there are scenarios in which the Key Vault and/or its objects are accidentally purged and hence will not be recoverable. Setting enablePurgeProtection to "true" ensures that the Key Vault and its objects cannot be purged. Enabling both the parameters on Key Vaults ensures that Key Vaults and their objects cannot be deleted/purged permanently. | link | count: 002 Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Key Vault | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 8.6 | CIS_Azure_2.0.0_8.6 | CIS Microsoft Azure Foundations Benchmark recommendation 8.6 | 8 | Enable Role Based Access Control for Azure Key Vault | Shared | Implementation needs to be properly designed from the ground up, as this is a fundamental change to the way key vaults are accessed/managed. Changing permissions to key vaults will result in loss of service as permissions are re-applied. For the least amount of downtime, map your current groups and users to their corresponding permission needs. | WARNING: Role assignments disappear when a Key Vault has been deleted (soft-delete) and recovered. Afterwards it will be required to recreate all role assignments. This is a limitation of the soft-delete feature across all Azure services. The new RBAC permissions model for Key Vaults enables a much finer grained access control for key vault secrets, keys, certificates, etc., than the vault access policy. This in turn will permit the use of privileged identity management over these roles, thus securing the key vaults with JIT Access management. | link | count: 001 Azure Key Vault should use RBAC permission model (12d4fa5e-1f9f-4c21-97a9-b99b3c6611b5) |
Key Vault | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 8.7 | CIS_Azure_2.0.0_8.7 | CIS Microsoft Azure Foundations Benchmark recommendation 8.7 | 8 | Ensure that Private Endpoints are Used for Azure Key Vault | Shared | Incorrect or poorly-timed changing of network configuration could result in service interruption. There are also additional costs tiers for running a private endpoint per petabyte or more of networking traffic. | Private endpoints will secure network traffic from Azure Key Vault to the resources requesting secrets and keys. Private endpoints will keep network requests to Azure Key Vault limited to the endpoints attached to the resources that are whitelisted to communicate with each other. Assigning the Key Vault to a network without an endpoint will allow other resources on that network to view all traffic from the Key Vault to its destination. In spite of the complexity in configuration, this is recommended for high security secrets. | link | count: 001 Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9) |
Key Vault | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 8.8 | CIS_Azure_2.0.0_8.8 | CIS Microsoft Azure Foundations Benchmark recommendation 8.8 | 8 | Ensure Automatic Key Rotation is Enabled Within Azure Key Vault for the Supported Services | Shared | There are an additional costs per operation in running the needed applications. | Automatic Key Rotation is available in Public Preview. The currently supported applications are Key Vault, Managed Disks, and Storage accounts accessing keys within Key Vault. The number of supported applications will incrementally increased. Once set up, Automatic Private Key Rotation removes the need for manual administration when keys expire at intervals determined by your organization's policy. The recommended key lifetime is 2 years. Your organization should determine its own key expiration policy. | link | count: 001 Keys should have a rotation policy ensuring that their rotation is scheduled within the specified number of days after creation. (d8cf8476-a2ec-4916-896e-992351803c44) |
Key Vault | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.1 | CIS_Azure_2.0.0_9.1 | CIS Microsoft Azure Foundations Benchmark recommendation 9.1 | 9 | Ensure App Service Authentication is set up for apps in Azure App Service | Shared | This is only required for App Services which require authentication. Enabling on site like a marketing or support website will prevent unauthenticated access which would be undesirable. Adding Authentication requirement will increase cost of App Service and require additional security components to facilitate the authentication. | Azure App Service Authentication is a feature that can prevent anonymous HTTP requests from reaching a Web Application or authenticate those with tokens before they reach the app. If an anonymous request is received from a browser, App Service will redirect to a logon page. To handle the logon process, a choice from a set of identity providers can be made, or a custom authentication mechanism can be implemented. By Enabling App Service Authentication, every incoming HTTP request passes through it before being handled by the application code. It also handles authentication of users with the specified provider (Azure Active Directory, Facebook, Google, Microsoft Account, and Twitter), validation, storing and refreshing of tokens, managing the authenticated sessions and injecting identity information into request headers. | link | count: 005 App Service apps should have authentication enabled (95bccee9-a7f8-4bec-9ee9-62c3473701fc), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Function apps should have authentication enabled (c75248c1-ea1d-4a9c-8fc9-29a6aabd5da8), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.10 | CIS_Azure_2.0.0_9.10 | CIS Microsoft Azure Foundations Benchmark recommendation 9.10 | 9 | Ensure FTP deployments are Disabled | Shared | Any deployment workflows that rely on FTP or FTPs rather than the WebDeploy or HTTPs endpoints may be affected. | By default, Azure Functions, Web, and API Services can be deployed over FTP. If FTP is required for an essential deployment workflow, FTPS should be required for FTP login for all App Service Apps and Functions. Azure FTP deployment endpoints are public. An attacker listening to traffic on a wifi network used by a remote employee or a corporate network could see login traffic in clear-text which would then grant them full control of the code base of the app or service. This finding is more severe if User Credentials for deployment are set at the subscription level rather than using the default Application Credentials which are unique per App. | link | count: 005 App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.11 | CIS_Azure_2.0.0_9.11 | CIS Microsoft Azure Foundations Benchmark recommendation 9.11 | 9 | Ensure Azure Key Vaults are Used to Store Secrets | Shared | Integrating references to secrets within the key vault are required to be specifically integrated within the application code. This will require additional configuration to be made during the writing of an application, or refactoring of an already written one. There are also additional costs that are charged per 10000 requests to the Key Vault. | Azure Key Vault will store multiple types of sensitive information such as encryption keys, certificate thumbprints, and Managed Identity Credentials. Access to these 'Secrets' can be controlled through granular permissions. The credentials given to an application have permissions to create, delete, or modify data stored within the systems they access. If these credentials are stored within the application itself, anyone with access to the application or a copy of the code has access to them. Storing within Azure Key Vault as secrets increases security by controlling access. This also allows for updates of the credentials without redeploying the entire application. | link | count: 009 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Ensure cryptographic mechanisms are under configuration management (b8dad106-6444-5f55-307e-1e1cc9723e39), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.2 | CIS_Azure_2.0.0_9.2 | CIS Microsoft Azure Foundations Benchmark recommendation 9.2 | 9 | Ensure Web App Redirects All HTTP traffic to HTTPS in Azure App Service | Shared | When it is enabled, every incoming HTTP request is redirected to the HTTPS port. This means an extra level of security will be added to the HTTP requests made to the app. | Azure Web Apps allows sites to run under both HTTP and HTTPS by default. Web apps can be accessed by anyone using non-secure HTTP links by default. Non-secure HTTP requests can be restricted and all HTTP requests redirected to the secure HTTPS port. It is recommended to enforce HTTPS-only traffic. Enabling HTTPS-only traffic will redirect all non-secure HTTP requests to HTTPS ports. HTTPS uses the TLS/SSL protocol to provide a secure connection which is both encrypted and authenticated. It is therefore important to support HTTPS for the security benefits. | link | count: 004 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.3 | CIS_Azure_2.0.0_9.3 | CIS Microsoft Azure Foundations Benchmark recommendation 9.3 | 9 | Ensure Web App is using the latest version of TLS encryption | Shared | n/a | The TLS (Transport Layer Security) protocol secures transmission of data over the internet using standard encryption technology. Encryption should be set with the latest version of TLS. App service allows TLS 1.2 by default, which is the recommended TLS level by industry standards such as PCI DSS. App service currently allows the web app to set TLS versions 1.0, 1.1 and 1.2. It is highly recommended to use the latest TLS 1.2 version for web app secure connections. | link | count: 005 App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.4 | CIS_Azure_2.0.0_9.4 | CIS Microsoft Azure Foundations Benchmark recommendation 9.4 | 9 | Ensure the web app has 'Client Certificates (Incoming client certificates)' set to 'On' | Shared | Utilizing and maintaining client certificates will require additional work to obtain and manage replacement and key rotation. | Client certificates allow for the app to request a certificate for incoming requests. Only clients that have a valid certificate will be able to reach the app. The TLS mutual authentication technique in enterprise environments ensures the authenticity of clients to the server. If incoming client certificates are enabled, then only an authenticated client who has valid certificates can access the app. | link | count: 003 [Deprecated]: App Service apps should have 'Client Certificates (Incoming client certificates)' enabled (5bb220d9-2698-4ee4-8404-b9c30c9df609), [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.5 | CIS_Azure_2.0.0_9.5 | CIS Microsoft Azure Foundations Benchmark recommendation 9.5 | 9 | Ensure that Register with Azure Active Directory is enabled on App Service | Shared | n/a | Managed service identity in App Service provides more security by eliminating secrets from the app, such as credentials in the connection strings. When registering with Azure Active Directory in App Service, the app will connect to other Azure services securely without the need for usernames and passwords. App Service provides a highly scalable, self-patching web hosting service in Azure. It also provides a managed identity for apps, which is a turn-key solution for securing access to Azure SQL Database and other Azure services. | link | count: 006 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.6 | CIS_Azure_2.0.0_9.6 | CIS Microsoft Azure Foundations Benchmark recommendation 9.6 | 9 | Ensure That 'PHP version' is the Latest, If Used to Run the Web App | Shared | If your app is written using version-dependent features or libraries, they may not be available on the latest version. If you wish to upgrade, research the impact thoroughly. Upgrading may have unforeseen consequences that could result in downtime. | Periodically newer versions are released for PHP software either due to security flaws or to include additional functionality. Using the latest PHP version for web apps is recommended in order to take advantage of security fixes, if any, and/or additional functionalities of the newer version. Newer versions may contain security enhancements and additional functionality. Using the latest software version is recommended in order to take advantage of enhancements and new capabilities. With each software installation, organizations need to determine if a given update meets their requirements. They must also verify the compatibility and support provided for any additional software against the update revision that is selected. | link | count: 003 App Service app slots that use PHP should use a specified 'PHP version' (f466b2a6-823d-470d-8ea5-b031e72d79ae), App Service apps that use PHP should use a specified 'PHP version' (7261b898-8a84-4db8-9e04-18527132abb3), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.7 | CIS_Azure_2.0.0_9.7 | CIS Microsoft Azure Foundations Benchmark recommendation 9.7 | 9 | Ensure that 'Python version' is the Latest Stable Version, if Used to Run the Web App | Shared | If your app is written using version-dependent features or libraries, they may not be available on the latest version. If you wish to upgrade, research the impact thoroughly. Upgrading may have unforeseen consequences that could result in downtime. | Periodically, newer versions are released for Python software either due to security flaws or to include additional functionality. Using the latest full Python version for web apps is recommended in order to take advantage of security fixes, if any, and/or additional functionalities of the newer version. Newer versions may contain security enhancements and additional functionality. Using the latest software version is recommended in order to take advantage of enhancements and new capabilities. With each software installation, organizations need to determine if a given update meets their requirements. They must also verify the compatibility and support provided for any additional software against the update revision that is selected. Using the latest full version will keep your stack secure to vulnerabilities and exploits. | link | count: 003 App Service app slots that use Python should use a specified 'Python version' (9c014953-ef68-4a98-82af-fd0f6b2306c8), App Service apps that use Python should use a specified 'Python version' (7008174a-fd10-4ef0-817e-fc820a951d73), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.8 | CIS_Azure_2.0.0_9.8 | CIS Microsoft Azure Foundations Benchmark recommendation 9.8 | 9 | Ensure that 'Java version' is the latest, if used to run the Web App | Shared | If your app is written using version-dependent features or libraries, they may not be available on the latest version. If you wish to upgrade, research the impact thoroughly. Upgrading may have unforeseen consequences that could result in downtime. | Periodically, newer versions are released for Java software either due to security flaws or to include additional functionality. Using the latest Java version for web apps is recommended in order to take advantage of security fixes, if any, and/or new functionalities of the newer version. Newer versions may contain security enhancements and additional functionality. Using the latest software version is recommended in order to take advantage of enhancements and new capabilities. With each software installation, organizations need to determine if a given update meets their requirements. They must also verify the compatibility and support provided for any additional software against the update revision that is selected. | link | count: 003 Function app slots that use Java should use a specified 'Java version' (e1d1b522-02b0-4d18-a04f-5ab62d20445f), Function apps that use Java should use a specified 'Java version' (9d0b6ea4-93e2-4578-bf2f-6bb17d22b4bc), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CIS_Azure_2.0.0 | 9.9 | CIS_Azure_2.0.0_9.9 | CIS Microsoft Azure Foundations Benchmark recommendation 9.9 | 9 | Ensure that 'HTTP Version' is the Latest, if Used to Run the Web App | Shared | n/a | Periodically, newer versions are released for HTTP either due to security flaws or to include additional functionality. Using the latest HTTP version for web apps to take advantage of security fixes, if any, and/or new functionalities of the newer version. Newer versions may contain security enhancements and additional functionality. Using the latest version is recommended in order to take advantage of enhancements and new capabilities. With each software installation, organizations need to determine if a given update meets their requirements. They must also verify the compatibility and support provided for any additional software against the update revision that is selected. HTTP 2.0 has additional performance improvements on the head-of-line blocking problem of old HTTP version, header compression, and prioritization of requests. HTTP 2.0 no longer supports HTTP 1.1's chunked transfer encoding mechanism, as it provides its own, more efficient, mechanisms for data streaming. | link | count: 003 App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
App Service, Regulatory Compliance | CIS Microsoft Azure Foundations Benchmark v2.0.0 (06f19060-9e68-4070-92ca-f15cc126059e) |
| CMMC_2.0_L2 | AC.L1-3.1.1 | CMMC_2.0_L2_AC.L1-3.1.1 | 404 not found | n/a | n/a | count: 057 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, General, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Search, Security Center, Service Bus, Service Fabric, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AC.L1-3.1.2 | CMMC_2.0_L2_AC.L1-3.1.2 | 404 not found | n/a | n/a | count: 019 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
App Service, Azure Ai Services, Compute, General, Security Center, Service Fabric, SQL, Storage | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AC.L2-3.1.12 | CMMC_2.0_L2_AC.L2-3.1.12 | 404 not found | n/a | n/a | count: 035 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AC.L2-3.1.13 | CMMC_2.0_L2_AC.L2-3.1.13 | 404 not found | n/a | n/a | count: 029 App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AC.L2-3.1.14 | CMMC_2.0_L2_AC.L2-3.1.14 | 404 not found | n/a | n/a | count: 029 App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AC.L2-3.1.3 | CMMC_2.0_L2_AC.L2-3.1.3 | 404 not found | n/a | n/a | count: 053 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, API Management, App Configuration, App Service, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AC.L2-3.1.4 | CMMC_2.0_L2_AC.L2-3.1.4 | 404 not found | n/a | n/a | count: 001 There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AC.L2-3.1.5 | CMMC_2.0_L2_AC.L2-3.1.5 | 404 not found | n/a | n/a | count: 003 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
General, Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AU.L2-3.3.1 | CMMC_2.0_L2_AU.L2-3.3.1 | 404 not found | n/a | n/a | count: 038 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Search, Security Center, Service Bus, SQL, Stream Analytics | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AU.L2-3.3.2 | CMMC_2.0_L2_AU.L2-3.3.2 | 404 not found | n/a | n/a | count: 036 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Search, Security Center, Service Bus, SQL, Stream Analytics | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AU.L2-3.3.4 | CMMC_2.0_L2_AU.L2-3.3.4 | 404 not found | n/a | n/a | count: 010 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4) |
Security Center, SQL | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | AU.L2-3.3.5 | CMMC_2.0_L2_AU.L2-3.3.5 | 404 not found | n/a | n/a | count: 010 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4) |
Security Center, SQL | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | CM.L2-3.4.1 | CMMC_2.0_L2_CM.L2-3.4.1 | 404 not found | n/a | n/a | count: 025 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Guest Configuration, Kubernetes | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | CM.L2-3.4.2 | CMMC_2.0_L2_CM.L2-3.4.2 | 404 not found | n/a | n/a | count: 027 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Guest Configuration, Kubernetes, Network | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | CM.L2-3.4.6 | CMMC_2.0_L2_CM.L2-3.4.6 | 404 not found | n/a | n/a | count: 003 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | CM.L2-3.4.7 | CMMC_2.0_L2_CM.L2-3.4.7 | 404 not found | n/a | n/a | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | CM.L2-3.4.8 | CMMC_2.0_L2_CM.L2-3.4.8 | 404 not found | n/a | n/a | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | CM.L2-3.4.9 | CMMC_2.0_L2_CM.L2-3.4.9 | 404 not found | n/a | n/a | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IA.L1-3.5.1 | CMMC_2.0_L2_IA.L1-3.5.1 | 404 not found | n/a | n/a | count: 005 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Service Fabric, SQL | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IA.L1-3.5.2 | CMMC_2.0_L2_IA.L1-3.5.2 | 404 not found | n/a | n/a | count: 018 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Guest Configuration, Key Vault, Security Center, Service Fabric, SQL | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IA.L2-3.5.10 | CMMC_2.0_L2_IA.L2-3.5.10 | 404 not found | n/a | n/a | count: 007 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IA.L2-3.5.3 | CMMC_2.0_L2_IA.L2-3.5.3 | 404 not found | n/a | n/a | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IA.L2-3.5.4 | CMMC_2.0_L2_IA.L2-3.5.4 | 404 not found | n/a | n/a | count: 001 Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IA.L2-3.5.5 | CMMC_2.0_L2_IA.L2-3.5.5 | 404 not found | n/a | n/a | count: 005 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Service Fabric, SQL | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IA.L2-3.5.6 | CMMC_2.0_L2_IA.L2-3.5.6 | 404 not found | n/a | n/a | count: 006 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Security Center, Service Fabric, SQL | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IA.L2-3.5.7 | CMMC_2.0_L2_IA.L2-3.5.7 | 404 not found | n/a | n/a | count: 005 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IA.L2-3.5.8 | CMMC_2.0_L2_IA.L2-3.5.8 | 404 not found | n/a | n/a | count: 004 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | IR.L2-3.6.2 | CMMC_2.0_L2_IR.L2-3.6.2 | 404 not found | n/a | n/a | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | MP.L2-3.8.9 | CMMC_2.0_L2_MP.L2-3.8.9 | 404 not found | n/a | n/a | count: 006 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Backup, Key Vault, SQL | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | RA.L2-3.11.2 | CMMC_2.0_L2_RA.L2-3.11.2 | 404 not found | n/a | n/a | count: 019 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Security Center, SQL, Synapse | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | RA.L2-3.11.3 | CMMC_2.0_L2_RA.L2-3.11.3 | 404 not found | n/a | n/a | count: 019 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Security Center, SQL, Synapse | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SC.L1-3.13.1 | CMMC_2.0_L2_SC.L1-3.13.1 | 404 not found | n/a | n/a | count: 057 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SC.L1-3.13.5 | CMMC_2.0_L2_SC.L1-3.13.5 | 404 not found | n/a | n/a | count: 052 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SC.L2-3.13.10 | CMMC_2.0_L2_SC.L2-3.13.10 | 404 not found | n/a | n/a | count: 037 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) (47031206-ce96-41f8-861b-6a915f3de284), Azure API for FHIR should use a customer-managed key to encrypt data at rest (051cba44-2429-45b9-9649-46cec11c7119), Azure Automation accounts should use customer-managed keys to encrypt data at rest (56a5ee18-2ae6-4810-86f7-18e39ce5629b), Azure Batch account should use customer-managed keys to encrypt data (99e9ccd8-3db9-4592-b0d1-14b1715a4d8a), Azure Container Instance container group should use customer-managed key for encryption (0aa61e00-0a01-4a3c-9945-e93cffedf0e6), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password (86efb160-8de7-451d-bc08-5d475b0aadae), Azure Data Explorer encryption at rest should use a customer-managed key (81e74cea-30fd-40d5-802f-d72103c2aaaa), Azure data factories should be encrypted with a customer-managed key (4ec52d6d-beb7-40c4-9a9e-fe753254690e), Azure HDInsight clusters should use customer-managed keys to encrypt data at rest (64d314f6-6062-4780-a861-c23e8951bee5), Azure HDInsight clusters should use encryption at host to encrypt data at rest (1fd32ebd-e4c3-4e13-a54a-d7422d4d95f6), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Stream Analytics jobs should use customer-managed keys to encrypt data (87ba29ef-1ab3-4d82-b763-87fcd4f531f7), Azure Synapse workspaces should use customer-managed keys to encrypt data at rest (f7d52b2d-e161-4dfa-a82b-55e564167385), Bot Service should be encrypted with a customer-managed key (51522a96-0869-4791-82f3-981000c2c67f), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Certificates using RSA cryptography should have the specified minimum key size (cee51871-e572-4576-855c-047c820360f0), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Event Hub namespaces should use a customer-managed key for encryption (a1ad735a-e96f-45d2-a7b2-9a4932cab7ec), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Keys should be the specified cryptographic type RSA or EC (75c4f823-d65c-4f29-a733-01d0077fdbcb), Keys using elliptic curve cryptography should have the specified curve names (ff25f3c8-b739-4538-9d07-3d6d25cfb255), Keys using RSA cryptography should have a specified minimum key size (82067dbb-e53b-4e06-b631-546d197452d9), Logic Apps Integration Service Environment should be encrypted with customer-managed keys (1fafeaf6-7927-4059-a50a-8eb2a7a6f2b5), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), OS and data disks should be encrypted with a customer-managed key (702dd420-7fcc-42c5-afe8-4026edd20fe0), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Service Bus Premium namespaces should use a customer-managed key for encryption (295fc8b1-dc9f-4f53-9c61-3f313ceab40a), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
API for FHIR, Automation, Azure Data Explorer, Backup, Batch, Bot Service, Cognitive Services, Compute, Container Instance, Container Registry, Cosmos DB, Data Box, Data Factory, Event Hub, HDInsight, Internet of Things, Key Vault, Kubernetes, Logic Apps, Machine Learning, Monitoring, Service Bus, SQL, Storage, Stream Analytics, Synapse | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SC.L2-3.13.11 | CMMC_2.0_L2_SC.L2-3.13.11 | 404 not found | n/a | n/a | count: 004 Certificates using RSA cryptography should have the specified minimum key size (cee51871-e572-4576-855c-047c820360f0), Keys should be the specified cryptographic type RSA or EC (75c4f823-d65c-4f29-a733-01d0077fdbcb), Keys using elliptic curve cryptography should have the specified curve names (ff25f3c8-b739-4538-9d07-3d6d25cfb255), Keys using RSA cryptography should have a specified minimum key size (82067dbb-e53b-4e06-b631-546d197452d9) |
Key Vault | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SC.L2-3.13.16 | CMMC_2.0_L2_SC.L2-3.13.16 | 404 not found | n/a | n/a | count: 015 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Security Center, Service Fabric, SQL, Storage | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SC.L2-3.13.2 | CMMC_2.0_L2_SC.L2-3.13.2 | 404 not found | n/a | n/a | count: 052 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SC.L2-3.13.6 | CMMC_2.0_L2_SC.L2-3.13.6 | 404 not found | n/a | n/a | count: 027 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8) |
Azure Ai Services, Container Registry, Cosmos DB, Key Vault, Network, Search, Security Center, SQL, Storage | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SC.L2-3.13.8 | CMMC_2.0_L2_SC.L2-3.13.8 | 404 not found | n/a | n/a | count: 016 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, SQL, Storage | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SI.L1-3.14.1 | CMMC_2.0_L2_SI.L1-3.14.1 | 404 not found | n/a | n/a | count: 020 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
App Service, Guest Configuration, Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SI.L1-3.14.2 | CMMC_2.0_L2_SI.L1-3.14.2 | 404 not found | n/a | n/a | count: 013 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Compute, Guest Configuration, Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SI.L1-3.14.4 | CMMC_2.0_L2_SI.L1-3.14.4 | 404 not found | n/a | n/a | count: 005 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Compute, Guest Configuration, Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SI.L1-3.14.5 | CMMC_2.0_L2_SI.L1-3.14.5 | 404 not found | n/a | n/a | count: 006 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Compute, Guest Configuration, Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SI.L2-3.14.3 | CMMC_2.0_L2_SI.L2-3.14.3 | 404 not found | n/a | n/a | count: 012 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SI.L2-3.14.6 | CMMC_2.0_L2_SI.L2-3.14.6 | 404 not found | n/a | n/a | count: 028 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8) |
Kubernetes, Monitoring, Network, Security Center, SQL | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_2.0_L2 | SI.L2-3.14.7 | CMMC_2.0_L2_SI.L2-3.14.7 | 404 not found | n/a | n/a | count: 022 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
Kubernetes, Monitoring, Network, Security Center, SQL | [Preview]: CMMC 2.0 Level 2 (4e50fd13-098b-3206-61d6-d1d78205cb45) | ||||
| CMMC_L3 | AC.1.001 | CMMC_L3_AC.1.001 | CMMC L3 AC.1.001 | Access Control | Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems). | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Access control policies (e.g., identity- or role-based policies, control matrices, and cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, and domains) in systems. Access enforcement mechanisms can be employed at the application and service level to provide increased information security. Other systems include systems internal and external to the organization. This requirement focuses on account management for systems and applications. The definition of and enforcement of access authorizations, other than those determined by account type (e.g., privileged verses non-privileged) are addressed in requirement AC.1.002. | link | count: 031 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), CORS should not allow every domain to access your API for FHIR (0fea8f8a-4169-495d-8307-30ec335f387d), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Windows machines should meet requirements for 'Security Options - Network Access' (3ff60f98-7fa4-410a-9f7f-0b00f5afdbdd), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
API for FHIR, App Service, Azure Ai Services, Container Registry, Guest Configuration, Key Vault, Kubernetes, Security Center, SQL, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AC.1.002 | CMMC_L3_AC.1.002 | CMMC L3 AC.1.002 | Access Control | Limit information system access to the types of transactions and functions that authorized users are permitted to execute. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. System account types include individual, shared, group, system, anonymous, guest, emergency, developer, manufacturer, vendor, and temporary. Other attributes required for authorizing access include restrictions on time-of-day, day-of-week, and point-oforigin. In defining other account attributes, organizations consider system-related requirements (e.g., system upgrades scheduled maintenance,) and mission or business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements). | link | count: 027 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), CORS should not allow every domain to access your API for FHIR (0fea8f8a-4169-495d-8307-30ec335f387d), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112), Windows machines should meet requirements for 'Security Options - Network Access' (3ff60f98-7fa4-410a-9f7f-0b00f5afdbdd) |
API for FHIR, App Service, Azure Ai Services, Cache, Container Registry, Guest Configuration, Key Vault, Kubernetes, Security Center, SQL, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AC.1.003 | CMMC_L3_AC.1.003 | CMMC L3 AC.1.003 | Access Control | Verify and control/limit connections to and use of external information systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | External systems are systems or components of systems for which organizations typically have no direct supervision and authority over the application of security requirements and controls or the determination of the effectiveness of implemented controls on those systems. External systems include personally owned systems, components, or devices and privately-owned computing and communications devices resident in commercial or public facilities. This requirement also addresses the use of external systems for the processing, storage, or transmission of CUI, including accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational systems. Organizations establish terms and conditions for the use of external systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum, the types of applications that can be accessed on organizational systems from external systems. If terms and conditions with the owners of external systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems. This requirement recognizes that there are circumstances where individuals using external systems (e.g., contractors, coalition partners) need to access organizational systems. In those situations, organizations need confidence that the external systems contain the necessary controls so as not to compromise, damage, or otherwise harm organizational systems. Verification that the required controls have been effectively implemented can be achieved by third-party, independent assessments, attestations, or other means, depending on the assurance or confidence level required by organizations. Note that while “external” typically refers to outside of the organization’s direct supervision and authority, that is not always the case. Regarding the protection of CUI across an organization, the organization may have systems that process CUI and others that do not. And among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore, from the perspective of a given system, other systems within the organization may be considered “external" to that system. | link | count: 003 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c) |
Network, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AC.2.007 | CMMC_L3_AC.2.007 | CMMC L3 AC.2.007 | Access Control | Employ the principle of least privilege, including for specific security functions and privileged accounts. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations employ the principle of least privilege for specific duties and authorized accesses for users and processes. The principle of least privilege is applied with the goal of authorized privileges no higher than necessary to accomplish required organizational missions or business functions. Organizations consider the creation of additional processes, roles, and system accounts as necessary, to achieve least privilege. Organizations also apply least privilege to the development, implementation, and operation of organizational systems. Security functions include establishing system accounts, setting events to be logged, setting intrusion detection parameters, and configuring access authorizations (i.e., permissions, privileges). Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from having access to privileged information or functions. Organizations may differentiate in the application of this requirement between allowed privileges for local accounts and for domain accounts provided organizations retain the ability to control system configurations for key security parameters and as otherwise necessary to sufficiently mitigate risk. | link | count: 004 Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AC.2.008 | CMMC_L3_AC.2.008 | CMMC L3 AC.2.008 | Access Control | Use non-privileged accounts or roles when accessing nonsecurity functions. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement limits exposure when operating from within privileged accounts or roles. The inclusion of roles addresses situations where organizations implement access control policies such as role-based access control and where a change of role provides the same degree of assurance in the change of access authorizations for the user and all processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account. | link | count: 002 Windows machines should meet requirements for 'Security Options - User Account Control' (492a29ed-d143-4f03-b6a4-705ce081b463), Windows machines should meet requirements for 'User Rights Assignment' (e068b215-0026-4354-b347-8fb2766f73a2) |
Guest Configuration | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AC.2.013 | CMMC_L3_AC.2.013 | CMMC L3 AC.2.013 | Access Control | Monitor and control remote access sessions. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Remote access is access to organizational systems by users (or processes acting on behalf of users) communicating through external networks (e.g., the Internet). Remote access methods include dial-up, broadband, and wireless. Organizations often employ encrypted virtual private networks (VPNs) to enhance confidentiality over remote connections. The use of encrypted VPNs does not make the access non-remote; however, the use of VPNs, when adequately provisioned with appropriate control (e.g., employing encryption techniques for confidentiality protection), may provide sufficient assurance to the organization that it can effectively treat such connections as internal networks. VPNs with encrypted tunnels can affect the capability to adequately monitor network communications traffic for malicious code. Automated monitoring and control of remote access sessions allows organizations to detect cyberattacks and help to ensure ongoing compliance with remote access policies by auditing connection activities of remote users on a variety of system components (e.g., servers, workstations, notebook computers, smart phones, and tablets). | link | count: 010 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
App Service, Guest Configuration, Network, Security Center, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AC.2.016 | CMMC_L3_AC.2.016 | CMMC L3 AC.2.016 | Access Control | Control the flow of CUI in accordance with approved authorizations. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Information flow control regulates where information can travel within a system and between systems (versus who can access the information) and without explicit regard to subsequent accesses to that information. Flow control restrictions include the following: keeping exportcontrolled information from being transmitted in the clear to the Internet; blocking outside traffic that claims to be from within the organization; restricting requests to the Internet that are not from the internal web proxy server; and limiting information transfers between organizations based on data structures and content. Organizations commonly use information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within systems and between interconnected systems. Flow control is based on characteristics of the information or the information path. Enforcement occurs in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, firewalls) that employ rule sets or establish configuration settings that restrict system services, provide a packetfiltering capability based on header information, or message-filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Organizations also consider the trustworthiness of filtering and inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Transferring information between systems representing different security domains with different security policies introduces risk that such transfers violate one or more domain security policies. In such situations, information owners or stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes: prohibiting information transfers between interconnected systems (i.e., allowing access only); employing hardware mechanisms to enforce one-way information flows; and implementing trustworthy regrading mechanisms to reassign security attributes and security labels. | link | count: 017 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), CORS should not allow every domain to access your API for FHIR (0fea8f8a-4169-495d-8307-30ec335f387d), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Windows machines should meet requirements for 'Security Options - Network Access' (3ff60f98-7fa4-410a-9f7f-0b00f5afdbdd) |
API for FHIR, App Service, Azure Ai Services, Container Registry, Guest Configuration, Network, Security Center, SQL, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AC.3.017 | CMMC_L3_AC.3.017 | CMMC L3 AC.3.017 | Access Control | Separate the duties of individuals to reduce the risk of malevolent activity without collusion. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes dividing mission functions and system support functions among different individuals or roles; conducting system support functions with different individuals (e.g., configuration management, quality assurance and testing, system management, programming, and network security); and ensuring that security personnel administering access control functions do not also administer audit functions. Because separation of duty violations can span systems and application domains, organizations consider the entirety of organizational systems and system components when developing policy on separation of duties. | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AC.3.018 | CMMC_L3_AC.3.018 | CMMC L3 AC.3.018 | Access Control | Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Privileged functions include establishing system accounts, performing system integrity checks, conducting patching operations, or administering cryptographic key management activities. Nonprivileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. Note that this requirement represents a condition to be achieved by the definition of authorized privileges in AC.1.002. Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat. | link | count: 003 An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Windows machines should meet requirements for 'System Audit Policies - Privilege Use' (87845465-c458-45f3-af66-dcd62176f397) |
General, Guest Configuration, Monitoring | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AC.3.021 | CMMC_L3_AC.3.021 | CMMC L3 AC.3.021 | Access Control | Authorize remote execution of privileged commands and remote access to security-relevant information. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | A privileged command is a human-initiated (interactively or via a process operating on behalf of the human) command executed on a system involving the control, monitoring, or administration of the system including security functions and associated security-relevant information. Securityrelevant information is any information within the system that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Privileged commands give individuals the ability to execute sensitive, security-critical, or security-relevant system functions. Controlling such access from remote locations helps to ensure that unauthorized individuals are not able to execute such commands freely with the potential to do serious or catastrophic damage to organizational systems. Note that the ability to affect the integrity of the system is considered security-relevant as that could enable the means to by-pass security functions although not directly impacting the function itself. | link | count: 010 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Windows machines should meet requirements for 'Security Options - User Account Control' (492a29ed-d143-4f03-b6a4-705ce081b463), Windows machines should meet requirements for 'User Rights Assignment' (e068b215-0026-4354-b347-8fb2766f73a2) |
Guest Configuration, Monitoring, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AU.2.041 | CMMC_L3_AU.2.041 | CMMC L3 AU.2.041 | Audit and Accountability | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement ensures that the contents of the audit record include the information needed to link the audit event to the actions of an individual to the extent feasible. Organizations consider logging for traceability including results from monitoring of account usage, remote access, wireless connectivity, mobile device connection, communications at system boundaries, configuration settings, physical access, nonlocal maintenance, use of maintenance tools, temperature and humidity, equipment delivery and removal, system component inventory, use of mobile code, and use of Voice over Internet Protocol (VoIP). | link | count: 015 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
Monitoring, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AU.2.042 | CMMC_L3_AU.2.042 | CMMC L3 AU.2.042 | Audit and Accountability | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | An event is any observable occurrence in a system, which includes unlawful or unauthorized system activity. Organizations identify event types for which a logging functionality is needed as those events which are significant and relevant to the security of systems and the environments in which those systems operate to meet specific and ongoing auditing needs. Event types can include password changes, failed logons or failed accesses related to systems, administrative privilege usage, or third-party credential usage. In determining event types that require logging, organizations consider the monitoring and auditing appropriate for each of the CUI security requirements. Monitoring and auditing requirements can be balanced with other system needs. For example, organizations may determine that systems must have the capability to log every file access both successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit logging capability and can facilitate the identification of root causes to problems. Organizations consider in the definition of event types, the logging necessary to cover related events such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across multiple organizations) and actions that occur in service-oriented or cloudbased architectures. Audit record content that may be necessary to satisfy this requirement includes time stamps, source and destination addresses, user or process identifiers, event descriptions, success or fail indications, filenames involved, and access control or flow control rules invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the system after the event occurred). Detailed information that organizations may consider in audit records includes full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit log information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. Audit logs are reviewed and analyzed as often as needed to provide important information to organizations to facilitate risk-based decision making. | link | count: 015 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Activity log should be retained for at least one year (b02aacc0-b073-424e-8298-42b22829ee0a), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
Monitoring, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AU.3.046 | CMMC_L3_AU.3.046 | CMMC L3 AU.3.046 | Audit and Accountability | Alert in the event of an audit logging process failure. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Audit logging process failures include software and hardware errors, failures in the audit record capturing mechanisms, and audit record storage capacity being reached or exceeded. This requirement applies to each audit record data storage repository (i.e., distinct system component where audit records are stored), the total audit record storage capacity of organizations (i.e., all audit record data storage repositories combined), or both. | link | count: 007 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917) |
Monitoring, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AU.3.048 | CMMC_L3_AU.3.048 | CMMC L3 AU.3.048 | Audit and Accountability | Collect audit information (e.g., logs) into one or more central repositories. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations must aggregate and store audit logs in a central location to enable analysis activities and protect audit information. The repository should have the necessary infrastructure, capacity, and protection mechanisms to meet the organization’s audit requirements. | link | count: 008 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
App Service, Internet of Things, Monitoring | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | AU.3.049 | CMMC_L3_AU.3.049 | CMMC L3 AU.3.049 | Audit and Accountability | Protect audit information and audit logging tools from unauthorized access, modification, and deletion. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Audit information includes all information (e.g., audit records, audit log settings, and audit reports) needed to successfully audit system activity. Audit logging tools are those programs and devices used to conduct audit and logging activities. This requirement focuses on the technical protection of audit information and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by media protection and physical and environmental protection requirements. | link | count: 002 An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9) |
Monitoring | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | CA.2.158 | CMMC_L3_CA.2.158 | CMMC L3 CA.2.158 | Security Assessment | Periodically assess the security controls in organizational systems to determine if the controls are effective in their application. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations assess security controls in organizational systems and the environments in which those systems operate as part of the system development life cycle. Security controls are the safeguards or countermeasures organizations implement to satisfy security requirements. By assessing the implemented security controls, organizations determine if the security safeguards or countermeasures are in place and operating as intended. Security control assessments ensure that information security is built into organizational systems; identify weaknesses and deficiencies early in the development process; provide essential information needed to make risk-based decisions; and ensure compliance to vulnerability mitigation procedures. Assessments are conducted on the implemented security controls as documented in system security plans. Security assessment reports document assessment results in sufficient detail as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the security controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting security requirements. Security assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. Organizations ensure that security assessment results are current, relevant to the determination of security control effectiveness, and obtained with the appropriate level of assessor independence. Organizations can choose to use other types of assessment activities such as vulnerability scanning and system monitoring to maintain the security posture of systems during the system life cycle. | link | count: 010 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Security Center standard pricing tier should be selected (a1181c5f-672a-477a-979a-7d58aa086233), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Monitoring, Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | CA.3.161 | CMMC_L3_CA.3.161 | CMMC L3 CA.3.161 | Security Assessment | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Continuous monitoring programs facilitate ongoing awareness of threats, vulnerabilities, and information security to support organizational risk management decisions. The terms continuous and ongoing imply that organizations assess and analyze security controls and information security-related risks at a frequency sufficient to support risk-based decisions. The results of continuous monitoring programs generate appropriate risk response actions by organizations. Providing access to security information on a continuing basis through reports or dashboards gives organizational officials the capability to make effective and timely risk management decisions. Automation supports more frequent updates to hardware, software, firmware inventories, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Monitoring requirements, including the need for specific monitoring, may also be referenced in other requirements. | link | count: 010 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Security Center standard pricing tier should be selected (a1181c5f-672a-477a-979a-7d58aa086233), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Monitoring, Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | CM.2.061 | CMMC_L3_CM.2.061 | CMMC L3 CM.2.061 | Configuration Management | Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Baseline configurations are documented, formally reviewed, and agreed-upon specifications for systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, and changes to systems. Baseline configurations include information about system components (e.g., standard software packages installed on workstations, notebook computers, servers, network components, or mobile devices; current version numbers and update and patch information on operating systems and applications; and configuration settings and parameters), network topology, and the logical placement of those components within the system architecture. Baseline configurations of systems also reflect the current enterprise architecture. Maintaining effective baseline configurations requires creating new baselines as organizational systems change over time. Baseline configuration maintenance includes reviewing and updating the baseline configuration when changes are made based on security risks and deviations from the established baseline configuration Organizations can implement centralized system component inventories that include components from multiple organizational systems. In such situations, organizations ensure that the resulting inventories include system-specific information required for proper component accountability (e.g., system association, system owner). Information deemed necessary for effective accountability of system components includes hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include manufacturer, device type, model, serial number, and physical location. | link | count: 003 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd) |
Guest Configuration, Monitoring, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | CM.2.062 | CMMC_L3_CM.2.062 | CMMC L3 CM.2.062 | Configuration Management | Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Systems can provide a wide variety of functions and services. Some of the functions and services routinely provided by default, may not be necessary to support essential organizational missions, functions, or operations. It is sometimes convenient to provide multiple services from single system components. However, doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per component. Organizations review functions and services provided by systems or components of systems, to determine which functions and services are candidates for elimination. Organizations disable unused or unnecessary physical and logical ports and protocols to prevent unauthorized connection of devices, transfer of information, and tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services. | link | count: 002 Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Windows machines should meet requirements for 'System Audit Policies - Privilege Use' (87845465-c458-45f3-af66-dcd62176f397) |
Guest Configuration, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | CM.2.063 | CMMC_L3_CM.2.063 | CMMC L3 CM.2.063 | Configuration Management | Control and monitor user-installed software. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Users can install software in organizational systems if provided the necessary privileges. To maintain control over the software installed, organizations identify permitted and prohibited actions regarding software installation through policies. Permitted software installations include updates and security patches to existing software and applications from organization-approved “app stores.” Prohibited software installations may include software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods, automated methods, or both. | link | count: 004 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Security Center standard pricing tier should be selected (a1181c5f-672a-477a-979a-7d58aa086233), Windows machines should meet requirements for 'Security Options - User Account Control' (492a29ed-d143-4f03-b6a4-705ce081b463) |
Guest Configuration, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | CM.2.064 | CMMC_L3_CM.2.064 | CMMC L3 CM.2.064 | Configuration Management | Establish and enforce security configuration settings for information technology products employed in organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture or functionality of the system. Information technology products for which security-related configuration settings can be defined include mainframe computers, servers, workstations, input and output devices (e.g., scanners, copiers, and printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications. Security parameters are those parameters impacting the security state of systems including the parameters required to satisfy other security requirements. Security parameters include: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific configuration settings for systems. The established settings become part of the systems configuration baseline. Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations including information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors. | link | count: 010 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration, Key Vault, Network, Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | CM.2.065 | CMMC_L3_CM.2.065 | CMMC L3 CM.2.065 | Configuration Management | Track, review, approve or disapprove, and log changes to organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Tracking, reviewing, approving/disapproving, and logging changes is called configuration change control. Configuration change control for organizational systems involves the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications. Configuration change control includes changes to baseline configurations for components and configuration items of systems, changes to configuration settings for information technology products (e.g., operating systems, applications, firewalls, routers, and mobile devices), unscheduled and unauthorized changes, and changes to remediate vulnerabilities. Processes for managing configuration changes to systems include Configuration Control Boards or Change Advisory Boards that review and approve proposed changes to systems. For new development systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards or Change Advisory Boards. Audit logs of changes include activities before and after changes are made to organizational systems and the activities required to implement such changes. | link | count: 006 An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7), Windows machines should meet requirements for 'System Audit Policies - Policy Change' (2a7a701e-dff3-4da9-9ec5-42cb98594c0b) |
Guest Configuration, Monitoring | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | CM.3.068 | CMMC_L3_CM.3.068 | CMMC L3 CM.3.068 | Configuration Management | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Restricting the use of nonessential software (programs) includes restricting the roles allowed to approve program execution; prohibiting auto-execute; program blacklisting and whitelisting; or restricting the number of program instances executed at the same time. The organization makes a security-based determination which functions, ports, protocols, and/or services are restricted. Bluetooth, File Transfer Protocol (FTP), and peer-to-peer networking are examples of protocols organizations consider preventing the use of, restricting, or disabling. | link | count: 024 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), CORS should not allow every domain to access your API for FHIR (0fea8f8a-4169-495d-8307-30ec335f387d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517) |
API for FHIR, App Service, Azure Ai Services, Container Registry, Kubernetes, Security Center, SQL, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | CM.3.069 | CMMC_L3_CM.3.069 | CMMC L3 CM.3.069 | Configuration Management | Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | The process used to identify software programs that are not authorized to execute on systems is commonly referred to as blacklisting. The process used to identify software programs that are authorized to execute on systems is commonly referred to as whitelisting. Whitelisting is the stronger of the two policies for restricting software program execution. In addition to whitelisting, organizations consider verifying the integrity of whitelisted software programs using, for example, cryptographic checksums, digital signatures, or hash functions. Verification of whitelisted software can occur either prior to execution or at system startup. | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | IA.1.077 | CMMC_L3_IA.1.077 | CMMC L3 IA.1.077 | Identification and Authentication | Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Individual authenticators include the following: passwords, key cards, cryptographic devices, and one-time password devices. Initial authenticator content is the actual content of the authenticator, for example, the initial password. In contrast, the requirements about authenticator content include the minimum password length. Developers ship system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant security risk. Systems support authenticator management by organization-defined settings and restrictions for various authenticator characteristics including minimum password length, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication. Authenticator management includes issuing and revoking, when no longer needed, authenticators for temporary access such as that required for remote maintenance. Device authenticators include certificates and passwords. | link | count: 009 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | IA.2.078 | CMMC_L3_IA.2.078 | CMMC L3 IA.2.078 | Identification and Authentication | Enforce a minimum password complexity and change of characters when new passwords are created. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement applies to single-factor authentication of individuals using passwords as individual or group authenticators, and in a similar manner, when passwords are used as part of multifactor authenticators. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. To mitigate certain brute force attacks against passwords, organizations may also consider salting passwords. | link | count: 007 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | IA.2.079 | CMMC_L3_IA.2.079 | CMMC L3 IA.2.079 | Identification and Authentication | Prohibit password reuse for a specified number of generations. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Password lifetime restrictions do not apply to temporary passwords. | link | count: 005 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | IA.2.081 | CMMC_L3_IA.2.081 | CMMC L3 IA.2.081 | Identification and Authentication | Store and transmit only cryptographically-protected passwords. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Cryptographically-protected passwords use salted one-way cryptographic hashes of passwords. | link | count: 005 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | IA.3.083 | CMMC_L3_IA.3.083 | CMMC L3 IA.3.083 | Identification and Authentication | Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Multifactor authentication requires the use of two or more different factors to authenticate. The factors are defined as something you know (e.g., password, personal identification number [PIN]); something you have (e.g., cryptographic identification device, token); or something you are (e.g., biometric). Multifactor authentication solutions that feature physical authenticators include hardware authenticators providing time-based or challenge-response authenticators and smart cards. In addition to authenticating users at the system level (i.e., at logon), organizations may also employ authentication mechanisms at the application level, when necessary, to provide increased information security. Access to organizational systems is defined as local access or network access. Local access is any access to organizational systems by users (or processes acting on behalf of users) where such access is obtained by direct connections without the use of networks. Network access is access to systems by users (or processes acting on behalf of users) where such access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks. The use of encrypted virtual private networks for connections between organization-controlled and non-organization controlled endpoints may be treated as internal networks with regard to protecting the confidentiality of information. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | IA.3.084 | CMMC_L3_IA.3.084 | CMMC L3 IA.3.084 | Identification and Authentication | Employ replay-resistant authentication mechanisms for network access to privileged and nonprivileged accounts. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Authentication processes resist replay attacks if it is impractical to successfully authenticate by recording or replaying previous authentication messages. Replay-resistant techniques include protocols that use nonces or challenges such as time synchronous or challenge-response one-time authenticators. | link | count: 008 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Guest Configuration, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | IR.2.092 | CMMC_L3_IR.2.092 | CMMC L3 IR.2.092 | Incident Response | Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations recognize that incident handling capability is dependent on the capabilities of organizational systems and the mission/business processes being supported by those systems. Organizations consider incident handling as part of the definition, design, and development of mission/business processes and systems. Incident-related information can be obtained from a variety of sources including audit monitoring, network monitoring, physical access monitoring, user and administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including mission/business owners, system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive. As part of user response activities, incident response training is provided by organizations and is linked directly to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, regular users may only need to know who to call or how to recognize an incident on the system; system administrators may require additional training on how to handle or remediate incidents; and incident responders may receive more specific training on forensics, reporting, system recovery, and restoration. Incident response training includes user training in the identification/reporting of suspicious activities from external and internal sources. User response activities also includes incident response assistance which may consist of help desk support, assistance groups, and access to forensics services or consumer redress services, when required. | link | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | IR.2.093 | CMMC_L3_IR.2.093 | CMMC L3 IR.2.093 | Incident Response | Detect and report events. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | The monitoring, identification, and reporting of events are the foundation for incident identification and commence the incident life cycle. Events potentially affect the productivity of organizational assets and, in turn, associated services. These events must be captured and analyzed so that the organization can determine whether an event will become (or has become) an incident that requires organizational action. The extent to which an organization can identify events improves its ability to manage and control incidents and their potential effects. | link | count: 019 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Deploy Advanced Threat Protection for Cosmos DB Accounts (b5f04e03-92a3-4b09-9410-2cc5e5047656), Deploy Defender for Storage (Classic) on storage accounts (361c2074-3595-4e5d-8cab-4f21dffc835c), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8) |
Cosmos DB, Key Vault, Monitoring, Network, Security Center, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | RE.2.137 | CMMC_L3_RE.2.137 | CMMC L3 RE.2.137 | Recovery | Regularly perform and test data back-ups. | Customer | The customer is responsible for implementing this requirement. | Backups are used to recover data in the event of a hardware or software failure. Backups should be performed and tested regularly based on an organizational defined frequency. | link | count: 006 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Backup, Compute, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | RE.3.139 | CMMC_L3_RE.3.139 | CMMC L3 RE.3.139 | Recovery | Regularly perform complete, comprehensive and resilient data backups as organizationally-defined. | Customer | The customer is responsible for implementing this requirement. | The processes and tools used to properly back up critical information with a proven methodology for timely recovery of it. When attackers compromise machines, they often make significant changes to configurations and software. Sometimes attackers also make subtle alterations of data stored on compromised machines, potentially jeopardizing organizational effectiveness with polluted data. When the attackers are discovered, it can be extremely difficult for organizations without a trustworthy data recovery capability to remove all aspects of the attacker’s presence on the machine. This practice is based on the following CIS controls: 10.1 Ensure that all system data is automatically backed up on a regular basis. 10.2 Ensure that all of the organization’s key systems are backed up as a complete system, through processes such as imaging, to enable the quick recovery of an entire system. 10.5 Ensure that all backups have at least one offline (i.e., not accessible via a network connection) backup destination. | link | count: 006 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Backup, Compute, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | RM.2.141 | CMMC_L3_RM.2.141 | CMMC L3 RM.2.141 | Risk Assessment | Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Clearly defined system boundaries are a prerequisite for effective risk assessments. Such risk assessments consider threats, vulnerabilities, likelihood, and impact to organizational operations, organizational assets, and individuals based on the operation and use of organizational systems. Risk assessments also consider risk from external parties (e.g., service providers, contractors operating systems on behalf of the organization, individuals accessing organizational systems, outsourcing entities). Risk assessments, either formal or informal, can be conducted at the organization level, the mission or business process level, or the system level, and at any phase in the system development life cycle. | link | count: 013 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Security Center standard pricing tier should be selected (a1181c5f-672a-477a-979a-7d58aa086233), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | RM.2.142 | CMMC_L3_RM.2.142 | CMMC L3 RM.2.142 | Risk Assessment | Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations determine the required vulnerability scanning for all system components, ensuring that potential sources of vulnerabilities such as networked printers, scanners, and copiers are not overlooked. The vulnerabilities to be scanned are readily updated as new vulnerabilities are discovered, announced, and scanning methods developed. This process ensures that potential vulnerabilities in the system are identified and addressed as quickly as possible. Vulnerability analyses for custom software applications may require additional approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can employ these analysis approaches in source code reviews and in a variety of tools (e.g., static analysis tools, web-based application scanners, binary analyzers) and in source code reviews. Vulnerability scanning includes: scanning for patch levels; scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and scanning for improperly configured or incorrectly operating information flow control mechanisms. To facilitate interoperability, organizations consider using products that are Security Content Automated Protocol (SCAP)-validated, scanning tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention, and that employ the Open Vulnerability Assessment Language (OVAL) to determine the presence of system vulnerabilities. Sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). Security assessments, such as red team exercises, provide additional sources of potential vulnerabilities for which to scan. Organizations also consider using scanning tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS). In certain situations, the nature of the vulnerability scanning may be more intrusive or the system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system components facilitates thorough vulnerability scanning and protects the sensitive nature of such scanning. | link | count: 013 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Security Center standard pricing tier should be selected (a1181c5f-672a-477a-979a-7d58aa086233), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | RM.2.143 | CMMC_L3_RM.2.143 | CMMC L3 RM.2.143 | Risk Assessment | Remediate vulnerabilities in accordance with risk assessments. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Vulnerabilities discovered, for example, via the scanning conducted in response to RM.2.142, are remediated with consideration of the related assessment of risk. The consideration of risk influences the prioritization of remediation efforts and the level of effort to be expended in the remediation for specific vulnerabilities. | link | count: 018 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Security Center standard pricing tier should be selected (a1181c5f-672a-477a-979a-7d58aa086233), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | RM.3.144 | CMMC_L3_RM.3.144 | CMMC L3 RM.3.144 | Risk Management | Periodically perform risk assessments to identify and prioritize risks according to the defined risk categories, risk sources and risk measurement criteria. | Shared | Microsoft and the customer share responsibility for implementing this requirement. | Organizations must evaluate potential cybersecurity risks to operations, assets, and individuals. | link | count: 008 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Security Center standard pricing tier should be selected (a1181c5f-672a-477a-979a-7d58aa086233) |
Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.1.175 | CMMC_L3_SC.1.175 | CMMC L3 SC.1.175 | System and Communications Protection | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Communications can be monitored, controlled, and protected at boundary components and by restricting or prohibiting interfaces in organizational systems. Boundary components include gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within a system security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). Restricting or prohibiting interfaces in organizational systems includes restricting external web communications traffic to designated web servers within managed interfaces and prohibiting external traffic that appears to be spoofing internal addresses. Organizations consider the shared nature of commercial telecommunications services in the implementation of security requirements associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers and may also include third party-provided access lines and other service elements. Such transmission services may represent sources of increased risk despite contract security provisions. | link | count: 031 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112), Windows machines should meet requirements for 'Security Options - Network Access' (3ff60f98-7fa4-410a-9f7f-0b00f5afdbdd), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
App Service, Azure Ai Services, Cache, Container Registry, Guest Configuration, Kubernetes, Network, Security Center, SQL, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.1.176 | CMMC_L3_SC.1.176 | CMMC L3 SC.1.176 | System and Communications Protection | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones (DMZs). DMZs are typically implemented with boundary control devices and techniques that include routers, gateways, firewalls, virtualization, or cloud-based technologies. | link | count: 005 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517) |
Security Center, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.2.179 | CMMC_L3_SC.2.179 | CMMC L3 SC.2.179 | System and Communications Protection | Use encrypted sessions for the management of network devices. | Customer | The customer is responsible for implementing this requirement. | Management of network devices is a security critical process and needs to have confidentiality protection and authentication to protect against adversaries trying to gain information or change the network infrastructure. Confidentiality protection prevents an adversary from sniffing passwords or configuration information. Authenticity protection includes, for example, protecting against man-in-the-middle attacks, session hijacking, and the insertion of false information into communications sessions. This requirement addresses communications protection at the session versus packet level (e.g., sessions in service-oriented architectures providing web-based services). | link | count: 001 Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.3.177 | CMMC_L3_SC.3.177 | CMMC L3 SC.3.177 | System and Communications Protection | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Cryptography can be employed to support many security solutions including the protection of controlled unclassified information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Cryptographic standards include FIPSvalidated cryptography and/or NSA-approved cryptography. | link | count: 026 Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure API for FHIR should use a customer-managed key to encrypt data at rest (051cba44-2429-45b9-9649-46cec11c7119), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Data Explorer encryption at rest should use a customer-managed key (81e74cea-30fd-40d5-802f-d72103c2aaaa), Azure Stream Analytics jobs should use customer-managed keys to encrypt data (87ba29ef-1ab3-4d82-b763-87fcd4f531f7), Azure Synapse workspaces should use customer-managed keys to encrypt data at rest (f7d52b2d-e161-4dfa-a82b-55e564167385), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Certificates using RSA cryptography should have the specified minimum key size (cee51871-e572-4576-855c-047c820360f0), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Keys should be the specified cryptographic type RSA or EC (75c4f823-d65c-4f29-a733-01d0077fdbcb), Keys using elliptic curve cryptography should have the specified curve names (ff25f3c8-b739-4538-9d07-3d6d25cfb255), Keys using RSA cryptography should have a specified minimum key size (82067dbb-e53b-4e06-b631-546d197452d9), Require encryption on Data Lake Store accounts (a7ff3161-0087-490a-9ad9-ad6217f4f43a), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
API for FHIR, Automation, Azure Data Explorer, Cognitive Services, Container Registry, Data Box, Data Lake, Guest Configuration, Key Vault, Kubernetes, Security Center, Service Fabric, SQL, Storage, Stream Analytics, Synapse | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.3.180 | CMMC_L3_SC.3.180 | CMMC L3 SC.3.180 | System and Communications Protection | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations apply systems security engineering principles to new development systems or systems undergoing major upgrades. For legacy systems, organizations apply systems security engineering principles to system upgrades and modifications to the extent feasible, given the current state of hardware, software, and firmware components within those systems. The application of systems security engineering concepts and principles helps to develop trustworthy, secure, and resilient systems and system components and reduce the susceptibility of organizations to disruptions, hazards, and threats. Examples of these concepts and principles include developing layered protections; establishing security policies, architecture, and controls as the foundation for design; incorporating security requirements into the system development life cycle; delineating physical and logical security boundaries; ensuring that developers are trained on how to build secure software; and performing threat modeling to identify use cases, threat agents, attack vectors and patterns, design patterns, and compensating controls needed to mitigate risk. Organizations that apply security engineering concepts and principles can facilitate the development of trustworthy, secure systems, system components, and system services; reduce risk to acceptable levels; and make informed risk-management decisions. | link | count: 001 Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517) |
Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.3.181 | CMMC_L3_SC.3.181 | CMMC L3 SC.3.181 | System and Communications Protection | Separate user functionality from system management functionality. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | System management functionality includes functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from system management functionality is physical or logical. Organizations can implement separation of system management functionality from user functionality by using different computers, different central processing units, different instances of operating systems, or different network addresses; virtualization techniques; or combinations of these or other methods, as appropriate. This type of separation includes web administrative interfaces that use separate authentication methods for users of any other system resources. Separation of system and user functionality may include isolating administrative interfaces on different domains and with additional access controls. | link | count: 006 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.3.183 | CMMC_L3_SC.3.183 | CMMC L3 SC.3.183 | System and Communications Protection | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement applies to inbound and outbound network communications traffic at the system boundary and at identified points within the system. A deny-all, permit-by-exception network communications traffic policy ensures that only those connections which are essential and approved are allowed. | link | count: 031 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), CORS should not allow every domain to access your API for FHIR (0fea8f8a-4169-495d-8307-30ec335f387d), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8), Windows machines should meet requirements for 'Security Options - Network Access' (3ff60f98-7fa4-410a-9f7f-0b00f5afdbdd), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
API for FHIR, App Service, Azure Ai Services, Container Registry, Guest Configuration, Key Vault, Kubernetes, Network, Security Center, SQL, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.3.185 | CMMC_L3_SC.3.185 | CMMC L3 SC.3.185 | System and Communications Protection | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement applies to internal and external networks and any system components that can transmit information including servers, notebook computers, desktop computers, mobile devices, printers, copiers, scanners, and facsimile machines. Communication paths outside the physical protection of controlled boundaries are susceptible to both interception and modification. Organizations relying on commercial providers offering transmission services as commodity services rather than as fully dedicated services (i.e., services which can be highly specialized to individual customer needs), may find it difficult to obtain the necessary assurances regarding the implementation of the controls for transmission confidentiality. In such situations, organizations determine what types of confidentiality services are available in commercial telecommunication service packages. If it is infeasible or impractical to obtain the necessary safeguards and assurances of the effectiveness of the safeguards through appropriate contracting vehicles, organizations implement compensating safeguards or explicitly accept the additional risk. An example of an alternative physical safeguard is a protected distribution system (PDS) where the distribution medium is protected against electronic or physical intercept, thereby ensuring the confidentiality of the information being transmitted. | link | count: 010 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, SQL, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.3.187 | CMMC_L3_SC.3.187 | CMMC L3 SC.3.187 | System and Communications Protection | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Cryptographic key management and establishment can be performed using manual procedures or mechanisms supported by manual procedures. Organizations define key management requirements in accordance with applicable federal laws, Executive Orders, policies, directives, regulations, and standards specifying appropriate options, levels, and parameters. | link | count: 008 Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d), Keys should be the specified cryptographic type RSA or EC (75c4f823-d65c-4f29-a733-01d0077fdbcb), Keys using elliptic curve cryptography should have the specified curve names (ff25f3c8-b739-4538-9d07-3d6d25cfb255), Keys using RSA cryptography should have a specified minimum key size (82067dbb-e53b-4e06-b631-546d197452d9) |
Key Vault, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.3.190 | CMMC_L3_SC.3.190 | CMMC L3 SC.3.190 | System and Communications Protection | Protect the authenticity of communications sessions. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Authenticity protection includes protecting against man-in-the-middle attacks, session hijacking, and the insertion of false information into communications sessions. This requirement addresses communications protection at the session versus packet level (e.g., sessions in service-oriented architectures providing web-based services) and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. | link | count: 011 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Certificates using RSA cryptography should have the specified minimum key size (cee51871-e572-4576-855c-047c820360f0), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Guest Configuration, Key Vault, Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SC.3.191 | CMMC_L3_SC.3.191 | CMMC L3 SC.3.191 | System and Communications Protection | Protect the confidentiality of CUI at rest. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Information at rest refers to the state of information when it is not in process or in transit and is located on storage devices as specific components of systems. The focus of protection at rest is not on the type of storage device or the frequency of access but rather the state of the information. Organizations can use different mechanisms to achieve confidentiality protections, including the use of cryptographic mechanisms and file share scanning. Organizations may also use other controls including secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved or continuous monitoring to identify malicious code at rest. | link | count: 014 Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Require encryption on Data Lake Store accounts (a7ff3161-0087-490a-9ad9-ad6217f4f43a), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Automation, Azure Data Explorer, Data Box, Data Lake, Security Center, Service Fabric, SQL, Storage | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SI.1.210 | CMMC_L3_SI.1.210 | CMMC L3 SI.1.210 | System and Information Integrity | Identify, report, and correct information and information system flaws in a timely manner. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations identify systems that are affected by announced software and firmware flaws including potential vulnerabilities resulting from those flaws and report this information to designated personnel with information security responsibilities. Security-relevant updates include patches, service packs, hot fixes, and anti-virus signatures. Organizations address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations can take advantage of available resources such as the Common Weakness Enumeration (CWE) database or Common Vulnerabilities and Exposures (CVE) database in remediating flaws discovered in organizational systems. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types of remediation. | link | count: 011 App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
App Service, Compute, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SI.1.211 | CMMC_L3_SI.1.211 | CMMC L3 SI.1.211 | System and Information Integrity | Provide protection from malicious code at appropriate locations within organizational information systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Designated locations include system entry and exit points which may include firewalls, remoteaccess servers, workstations, electronic mail servers, web servers, proxy servers, notebook computers, and mobile devices. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. Malicious code protection mechanisms include anti-virus signature definitions and reputationbased technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. | link | count: 004 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Compute, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SI.1.212 | CMMC_L3_SI.1.212 | CMMC L3 SI.1.212 | System and Information Integrity | Update malicious code protection mechanisms when new releases are available. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Malicious code protection mechanisms include anti-virus signature definitions and reputationbased technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. | link | count: 001 Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57) |
Compute | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SI.1.213 | CMMC_L3_SI.1.213 | CMMC L3 SI.1.213 | System and Information Integrity | Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Periodic scans of organizational systems and real-time scans of files from external sources can detect malicious code. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. | link | count: 010 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Compute, Security Center | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SI.2.216 | CMMC_L3_SI.2.216 | CMMC L3 SI.2.216 | System and Information Integrity | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | System monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at the system boundary (i.e., part of perimeter defense and boundary protection). Internal monitoring includes the observation of events occurring within the system. Organizations can monitor systems, for example, by observing audit record activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives may guide determination of the events. System monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Strategic locations for monitoring devices include selected perimeter locations and near server farms supporting critical applications, with such devices being employed at managed system interfaces. The granularity of monitoring information collected is based on organizational monitoring objectives and the capability of systems to support such objectives. System monitoring is an integral part of continuous monitoring and incident response programs. Output from system monitoring serves as input to continuous monitoring and incident response programs. A network connection is any connection with a device that communicates through a network (e.g., local area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Local, network, and remote connections can be either wired or wireless. Unusual or unauthorized activities or conditions related to inbound/outbound communications traffic include internal traffic that indicates the presence of malicious code in systems or propagating among system components, the unauthorized exporting of information, or signaling to external systems. Evidence of malicious code is used to identify potentially compromised systems or system components. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other requirements. | link | count: 023 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8) |
Monitoring, Network, Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| CMMC_L3 | SI.2.217 | CMMC_L3_SI.2.217 | CMMC L3 SI.2.217 | System and Information Integrity | Identify unauthorized use of organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | System monitoring includes external and internal monitoring. System monitoring can detect unauthorized use of organizational systems. System monitoring is an integral part of continuous monitoring and incident response programs. Monitoring is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Output from system monitoring serves as input to continuous monitoring and incident response programs. Unusual/unauthorized activities or conditions related to inbound and outbound communications traffic include internal traffic that indicates the presence of malicious code in systems or propagating among system components, the unauthorized exporting of information, or signaling to external systems. Evidence of malicious code is used to identify potentially compromised systems or system components. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other requirements. | link | count: 011 Activity log should be retained for at least one year (b02aacc0-b073-424e-8298-42b22829ee0a), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6) |
Monitoring, Network, Security Center, SQL | CMMC Level 3 (b5629c75-5c77-4422-87b9-2509e680f8de) |
| FedRAMP_High_R4 | AC-1 | FedRAMP_High_R4_AC-1 | FedRAMP High AC-1 | Access Control | Access Control Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the access control policy and associated access controls; and b. Reviews and updates the current: 1. Access control policy [Assignment: organization-defined frequency]; and 2. Access control procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AC family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-10 | FedRAMP_High_R4_AC-10 | FedRAMP High AC-10 | Access Control | Concurrent Session Control | Shared | n/a | The information system limits the number of concurrent sessions for each [Assignment: organization-defined account and/or account type] to [Assignment: organization-defined number]. Supplemental Guidance: Organizations may define the maximum number of concurrent sessions for information system accounts globally, by account type (e.g., privileged user, non-privileged user, domain, specific application), by account, or a combination. For example, organizations may limit the number of concurrent sessions for system administrators or individuals working in particularly sensitive domains or mission-critical applications. This control addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. Control Enhancements: None. References: None. | link | count: 001 Define and enforce the limit of concurrent sessions (d8350d4c-9314-400b-288f-20ddfce04fbd) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-12 | FedRAMP_High_R4_AC-12 | FedRAMP High AC-12 | Access Control | Session Termination | Shared | n/a | The information system automatically terminates a user session after [Assignment: organization-defined conditions or trigger events requiring session disconnect]. Supplemental Guidance: This control addresses the termination of user-initiated logical sessions in contrast to SC-10 which addresses the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user’s logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, time-of-day restrictions on information system use. Related controls: SC-10, SC-23. References: None. | link | count: 001 Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-12(1) | FedRAMP_High_R4_AC-12(1) | FedRAMP High AC-12 (1) | Access Control | User-Initiated Logouts / Message Displays | Shared | n/a | The information system: (a) Provides a logout capability for user-initiated communications sessions whenever authentication is used to gain access to [Assignment: organization-defined information resources]; and (b) Displays an explicit logout message to users indicating the reliable termination of authenticated communications sessions. Supplemental Guidance: Information resources to which users gain access via authentication include, for example, local workstations, databases, and password-protected websites/web- based services. Logout messages for web page access, for example, can be displayed after authenticated sessions have been terminated. However, for some types of interactive sessions including, for example, file transfer protocol (FTP) sessions, information systems typically send logout messages as final messages prior to terminating sessions. | link | count: 002 Display an explicit logout message (0471c6b7-1588-701c-2713-1fade73b75f6), Provide the logout capability (db580551-0b3c-4ea1-8a4c-4cdb5feb340f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-14 | FedRAMP_High_R4_AC-14 | FedRAMP High AC-14 | Access Control | Permitted Actions Without Identification Or Authentication | Shared | n/a | The organization: a. Identifies [Assignment: organization-defined user actions] that can be performed on the information system without identification or authentication consistent with organizational missions/business functions; and b. Documents and provides supporting rationale in the security plan for the information system, user actions not requiring identification or authentication. Supplemental Guidance: This control addresses situations in which organizations determine that no identification or authentication is required in organizational information systems. Organizations may allow a limited number of user actions without identification or authentication including, for example, when individuals access public websites or other publicly accessible federal information systems, when individuals use mobile phones to receive calls, or when facsimiles are received. Organizations also identify actions that normally require identification or authentication but may under certain circumstances (e.g., emergencies), allow identification or authentication mechanisms to be bypassed. Such bypasses may occur, for example, via a software-readable physical switch that commands bypass of the logon functionality and is protected from accidental or unmonitored use. This control does not apply to situations where identification and authentication have already occurred and are not repeated, but rather to situations where identification and authentication have not yet occurred. Organizations may decide that there are no user actions that can be performed on organizational information systems without identification and authentication and thus, the values for assignment statements can be none. Related controls: CP-2, IA-2. Control Enhancements: None. (1) PERMITTED ACTIONS WITHOUT IDENTIFICATION OR AUTHENTICATION | NECESSARY USES [Withdrawn: Incorporated into AC-14]. References: None. | link | count: 001 Identify actions allowed without authentication (92a7591f-73b3-1173-a09c-a08882d84c70) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-17 | FedRAMP_High_R4_AC-17 | FedRAMP High AC-17 | Access Control | Remote Access | Shared | n/a | The organization: a. Establishes and documents usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and b. Authorizes remote access to the information system prior to allowing such connections. Supplemental Guidance: Remote access is access to organizational information systems by users (or processes acting on behalf of users) communicating through external networks (e.g., the Internet). Remote access methods include, for example, dial-up, broadband, and wireless. Organizations often employ encrypted virtual private networks (VPNs) to enhance confidentiality and integrity over remote connections. The use of encrypted VPNs does not make the access non-remote; however, the use of VPNs, when adequately provisioned with appropriate security controls (e.g., employing appropriate encryption techniques for confidentiality and integrity protection) may provide sufficient assurance to the organization that it can effectively treat such connections as internal networks. Still, VPN connections traverse external networks, and the encrypted VPN does not enhance the availability of remote connections. Also, VPNs with encrypted tunnels can affect the organizational capability to adequately monitor network communications traffic for malicious code. Remote access controls apply to information systems other than public web servers or systems designed for public access. This control addresses authorization prior to allowing remote access without specifying the formats for such authorization. While organizations may use interconnection security agreements to authorize remote access connections, such agreements are not required by this control. Enforcing access restrictions for remote connections is addressed in AC-3. Related controls: AC-2, AC-3, AC-18, AC-19, AC-20, CA-3, CA-7, CM-8, IA-2, IA-3, IA-8, MA-4, PE-17, PL-4, SC-10, SI-4. References: NIST Special Publications 800-46, 800-77, 800-113, 800-114, 800-121. | link | count: 041 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-17(1) | FedRAMP_High_R4_AC-17(1) | FedRAMP High AC-17 (1) | Access Control | Automated Monitoring / Control | Shared | n/a | The information system monitors and controls remote access methods. Supplemental Guidance: Automated monitoring and control of remote access sessions allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote users on a variety of information system components (e.g., servers, workstations, notebook computers, smart phones, and tablets). Related controls: AU-2, AU-12. | link | count: 037 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-17(2) | FedRAMP_High_R4_AC-17(2) | FedRAMP High AC-17 (2) | Access Control | Protection Of Confidentiality / Integrity Using Encryption | Shared | n/a | The information system implements cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions. Supplemental Guidance: The encryption strength of mechanism is selected based on the security categorization of the information. Related controls: SC-8, SC-12, SC-13. | link | count: 002 Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-17(3) | FedRAMP_High_R4_AC-17(3) | FedRAMP High AC-17 (3) | Access Control | Managed Access Control Points | Shared | n/a | The information system routes all remote accesses through [Assignment: organization-defined number] managed network access control points. Supplemental Guidance: Limiting the number of access control points for remote accesses reduces the attack surface for organizations. Organizations consider the Trusted Internet Connections (TIC) initiative requirements for external network connections. Related control: SC-7. | link | count: 001 Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-17(4) | FedRAMP_High_R4_AC-17(4) | FedRAMP High AC-17 (4) | Access Control | Privileged Commands / Access | Shared | n/a | The organization: (a) Authorizes the execution of privileged commands and access to security-relevant information via remote access only for [Assignment: organization-defined needs]; and (b) Documents the rationale for such access in the security plan for the information system. Supplemental Guidance: Related control: AC-6. | link | count: 005 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Authorize remote access to privileged commands (01c387ea-383d-4ca9-295a-977fab516b03), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-17(9) | FedRAMP_High_R4_AC-17(9) | FedRAMP High AC-17 (9) | Access Control | Disconnect / Disable Access | Shared | n/a | The organization provides the capability to expeditiously disconnect or disable remote access to the information system within [Assignment: organization-defined time period]. Supplemental Guidance: This control enhancement requires organizations to have the capability to rapidly disconnect current users remotely accessing the information system and/or disable further remote access. The speed of disconnect or disablement varies based on the criticality of missions/business functions and the need to eliminate immediate or future remote access to organizational information systems. | link | count: 001 Provide capability to disconnect or disable remote access (4edaca8c-0912-1ac5-9eaa-6a1057740fae) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-18 | FedRAMP_High_R4_AC-18 | FedRAMP High AC-18 | Access Control | Wireless Access | Shared | n/a | The organization: a. Establishes usage restrictions, configuration/connection requirements, and implementation guidance for wireless access; and b. Authorizes wireless access to the information system prior to allowing such connections. Supplemental Guidance: Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual authentication. Related controls: AC-2, AC-3, AC-17, AC-19, CA-3, CA-7, CM-8, IA-2, IA-3, IA-8, PL-4, SI-4. References: NIST Special Publications 800-48, 800-94, 800-97. | link | count: 002 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-18(1) | FedRAMP_High_R4_AC-18(1) | FedRAMP High AC-18 (1) | Access Control | Authentication And Encryption | Shared | n/a | The information system protects wireless access to the system using authentication of [Selection (one or more): users; devices] and encryption. Supplemental Guidance: Related controls: SC-8, SC-13. | link | count: 003 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-19 | FedRAMP_High_R4_AC-19 | FedRAMP High AC-19 | Access Control | Access Control For Mobile Devices | Shared | n/a | The organization: a. Establishes usage restrictions, configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices; and b. Authorizes the connection of mobile devices to organizational information systems. Supplemental Guidance: A mobile device is a computing device that: (i) has a small form factor such that it can easily be carried by a single individual; (ii) is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); (iii) possesses local, non- removable or removable data storage; and (iv) includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones, E-readers, and tablets. Mobile devices are typically associated with a single individual and the device is usually in close proximity to the individual; however, the degree of proximity can vary depending upon on the form factor and size of the device. The processing, storage, and transmission capability of the mobile device may be comparable to or merely a subset of desktop systems, depending upon the nature and intended purpose of the device. Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different classes/types of such devices. Usage restrictions and specific implementation guidance for mobile devices include, for example, configuration management, device identification and authentication, implementation of mandatory protective software (e.g., malicious code detection, firewall), scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting primary operating system (and possibly other resident software) integrity checks, and disabling unnecessary hardware (e.g., wireless, infrared). Organizations are cautioned that the need to provide adequate security for mobile devices goes beyond the requirements in this control. Many safeguards and countermeasures for mobile devices are reflected in other security controls in the catalog allocated in the initial control baselines as starting points for the development of security plans and overlays using the tailoring process. There may also be some degree of overlap in the requirements articulated by the security controls within the different families of controls. AC-20 addresses mobile devices that are not organization-controlled. Related controls: AC-3, AC-7, AC-18, AC-20, CA-9, CM-2, IA-2, IA-3, MP-2, MP-4, MP-5, PL-4, SC-7, SC-43, SI-3, SI-4. References: OMB Memorandum 06-16; NIST Special Publications 800-114, 800-124, 800-164. | link | count: 001 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-19(5) | FedRAMP_High_R4_AC-19(5) | FedRAMP High AC-19 (5) | Access Control | Full Device / Container-Based Encryption | Shared | n/a | The organization employs [Selection: full-device encryption; container encryption] to protect the confidentiality and integrity of information on [Assignment: organization-defined mobile devices]. Supplemental Guidance: Container-based encryption provides a more fine-grained approach to the encryption of data/information on mobile devices, including for example, encrypting selected data structures such as files, records, or fields. Related controls: MP-5, SC-13, SC-28. References: OMB Memorandum 06-16; NIST Special Publications 800-114, 800-124, 800-164. | link | count: 002 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2 | FedRAMP_High_R4_AC-2 | FedRAMP High AC-2 | Access Control | Account Management | Shared | n/a | The organization: a. Identifies and selects the following types of information system accounts to support organizational missions/business functions: [Assignment: organization-defined information system account types]; b. Assigns account managers for information system accounts; c. Establishes conditions for group and role membership; d. Specifies authorized users of the information system, group and role membership, and access authorizations (i.e., privileges) and other attributes (as required) for each account; e. Requires approvals by [Assignment: organization-defined personnel or roles] for requests to create information system accounts; f. Creates, enables, modifies, disables, and removes information system accounts in accordance with [Assignment: organization-defined procedures or conditions]; g. Monitors the use of, information system accounts; h. Notifies account managers: 1. When accounts are no longer required; 2. When users are terminated or transferred; and 3. When individual information system usage or need-to-know changes; i. Authorizes access to the information system based on: 1. A valid access authorization; 2. Intended system usage; and 3. Other attributes as required by the organization or associated missions/business functions; j. Reviews accounts for compliance with account management requirements [Assignment: organization-defined frequency]; and k. Establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group. Supplemental Guidance: Information system account types include individual, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service. Some of the account management requirements listed above can be implemented by organizational information systems. The identification of authorized users of the information system and the specification of access privileges reflects the requirements in other security controls in the security plan. Users requiring administrative privileges on information system accounts receive additional scrutiny by appropriate organizational personnel (e.g., system owner, mission/business owner, or chief information security officer) responsible for approving such accounts and privileged access. Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. Other attributes required for authorizing access include, for example, restrictions on time-of-day, day-of-week, and point-of-origin. In defining other account attributes, organizations consider system-related requirements (e.g., scheduled maintenance, system upgrades) and mission/business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements). Failure to consider these factors could affect information system availability. Temporary and emergency accounts are accounts intended for short-term use. Organizations establish temporary accounts as a part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. Organizations establish emergency accounts in response to crisis situations and with the need for rapid account activation. Therefore, emergency account activation may bypass normal account authorization processes. Emergency and temporary accounts are not to be confused with infrequently used accounts (e.g., local logon accounts used for special tasks defined by organizations or when network resources are unavailable). Such accounts remain available and are not subject to automatic disabling or removal dates. Conditions for disabling or deactivating accounts include, for example: (i) when shared/group, emergency, or temporary accounts are no longer required; or (ii) when individuals are transferred or terminated. Some types of information system accounts may require specialized training. Related controls: AC-3, AC-4, AC-5, AC-6, AC-10, AC-17, AC-19, AC-20, AU-9, IA-2, IA-4, IA-5, IA-8, CM-5, CM-6, CM-11, MA-3, MA-4, MA-5, PL-4, SC-13. References: None. | link | count: 025 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, General, Regulatory Compliance, Security Center, Service Fabric, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(1) | FedRAMP_High_R4_AC-2(1) | FedRAMP High AC-2 (1) | Access Control | Automated System Account Management | Shared | n/a | The organization employs automated mechanisms to support the management of information system accounts. Supplemental Guidance: The use of automated mechanisms can include, for example: using email or text messaging to automatically notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using telephonic notification to report atypical system account usage. | link | count: 007 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(10) | FedRAMP_High_R4_AC-2(10) | FedRAMP High AC-2 (10) | Access Control | Shared / Group Account Credential Termination | Shared | n/a | The information system terminates shared/group account credentials when members leave the group. | link | count: 001 Terminate customer controlled account credentials (76d66b5c-85e4-93f5-96a5-ebb2fad61dc6) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(11) | FedRAMP_High_R4_AC-2(11) | FedRAMP High AC-2 (11) | Access Control | Usage Conditions | Shared | n/a | The information system enforces [Assignment: organization-defined circumstances and/or usage conditions] for [Assignment: organization-defined information system accounts]. Supplemental Guidance: Organizations can describe the specific conditions or circumstances under which information system accounts can be used, for example, by restricting usage to certain days of the week, time of day, or specific durations of time. | link | count: 001 Enforce appropriate usage of all accounts (fd81a1b3-2d7a-107c-507e-29b87d040c19) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(12) | FedRAMP_High_R4_AC-2(12) | FedRAMP High AC-2 (12) | Access Control | Account Monitoring / Atypical Usage | Shared | n/a | The organization: (a) Monitors information system accounts for [Assignment: organization-defined atypical use]; and (b) Reports atypical usage of information system accounts to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Atypical usage includes, for example, accessing information systems at certain times of the day and from locations that are not consistent with the normal usage patterns of individuals working in organizations. Related control: CA-7. | link | count: 013 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81) |
Kubernetes, Regulatory Compliance, Security Center, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(13) | FedRAMP_High_R4_AC-2(13) | FedRAMP High AC-2 (13) | Access Control | Disable Accounts For High-Risk Individuals | Shared | n/a | The organization disables accounts of users posing a significant risk within [Assignment: organization-defined time period] of discovery of the risk. Supplemental Guidance: Users posing a significant risk to organizations include individuals for whom reliable evidence or intelligence indicates either the intention to use authorized access to information systems to cause harm or through whom adversaries will cause harm. Harm includes potential adverse impacts to organizational operations and assets, individuals, other organizations, or the Nation. Close coordination between authorizing officials, information system administrators, and human resource managers is essential in order for timely execution of this control enhancement. Related control: PS-4. | link | count: 001 Disable user accounts posing a significant risk (22c16ae4-19d0-29cb-422f-cb44061180ee) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(3) | FedRAMP_High_R4_AC-2(3) | FedRAMP High AC-2 (3) | Access Control | Disable Inactive Accounts | Shared | n/a | The information system automatically disables inactive accounts after [Assignment: organization-defined time period]. | link | count: 002 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(4) | FedRAMP_High_R4_AC-2(4) | FedRAMP High AC-2 (4) | Access Control | Automated Audit Actions | Shared | n/a | The information system automatically audits account creation, modification, enabling, disabling, and removal actions, and notifies [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Related controls: AU-2, AU-12. | link | count: 005 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(5) | FedRAMP_High_R4_AC-2(5) | FedRAMP High AC-2 (5) | Access Control | Inactivity Logout | Shared | n/a | The organization requires that users log out when [Assignment: organization-defined time-period of expected inactivity or description of when to log out]. Supplemental Guidance: Related control: SC-23. | link | count: 001 Define and enforce inactivity log policy (2af4640d-11a6-a64b-5ceb-a468f4341c0c) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(7) | FedRAMP_High_R4_AC-2(7) | FedRAMP High AC-2 (7) | Access Control | Role-Based Schemes | Shared | n/a | The organization: (a) Establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles; (b) Monitors privileged role assignments; and (c) Takes [Assignment: organization-defined actions] when privileged role assignments are no longer appropriate. Supplemental Guidance: Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. These privileged roles include, for example, key management, account management, network and system administration, database administration, and web administration. | link | count: 010 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Azure Ai Services, General, Regulatory Compliance, Service Fabric, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-2(9) | FedRAMP_High_R4_AC-2(9) | FedRAMP High AC-2 (9) | Access Control | Restrictions On Use Of Shared Groups / Accounts | Shared | n/a | The organization only permits the use of shared/group accounts that meet [Assignment: organization-defined conditions for establishing shared/group accounts]. | link | count: 001 Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-20 | FedRAMP_High_R4_AC-20 | FedRAMP High AC-20 | Access Control | Use Of External Information Systems | Shared | n/a | The organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to: a. Access the information system from external information systems; and b. Process, store, or transmit organization-controlled information using external information systems. Supplemental Guidance: External information systems are information systems or components of information systems that are outside of the authorization boundary established by organizations and for which organizations typically have no direct supervision and authority over the application of required security controls or the assessment of control effectiveness. External information systems include, for example: (i) personally owned information systems/devices (e.g., notebook computers, smart phones, tablets, personal digital assistants); (ii) privately owned computing and communications devices resident in commercial or public facilities (e.g., hotels, train stations, convention centers, shopping malls, or airports); (iii) information systems owned or controlled by nonfederal governmental organizations; and (iv) federal information systems that are not owned by, operated by, or under the direct supervision and authority of organizations. This control also addresses the use of external information systems for the processing, storage, or transmission of organizational information, including, for example, accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational information systems. For some external information systems (i.e., information systems operated by other federal agencies, including organizations subordinate to those agencies), the trust relationships that have been established between those organizations and the originating organization may be such, that no explicit terms and conditions are required. Information systems within these organizations would not be considered external. These situations occur when, for example, there are pre-existing sharing/trust agreements (either implicit or explicit) established between federal agencies or organizations subordinate to those agencies, or when such trust agreements are specified by applicable laws, Executive Orders, directives, or policies. Authorized individuals include, for example, organizational personnel, contractors, or other individuals with authorized access to organizational information systems and over which organizations have the authority to impose rules of behavior with regard to system access. Restrictions that organizations impose on authorized individuals need not be uniform, as those restrictions may vary depending upon the trust relationships between organizations. Therefore, organizations may choose to impose different security restrictions on contractors than on state, local, or tribal governments. This control does not apply to the use of external information systems to access public interfaces to organizational information systems (e.g., individuals accessing federal information through www.usa.gov). Organizations establish terms and conditions for the use of external information systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum: types of applications that can be accessed on organizational information systems from external information systems; and the highest security category of information that can be processed, stored, or transmitted on external information systems. If terms and conditions with the owners of external information systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems. Related controls: AC-3, AC-17, AC-19, CA-3, PL-4, SA-9. References: FIPS Publication 199. | link | count: 002 Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-20(1) | FedRAMP_High_R4_AC-20(1) | FedRAMP High AC-20 (1) | Access Control | Limits On Authorized Use | Shared | n/a | The organization permits authorized individuals to use an external information system to access the information system or to process, store, or transmit organization-controlled information only when the organization: (a) Verifies the implementation of required security controls on the external system as specified in the organization’s information security policy and security plan; or (b) Retains approved information system connection or processing agreements with the organizational entity hosting the external information system. Supplemental Guidance: This control enhancement recognizes that there are circumstances where individuals using external information systems (e.g., contractors, coalition partners) need to access organizational information systems. In those situations, organizations need confidence that the external information systems contain the necessary security safeguards (i.e., security controls), so as not to compromise, damage, or otherwise harm organizational information systems. Verification that the required security controls have been implemented can be achieved, for example, by third-party, independent assessments, attestations, or other means, depending on the confidence level required by organizations. Related control: CA-2. | link | count: 001 Verify security controls for external information systems (dc7ec756-221c-33c8-0afe-c48e10e42321) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-20(2) | FedRAMP_High_R4_AC-20(2) | FedRAMP High AC-20 (2) | Access Control | Portable Storage Devices | Shared | n/a | The organization [Selection: restricts; prohibits] the use of organization-controlled portable storage devices by authorized individuals on external information systems. Supplemental Guidance: Limits on the use of organization-controlled portable storage devices in external information systems include, for example, complete prohibition of the use of such devices or restrictions on how the devices may be used and under what conditions the devices may be used. | link | count: 003 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-21 | FedRAMP_High_R4_AC-21 | FedRAMP High AC-21 | Access Control | Information Sharing | Shared | n/a | The organization: a. Facilitates information sharing by enabling authorized users to determine whether access authorizations assigned to the sharing partner match the access restrictions on the information for [Assignment: organization-defined information sharing circumstances where user discretion is required]; and b. Employs [Assignment: organization-defined automated mechanisms or manual processes] to assist users in making information sharing/collaboration decisions. Supplemental Guidance: This control applies to information that may be restricted in some manner (e.g., privileged medical information, contract-sensitive information, proprietary information, personally identifiable information, classified information related to special access programs or compartments) based on some formal or administrative determination. Depending on the particular information-sharing circumstances, sharing partners may be defined at the individual, group, or organizational level. Information may be defined by content, type, security category, or special access program/compartment. Related control: AC-3. References: None. | link | count: 002 Automate information sharing decisions (e54901fe-42c2-7f3b-3c5f-327aa5320a69), Facilitate information sharing (a44c9fba-43f8-4b7b-7ee6-db52c96b4366) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-22 | FedRAMP_High_R4_AC-22 | FedRAMP High AC-22 | Access Control | Publicly Accessible Content | Shared | n/a | The organization: a. Designates individuals authorized to post information onto a publicly accessible information system; b. Trains authorized individuals to ensure that publicly accessible information does not contain nonpublic information; c. Reviews the proposed content of information prior to posting onto the publicly accessible information system to ensure that nonpublic information is not included; and d. Reviews the content on the publicly accessible information system for nonpublic information [Assignment: organization-defined frequency] and removes such information, if discovered. Supplemental Guidance: In accordance with federal laws, Executive Orders, directives, policies, regulations, standards, and/or guidance, the general public is not authorized access to nonpublic information (e.g., information protected under the Privacy Act and proprietary information). This control addresses information systems that are controlled by the organization and accessible to the general public, typically without identification or authentication. The posting of information on non-organization information systems is covered by organizational policy. Related controls: AC-3, AC-4, AT-2, AT-3, AU-13. Control Enhancements: None. References: None. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Review content prior to posting publicly accessible information (9e3c505e-7aeb-2096-3417-b132242731fc), Review publicly accessible content for nonpublic information (b5244f81-6cab-3188-2412-179162294996), Train personnel on disclosure of nonpublic information (97f0d974-1486-01e2-2088-b888f46c0589) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-3 | FedRAMP_High_R4_AC-3 | FedRAMP High AC-3 | Access Control | Access Enforcement | Shared | n/a | The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. Supplemental Guidance: Access control policies (e.g., identity-based policies, role-based policies, attribute-based policies) and access enforcement mechanisms (e.g., access control lists, access control matrices, cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, domains) in information systems. In addition to enforcing authorized access at the information system level and recognizing that information systems can host many applications and services in support of organizational missions and business operations, access enforcement mechanisms can also be employed at the application and service level to provide increased information security. Related controls: AC-2, AC-4, AC-5, AC-6, AC-16, AC-17, AC-18, AC-19, AC-20, AC-21, AC-22, AU-9, CM-5, CM-6, CM-11, MA-3, MA-4, MA-5, PE-3. References: None. | link | count: 021 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
App Service, Azure Ai Services, Compute, Guest Configuration, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-4 | FedRAMP_High_R4_AC-4 | FedRAMP High AC-4 | Access Control | Information Flow Enforcement | Shared | n/a | The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems based on [Assignment: organization-defined information flow control policies]. Supplemental Guidance: Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. Flow control restrictions include, for example, keeping export-controlled information from being transmitted in the clear to the Internet, blocking outside traffic that claims to be from within the organization, restricting web requests to the Internet that are not from the internal web proxy server, and limiting information transfers between organizations based on data structures and content. Transferring information between information systems representing different security domains with different security policies introduces risk that such transfers violate one or more domain security policies. In such situations, information owners/stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes, for example: (i) prohibiting information transfers between interconnected systems (i.e., allowing access only); (ii) employing hardware mechanisms to enforce one-way information flows; and (iii) implementing trustworthy regarding mechanisms to reassign security attributes and security labels. Organizations commonly employ information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path. Enforcement occurs, for example, in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, firewalls) that employ rule sets or establish configuration settings that restrict information system services, provide a packet-filtering capability based on header information, or message- filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Organizations also consider the trustworthiness of filtering/inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Control enhancements 3 through 22 primarily address cross-domain solution needs which focus on more advanced filtering techniques, in-depth analysis, and stronger flow enforcement mechanisms implemented in cross-domain products, for example, high-assurance guards. Such capabilities are generally not available in commercial off-the-shelf information technology products. Related controls: AC-3, AC-17, AC-19, AC-21, CM-6, CM-7, SA-8, SC-2, SC-5, SC-7, SC-18. References: None. | link | count: 053 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, API Management, App Configuration, App Service, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Regulatory Compliance, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-4(21) | FedRAMP_High_R4_AC-4(21) | FedRAMP High AC-4 (21) | Access Control | Physical / Logical Separation Of Information Flows | Shared | n/a | The information system separates information flows logically or physically using [Assignment: organization-defined mechanisms and/or techniques] to accomplish [Assignment: organization- defined required separations by types of information]. Supplemental Guidance: Enforcing the separation of information flows by type can enhance protection by ensuring that information is not commingled while in transit and by enabling flow control by transmission paths perhaps not otherwise achievable. Types of separable information include, for example, inbound and outbound communications traffic, service requests and responses, and information of differing security categories. | link | count: 004 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-4(8) | FedRAMP_High_R4_AC-4(8) | FedRAMP High AC-4 (8) | Access Control | Security Policy Filters | Shared | n/a | The information system enforces information flow control using [Assignment: organization-defined security policy filters] as a basis for flow control decisions for [Assignment: organization-defined information flows]. Supplemental Guidance: Organization-defined security policy filters can address data structures and content. For example, security policy filters for data structures can check for maximum file lengths, maximum field sizes, and data/file types (for structured and unstructured data). Security policy filters for data content can check for specific words (e.g., dirty/clean word filters), enumerated values or data value ranges, and hidden content. Structured data permits the interpretation of data content by applications. Unstructured data typically refers to digital information without a particular data structure or with a data structure that does not facilitate the development of rule sets to address the particular sensitivity of the information conveyed by the data or the associated flow enforcement decisions. Unstructured data consists of: (i) bitmap objects that are inherently non language-based (i.e., image, video, or audio files); and (ii) textual objects that are based on written or printed languages (e.g., commercial off-the- shelf word processing documents, spreadsheets, or emails). Organizations can implement more than one security policy filter to meet information flow control objectives (e.g., employing clean word lists in conjunction with dirty word lists may help to reduce false positives). | link | count: 001 Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-5 | FedRAMP_High_R4_AC-5 | FedRAMP High AC-5 | Access Control | Separation Of Duties | Shared | n/a | The organization: a. Separates [Assignment: organization-defined duties of individuals]; b. Documents separation of duties of individuals; and c. Defines information system access authorizations to support separation of duties. Supplemental Guidance: Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes, for example: (i) dividing mission functions and information system support functions among different individuals and/or roles; (ii) conducting information system support functions with different individuals (e.g., system management, programming, configuration management, quality assurance and testing, and network security); and (iii) ensuring security personnel administering access control functions do not also administer audit functions. Related controls: AC-3, AC-6, PE-3, PE-4, PS-2. Control Enhancements: None. References: None. | link | count: 004 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-6 | FedRAMP_High_R4_AC-6 | FedRAMP High AC-6 | Access Control | Least Privilege | Shared | n/a | The organization employs the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions. Supplemental Guidance: Organizations employ least privilege for specific duties and information systems. The principle of least privilege is also applied to information system processes, ensuring that the processes operate at privilege levels no higher than necessary to accomplish required organizational missions/business functions. Organizations consider the creation of additional processes, roles, and information system accounts as necessary, to achieve least privilege. Organizations also apply least privilege to the development, implementation, and operation of organizational information systems. Related controls: AC-2, AC-3, AC-5, CM-6, CM-7, PL-2. References: None. | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f) |
General, Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-6(1) | FedRAMP_High_R4_AC-6(1) | FedRAMP High AC-6 (1) | Access Control | Authorize Access To Security Functions | Shared | n/a | The organization explicitly authorizes access to [Assignment: organization-defined security functions (deployed in hardware, software, and firmware) and security-relevant information]. Supplemental Guidance: Security functions include, for example, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Security-relevant information includes, for example, filtering rules for routers/firewalls, cryptographic key management information, configuration parameters for security services, and access control lists. Explicitly authorized personnel include, for example, security administrators, system and network administrators, system security officers, system maintenance personnel, system programmers, and other privileged users. Related controls: AC-17, AC-18, AC-19. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-6(5) | FedRAMP_High_R4_AC-6(5) | FedRAMP High AC-6 (5) | Access Control | Privileged Accounts | Shared | n/a | The organization restricts privileged accounts on the information system to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from having access to privileged information/functions. Organizations may differentiate in the application of this control enhancement between allowed privileges for local accounts and for domain accounts provided organizations retain the ability to control information system configurations for key security parameters and as otherwise necessary to sufficiently mitigate risk. Related control: CM-6. | link | count: 001 Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-6(7) | FedRAMP_High_R4_AC-6(7) | FedRAMP High AC-6 (7) | Access Control | Review Of User Privileges | Shared | n/a | The organization: (a) Reviews [Assignment: organization-defined frequency] the privileges assigned to [Assignment: organization-defined roles or classes of users] to validate the need for such privileges; and (b) Reassigns or removes privileges, if necessary, to correctly reflect organizational mission/business needs. Supplemental Guidance: The need for certain assigned user privileges may change over time reflecting changes in organizational missions/business function, environments of operation, technologies, or threat. Periodic review of assigned user privileges is necessary to determine if the rationale for assigning such privileges remains valid. If the need cannot be revalidated, organizations take appropriate corrective actions. Related control: CA-7. | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
General, Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-6(8) | FedRAMP_High_R4_AC-6(8) | FedRAMP High AC-6 (8) | Access Control | Privilege Levels For Code Execution | Shared | n/a | The information system prevents [Assignment: organization-defined software] from executing at higher privilege levels than users executing the software. Supplemental Guidance: In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. | link | count: 001 Enforce software execution privileges (68d2e478-3b19-23eb-1357-31b296547457) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-6(9) | FedRAMP_High_R4_AC-6(9) | FedRAMP High AC-6 (9) | Access Control | Auditing Use Of Privileged Functions | Shared | n/a | The information system audits the execution of privileged functions. Supplemental Guidance: Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat (APT). Related control: AU-2. | link | count: 006 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AC-7 | FedRAMP_High_R4_AC-7 | FedRAMP High AC-7 | Access Control | Unsuccessful Logon Attempts | Shared | n/a | The information system: a. Enforces a limit of [Assignment: organization-defined number] consecutive invalid logon attempts by a user during a [Assignment: organization-defined time period]; and b. Automatically [Selection: locks the account/node for an [Assignment: organization-defined time period]; locks the account/node until released by an administrator; delays next logon prompt according to [Assignment: organization-defined delay algorithm]] when the maximum number of unsuccessful attempts is exceeded. Supplemental Guidance: This control applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by information systems are usually temporary and automatically release after a predetermined time period established by organizations. If a delay algorithm is selected, organizations may choose to employ different algorithms for different information system components based on the capabilities of those components. Responses to unsuccessful logon attempts may be implemented at both the operating system and the application levels. Related controls: AC-2, AC-9, AC-14, IA-5. References: None. | link | count: 001 Enforce a limit of consecutive failed login attempts (b4409bff-2287-8407-05fd-c73175a68302) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AT-1 | FedRAMP_High_R4_AT-1 | FedRAMP High AT-1 | Awareness And Training | Security Awareness And Training Policy Andprocedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A security awareness and training policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the security awareness and training policy and associated security awareness and training controls; and b. Reviews and updates the current: 1. Security awareness and training policy [Assignment: organization-defined frequency]; and 2. Security awareness and training procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AT family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-16, 800-50, 800-100. | link | count: 002 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AT-2 | FedRAMP_High_R4_AT-2 | FedRAMP High AT-2 | Awareness And Training | Security Awareness Training | Shared | n/a | The organization provides basic security awareness training to information system users (including managers, senior executives, and contractors): a. As part of initial training for new users; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Organizations determine the appropriate content of security awareness training and security awareness techniques based on the specific organizational requirements and the information systems to which personnel have authorized access. The content includes a basic understanding of the need for information security and user actions to maintain security and to respond to suspected security incidents. The content also addresses awareness of the need for operations security. Security awareness techniques can include, for example, displaying posters, offering supplies inscribed with security reminders, generating email advisories/notices from senior organizational officials, displaying logon screen messages, and conducting information security awareness events. Related controls: AT-3, AT-4, PL-4. References: C.F.R. Part 5 Subpart C (5 C.F.R. 930.301); Executive Order 13587; NIST Special Publication 800-50. | link | count: 003 Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AT-2(2) | FedRAMP_High_R4_AT-2(2) | FedRAMP High AT-2 (2) | Awareness And Training | Insider Threat | Shared | n/a | The organization includes security awareness training on recognizing and reporting potential indicators of insider threat. Supplemental Guidance: Potential indicators and possible precursors of insider threat can include behaviors such as inordinate, long-term job dissatisfaction, attempts to gain access to information not required for job performance, unexplained access to financial resources, bullying or sexual harassment of fellow employees, workplace violence, and other serious violations of organizational policies, procedures, directives, rules, or practices. Security awareness training includes how to communicate employee and management concerns regarding potential indicators of insider threat through appropriate organizational channels in accordance with established organizational policies and procedures. Related controls: PL-4, PM-12, PS-3, PS-6. References: C.F.R. Part 5 Subpart C (5 C.F.R 930.301); Executive Order 13587; NIST Special Publication 800-50. | link | count: 001 Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AT-3 | FedRAMP_High_R4_AT-3 | FedRAMP High AT-3 | Awareness And Training | Role-Based Security Training | Shared | n/a | The organization provides role-based security training to personnel with assigned security roles and responsibilities: a. Before authorizing access to the information system or performing assigned duties; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Organizations determine the appropriate content of security training based on the assigned roles and responsibilities of individuals and the specific security requirements of organizations and the information systems to which personnel have authorized access. In addition, organizations provide enterprise architects, information system developers, software developers, acquisition/procurement officials, information system managers, system/network administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation activities, security control assessors, and other personnel having access to system-level software, adequate security-related technical training specifically tailored for their assigned duties. Comprehensive role-based training addresses management, operational, and technical roles and responsibilities covering physical, personnel, and technical safeguards and countermeasures. Such training can include for example, policies, procedures, tools, and artifacts for the organizational security roles defined. Organizations also provide the training necessary for individuals to carry out their responsibilities related to operations and supply chain security within the context of organizational information security programs. Role-based security training also applies to contractors providing services to federal agencies. Related controls: AT-2, AT-4, PL-4, PS-7, SA-3, SA-12, SA-16. References: C.F.R. Part 5 Subpart C (5 C.F.R. 930.301); NIST Special Publications 800-16, 800-50. | link | count: 003 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AT-3(3) | FedRAMP_High_R4_AT-3(3) | FedRAMP High AT-3 (3) | Awareness And Training | Practical Exercises | Shared | n/a | The organization includes practical exercises in security training that reinforce training objectives. Supplemental Guidance: Practical exercises may include, for example, security training for software developers that includes simulated cyber attacks exploiting common software vulnerabilities (e.g., buffer overflows), or spear/whale phishing attacks targeted at senior leaders/executives. These types of practical exercises help developers better understand the effects of such vulnerabilities and appreciate the need for security coding standards and processes. | link | count: 001 Provide role-based practical exercises (d041726f-00e0-41ca-368c-b1a122066482) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AT-3(4) | FedRAMP_High_R4_AT-3(4) | FedRAMP High AT-3 (4) | Awareness And Training | Suspicious Communications And Anomalous System Behavior | Shared | n/a | The organization provides training to its personnel on [Assignment: organization-defined indicators of malicious code] to recognize suspicious communications and anomalous behavior in organizational information systems. Supplemental Guidance: A well-trained workforce provides another organizational safeguard that can be employed as part of a defense-in-depth strategy to protect organizations against malicious code coming in to organizations via email or the web applications. Personnel are trained to look for indications of potentially suspicious email (e.g., receiving an unexpected email, receiving an email containing strange or poor grammar, or receiving an email from an unfamiliar sender but who appears to be from a known sponsor or contractor). Personnel are also trained on how to respond to such suspicious email or web communications (e.g., not opening attachments, not clicking on embedded web links, and checking the source of email addresses). For this process to work effectively, all organizational personnel are trained and made aware of what constitutes suspicious communications. Training personnel on how to recognize anomalous behaviors in organizational information systems can potentially provide early warning for the presence of malicious code. Recognition of such anomalous behavior by organizational personnel can supplement automated malicious code detection and protection tools and systems employed by organizations. | link | count: 001 Provide role-based training on suspicious activities (f6794ab8-9a7d-3b24-76ab-265d3646232b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AT-4 | FedRAMP_High_R4_AT-4 | FedRAMP High AT-4 | Awareness And Training | Security Training Records | Shared | n/a | The organization: a. Documents and monitors individual information system security training activities including basic security awareness training and specific information system security training; and b. Retains individual training records for [Assignment: organization-defined time period]. Supplemental Guidance: Documentation for specialized training may be maintained by individual supervisors at the option of the organization. Related controls: AT-2, AT-3, PM-14. Control Enhancements: None. References: None. | link | count: 003 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a), Retain training records (3153d9c0-2584-14d3-362d-578b01358aeb) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-1 | FedRAMP_High_R4_AU-1 | FedRAMP High AU-1 | Audit And Accountability | Audit And Accountability Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls; and b. Reviews and updates the current: 1. Audit and accountability policy [Assignment: organization-defined frequency]; and 2. Audit and accountability procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AU family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 004 Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-10 | FedRAMP_High_R4_AU-10 | FedRAMP High AU-10 | Audit And Accountability | Non-Repudiation | Shared | n/a | The information system protects against an individual (or process acting on behalf of an individual) falsely denying having performed [Assignment: organization-defined actions to be covered by non-repudiation]. Supplemental Guidance: Types of individual actions covered by non-repudiation include, for example, creating information, sending and receiving messages, approving information (e.g., indicating concurrence or signing a contract). Non-repudiation protects individuals against later claims by: (i) authors of not having authored particular documents; (ii) senders of not having transmitted messages; (iii) receivers of not having received messages; or (iv) signatories of not having signed documents. Non-repudiation services can be used to determine if information originated from a particular individual, or if an individual took specific actions (e.g., sending an email, signing a contract, approving a procurement request) or received specific information. Organizations obtain non-repudiation services by employing various techniques or mechanisms (e.g., digital signatures, digital message receipts). Related controls: SC-12, SC-8, SC-13, SC-16, SC-17, SC-23. References: None. | link | count: 001 Establish electronic signature and certificate requirements (6f3866e8-6e12-69cf-788c-809d426094a1) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-11 | FedRAMP_High_R4_AU-11 | FedRAMP High AU-11 | Audit And Accountability | Audit Record Retention | Shared | n/a | The organization retains audit records for [Assignment: organization-defined time period consistent with records retention policy] to provide support for after-the-fact investigations of security incidents and to meet regulatory and organizational information retention requirements. Supplemental Guidance: Organizations retain audit records until it is determined that they are no longer needed for administrative, legal, audit, or other operational purposes. This includes, for example, retention and availability of audit records relative to Freedom of Information Act (FOIA) requests, subpoenas, and law enforcement actions. Organizations develop standard categories of audit records relative to such types of actions and standard response processes for each type of action. The National Archives and Records Administration (NARA) General Records Schedules provide federal policy on record retention. Related controls: AU-4, AU-5, AU-9, MP-6. References: None. | link | count: 004 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
Regulatory Compliance, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-12 | FedRAMP_High_R4_AU-12 | FedRAMP High AU-12 | Audit And Accountability | Audit Generation | Shared | n/a | The information system: a. Provides audit record generation capability for the auditable events defined in AU-2 a. at [Assignment: organization-defined information system components]; b. Allows [Assignment: organization-defined personnel or roles] to select which auditable events are to be audited by specific components of the information system; and c. Generates audit records for the events defined in AU-2 d. with the content defined in AU-3. Supplemental Guidance: Audit records can be generated from many different information system components. The list of audited events is the set of events for which audits are to be generated. These events are typically a subset of all events for which the information system is capable of generating audit records. Related controls: AC-3, AU-2, AU-3, AU-6, AU-7. References: None. | link | count: 037 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-12(1) | FedRAMP_High_R4_AU-12(1) | FedRAMP High AU-12 (1) | Audit And Accountability | System-Wide / Time-Correlated Audit Trail | Shared | n/a | The information system compiles audit records from [Assignment: organization-defined information system components] into a system-wide (logical or physical) audit trail that is time- correlated to within [Assignment: organization-defined level of tolerance for relationship between time stamps of individual records in the audit trail]. Supplemental Guidance: Audit trails are time-correlated if the time stamps in the individual audit records can be reliably related to the time stamps in other audit records to achieve a time ordering of the records within organizational tolerances. Related controls: AU-8, AU-12. | link | count: 034 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Compile Audit records into system wide audit (214ea241-010d-8926-44cc-b90a96d52adc), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-12(3) | FedRAMP_High_R4_AU-12(3) | FedRAMP High AU-12 (3) | Audit And Accountability | Changes By Authorized Individuals | Shared | n/a | The information system provides the capability for [Assignment: organization-defined individuals or roles] to change the auditing to be performed on [Assignment: organization-defined information system components] based on [Assignment: organization-defined selectable event criteria] within [Assignment: organization-defined time thresholds]. Supplemental Guidance: This control enhancement enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve information system resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting. Organizations can establish time thresholds in which audit actions are changed, for example, near real-time, within minutes, or within hours. Related control: AU-7. | link | count: 001 Provide the capability to extend or limit auditing on customer-deployed resources (d200f199-69f4-95a6-90b0-37ff0cf1040c) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-2 | FedRAMP_High_R4_AU-2 | FedRAMP High AU-2 | Audit And Accountability | Audit Events | Shared | n/a | The organization: a. Determines that the information system is capable of auditing the following events: [Assignment: organization-defined auditable events]; b. Coordinates the security audit function with other organizational entities requiring audit- related information to enhance mutual support and to help guide the selection of auditable events; c. Provides a rationale for why the auditable events are deemed to be adequate to support after- the-fact investigations of security incidents; and d. Determines that the following events are to be audited within the information system: [Assignment: organization-defined audited events (the subset of the auditable events defined in AU-2 a.) along with the frequency of (or situation requiring) auditing for each identified event]. Supplemental Guidance: An event is any observable occurrence in an organizational information system. Organizations identify audit events as those events which are significant and relevant to the security of information systems and the environments in which those systems operate in order to meet specific and ongoing audit needs. Audit events can include, for example, password changes, failed logons, or failed accesses related to information systems, administrative privilege usage, PIV credential usage, or third-party credential usage. In determining the set of auditable events, organizations consider the auditing appropriate for each of the security controls to be implemented. To balance auditing requirements with other information system needs, this control also requires identifying that subset of auditable events that are audited at a given point in time. For example, organizations may determine that information systems must have the capability to log every file access both successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. Auditing requirements, including the need for auditable events, may be referenced in other security controls and control enhancements. Organizations also include auditable events that are required by applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit capability and can facilitate the identification of root causes to problems. Organizations consider in the definition of auditable events, the auditing necessary to cover related events such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across multiple organizations) and actions that occur in service-oriented architectures. Related controls: AC-6, AC-17, AU-3, AU-12, MA-4, MP-2, MP-4, SI-4. References: NIST Special Publication 800-92; Web: http://idmanagement.gov. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-2(3) | FedRAMP_High_R4_AU-2(3) | FedRAMP High AU-2 (3) | Audit And Accountability | Reviews And Updates | Shared | n/a | The organization reviews and updates the audited events [Assignment: organization-defined frequency]. Supplemental Guidance: Over time, the events that organizations believe should be audited may change. Reviewing and updating the set of audited events periodically is necessary to ensure that the current set is still necessary and sufficient. | link | count: 001 Review and update the events defined in AU-02 (a930f477-9dcb-2113-8aa7-45bb6fc90861) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-3 | FedRAMP_High_R4_AU-3 | FedRAMP High AU-3 | Audit And Accountability | Content Of Audit Records | Shared | n/a | The information system generates audit records containing information that establishes what type of event occurred, when the event occurred, where the event occurred, the source of the event, the outcome of the event, and the identity of any individuals or subjects associated with the event. Supplemental Guidance: Audit record content that may be necessary to satisfy the requirement of this control, includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred). Related controls: AU-2, AU-8, AU-12, SI-11. References: None. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-3(1) | FedRAMP_High_R4_AU-3(1) | FedRAMP High AU-3 (1) | Audit And Accountability | Additional Audit Information | Shared | n/a | The information system generates audit records containing the following additional information: [Assignment: organization-defined additional, more detailed information]. Supplemental Guidance: Detailed information that organizations may consider in audit records includes, for example, full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. | link | count: 001 Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-4 | FedRAMP_High_R4_AU-4 | FedRAMP High AU-4 | Audit And Accountability | Audit Storage Capacity | Shared | n/a | The organization allocates audit record storage capacity in accordance with [Assignment: organization-defined audit record storage requirements]. Supplemental Guidance: Organizations consider the types of auditing to be performed and the audit processing requirements when allocating audit storage capacity. Allocating sufficient audit storage capacity reduces the likelihood of such capacity being exceeded and resulting in the potential loss or reduction of auditing capability. Related controls: AU-2, AU-5, AU-6, AU-7, AU-11, SI-4. References: None. | link | count: 001 Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-5 | FedRAMP_High_R4_AU-5 | FedRAMP High AU-5 | Audit And Accountability | Response To Audit Processing Failures | Shared | n/a | The information system: a. Alerts [Assignment: organization-defined personnel or roles] in the event of an audit processing failure; and b. Takes the following additional actions: [Assignment: organization-defined actions to be taken (e.g., shut down information system, overwrite oldest audit records, stop generating audit records)]. Supplemental Guidance: Audit processing failures include, for example, software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. Organizations may choose to define additional actions for different audit processing failures (e.g., by type, by location, by severity, or a combination of such factors). This control applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the total audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both. Related controls: AU-4, SI-12. References: None. | link | count: 001 Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-5(2) | FedRAMP_High_R4_AU-5(2) | FedRAMP High AU-5 (2) | Audit And Accountability | Real-Time Alerts | Shared | n/a | The information system provides an alert in [Assignment: organization-defined real-time period] to [Assignment: organization-defined personnel, roles, and/or locations] when the following audit failure events occur: [Assignment: organization-defined audit failure events requiring real-time alerts]. Supplemental Guidance: Alerts provide organizations with urgent messages. Real-time alerts provide these messages at information technology speed (i.e., the time from event detection to alert occurs in seconds or less). | link | count: 001 Provide real-time alerts for audit event failures (0f4fa857-079d-9d3d-5c49-21f616189e03) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-6 | FedRAMP_High_R4_AU-6 | FedRAMP High AU-6 | Audit And Accountability | Audit Review, Analysis, And Reporting | Shared | n/a | The organization: a. Reviews and analyzes information system audit records [Assignment: organization-defined frequency] for indications of [Assignment: organization-defined inappropriate or unusual activity]; and b. Reports findings to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Audit review, analysis, and reporting covers information security-related auditing performed by organizations including, for example, auditing that results from monitoring of account usage, remote access, wireless connectivity, mobile device connection, configuration settings, system component inventory, use of maintenance tools and nonlocal maintenance, physical access, temperature and humidity, equipment delivery and removal, communications at the information system boundaries, use of mobile code, and use of VoIP. Findings can be reported to organizational entities that include, for example, incident response team, help desk, information security group/department. If organizations are prohibited from reviewing and analyzing audit information or unable to conduct such activities (e.g., in certain national security applications or systems), the review/analysis may be carried out by other organizations granted such authority. Related controls: AC-2, AC-3, AC-6, AC-17, AT-3, AU-7, AU-16, CA-7, CM-5, CM-10, CM-11, IA-3, IA-5, IR-5, IR-6, MA-4, MP-4, PE-3, PE-6, PE-14, PE-16, RA-5, SC-7, SC-18, SC-19, SI-3, SI-4, SI-7. References: None. | link | count: 025 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-6(1) | FedRAMP_High_R4_AU-6(1) | FedRAMP High AU-6 (1) | Audit And Accountability | Process Integration | Shared | n/a | The organization employs automated mechanisms to integrate audit review, analysis, and reporting processes to support organizational processes for investigation and response to suspicious activities. Supplemental Guidance: Organizational processes benefiting from integrated audit review, analysis, and reporting include, for example, incident response, continuous monitoring, contingency planning, and Inspector General audits. Related controls: AU-12, PM-7. | link | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-6(10) | FedRAMP_High_R4_AU-6(10) | FedRAMP High AU-6 (10) | Audit And Accountability | Audit Level Adjustment | Shared | n/a | The organization adjusts the level of audit review, analysis, and reporting within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information. Supplemental Guidance: The frequency, scope, and/or depth of the audit review, analysis, and reporting may be adjusted to meet organizational needs based on new information received. | link | count: 001 Adjust level of audit review, analysis, and reporting (de251b09-4a5e-1204-4bef-62ac58d47999) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-6(3) | FedRAMP_High_R4_AU-6(3) | FedRAMP High AU-6 (3) | Audit And Accountability | Correlate Audit Repositories | Shared | n/a | The organization analyzes and correlates audit records across different repositories to gain organization-wide situational awareness. Supplemental Guidance: Organization-wide situational awareness includes awareness across all three tiers of risk management (i.e., organizational, mission/business process, and information system) and supports cross-organization awareness. Related controls: AU-12, IR-4. | link | count: 002 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-6(4) | FedRAMP_High_R4_AU-6(4) | FedRAMP High AU-6 (4) | Audit And Accountability | Central Review And Analysis | Shared | n/a | The information system provides the capability to centrally review and analyze audit records from multiple components within the system. Supplemental Guidance: Automated mechanisms for centralized reviews and analyses include, for example, Security Information Management products. Related controls: AU-2, AU-12. | link | count: 033 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Search, Security Center, Service Bus, SQL, Stream Analytics | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-6(5) | FedRAMP_High_R4_AU-6(5) | FedRAMP High AU-6 (5) | Audit And Accountability | Integration / Scanning And Monitoring Capabilities | Shared | n/a | The organization integrates analysis of audit records with analysis of [Selection (one or more): vulnerability scanning information; performance data; information system monitoring information; [Assignment: organization-defined data/information collected from other sources]] to further enhance the ability to identify inappropriate or unusual activity. Supplemental Guidance: This control enhancement does not require vulnerability scanning, the generation of performance data, or information system monitoring. Rather, the enhancement requires that the analysis of information being otherwise produced in these areas is integrated with the analysis of audit information. Security Event and Information Management System tools can facilitate audit record aggregation/consolidation from multiple information system components as well as audit record correlation and analysis. The use of standardized audit record analysis scripts developed by organizations (with localized script adjustments, as necessary) provides more cost-effective approaches for analyzing audit record information collected. The correlation of audit record information with vulnerability scanning information is important in determining the veracity of vulnerability scans and correlating attack detection events with scanning results. Correlation with performance data can help uncover denial of service attacks or cyber attacks resulting in unauthorized use of resources. Correlation with system monitoring information can assist in uncovering attacks and in better relating audit information to operational situations. Related controls: AU-12, IR-4, RA-5. | link | count: 034 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Integrate Audit record analysis (85335602-93f5-7730-830b-d43426fd51fa), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-6(7) | FedRAMP_High_R4_AU-6(7) | FedRAMP High AU-6 (7) | Audit And Accountability | Permitted Actions | Shared | n/a | The organization specifies the permitted actions for each [Selection (one or more): information system process; role; user] associated with the review, analysis, and reporting of audit information. Supplemental Guidance: Organizations specify permitted actions for information system processes, roles, and/or users associated with the review, analysis, and reporting of audit records through account management techniques. Specifying permitted actions on audit information is a way to enforce the principle of least privilege. Permitted actions are enforced by the information system and include, for example, read, write, execute, append, and delete. | link | count: 001 Specify permitted actions associated with customer audit information (3eecf628-a1c8-1b48-1b5c-7ca781e97970) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-7 | FedRAMP_High_R4_AU-7 | FedRAMP High AU-7 | Audit And Accountability | Audit Reduction And Report Generation | Shared | n/a | The information system provides an audit reduction and report generation capability that: a. Supports on-demand audit review, analysis, and reporting requirements and after-the-fact investigations of security incidents; and b. Does not alter the original content or time ordering of audit records. Supplemental Guidance: Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Audit reduction and report generation capabilities do not always emanate from the same information system or from the same organizational entities conducting auditing activities. Audit reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the information system can generate customizable reports. Time ordering of audit records can be a significant issue if the granularity of the timestamp in the record is insufficient. Related control: AU-6. References: None. | link | count: 002 Ensure audit records are not altered (27ce30dd-3d56-8b54-6144-e26d9a37a541), Provide audit review, analysis, and reporting capability (44f8a42d-739f-8030-89a8-4c2d5b3f6af3) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-7(1) | FedRAMP_High_R4_AU-7(1) | FedRAMP High AU-7 (1) | Audit And Accountability | Automatic Processing | Shared | n/a | The information system provides the capability to process audit records for events of interest based on [Assignment: organization-defined audit fields within audit records]. Supplemental Guidance: Events of interest can be identified by the content of specific audit record fields including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations may define audit event criteria to any degree of granularity required, for example, locations selectable by general networking location (e.g., by network or subnetwork) or selectable by specific information system component. Related controls: AU-2, AU-12. | link | count: 001 Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-8 | FedRAMP_High_R4_AU-8 | FedRAMP High AU-8 | Audit And Accountability | Time Stamps | Shared | n/a | The information system: a. Uses internal system clocks to generate time stamps for audit records; and b. Records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT) and meets [Assignment: organization-defined granularity of time measurement]. Supplemental Guidance: Time stamps generated by the information system include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Granularity of time measurements refers to the degree of synchronization between information system clocks and reference clocks, for example, clocks synchronizing within hundreds of milliseconds or within tens of milliseconds. Organizations may define different time granularities for different system components. Time service can also be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities. Related controls: AU-3, AU-12. References: None. | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-8(1) | FedRAMP_High_R4_AU-8(1) | FedRAMP High AU-8 (1) | Audit And Accountability | Synchronization With Authoritative Time Source | Shared | n/a | The information system: (a) Compares the internal information system clocks [Assignment: organization-defined frequency] with [Assignment: organization-defined authoritative time source]; and (b) Synchronizes the internal system clocks to the authoritative time source when the time difference is greater than [Assignment: organization-defined time period]. Supplemental Guidance: This control enhancement provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-9 | FedRAMP_High_R4_AU-9 | FedRAMP High AU-9 | Audit And Accountability | Protection Of Audit Information | Shared | n/a | The information system protects audit information and audit tools from unauthorized access, modification, and deletion. Supplemental Guidance: Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. This control focuses on technical protection of audit information. Physical protection of audit information is addressed by media protection controls and physical and environmental protection controls. Related controls: AC-3, AC-6, MP-2, MP-4, PE-2, PE-3, PE-6. References: None. | link | count: 002 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-9(2) | FedRAMP_High_R4_AU-9(2) | FedRAMP High AU-9 (2) | Audit And Accountability | Audit Backup On Separate Physical Systems / Components | Shared | n/a | The information system backs up audit records [Assignment: organization-defined frequency] onto a physically different system or system component than the system or component being audited. Supplemental Guidance: This control enhancement helps to ensure that a compromise of the information system being audited does not also result in a compromise of the audit records. Related controls: AU-4, AU-5, AU-11. | link | count: 001 Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-9(3) | FedRAMP_High_R4_AU-9(3) | FedRAMP High AU-9 (3) | Audit And Accountability | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to protect the integrity of audit information and audit tools. Supplemental Guidance: Cryptographic mechanisms used for protecting the integrity of audit information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. Related controls: AU-10, SC-12, SC-13. | link | count: 001 Maintain integrity of audit system (c0559109-6a27-a217-6821-5a6d44f92897) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | AU-9(4) | FedRAMP_High_R4_AU-9(4) | FedRAMP High AU-9 (4) | Audit And Accountability | Access By Subset Of Privileged Users | Shared | n/a | The organization authorizes access to management of audit functionality to only [Assignment: organization-defined subset of privileged users]. Supplemental Guidance: Individuals with privileged access to an information system and who are also the subject of an audit by that system, may affect the reliability of audit information by inhibiting audit activities or modifying audit records. This control enhancement requires that privileged access be further defined between audit-related privileges and other privileges, thus limiting the users with audit-related privileges. Related control: AC-5. | link | count: 001 Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-1 | FedRAMP_High_R4_CA-1 | FedRAMP High CA-1 | Security Assessment And Authorization | Security Assessment And Authorization Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A security assessment and authorization policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the security assessment and authorization policy and associated security assessment and authorization controls; and b. Reviews and updates the current: 1. Security assessment and authorization policy [Assignment: organization-defined frequency]; and 2. Security assessment and authorization procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-37, 800-53A, 800-100. | link | count: 001 Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-2 | FedRAMP_High_R4_CA-2 | FedRAMP High CA-2 | Security Assessment And Authorization | Security Assessments | Shared | n/a | The organization: a. Develops a security assessment plan that describes the scope of the assessment including: 1. Security controls and control enhancements under assessment; 2. Assessment procedures to be used to determine security control effectiveness; and 3. Assessment environment, assessment team, and assessment roles and responsibilities; b. Assesses the security controls in the information system and its environment of operation [Assignment: organization-defined frequency] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security requirements; c. Produces a security assessment report that documents the results of the assessment; and d. Provides the results of the security control assessment to [Assignment: organization-defined individuals or roles]. Supplemental Guidance: Organizations assess security controls in organizational information systems and the environments in which those systems operate as part of: (i) initial and ongoing security authorizations; (ii) FISMA annual assessments; (iii) continuous monitoring; and (iv) system development life cycle activities. Security assessments: (i) ensure that information security is built into organizational information systems; (ii) identify weaknesses and deficiencies early in the development process; (iii) provide essential information needed to make risk-based decisions as part of security authorization processes; and (iv) ensure compliance to vulnerability mitigation procedures. Assessments are conducted on the implemented security controls from Appendix F (main catalog) and Appendix G (Program Management controls) as documented in System Security Plans and Information Security Program Plans. Organizations can use other types of assessment activities such as vulnerability scanning and system monitoring to maintain the security posture of information systems during the entire life cycle. Security assessment reports document assessment results in sufficient detail as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the security controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting security requirements. The FISMA requirement for assessing security controls at least annually does not require additional assessment activities to those activities already in place in organizational security authorization processes. Security assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. For example, assessments conducted in support of security authorization decisions are provided to authorizing officials or authorizing official designated representatives. To satisfy annual assessment requirements, organizations can use assessment results from the following sources: (i) initial or ongoing information system authorizations; (ii) continuous monitoring; or (iii) system development life cycle activities. Organizations ensure that security assessment results are current, relevant to the determination of security control effectiveness, and obtained with the appropriate level of assessor independence. Existing security control assessment results can be reused to the extent that the results are still valid and can also be supplemented with additional assessments as needed. Subsequent to initial authorizations and in accordance with OMB policy, organizations assess security controls during continuous monitoring. Organizations establish the frequency for ongoing security control assessments in accordance with organizational continuous monitoring strategies. Information Assurance Vulnerability Alerts provide useful examples of vulnerability mitigation procedures. External audits (e.g., audits by external entities such as regulatory agencies) are outside the scope of this control. Related controls: CA-5, CA-6, CA-7, PM-9, RA-5, SA-11, SA-12, SI-4. References: Executive Order 13587; FIPS Publication 199; NIST Special Publications 800-37, 800-39, 800-53A, 800-115, 800-137. | link | count: 004 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-2(1) | FedRAMP_High_R4_CA-2(1) | FedRAMP High CA-2 (1) | Security Assessment And Authorization | Independent Assessors | Shared | n/a | The organization employs assessors or assessment teams with [Assignment: organization-defined level of independence] to conduct security control assessments. Supplemental Guidance: Independent assessors or assessment teams are individuals or groups who conduct impartial assessments of organizational information systems. Impartiality implies that assessors are free from any perceived or actual conflicts of interest with regard to the development, operation, or management of the organizational information systems under assessment or to the determination of security control effectiveness. To achieve impartiality, assessors should not: (i) create a mutual or conflicting interest with the organizations where the assessments are being conducted; (ii) assess their own work; (iii) act as management or employees of the organizations they are serving; or (iv) place themselves in positions of advocacy for the organizations acquiring their services. Independent assessments can be obtained from elements within organizations or can be contracted to public or private sector entities outside of organizations. Authorizing officials determine the required level of independence based on the security categories of information systems and/or the ultimate risk to organizational operations, organizational assets, or individuals. Authorizing officials also determine if the level of assessor independence provides sufficient assurance that the results are sound and can be used to make credible, risk-based decisions. This includes determining whether contracted security assessment services have sufficient independence, for example, when information system owners are not directly involved in contracting processes or cannot unduly influence the impartiality of assessors conducting assessments. In special situations, for example, when organizations that own the information systems are small or organizational structures require that assessments are conducted by individuals that are in the developmental, operational, or management chain of system owners, independence in assessment processes can be achieved by ensuring that assessment results are carefully reviewed and analyzed by independent teams of experts to validate the completeness, accuracy, integrity, and reliability of the results. Organizations recognize that assessments performed for purposes other than direct support to authorization decisions are, when performed by assessors with sufficient independence, more likely to be useable for such decisions, thereby reducing the need to repeat assessments. | link | count: 001 Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-2(2) | FedRAMP_High_R4_CA-2(2) | FedRAMP High CA-2 (2) | Security Assessment And Authorization | Specialized Assessments | Shared | n/a | The organization includes as part of security control assessments, [Assignment: organization- defined frequency], [Selection: announced; unannounced], [Selection (one or more): in-depth monitoring; vulnerability scanning; malicious user testing; insider threat assessment; performance/load testing; [Assignment: organization-defined other forms of security assessment]]. Supplemental Guidance: Organizations can employ information system monitoring, insider threat assessments, malicious user testing, and other forms of testing (e.g., verification and validation) to improve readiness by exercising organizational capabilities and indicating current performance levels as a means of focusing actions to improve security. Organizations conduct assessment activities in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Authorizing officials approve the assessment methods in coordination with the organizational risk executive function. Organizations can incorporate vulnerabilities uncovered during assessments into vulnerability remediation processes. Related controls: PE-3, SI-2. | link | count: 001 Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-2(3) | FedRAMP_High_R4_CA-2(3) | FedRAMP High CA-2 (3) | Security Assessment And Authorization | External Organizations | Shared | n/a | The organization accepts the results of an assessment of [Assignment: organization-defined information system] performed by [Assignment: organization-defined external organization] when the assessment meets [Assignment: organization-defined requirements]. Supplemental Guidance: Organizations may often rely on assessments of specific information systems by other (external) organizations. Utilizing such existing assessments (i.e., reusing existing assessment evidence) can significantly decrease the time and resources required for organizational assessments by limiting the amount of independent assessment activities that organizations need to perform. The factors that organizations may consider in determining whether to accept assessment results from external organizations can vary. Determinations for accepting assessment results can be based on, for example, past assessment experiences one organization has had with another organization, the reputation that organizations have with regard to assessments, the level of detail of supporting assessment documentation provided, or mandates imposed upon organizations by federal legislation, policies, or directives. | link | count: 001 Accept assessment results (3054c74b-9b45-2581-56cf-053a1a716c39) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-3 | FedRAMP_High_R4_CA-3 | FedRAMP High CA-3 | Security Assessment And Authorization | System Interconnections | Shared | n/a | The organization: a. Authorizes connections from the information system to other information systems through the use of Interconnection Security Agreements; b. Documents, for each interconnection, the interface characteristics, security requirements, and the nature of the information communicated; and c. Reviews and updates Interconnection Security Agreements [Assignment: organization-defined frequency]. Supplemental Guidance: This control applies to dedicated connections between information systems (i.e., system interconnections) and does not apply to transitory, user-controlled connections such as email and website browsing. Organizations carefully consider the risks that may be introduced when information systems are connected to other systems with different security requirements and security controls, both within organizations and external to organizations. Authorizing officials determine the risk associated with information system connections and the appropriate controls employed. If interconnecting systems have the same authorizing official, organizations do not need to develop Interconnection Security Agreements. Instead, organizations can describe the interface characteristics between those interconnecting systems in their respective security plans. If interconnecting systems have different authorizing officials within the same organization, organizations can either develop Interconnection Security Agreements or describe the interface characteristics between systems in the security plans for the respective systems. Organizations may also incorporate Interconnection Security Agreement information into formal contracts, especially for interconnections established between federal agencies and nonfederal (i.e., private sector) organizations. Risk considerations also include information systems sharing the same networks. For certain technologies (e.g., space, unmanned aerial vehicles, and medical devices), there may be specialized connections in place during preoperational testing. Such connections may require Interconnection Security Agreements and be subject to additional security controls. Related controls: AC-3, AC-4, AC-20, AU-2, AU-12, AU-16, CA-7, IA-3, SA-9, SC-7, SI-4. References: FIPS Publication 199; NIST Special Publication 800-47. | link | count: 002 Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-3(3) | FedRAMP_High_R4_CA-3(3) | FedRAMP High CA-3 (3) | Security Assessment And Authorization | Unclassified Non-National Security System Connections | Shared | n/a | The organization prohibits the direct connection of an [Assignment: organization-defined unclassified, non-national security system] to an external network without the use of [Assignment; organization-defined boundary protection device]. Supplemental Guidance: Organizations typically do not have control over external networks (e.g., the Internet). Approved boundary protection devices (e.g., routers, firewalls) mediate communications (i.e., information flows) between unclassified non-national security systems and external networks. This control enhancement is required for organizations processing, storing, or transmitting Controlled Unclassified Information (CUI). | link | count: 001 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-3(5) | FedRAMP_High_R4_CA-3(5) | FedRAMP High CA-3 (5) | Security Assessment And Authorization | Restrictions On External System Connections | Shared | n/a | The organization employs [Selection: allow-all, deny-by-exception; deny-all, permit-by-exception] policy for allowing [Assignment: organization-defined information systems] to connect to external information systems. Supplemental Guidance: Organizations can constrain information system connectivity to external domains (e.g., websites) by employing one of two policies with regard to such connectivity: (i) allow-all, deny by exception, also known as blacklisting (the weaker of the two policies); or (ii) deny-all, allow by exception, also known as whitelisting (the stronger of the two policies). For either policy, organizations determine what exceptions, if any, are acceptable. Related control: CM-7. | link | count: 001 Employ restrictions on external system interconnections (80029bc5-834f-3a9c-a2d8-acbc1aab4e9f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-5 | FedRAMP_High_R4_CA-5 | FedRAMP High CA-5 | Security Assessment And Authorization | Plan Of Action And Milestones | Shared | n/a | The organization: a. Develops a plan of action and milestones for the information system to document the organization’s planned remedial actions to correct weaknesses or deficiencies noted during the assessment of the security controls and to reduce or eliminate known vulnerabilities in the system; and b. Updates existing plan of action and milestones [Assignment: organization-defined frequency] based on the findings from security controls assessments, security impact analyses, and continuous monitoring activities. Supplemental Guidance: Plans of action and milestones are key documents in security authorization packages and are subject to federal reporting requirements established by OMB. Related controls: CA-2, CA-7, CM-4, PM-4. References: OMB Memorandum 02-01; NIST Special Publication 800-37. | link | count: 002 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-6 | FedRAMP_High_R4_CA-6 | FedRAMP High CA-6 | Security Assessment And Authorization | Security Authorization | Shared | n/a | The organization: a. Assigns a senior-level executive or manager as the authorizing official for the information system; b. Ensures that the authorizing official authorizes the information system for processing before commencing operations; and c. Updates the security authorization [Assignment: organization-defined frequency]. Supplemental Guidance: Security authorizations are official management decisions, conveyed through authorization decision documents, by senior organizational officials or executives (i.e., authorizing officials) to authorize operation of information systems and to explicitly accept the risk to organizational operations and assets, individuals, other organizations, and the Nation based on the implementation of agreed-upon security controls. Authorizing officials provide budgetary oversight for organizational information systems or assume responsibility for the mission/business operations supported by those systems. The security authorization process is an inherently federal responsibility and therefore, authorizing officials must be federal employees. Through the security authorization process, authorizing officials assume responsibility and are accountable for security risks associated with the operation and use of organizational information systems. Accordingly, authorizing officials are in positions with levels of authority commensurate with understanding and accepting such information security-related risks. OMB policy requires that organizations conduct ongoing authorizations of information systems by implementing continuous monitoring programs. Continuous monitoring programs can satisfy three-year reauthorization requirements, so separate reauthorization processes are not necessary. Through the employment of comprehensive continuous monitoring processes, critical information contained in authorization packages (i.e., security plans, security assessment reports, and plans of action and milestones) is updated on an ongoing basis, providing authorizing officials and information system owners with an up-to-date status of the security state of organizational information systems and environments of operation. To reduce the administrative cost of security reauthorization, authorizing officials use the results of continuous monitoring processes to the maximum extent possible as the basis for rendering reauthorization decisions. Related controls: CA-2, CA-7, PM-9, PM-10. Control Enhancements: None. References: OMB Circular A-130; OMB Memorandum 11-33; NIST Special Publications 800-37, 800-137. | link | count: 003 Assign an authorizing official (AO) (e29a8f1b-149b-2fa3-969d-ebee1baa9472), Ensure resources are authorized (0716f0f5-4955-2ccb-8d5e-c6be14d57c0f), Update the security authorization (449ebb52-945b-36e5-3446-af6f33770f8f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-7 | FedRAMP_High_R4_CA-7 | FedRAMP High CA-7 | Security Assessment And Authorization | Continuous Monitoring | Shared | n/a | The organization develops a continuous monitoring strategy and implements a continuous monitoring program that includes: a. Establishment of [Assignment: organization-defined metrics] to be monitored; b. Establishment of [Assignment: organization-defined frequencies] for monitoring and [Assignment: organization-defined frequencies] for assessments supporting such monitoring; c. Ongoing security control assessments in accordance with the organizational continuous monitoring strategy; d. Ongoing security status monitoring of organization-defined metrics in accordance with the organizational continuous monitoring strategy; e. Correlation and analysis of security-related information generated by assessments and monitoring; f. Response actions to address results of the analysis of security-related information; and g. Reporting the security status of organization and the information system to [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency]. Supplemental Guidance: Continuous monitoring programs facilitate ongoing awareness of threats, vulnerabilities, and information security to support organizational risk management decisions. The terms continuous and ongoing imply that organizations assess/analyze security controls and information security-related risks at a frequency sufficient to support organizational risk-based decisions. The results of continuous monitoring programs generate appropriate risk response actions by organizations. Continuous monitoring programs also allow organizations to maintain the security authorizations of information systems and common controls over time in highly dynamic environments of operation with changing mission/business needs, threats, vulnerabilities, and technologies. Having access to security-related information on a continuing basis through reports/dashboards gives organizational officials the capability to make more effective and timely risk management decisions, including ongoing security authorization decisions. Automation supports more frequent updates to security authorization packages, hardware/software/firmware inventories, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Continuous monitoring activities are scaled in accordance with the security categories of information systems. Related controls: CA-2, CA-5, CA-6, CM-3, CM-4, PM-6, PM-9, RA-5, SA-11, SA-12, SI-2, SI-4. References: OMB Memorandum 11-33; NIST Special Publications 800-37, 800-39, 800-53A, 800-115, 800-137; US-CERT Technical Cyber Security Alerts; DoD Information Assurance Vulnerability Alerts. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-7(1) | FedRAMP_High_R4_CA-7(1) | FedRAMP High CA-7 (1) | Security Assessment And Authorization | Independent Assessment | Shared | n/a | The organization employs assessors or assessment teams with [Assignment: organization-defined level of independence] to monitor the security controls in the information system on an ongoing basis. Supplemental Guidance: Organizations can maximize the value of assessments of security controls during the continuous monitoring process by requiring that such assessments be conducted by assessors or assessment teams with appropriate levels of independence based on continuous monitoring strategies. Assessor independence provides a degree of impartiality to the monitoring process. To achieve such impartiality, assessors should not: (i) create a mutual or conflicting interest with the organizations where the assessments are being conducted; (ii) assess their own work; (iii) act as management or employees of the organizations they are serving; or (iv) place themselves in advocacy positions for the organizations acquiring their services. | link | count: 001 Employ independent assessors for continuous monitoring (3baee3fd-30f5-882c-018c-cc78703a0106) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-7(3) | FedRAMP_High_R4_CA-7(3) | FedRAMP High CA-7 (3) | Security Assessment And Authorization | Trend Analyses | Shared | n/a | The organization employs trend analyses to determine if security control implementations, the frequency of continuous monitoring activities, and/or the types of activities used in the continuous monitoring process need to be modified based on empirical data. Supplemental Guidance: Trend analyses can include, for example, examining recent threat information regarding the types of threat events that have occurred within the organization or across the federal government, success rates of certain types of cyber attacks, emerging vulnerabilities in information technologies, evolving social engineering techniques, results from multiple security control assessments, the effectiveness of configuration settings, and findings from Inspectors General or auditors. | link | count: 001 Analyse data obtained from continuous monitoring (6a379d74-903b-244a-4c44-838728bea6b0) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-8(1) | FedRAMP_High_R4_CA-8(1) | FedRAMP High CA-8 (1) | Security Assessment And Authorization | Independent Penetration Agent Or Team | Shared | n/a | The organization employs an independent penetration agent or penetration team to perform penetration testing on the information system or system components. Supplemental Guidance: Independent penetration agents or teams are individuals or groups who conduct impartial penetration testing of organizational information systems. Impartiality implies that penetration agents or teams are free from any perceived or actual conflicts of interest with regard to the development, operation, or management of the information systems that are the targets of the penetration testing. Supplemental guidance for CA-2 (1) provides additional information regarding independent assessments that can be applied to penetration testing. Related control: CA-2. | link | count: 001 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CA-9 | FedRAMP_High_R4_CA-9 | FedRAMP High CA-9 | Security Assessment And Authorization | Internal System Connections | Shared | n/a | The organization: a. Authorizes internal connections of [Assignment: organization-defined information system components or classes of components] to the information system; and b. Documents, for each internal connection, the interface characteristics, security requirements, and the nature of the information communicated. Supplemental Guidance: This control applies to connections between organizational information systems and (separate) constituent system components (i.e., intra-system connections) including, for example, system connections with mobile devices, notebook/desktop computers, printers, copiers, facsimile machines, scanners, sensors, and servers. Instead of authorizing each individual internal connection, organizations can authorize internal connections for a class of components with common characteristics and/or configurations, for example, all digital printers, scanners, and copiers with a specified processing, storage, and transmission capability or all smart phones with a specific baseline configuration. Related controls: AC-3, AC-4, AC-18, AC-19, AU-2, AU-12, CA-7, CM-2, IA-3, SC-7, SI-4. References: None. | link | count: 001 Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-1 | FedRAMP_High_R4_CM-1 | FedRAMP High CM-1 | Configuration Management | Configuration Management Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the configuration management policy and associated configuration management controls; and b. Reviews and updates the current: 1. Configuration management policy [Assignment: organization-defined frequency]; and 2. Configuration management procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CM family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-10 | FedRAMP_High_R4_CM-10 | FedRAMP High CM-10 | Configuration Management | Software Usage Restrictions | Shared | n/a | The organization: a. Uses software and associated documentation in accordance with contract agreements and copyright laws; b. Tracks the use of software and associated documentation protected by quantity licenses to control copying and distribution; and c. Controls and documents the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work. Supplemental Guidance: Software license tracking can be accomplished by manual methods (e.g., simple spreadsheets) or automated methods (e.g., specialized tracking applications) depending on organizational needs. Related controls: AC-17, CM-8, SC-7. References: None. | link | count: 004 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Require compliance with intellectual property rights (725164e5-3b21-1ec2-7e42-14f077862841), Track software license usage (77cc89bb-774f-48d7-8a84-fb8c322c3000) |
Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-10(1) | FedRAMP_High_R4_CM-10(1) | FedRAMP High CM-10 (1) | Configuration Management | Open Source Software | Shared | n/a | The organization establishes the following restrictions on the use of open source software: [Assignment: organization-defined restrictions]. Supplemental Guidance: Open source software refers to software that is available in source code form. Certain software rights normally reserved for copyright holders are routinely provided under software license agreements that permit individuals to study, change, and improve the software. From a security perspective, the major advantage of open source software is that it provides organizations with the ability to examine the source code. However, there are also various licensing issues associated with open source software including, for example, the constraints on derivative use of such software. | link | count: 001 Restrict use of open source software (08c11b48-8745-034d-1c1b-a144feec73b9) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-11 | FedRAMP_High_R4_CM-11 | FedRAMP High CM-11 | Configuration Management | User-Installed Software | Shared | n/a | The organization: a. Establishes [Assignment: organization-defined policies] governing the installation of software by users; b. Enforces software installation policies through [Assignment: organization-defined methods]; and c. Monitors policy compliance at [Assignment: organization-defined frequency]. Supplemental Guidance: If provided the necessary privileges, users have the ability to install software in organizational information systems. To maintain control over the types of software installed, organizations identify permitted and prohibited actions regarding software installation. Permitted software installations may include, for example, updates and security patches to existing software and downloading applications from organization-approved “app stores.” Prohibited software installations may include, for example, software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods (e.g., periodic examination of user accounts), automated methods (e.g., configuration settings implemented on organizational information systems), or both. Related controls: AC-3, CM-2, CM-3, CM-5, CM-6, CM-7, PL-4. References: None. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-2 | FedRAMP_High_R4_CM-2 | FedRAMP High CM-2 | Configuration Management | Baseline Configuration | Shared | n/a | The organization develops, documents, and maintains under configuration control, a current baseline configuration of the information system. Supplemental Guidance: This control establishes baseline configurations for information systems and system components including communications and connectivity-related aspects of systems. Baseline configurations are documented, formally reviewed and agreed-upon sets of specifications for information systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, and/or changes to information systems. Baseline configurations include information about information system components (e.g., standard software packages installed on workstations, notebook computers, servers, network components, or mobile devices; current version numbers and patch information on operating systems and applications; and configuration settings/parameters), network topology, and the logical placement of those components within the system architecture. Maintaining baseline configurations requires creating new baselines as organizational information systems change over time. Baseline configurations of information systems reflect the current enterprise architecture. Related controls: CM-3, CM-6, CM-8, CM-9, SA-10, PM-5, PM-7. References: NIST Special Publication 800-128. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-2(2) | FedRAMP_High_R4_CM-2(2) | FedRAMP High CM-2 (2) | Configuration Management | Automation Support For Accuracy / Currency | Shared | n/a | The organization employs automated mechanisms to maintain an up-to-date, complete, accurate, and readily available baseline configuration of the information system. Supplemental Guidance: Automated mechanisms that help organizations maintain consistent baseline configurations for information systems include, for example, hardware and software inventory tools, configuration management tools, and network management tools. Such tools can be deployed and/or allocated as common controls, at the information system level, or at the operating system or component level (e.g., on workstations, servers, notebook computers, network components, or mobile devices). Tools can be used, for example, to track version numbers on operating system applications, types of software installed, and current patch levels. This control enhancement can be satisfied by the implementation of CM-8 (2) for organizations that choose to combine information system component inventory and baseline configuration activities. Related controls: CM-7, RA-5. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-2(3) | FedRAMP_High_R4_CM-2(3) | FedRAMP High CM-2 (3) | Configuration Management | Retention Of Previous Configurations | Shared | n/a | The organization retains [Assignment: organization-defined previous versions of baseline configurations of the information system] to support rollback. Supplemental Guidance: Retaining previous versions of baseline configurations to support rollback may include, for example, hardware, software, firmware, configuration files, and configuration records. | link | count: 001 Retain previous versions of baseline configs (5e4e9685-3818-5934-0071-2620c4fa2ca5) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-2(7) | FedRAMP_High_R4_CM-2(7) | FedRAMP High CM-2 (7) | Configuration Management | Configure Systems, Components, Or Devices For High-Risk Areas | Shared | n/a | The organization: (a) Issues [Assignment: organization-defined information systems, system components, or devices] with [Assignment: organization-defined configurations] to individuals traveling to locations that the organization deems to be of significant risk; and (b) Applies [Assignment: organization-defined security safeguards] to the devices when the individuals return. Supplemental Guidance: When it is known that information systems, system components, or devices (e.g., notebook computers, mobile devices) will be located in high-risk areas, additional security controls may be implemented to counter the greater threat in such areas coupled with the lack of physical security relative to organizational-controlled areas. For example, organizational policies and procedures for notebook computers used by individuals departing on and returning from travel include, for example, determining which locations are of concern, defining required configurations for the devices, ensuring that the devices are configured as intended before travel is initiated, and applying specific safeguards to the device after travel is completed. Specially configured notebook computers include, for example, computers with sanitized hard drives, limited applications, and additional hardening (e.g., more stringent configuration settings). Specified safeguards applied to mobile devices upon return from travel include, for example, examining the device for signs of physical tampering and purging/reimaging the hard disk drive. Protecting information residing on mobile devices is covered in the media protection family..\ | link | count: 002 Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-3 | FedRAMP_High_R4_CM-3 | FedRAMP High CM-3 | Configuration Management | Configuration Change Control | Shared | n/a | The organization: a. Determines the types of changes to the information system that are configuration-controlled; b. Reviews proposed configuration-controlled changes to the information system and approves or disapproves such changes with explicit consideration for security impact analyses; c. Documents configuration change decisions associated with the information system; d. Implements approved configuration-controlled changes to the information system; e. Retains records of configuration-controlled changes to the information system for [Assignment: organization-defined time period]; f. Audits and reviews activities associated with configuration-controlled changes to the information system; and g. Coordinates and provides oversight for configuration change control activities through [Assignment: organization-defined configuration change control element (e.g., committee, board] that convenes [Selection (one or more): [Assignment: organization-defined frequency]; [Assignment: organization-defined configuration change conditions]]. Supplemental Guidance: Configuration change controls for organizational information systems involve the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications. Configuration change control includes changes to baseline configurations for components and configuration items of information systems, changes to configuration settings for information technology products (e.g., operating systems, applications, firewalls, routers, and mobile devices), unscheduled/unauthorized changes, and changes to remediate vulnerabilities. Typical processes for managing configuration changes to information systems include, for example, Configuration Control Boards that approve proposed changes to systems. For new development information systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards. Auditing of changes includes activities before and after changes are made to organizational information systems and the auditing activities required to implement such changes. Related controls: CM-2, CM-4, CM-5, CM-6, CM-9, SA-10, SI-2, SI-12. References: NIST Special Publication 800-128. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-3(1) | FedRAMP_High_R4_CM-3(1) | FedRAMP High CM-3 (1) | Configuration Management | Automated Document / Notification / Prohibition Of Changes | Shared | n/a | The organization employs automated mechanisms to: (a) Document proposed changes to the information system; (b) Notify [Assignment: organized-defined approval authorities] of proposed changes to the information system and request change approval; (c) Highlight proposed changes to the information system that have not been approved or disapproved by [Assignment: organization-defined time period]; (d) Prohibit changes to the information system until designated approvals are received; (e) Document all changes to the information system; and (f) Notify [Assignment: organization-defined personnel] when approved changes to the information system are completed. | link | count: 006 Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-3(2) | FedRAMP_High_R4_CM-3(2) | FedRAMP High CM-3 (2) | Configuration Management | Test / Validate / Document Changes | Shared | n/a | The organization tests, validates, and documents changes to the information system before implementing the changes on the operational system. Supplemental Guidance: Changes to information systems include modifications to hardware, software, or firmware components and configuration settings defined in CM-6. Organizations ensure that testing does not interfere with information system operations. Individuals/groups conducting tests understand organizational security policies and procedures, information system security policies and procedures, and the specific health, safety, and environmental risks associated with particular facilities/processes. Operational systems may need to be taken off-line, or replicated to the extent feasible, before testing can be conducted. If information systems must be taken off-line for testing, the tests are scheduled to occur during planned system outages whenever possible. If testing cannot be conducted on operational systems, organizations employ compensating controls (e.g., testing on replicated systems). | link | count: 003 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-3(4) | FedRAMP_High_R4_CM-3(4) | FedRAMP High CM-3 (4) | Configuration Management | Security Representative | Shared | n/a | The organization requires an information security representative to be a member of the [Assignment: organization-defined configuration change control element]. Supplemental Guidance: Information security representatives can include, for example, senior agency information security officers, information system security officers, or information system security managers. Representation by personnel with information security expertise is important because changes to information system configurations can have unintended side effects, some of which may be security-relevant. Detecting such changes early in the process can help avoid unintended, negative consequences that could ultimately affect the security state of organizational information systems. The configuration change control element in this control enhancement reflects the change control elements defined by organizations in CM-3. | link | count: 001 Assign information security representative to change control (6abdf7c7-362b-3f35-099e-533ed50988f9) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-3(6) | FedRAMP_High_R4_CM-3(6) | FedRAMP High CM-3 (6) | Configuration Management | Cryptography Management | Shared | n/a | The organization ensures that cryptographic mechanisms used to provide [Assignment: organization-defined security safeguards] are under configuration management. Supplemental Guidance: Regardless of the cryptographic means employed (e.g., public key, private key, shared secrets), organizations ensure that there are processes and procedures in place to effectively manage those means. For example, if devices use certificates as a basis for identification and authentication, there needs to be a process in place to address the expiration of those certificates. Related control: SC-13. | link | count: 001 Ensure cryptographic mechanisms are under configuration management (b8dad106-6444-5f55-307e-1e1cc9723e39) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-4 | FedRAMP_High_R4_CM-4 | FedRAMP High CM-4 | Configuration Management | Security Impact Analysis | Shared | n/a | The organization analyzes changes to the information system to determine potential security impacts prior to change implementation. Supplemental Guidance: Organizational personnel with information security responsibilities (e.g., Information System Administrators, Information System Security Officers, Information System Security Managers, and Information System Security Engineers) conduct security impact analyses. Individuals conducting security impact analyses possess the necessary skills/technical expertise to analyze the changes to information systems and the associated security ramifications. Security impact analysis may include, for example, reviewing security plans to understand security control requirements and reviewing system design documentation to understand control implementation and how specific changes might affect the controls. Security impact analyses may also include assessments of risk to better understand the impact of the changes and to determine if additional security controls are required. Security impact analyses are scaled in accordance with the security categories of the information systems. Related controls: CA-2, CA-7, CM-3, CM-9, SA-4, SA-5, SA-10, SI-2. References: NIST Special Publication 800-128. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-4(1) | FedRAMP_High_R4_CM-4(1) | FedRAMP High CM-4 (1) | Configuration Management | Separate Test Environments | Shared | n/a | The organization analyzes changes to the information system in a separate test environment before implementation in an operational environment, looking for security impacts due to flaws, weaknesses, incompatibility, or intentional malice. Supplemental Guidance: Separate test environment in this context means an environment that is physically or logically isolated and distinct from the operational environment. The separation is sufficient to ensure that activities in the test environment do not impact activities in the operational environment, and information in the operational environment is not inadvertently transmitted to the test environment. Separate environments can be achieved by physical or logical means. If physically separate test environments are not used, organizations determine the strength of mechanism required when implementing logical separation (e.g., separation achieved through virtual machines). Related controls: SA-11, SC-3, SC-7. | link | count: 005 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-5 | FedRAMP_High_R4_CM-5 | FedRAMP High CM-5 | Configuration Management | Access Restrictions For Change | Shared | n/a | The organization defines, documents, approves, and enforces physical and logical access restrictions associated with changes to the information system. Supplemental Guidance: Any changes to the hardware, software, and/or firmware components of information systems can potentially have significant effects on the overall security of the systems. Therefore, organizations permit only qualified and authorized individuals to access information systems for purposes of initiating changes, including upgrades and modifications. Organizations maintain records of access to ensure that configuration change control is implemented and to support after-the-fact actions should organizations discover any unauthorized changes. Access restrictions for change also include software libraries. Access restrictions include, for example, physical and logical access controls (see AC-3 and PE-3), workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into information systems), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover). Related controls: AC-3, AC-6, PE-3. References: None. | link | count: 001 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-5(1) | FedRAMP_High_R4_CM-5(1) | FedRAMP High CM-5 (1) | Configuration Management | Automated Access Enforcement / Auditing | Shared | n/a | The information system enforces access restrictions and supports auditing of the enforcement actions. Supplemental Guidance: Related controls: AU-2, AU-12, AU-6, CM-3, CM-6. | link | count: 001 Enforce and audit access restrictions (8cd815bf-97e1-5144-0735-11f6ddb50a59) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-5(2) | FedRAMP_High_R4_CM-5(2) | FedRAMP High CM-5 (2) | Configuration Management | Review System Changes | Shared | n/a | The organization reviews information system changes [Assignment: organization-defined frequency] and [Assignment: organization-defined circumstances] to determine whether unauthorized changes have occurred. Supplemental Guidance: Indications that warrant review of information system changes and the specific circumstances justifying such reviews may be obtained from activities carried out by organizations during the configuration change process. Related controls: AU-6, AU-7, CM-3, CM-5, PE-6, PE-8. | link | count: 001 Review changes for any unauthorized changes (c246d146-82b0-301f-32e7-1065dcd248b7) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-5(3) | FedRAMP_High_R4_CM-5(3) | FedRAMP High CM-5 (3) | Configuration Management | Signed Components | Shared | n/a | The information system prevents the installation of [Assignment: organization-defined software and firmware components] without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization. Supplemental Guidance: Software and firmware components prevented from installation unless signed with recognized and approved certificates include, for example, software and firmware version updates, patches, service packs, device drivers, and basic input output system (BIOS) updates. Organizations can identify applicable software and firmware components by type, by specific items, or a combination of both. Digital signatures and organizational verification of such signatures, is a method of code authentication. Related controls: CM-7, SC-13, SI-7. | link | count: 001 Restrict unauthorized software and firmware installation (4ee5975d-2507-5530-a20a-83a725889c6f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-5(5) | FedRAMP_High_R4_CM-5(5) | FedRAMP High CM-5 (5) | Configuration Management | Limit Production / Operational Privileges | Shared | n/a | The organization: (a) Limits privileges to change information system components and system-related information within a production or operational environment; and (b) Reviews and reevaluates privileges [Assignment: organization-defined frequency]. Supplemental Guidance: In many organizations, information systems support multiple core missions/business functions. Limiting privileges to change information system components with respect to operational systems is necessary because changes to a particular information system component may have far-reaching effects on mission/business processes supported by the system where the component resides. The complex, many-to-many relationships between systems and mission/business processes are in some cases, unknown to developers. Related control: AC-2. | link | count: 002 Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-6 | FedRAMP_High_R4_CM-6 | FedRAMP High CM-6 | Configuration Management | Configuration Settings | Shared | n/a | The organization: a. Establishes and documents configuration settings for information technology products employed within the information system using [Assignment: organization-defined security configuration checklists] that reflect the most restrictive mode consistent with operational requirements; b. Implements the configuration settings; c. Identifies, documents, and approves any deviations from established configuration settings for [Assignment: organization-defined information system components] based on [Assignment: organization-defined operational requirements]; and d. Monitors and controls changes to the configuration settings in accordance with organizational policies and procedures. Supplemental Guidance: Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the information system that affect the security posture and/or functionality of the system. Information technology products for which security- related configuration settings can be defined include, for example, mainframe computers, servers (e.g., database, electronic mail, authentication, web, proxy, file, domain name), workstations, input/output devices (e.g., scanners, copiers, and printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications. Security-related parameters are those parameters impacting the security state of information systems including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: (i) registry settings; (ii) account, file, directory permission settings; and (iii) settings for functions, ports, protocols, services, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific settings for information systems. The established settings become part of the systems configuration baseline. Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those information system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations including, for example, information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors. Common secure configurations include the United States Government Configuration Baseline (USGCB) which affects the implementation of CM-6 and other controls such as AC-19 and CM-7. The Security Content Automation Protocol (SCAP) and the defined standards within the protocol (e.g., Common Configuration Enumeration) provide an effective method to uniquely identify, track, and control configuration settings. OMB establishes federal policy on configuration requirements for federal information systems. Related controls: AC-19, CM-2, CM-3, CM-7, SI-4. References: OMB Memoranda 07-11, 07-18, 08-22; NIST Special Publications 800-70, 800-128; Web: http://nvd.nist.gov, http://checklists.nist.gov, http://www.nsa.gov. | link | count: 023 App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Function apps should have Client Certificates (Incoming client certificates) enabled (ab6a902f-9493-453b-928d-62c30b11b5a6), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Guest Configuration, Kubernetes, Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-6(1) | FedRAMP_High_R4_CM-6(1) | FedRAMP High CM-6 (1) | Configuration Management | Automated Central Management / Application / Verification | Shared | n/a | The organization employs automated mechanisms to centrally manage, apply, and verify configuration settings for [Assignment: organization-defined information system components]. Supplemental Guidance: Related controls: CA-7, CM-4. | link | count: 003 Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-7 | FedRAMP_High_R4_CM-7 | FedRAMP High CM-7 | Configuration Management | Least Functionality | Shared | n/a | The organization: a. Configures the information system to provide only essential capabilities; and b. Prohibits or restricts the use of the following functions, ports, protocols, and/or services: [Assignment: organization-defined prohibited or restricted functions, ports, protocols, and/or services]. Supplemental Guidance: Information systems can provide a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Additionally, it is sometimes convenient to provide multiple services from single information system components, but doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per device (e.g., email servers or web servers, but not both). Organizations review functions and services provided by information systems or individual components of information systems, to determine which functions and services are candidates for elimination (e.g., Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing). Organizations consider disabling unused or unnecessary physical and logical ports/protocols (e.g., Universal Serial Bus, File Transfer Protocol, and Hyper Text Transfer Protocol) on information systems to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services. Related controls: AC-6, CM-2, RA-5, SA-5, SC-7. References: DoD Instruction 8551.01. | link | count: 003 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-7(2) | FedRAMP_High_R4_CM-7(2) | FedRAMP High CM-7 (2) | Configuration Management | Prevent Program Execution | Shared | n/a | The information system prevents program execution in accordance with [Selection (one or more): [Assignment: organization-defined policies regarding software program usage and restrictions]; rules authorizing the terms and conditions of software program usage]. Supplemental Guidance: Related controls: CM-8, PM-5. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-7(5) | FedRAMP_High_R4_CM-7(5) | FedRAMP High CM-7 (5) | Configuration Management | Authorized Software / Whitelisting | Shared | n/a | The organization: (a) Identifies [Assignment: organization-defined software programs authorized to execute on the information system]; (b) Employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the information system; and (c) Reviews and updates the list of authorized software programs [Assignment: organization- defined frequency]. Supplemental Guidance: The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting. In addition to whitelisting, organizations consider verifying the integrity of white-listed software programs using, for example, cryptographic checksums, digital signatures, or hash functions. Verification of white-listed software can occur either prior to execution or at system startup. Related controls: CM-2, CM-6, CM-8, PM-5, SA-10, SC-34, SI-7. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-8 | FedRAMP_High_R4_CM-8 | FedRAMP High CM-8 | Configuration Management | Information System Component Inventory | Shared | n/a | The organization: a. Develops and documents an inventory of information system components that: 1. Accurately reflects the current information system; 2. Includes all components within the authorization boundary of the information system; 3. Is at the level of granularity deemed necessary for tracking and reporting; and 4. Includes [Assignment: organization-defined information deemed necessary to achieve effective information system component accountability]; and b. Reviews and updates the information system component inventory [Assignment: organization-defined frequency]. Supplemental Guidance: Organizations may choose to implement centralized information system component inventories that include components from all organizational information systems. In such situations, organizations ensure that the resulting inventories include system-specific information required for proper component accountability (e.g., information system association, information system owner). Information deemed necessary for effective accountability of information system components includes, for example, hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include, for example, manufacturer, device type, model, serial number, and physical location. Related controls: CM-2, CM-6, PM-5. References: NIST Special Publication 800-128. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-8(1) | FedRAMP_High_R4_CM-8(1) | FedRAMP High CM-8 (1) | Configuration Management | Updates During Installations / Removals | Shared | n/a | The organization updates the inventory of information system components as an integral part of component installations, removals, and information system updates. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-8(3) | FedRAMP_High_R4_CM-8(3) | FedRAMP High CM-8 (3) | Configuration Management | Automated Unauthorized Component Detection | Shared | n/a | The organization: (a) Employs automated mechanisms [Assignment: organization-defined frequency] to detect the presence of unauthorized hardware, software, and firmware components within the information system; and (b) Takes the following actions when unauthorized components are detected: [Selection (one or more): disables network access by such components; isolates the components; notifies [Assignment: organization-defined personnel or roles]]. Supplemental Guidance: This control enhancement is applied in addition to the monitoring for unauthorized remote connections and mobile devices. Monitoring for unauthorized system components may be accomplished on an ongoing basis or by the periodic scanning of systems for that purpose. Automated mechanisms can be implemented within information systems or in other separate devices. Isolation can be achieved, for example, by placing unauthorized information system components in separate domains or subnets or otherwise quarantining such components. This type of component isolation is commonly referred to as sandboxing. Related controls: AC-17, AC-18, AC-19, CA-7, SI-3, SI-4, SI-7, RA-5. | link | count: 002 Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-8(4) | FedRAMP_High_R4_CM-8(4) | FedRAMP High CM-8 (4) | Configuration Management | Accountability Information | Shared | n/a | The organization includes in the information system component inventory information, a means for identifying by [Selection (one or more): name; position; role], individuals responsible/accountable for administering those components. Supplemental Guidance: Identifying individuals who are both responsible and accountable for administering information system components helps to ensure that the assigned components are properly administered and organizations can contact those individuals if some action is required (e.g., component is determined to be the source of a breach/compromise, component needs to be recalled/replaced, or component needs to be relocated). | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CM-9 | FedRAMP_High_R4_CM-9 | FedRAMP High CM-9 | Configuration Management | Configuration Management Plan | Shared | n/a | The organization develops, documents, and implements a configuration management plan for the information system that: a. Addresses roles, responsibilities, and configuration management processes and procedures; b. Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items; c. Defines the configuration items for the information system and places the configuration items under configuration management; and d. Protects the configuration management plan from unauthorized disclosure and modification. Supplemental Guidance: Configuration management plans satisfy the requirements in configuration management policies while being tailored to individual information systems. Such plans define detailed processes and procedures for how configuration management is used to support system development life cycle activities at the information system level. Configuration management plans are typically developed during the development/acquisition phase of the system development life cycle. The plans describe how to move changes through change management processes, how to update configuration settings and baselines, how to maintain information system component inventories, how to control development, test, and operational environments, and how to develop, release, and update key documents. Organizations can employ templates to help ensure consistent and timely development and implementation of configuration management plans. Such templates can represent a master configuration management plan for the organization at large with subsets of the plan implemented on a system by system basis. Configuration management approval processes include designation of key management stakeholders responsible for reviewing and approving proposed changes to information systems, and personnel that conduct security impact analyses prior to the implementation of changes to the systems. Configuration items are the information system items (hardware, software, firmware, and documentation) to be configuration-managed. As information systems continue through the system development life cycle, new configuration items may be identified and some existing configuration items may no longer need to be under configuration control. Related controls: CM-2, CM-3, CM-4, CM-5, CM-8, SA-10. References: NIST Special Publication 800-128. | link | count: 006 Create configuration plan protection (874a6f2e-2098-53bc-3a16-20dcdc425a7e), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-1 | FedRAMP_High_R4_CP-1 | FedRAMP High CP-1 | Contingency Planning | Contingency Planning Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A contingency planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls; and b. Reviews and updates the current: 1. Contingency planning policy [Assignment: organization-defined frequency]; and 2. Contingency planning procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CP family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: Federal Continuity Directive 1; NIST Special Publications 800-12, 800-34, 800-100. | link | count: 001 Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-10 | FedRAMP_High_R4_CP-10 | FedRAMP High CP-10 | Contingency Planning | Information System Recovery And Reconstitution | Shared | n/a | The organization provides for the recovery and reconstitution of the information system to a known state after a disruption, compromise, or failure. Supplemental Guidance: Recovery is executing information system contingency plan activities to restore organizational missions/business functions. Reconstitution takes place following recovery and includes activities for returning organizational information systems to fully operational states. Recovery and reconstitution operations reflect mission and business priorities, recovery point/time and reconstitution objectives, and established organizational metrics consistent with contingency plan requirements. Reconstitution includes the deactivation of any interim information system capabilities that may have been needed during recovery operations. Reconstitution also includes assessments of fully restored information system capabilities, reestablishment of continuous monitoring activities, potential information system reauthorizations, and activities to prepare the systems against future disruptions, compromises, or failures. Recovery/reconstitution capabilities employed by organizations can include both automated mechanisms and manual procedures. Related controls: CA-2, CA-6, CA-7, CP-2, CP-6, CP-7, CP-9, SC-24. References: Federal Continuity Directive 1; NIST Special Publication 800-34. | link | count: 001 Recover and reconstitute resources after any disruption (f33c3238-11d2-508c-877c-4262ec1132e1) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-10(2) | FedRAMP_High_R4_CP-10(2) | FedRAMP High CP-10 (2) | Contingency Planning | Transaction Recovery | Shared | n/a | The information system implements transaction recovery for systems that are transaction-based. Supplemental Guidance: Transaction-based information systems include, for example, database management systems and transaction processing systems. Mechanisms supporting transaction recovery include, for example, transaction rollback and transaction journaling. | link | count: 001 Implement transaction based recovery (ba02d0a0-566a-25dc-73f1-101c726a19c5) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-10(4) | FedRAMP_High_R4_CP-10(4) | FedRAMP High CP-10 (4) | Contingency Planning | Restore Within Time Period | Shared | n/a | The organization provides the capability to restore information system components within [Assignment: organization-defined restoration time-periods] from configuration-controlled and integrity-protected information representing a known, operational state for the components. Supplemental Guidance: Restoration of information system components includes, for example, reimaging which restores components to known, operational states. Related control: CM-2. | link | count: 001 Restore resources to operational state (f801d58e-5659-9a4a-6e8d-02c9334732e5) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-2 | FedRAMP_High_R4_CP-2 | FedRAMP High CP-2 | Contingency Planning | Contingency Plan | Shared | n/a | The organization: a. Develops a contingency plan for the information system that: 1. Identifies essential missions and business functions and associated contingency requirements; 2. Provides recovery objectives, restoration priorities, and metrics; 3. Addresses contingency roles, responsibilities, assigned individuals with contact information; 4. Addresses maintaining essential missions and business functions despite an information system disruption, compromise, or failure; 5. Addresses eventual, full information system restoration without deterioration of the security safeguards originally planned and implemented; and 6. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; b. Distributes copies of the contingency plan to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements]; c. Coordinates contingency planning activities with incident handling activities; d. Reviews the contingency plan for the information system [Assignment: organization-defined frequency]; e. Updates the contingency plan to address changes to the organization, information system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing; f. Communicates contingency plan changes to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements]; and g. Protects the contingency plan from unauthorized disclosure and modification. Supplemental Guidance: Contingency planning for information systems is part of an overall organizational program for achieving continuity of operations for mission/business functions. Contingency planning addresses both information system restoration and implementation of alternative mission/business processes when systems are compromised. The effectiveness of contingency planning is maximized by considering such planning throughout the phases of the system development life cycle. Performing contingency planning on hardware, software, and firmware development can be an effective means of achieving information system resiliency. Contingency plans reflect the degree of restoration required for organizational information systems since not all systems may need to fully recover to achieve the level of continuity of operations desired. Information system recovery objectives reflect applicable laws, Executive Orders, directives, policies, standards, regulations, and guidelines. In addition to information system availability, contingency plans also address other security-related events resulting in a reduction in mission and/or business effectiveness, such as malicious attacks compromising the confidentiality or integrity of information systems. Actions addressed in contingency plans include, for example, orderly/graceful degradation, information system shutdown, fallback to a manual mode, alternate information flows, and operating in modes reserved for when systems are under attack. By closely coordinating contingency planning with incident handling activities, organizations can ensure that the necessary contingency planning activities are in place and activated in the event of a security incident. Related controls: AC-14, CP-6, CP-7, CP-8, CP-9, CP-10, IR-4, IR-8, MP-2, MP-4, MP-5, PM-8, PM-11. References: Federal Continuity Directive 1; NIST Special Publication 800-34. | link | count: 008 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82), Review contingency plan (53fc1282-0ee3-2764-1319-e20143bb0ea5), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-2(1) | FedRAMP_High_R4_CP-2(1) | FedRAMP High CP-2 (1) | Contingency Planning | Coordinate With Related Plans | Shared | n/a | The organization coordinates contingency plan development with organizational elements responsible for related plans. Supplemental Guidance: Plans related to contingency plans for organizational information systems include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, Insider Threat Implementation Plan, and Occupant Emergency Plans. | link | count: 001 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-2(2) | FedRAMP_High_R4_CP-2(2) | FedRAMP High CP-2 (2) | Contingency Planning | Capacity Planning | Shared | n/a | The organization conducts capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations. Supplemental Guidance: Capacity planning is needed because different types of threats (e.g., natural disasters, targeted cyber attacks) can result in a reduction of the available processing, telecommunications, and support services originally intended to support the organizational missions/business functions. Organizations may need to anticipate degraded operations during contingency operations and factor such degradation into capacity planning. | link | count: 001 Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-2(3) | FedRAMP_High_R4_CP-2(3) | FedRAMP High CP-2 (3) | Contingency Planning | Resume Essential Missions / Business Functions | Shared | n/a | The organization plans for the resumption of essential missions and business functions within [Assignment: organization-defined time period] of contingency plan activation. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. The time period for resumption of essential missions/business functions may be dependent on the severity/extent of disruptions to the information system and its supporting infrastructure. Related control: PE-12. | link | count: 001 Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-2(4) | FedRAMP_High_R4_CP-2(4) | FedRAMP High CP-2 (4) | Contingency Planning | Resume All Missions / Business Functions | Shared | n/a | The organization plans for the resumption of all missions and business functions within [Assignment: organization-defined time period] of contingency plan activation. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. The time period for resumption of all missions/business functions may be dependent on the severity/extent of disruptions to the information system and its supporting infrastructure. Related control: PE-12. | link | count: 001 Resume all mission and business functions (91a54089-2d69-0f56-62dc-b6371a1671c0) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-2(5) | FedRAMP_High_R4_CP-2(5) | FedRAMP High CP-2 (5) | Contingency Planning | Continue Essential Missions / Business Functions | Shared | n/a | The organization plans for the continuance of essential missions and business functions with little or no loss of operational continuity and sustains that continuity until full information system restoration at primary processing and/or storage sites. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. Primary processing and/or storage sites defined by organizations as part of contingency planning may change depending on the circumstances associated with the contingency (e.g., backup sites may become primary sites). Related control: PE-12. | link | count: 001 Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-2(8) | FedRAMP_High_R4_CP-2(8) | FedRAMP High CP-2 (8) | Contingency Planning | Identify Critical Assets | Shared | n/a | The organization identifies critical information system assets supporting essential missions and business functions. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. Organizations identify critical information system assets so that additional safeguards and countermeasures can be employed (above and beyond those safeguards and countermeasures routinely implemented) to help ensure that organizational missions/business functions can continue to be conducted during contingency operations. In addition, the identification of critical information assets facilitates the prioritization of organizational resources. Critical information system assets include technical and operational aspects. Technical aspects include, for example, information technology services, information system components, information technology products, and mechanisms. Operational aspects include, for example, procedures (manually executed operations) and personnel (individuals operating technical safeguards and/or executing manual procedures). Organizational program protection plans can provide assistance in identifying critical assets. Related controls: SA-14, SA-15. | link | count: 001 Perform a business impact assessment and application criticality assessment (cb8841d4-9d13-7292-1d06-ba4d68384681) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-3 | FedRAMP_High_R4_CP-3 | FedRAMP High CP-3 | Contingency Planning | Contingency Training | Shared | n/a | The organization provides contingency training to information system users consistent with assigned roles and responsibilities: a. Within [Assignment: organization-defined time period] of assuming a contingency role or responsibility; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Contingency training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, regular users may only need to know when and where to report for duty during contingency operations and if normal duties are affected; system administrators may require additional training on how to set up information systems at alternate processing and storage sites; and managers/senior leaders may receive more specific training on how to conduct mission-essential functions in designated off-site locations and how to establish communications with other governmental entities for purposes of coordination on contingency-related activities. Training for contingency roles/responsibilities reflects the specific continuity requirements in the contingency plan. Related controls: AT-2, AT-3, CP-2, IR-2. References: Federal Continuity Directive 1; NIST Special Publications 800-16, 800-50. | link | count: 001 Provide contingency training (de936662-13dc-204c-75ec-1af80f994088) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-3(1) | FedRAMP_High_R4_CP-3(1) | FedRAMP High CP-3 (1) | Contingency Planning | Simulated Events | Shared | n/a | The organization incorporates simulated events into contingency training to facilitate effective response by personnel in crisis situations. | link | count: 001 Incorporate simulated contingency training (9c954fcf-6dd8-81f1-41b5-832ae5c62caf) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-4 | FedRAMP_High_R4_CP-4 | FedRAMP High CP-4 | Contingency Planning | Contingency Plan Testing | Shared | n/a | The organization: a. Tests the contingency plan for the information system [Assignment: organization-defined frequency] using [Assignment: organization-defined tests] to determine the effectiveness of the plan and the organizational readiness to execute the plan; b. Reviews the contingency plan test results; and c. Initiates corrective actions, if needed. Supplemental Guidance: Methods for testing contingency plans to determine the effectiveness of the plans and to identify potential weaknesses in the plans include, for example, walk-through and tabletop exercises, checklists, simulations (parallel, full interrupt), and comprehensive exercises. Organizations conduct testing based on the continuity requirements in contingency plans and include a determination of the effects on organizational operations, assets, and individuals arising due to contingency operations. Organizations have flexibility and discretion in the breadth, depth, and timelines of corrective actions. Related controls: CP-2, CP-3, IR-3. References: Federal Continuity Directive 1; FIPS Publication 199; NIST Special Publications 800-34, 800-84. | link | count: 003 Initiate contingency plan testing corrective actions (8bfdbaa6-6824-3fec-9b06-7961bf7389a6), Review the results of contingency plan testing (5d3abfea-a130-1208-29c0-e57de80aa6b0), Test the business continuity and disaster recovery plan (58a51cde-008b-1a5d-61b5-d95849770677) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-4(1) | FedRAMP_High_R4_CP-4(1) | FedRAMP High CP-4 (1) | Contingency Planning | Coordinate With Related Plans | Shared | n/a | The organization coordinates contingency plan testing with organizational elements responsible for related plans. Supplemental Guidance: Plans related to contingency plans for organizational information systems include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, and Occupant Emergency Plans. This control enhancement does not require organizations to create organizational elements to handle related plans or to align such elements with specific plans. It does require, however, that if such organizational elements are responsible for related plans, organizations should coordinate with those elements. Related controls: IR-8, PM-8. | link | count: 001 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-4(2) | FedRAMP_High_R4_CP-4(2) | FedRAMP High CP-4 (2) | Contingency Planning | Alternate Processing Site | Shared | n/a | The organization tests the contingency plan at the alternate processing site: (a) To familiarize contingency personnel with the facility and available resources; and (b) To evaluate the capabilities of the alternate processing site to support contingency operations. Supplemental Guidance: Related control: CP-7. | link | count: 002 Evaluate alternate processing site capabilities (60442979-6333-85f0-84c5-b887bac67448), Test contingency plan at an alternate processing location (ba99d512-3baa-1c38-8b0b-ae16bbd34274) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-6 | FedRAMP_High_R4_CP-6 | FedRAMP High CP-6 | Contingency Planning | Alternate Storage Site | Shared | n/a | The organization: a. Establishes an alternate storage site including necessary agreements to permit the storage and retrieval of information system backup information; and b. Ensures that the alternate storage site provides information security safeguards equivalent to that of the primary site. Supplemental Guidance: Alternate storage sites are sites that are geographically distinct from primary storage sites. An alternate storage site maintains duplicate copies of information and data in the event that the primary storage site is not available. Items covered by alternate storage site agreements include, for example, environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and coordination of delivery/retrieval of backup media. Alternate storage sites reflect the requirements in contingency plans so that organizations can maintain essential missions/business functions despite disruption, compromise, or failure in organizational information systems. Related controls: CP-2, CP-7, CP-9, CP-10, MP-4. References: NIST Special Publication 800-34. | link | count: 007 Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Regulatory Compliance, SQL, Storage | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-6(1) | FedRAMP_High_R4_CP-6(1) | FedRAMP High CP-6 (1) | Contingency Planning | Separation From Primary Site | Shared | n/a | The organization identifies an alternate storage site that is separated from the primary storage site to reduce susceptibility to the same threats. Supplemental Guidance: Threats that affect alternate storage sites are typically defined in organizational assessments of risk and include, for example, natural disasters, structural failures, hostile cyber attacks, and errors of omission/commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate storage sites based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites is less relevant. Related control: RA-3. | link | count: 006 Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Regulatory Compliance, SQL, Storage | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-6(2) | FedRAMP_High_R4_CP-6(2) | FedRAMP High CP-6 (2) | Contingency Planning | Recovery Time / Point Objectives | Shared | n/a | The organization configures the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives. | link | count: 001 Establish alternate storage site that facilitates recovery operations (245fe58b-96f8-9f1e-48c5-7f49903f66fd) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-6(3) | FedRAMP_High_R4_CP-6(3) | FedRAMP High CP-6 (3) | Contingency Planning | Accessibility | Shared | n/a | The organization identifies potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions. Supplemental Guidance: Area-wide disruptions refer to those types of disruptions that are broad in geographic scope (e.g., hurricane, regional power outage) with such determinations made by organizations based on organizational assessments of risk. Explicit mitigation actions include, for example: (i) duplicating backup information at other alternate storage sites if access problems occur at originally designated alternate sites; or (ii) planning for physical access to retrieve backup information if electronic accessibility to the alternate site is disrupted. Related control: RA-3. | link | count: 001 Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-7 | FedRAMP_High_R4_CP-7 | FedRAMP High CP-7 | Contingency Planning | Alternate Processing Site | Shared | n/a | The organization: a. Establishes an alternate processing site including necessary agreements to permit the transfer and resumption of [Assignment: organization-defined information system operations] for essential missions/business functions within [Assignment: organization-defined time period consistent with recovery time and recovery point objectives] when the primary processing capabilities are unavailable; b. Ensures that equipment and supplies required to transfer and resume operations are available at the alternate processing site or contracts are in place to support delivery to the site within the organization-defined time period for transfer/resumption; and c. Ensures that the alternate processing site provides information security safeguards equivalent to that of the primary site. Supplemental Guidance: Alternate processing sites are sites that are geographically distinct from primary processing sites. An alternate processing site provides processing capability in the event that the primary processing site is not available. Items covered by alternate processing site agreements include, for example, environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and coordination for the transfer/assignment of personnel. Requirements are specifically allocated to alternate processing sites that reflect the requirements in contingency plans to maintain essential missions/business functions despite disruption, compromise, or failure in organizational information systems. Related controls: CP-2, CP-6, CP-8, CP-9, CP-10, MA-6. References: NIST Special Publication 800-34. | link | count: 002 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Compute, Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-7(1) | FedRAMP_High_R4_CP-7(1) | FedRAMP High CP-7 (1) | Contingency Planning | Separation From Primary Site | Shared | n/a | The organization identifies an alternate processing site that is separated from the primary processing site to reduce susceptibility to the same threats. Supplemental Guidance: Threats that affect alternate processing sites are typically defined in organizational assessments of risk and include, for example, natural disasters, structural failures, hostile cyber attacks, and errors of omission/commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate processing sites based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites is less relevant. Related control: RA-3. | link | count: 001 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-7(2) | FedRAMP_High_R4_CP-7(2) | FedRAMP High CP-7 (2) | Contingency Planning | Accessibility | Shared | n/a | The organization identifies potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions. Supplemental Guidance: Area-wide disruptions refer to those types of disruptions that are broad in geographic scope (e.g., hurricane, regional power outage) with such determinations made by organizations based on organizational assessments of risk. Related control: RA-3. | link | count: 001 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-7(3) | FedRAMP_High_R4_CP-7(3) | FedRAMP High CP-7 (3) | Contingency Planning | Priority Of Service | Shared | n/a | The organization develops alternate processing site agreements that contain priority-of-service provisions in accordance with organizational availability requirements (including recovery time objectives). Supplemental Guidance: Priority-of-service agreements refer to negotiated agreements with service providers that ensure that organizations receive priority treatment consistent with their availability requirements and the availability of information resources at the alternate processing site. | link | count: 002 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-7(4) | FedRAMP_High_R4_CP-7(4) | FedRAMP High CP-7 (4) | Contingency Planning | Preparation For Use | Shared | n/a | The organization prepares the alternate processing site so that the site is ready to be used as the operational site supporting essential missions and business functions. Supplemental Guidance: Site preparation includes, for example, establishing configuration settings for information system components at the alternate processing site consistent with the requirements for such settings at the primary site and ensuring that essential supplies and other logistical considerations are in place. Related controls: CM-2, CM-6. | link | count: 001 Prepare alternate processing site for use as operational site (0f31d98d-5ce2-705b-4aa5-b4f6705110dd) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-8(1) | FedRAMP_High_R4_CP-8(1) | FedRAMP High CP-8 (1) | Contingency Planning | Priority Of Service Provisions | Shared | n/a | The organization: (a) Develops primary and alternate telecommunications service agreements that contain priority- of-service provisions in accordance with organizational availability requirements (including recovery time objectives); and (b) Requests Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness in the event that the primary and/or alternate telecommunications services are provided by a common carrier. Supplemental Guidance: Organizations consider the potential mission/business impact in situations where telecommunications service providers are servicing other organizations with similar priority-of-service provisions. | link | count: 001 Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-9 | FedRAMP_High_R4_CP-9 | FedRAMP High CP-9 | Contingency Planning | Information System Backup | Shared | n/a | The organization: a. Conducts backups of user-level information contained in the information system [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; b. Conducts backups of system-level information contained in the information system [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; c. Conducts backups of information system documentation including security-related documentation [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; and d. Protects the confidentiality, integrity, and availability of backup information at storage locations. Supplemental Guidance: System-level information includes, for example, system-state information, operating system and application software, and licenses. User-level information includes any information other than system-level information. Mechanisms employed by organizations to protect the integrity of information system backups include, for example, digital signatures and cryptographic hashes. Protection of system backup information while in transit is beyond the scope of this control. Information system backups reflect the requirements in contingency plans as well as other organizational requirements for backing up information. Related controls: CP-2, CP-6, MP-4, MP-5, SC-13. References: NIST Special Publication 800-34. | link | count: 009 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Backup, Key Vault, Regulatory Compliance, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-9(3) | FedRAMP_High_R4_CP-9(3) | FedRAMP High CP-9 (3) | Contingency Planning | Separate Storage For Critical Information | Shared | n/a | The organization stores backup copies of [Assignment: organization-defined critical information system software and other security-related information] in a separate facility or in a fire-rated container that is not collocated with the operational system. Supplemental Guidance: Critical information system software includes, for example, operating systems, cryptographic key management systems, and intrusion detection/prevention systems. Security-related information includes, for example, organizational inventories of hardware, software, and firmware components. Alternate storage sites typically serve as separate storage facilities for organizations. Related controls: CM-2, CM-8. | link | count: 001 Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | CP-9(5) | FedRAMP_High_R4_CP-9(5) | FedRAMP High CP-9 (5) | Contingency Planning | Transfer To Alternate Storage Site | Shared | n/a | The organization transfers information system backup information to the alternate storage site [Assignment: organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives]. Supplemental Guidance: Information system backup information can be transferred to alternate storage sites either electronically or by physical shipment of storage media. | link | count: 001 Transfer backup information to an alternate storage site (7bdb79ea-16b8-453e-4ca4-ad5b16012414) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-1 | FedRAMP_High_R4_IA-1 | FedRAMP High IA-1 | Identification And Authentication | Identification And Authentication Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls; and b. Reviews and updates the current: 1. Identification and authentication policy [Assignment: organization-defined frequency]; and 2. Identification and authentication procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the IA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: FIPS Publication 201; NIST Special Publications 800-12, 800-63, 800-73, 800-76, 800-78, 800-100. | link | count: 001 Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-2 | FedRAMP_High_R4_IA-2 | FedRAMP High IA-2 | Identification And Authentication | Identification And Authentication (Organizational Users) | Shared | n/a | The information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users). Supplemental Guidance: Organizational users include employees or individuals that organizations deem to have equivalent status of employees (e.g., contractors, guest researchers). This control applies to all accesses other than: (i) accesses that are explicitly identified and documented in AC-14; and (ii) accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity. Organizations employ passwords, tokens, or biometrics to authenticate user identities, or in the case multifactor authentication, or some combination thereof. Access to organizational information systems is defined as either local access or network access. Local access is any access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained by direct connections without the use of networks. Network access is access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks (e.g., the Internet). Internal networks include local area networks and wide area networks. In addition, the use of encrypted virtual private networks (VPNs) for network connections between organization- controlled endpoints and non-organization controlled endpoints may be treated as internal networks from the perspective of protecting the confidentiality and integrity of information traversing the network. Organizations can satisfy the identification and authentication requirements in this control by complying with the requirements in Homeland Security Presidential Directive 12 consistent with the specific organizational implementation plans. Multifactor authentication requires the use of two or more different factors to achieve authentication. The factors are defined as: (i) something you know (e.g., password, personal identification number [PIN]); (ii) something you have (e.g., cryptographic identification device, token); or (iii) something you are (e.g., biometric). Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card. In addition to identifying and authenticating users at the information system level (i.e., at logon), organizations also employ identification and authentication mechanisms at the application level, when necessary, to provide increased information security. Identification and authentication requirements for other than organizational users are described in IA-8. Related controls: AC-2, AC-3, AC-14, AC-17, AC-18, IA-4, IA-5, IA-8. References: HSPD-12; OMB Memoranda 04-04, 06-16, 11-11; FIPS Publication 201; NIST Special Publications 800-63, 800-73, 800-76, 800-78; FICAM Roadmap and Implementation Guidance; Web: http://idmanagement.gov. | link | count: 010 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
App Service, Azure Ai Services, Regulatory Compliance, Security Center, Service Fabric, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-2(1) | FedRAMP_High_R4_IA-2(1) | FedRAMP High IA-2 (1) | Identification And Authentication | Network Access To Privileged Accounts | Shared | n/a | The information system implements multifactor authentication for network access to privileged accounts. Supplemental Guidance: Related control: AC-6. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-2(11) | FedRAMP_High_R4_IA-2(11) | FedRAMP High IA-2 (11) | Identification And Authentication | Remote Access - Separate Device | Shared | n/a | The information system implements multifactor authentication for remote access to privileged and non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access and the device meets [Assignment: organization-defined strength of mechanism requirements]. Supplemental Guidance: For remote access to privileged/non-privileged accounts, the purpose of requiring a device that is separate from the information system gaining access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authentication credentials stored on the system. For example, adversaries deploying malicious code on organizational information systems can potentially compromise such credentials resident on the system and subsequently impersonate authorized users. Related control: AC-6. | link | count: 002 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-2(12) | FedRAMP_High_R4_IA-2(12) | FedRAMP High IA-2 (12) | Identification And Authentication | Acceptance Of Piv Credentials | Shared | n/a | The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials. Supplemental Guidance: This control enhancement applies to organizations implementing logical access control systems (LACS) and physical access control systems (PACS). Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 requires federal agencies to continue implementing the requirements specified in HSPD-12 to enable agency-wide use of PIV credentials. Related controls: AU-2, PE-3, SA-4. | link | count: 001 Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-2(2) | FedRAMP_High_R4_IA-2(2) | FedRAMP High IA-2 (2) | Identification And Authentication | Network Access To Non-Privileged Accounts | Shared | n/a | The information system implements multifactor authentication for network access to non- privileged accounts. | link | count: 002 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-2(3) | FedRAMP_High_R4_IA-2(3) | FedRAMP High IA-2 (3) | Identification And Authentication | Local Access To Privileged Accounts | Shared | n/a | The information system implements multifactor authentication for local access to privileged accounts. Supplemental Guidance: Related control: AC-6. | link | count: 001 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-2(5) | FedRAMP_High_R4_IA-2(5) | FedRAMP High IA-2 (5) | Identification And Authentication | Group Authentication | Shared | n/a | The organization requires individuals to be authenticated with an individual authenticator when a group authenticator is employed. Supplemental Guidance: Requiring individuals to use individual authenticators as a second level of authentication helps organizations to mitigate the risk of using group authenticators. | link | count: 001 Require use of individual authenticators (08ad71d0-52be-6503-4908-e015460a16ae) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-4 | FedRAMP_High_R4_IA-4 | FedRAMP High IA-4 | Identification And Authentication | Identifier Management | Shared | n/a | The organization manages information system identifiers by: a. Receiving authorization from [Assignment: organization-defined personnel or roles] to assign an individual, group, role, or device identifier; b. Selecting an identifier that identifies an individual, group, role, or device; c. Assigning the identifier to the intended individual, group, role, or device; d. Preventing reuse of identifiers for [Assignment: organization-defined time period]; and e. Disabling the identifier after [Assignment: organization-defined time period of inactivity]. Supplemental Guidance: Common device identifiers include, for example, media access control (MAC), Internet protocol (IP) addresses, or device-unique token identifiers. Management of individual identifiers is not applicable to shared information system accounts (e.g., guest and anonymous accounts). Typically, individual identifiers are the user names of the information system accounts assigned to those individuals. In such instances, the account management activities of AC-2 use account names provided by IA-4. This control also addresses individual identifiers not necessarily associated with information system accounts (e.g., identifiers used in physical security control databases accessed by badge reader systems for access to information systems). Preventing reuse of identifiers implies preventing the assignment of previously used individual, group, role, or device identifiers to different individuals, groups, roles, or devices. Related controls: AC-2, IA-2, IA-3, IA-5, IA-8, SC-37. References: FIPS Publication 201; NIST Special Publications 800-73, 800-76, 800-78. | link | count: 007 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Prevent identifier reuse for the defined time period (4781e5fd-76b8-7d34-6df3-a0a7fca47665), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-4(4) | FedRAMP_High_R4_IA-4(4) | FedRAMP High IA-4 (4) | Identification And Authentication | Identify User Status | Shared | n/a | The organization manages individual identifiers by uniquely identifying each individual as [Assignment: organization-defined characteristic identifying individual status]. Supplemental Guidance: Characteristics identifying the status of individuals include, for example, contractors and foreign nationals. Identifying the status of individuals by specific characteristics provides additional information about the people with whom organizational personnel are communicating. For example, it might be useful for a government employee to know that one of the individuals on an email message is a contractor. Related control: AT-2. | link | count: 001 Identify status of individual users (ca748dfe-3e28-1d18-4221-89aea30aa0a5) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-5 | FedRAMP_High_R4_IA-5 | FedRAMP High IA-5 | Identification And Authentication | Authenticator Management | Shared | n/a | The organization manages information system authenticators by: a. Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, or device receiving the authenticator; b. Establishing initial authenticator content for authenticators defined by the organization; c. Ensuring that authenticators have sufficient strength of mechanism for their intended use; d. Establishing and implementing administrative procedures for initial authenticator distribution, for lost/compromised or damaged authenticators, and for revoking authenticators; e. Changing default content of authenticators prior to information system installation; f. Establishing minimum and maximum lifetime restrictions and reuse conditions for authenticators; g. Changing/refreshing authenticators [Assignment: organization-defined time period by authenticator type]; h. Protecting authenticator content from unauthorized disclosure and modification; i. Requiring individuals to take, and having devices implement, specific security safeguards to protect authenticators; and j. Changing authenticators for group/role accounts when membership to those accounts changes. Supplemental Guidance: Individual authenticators include, for example, passwords, tokens, biometrics, PKI certificates, and key cards. Initial authenticator content is the actual content (e.g., the initial password) as opposed to requirements about authenticator content (e.g., minimum password length). In many cases, developers ship information system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant security risk. The requirement to protect individual authenticators may be implemented via control PL-4 or PS-6 for authenticators in the possession of individuals and by controls AC-3, AC-6, and SC-28 for authenticators stored within organizational information systems (e.g., passwords stored in hashed or encrypted formats, files containing encrypted or hashed passwords accessible with administrator privileges). Information systems support individual authenticator management by organization-defined settings and restrictions for various authenticator characteristics including, for example, minimum password length, password composition, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication. Specific actions that can be taken to safeguard authenticators include, for example, maintaining possession of individual authenticators, not loaning or sharing individual authenticators with others, and reporting lost, stolen, or compromised authenticators immediately. Authenticator management includes issuing and revoking, when no longer needed, authenticators for temporary access such as that required for remote maintenance. Device authenticators include, for example, certificates and passwords. Related controls: AC-2, AC-3, AC-6, CM-6, IA-2, IA-4, IA-8, PL-4, PS-5, PS-6, SC-12, SC-13, SC-17, SC-28. References: OMB Memoranda 04-04, 11-11; FIPS Publication 201; NIST Special Publications 800-73, 800-63, 800-76, 800-78; FICAM Roadmap and Implementation Guidance | link | count: 018 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Guest Configuration, Key Vault, Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-5(1) | FedRAMP_High_R4_IA-5(1) | FedRAMP High IA-5 (1) | Identification And Authentication | Password-Based Authentication | Shared | n/a | The information system, for password-based authentication: (a) Enforces minimum password complexity of [Assignment: organization-defined requirements for case sensitivity, number of characters, mix of upper-case letters, lower-case letters, numbers, and special characters, including minimum requirements for each type]; (b) Enforces at least the following number of changed characters when new passwords are created: [Assignment: organization-defined number]; (c) Stores and transmits only encrypted representations of passwords; (d) Enforces password minimum and maximum lifetime restrictions of [Assignment: organization- defined numbers for lifetime minimum, lifetime maximum]; (e) Prohibits password reuse for [Assignment: organization-defined number] generations; and (f) Allows the use of a temporary password for system logons with an immediate change to a permanent password. Supplemental Guidance: This control enhancement applies to single-factor authentication of individuals using passwords as individual or group authenticators, and in a similar manner, when passwords are part of multifactor authenticators. This control enhancement does not apply when passwords are used to unlock hardware authenticators (e.g., Personal Identity Verification cards). The implementation of such password mechanisms may not meet all of the requirements in the enhancement. Encrypted representations of passwords include, for example, encrypted versions of passwords and one-way cryptographic hashes of passwords. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. Password lifetime restrictions do not apply to temporary passwords. Related control: IA-6. | link | count: 015 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Guest Configuration, Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-5(11) | FedRAMP_High_R4_IA-5(11) | FedRAMP High IA-5 (11) | Identification And Authentication | Hardware Token-Based Authentication | Shared | n/a | The information system, for hardware token-based authentication, employs mechanisms that satisfy [Assignment: organization-defined token quality requirements]. Supplemental Guidance: Hardware token-based authentication typically refers to the use of PKI-based tokens, such as the U.S. Government Personal Identity Verification (PIV) card. Organizations define specific requirements for tokens, such as working with a particular PKI. | link | count: 001 Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-5(13) | FedRAMP_High_R4_IA-5(13) | FedRAMP High IA-5 (13) | Identification And Authentication | Expiration Of Cached Authenticators | Shared | n/a | The information system prohibits the use of cached authenticators after [Assignment: organization-defined time period]. | link | count: 001 Enforce expiration of cached authenticators (c7e8ddc1-14aa-1814-7fe1-aad1742b27da) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-5(2) | FedRAMP_High_R4_IA-5(2) | FedRAMP High IA-5 (2) | Identification And Authentication | Pki-Based Authentication | Shared | n/a | The information system, for PKI-based authentication: (a) Validates certifications by constructing and verifying a certification path to an accepted trust anchor including checking certificate status information; (b) Enforces authorized access to the corresponding private key; (c) Maps the authenticated identity to the account of the individual or group; and (d) Implements a local cache of revocation data to support path discovery and validation in case of inability to access revocation information via the network. Supplemental Guidance: Status information for certification paths includes, for example, certificate revocation lists or certificate status protocol responses. For PIV cards, validation of certifications involves the construction and verification of a certification path to the Common Policy Root trust anchor including certificate policy processing. Related control: IA-6. | link | count: 007 Bind authenticators and identities dynamically (6f311b49-9b0d-8c67-3d6e-db80ae528173), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish parameters for searching secret authenticators and verifiers (0065241c-72e9-3b2c-556f-75de66332a94), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Map authenticated identities to individuals (4012c2b7-4e0e-a7ab-1688-4aab43f14420), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-5(3) | FedRAMP_High_R4_IA-5(3) | FedRAMP High IA-5 (3) | Identification And Authentication | In-Person Or Trusted Third-Party Registration | Shared | n/a | The organization requires that the registration process to receive [Assignment: organization- defined types of and/or specific authenticators] be conducted [Selection: in person; by a trusted third party] before [Assignment: organization-defined registration authority] with authorization by [Assignment: organization-defined personnel or roles]. | link | count: 001 Distribute authenticators (098dcde7-016a-06c3-0985-0daaf3301d3a) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-5(4) | FedRAMP_High_R4_IA-5(4) | FedRAMP High IA-5 (4) | Identification And Authentication | Automated Support For Password Strength Determination | Shared | n/a | The organization employs automated tools to determine if password authenticators are sufficiently strong to satisfy [Assignment: organization-defined requirements]. Supplemental Guidance: This control enhancement focuses on the creation of strong passwords and the characteristics of such passwords (e.g., complexity) prior to use, the enforcement of which is carried out by organizational information systems in IA-5 (1). Related controls: CA-2, CA-7, RA-5. | link | count: 003 Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-5(6) | FedRAMP_High_R4_IA-5(6) | FedRAMP High IA-5 (6) | Identification And Authentication | Protection Of Authenticators | Shared | n/a | The organization protects authenticators commensurate with the security category of the information to which use of the authenticator permits access. Supplemental Guidance: For information systems containing multiple security categories of information without reliable physical or logical separation between categories, authenticators used to grant access to the systems are protected commensurate with the highest security category of information on the systems. | link | count: 001 Ensure authorized users protect provided authenticators (37dbe3dc-0e9c-24fa-36f2-11197cbfa207) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-5(7) | FedRAMP_High_R4_IA-5(7) | FedRAMP High IA-5 (7) | Identification And Authentication | No Embedded Unencrypted Static Authenticators | Shared | n/a | The organization ensures that unencrypted static authenticators are not embedded in applications or access scripts or stored on function keys. Supplemental Guidance: Organizations exercise caution in determining whether embedded or stored authenticators are in encrypted or unencrypted form. If authenticators are used in the manner stored, then those representations are considered unencrypted authenticators. This is irrespective of whether that representation is perhaps an encrypted version of something else (e.g., a password). | link | count: 001 Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-6 | FedRAMP_High_R4_IA-6 | FedRAMP High IA-6 | Identification And Authentication | Authenticator Feedback | Shared | n/a | The information system obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. Supplemental Guidance: The feedback from information systems does not provide information that would allow unauthorized individuals to compromise authentication mechanisms. For some types of information systems or system components, for example, desktops/notebooks with relatively large monitors, the threat (often referred to as shoulder surfing) may be significant. For other types of systems or components, for example, mobile devices with 2-4 inch screens, this threat may be less significant, and may need to be balanced against the increased likelihood of typographic input errors due to the small keyboards. Therefore, the means for obscuring the authenticator feedback is selected accordingly. Obscuring the feedback of authentication information includes, for example, displaying asterisks when users type passwords into input devices, or displaying feedback for a very limited time before fully obscuring it. Related control: PE-18. Control Enhancements: None. References: None. | link | count: 001 Obscure feedback information during authentication process (1ff03f2a-974b-3272-34f2-f6cd51420b30) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-7 | FedRAMP_High_R4_IA-7 | FedRAMP High IA-7 | Identification And Authentication | Cryptographic Module Authentication | Shared | n/a | The information system implements mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication. Supplemental Guidance: Authentication mechanisms may be required within a cryptographic module to authenticate an operator accessing the module and to verify that the operator is authorized to assume the requested role and perform services within that role. Related controls: SC-12, SC-13. Control Enhancements: None. References: FIPS Publication 140; Web: csrc.nist.gov/groups/STM/cmvp/index.html. | link | count: 001 Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-8 | FedRAMP_High_R4_IA-8 | FedRAMP High IA-8 | Identification And Authentication | Identification And Authentication (Non- Organizational Users) | Shared | n/a | The information system uniquely identifies and authenticates non-organizational users (or processes acting on behalf of non-organizational users). Supplemental Guidance: Non-organizational users include information system users other than organizational users explicitly covered by IA-2. These individuals are uniquely identified and authenticated for accesses other than those accesses explicitly identified and documented in AC-14. In accordance with the E-Authentication E-Government initiative, authentication of non- organizational users accessing federal information systems may be required to protect federal, proprietary, or privacy-related information (with exceptions noted for national security systems). Organizations use risk assessments to determine authentication needs and consider scalability, practicality, and security in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk. IA-2 addresses identification and authentication requirements for access to information systems by organizational users. Related controls: AC-2, AC-14, AC-17, AC-18, IA-2, IA-4, IA-5, MA-4, RA-3, SA-12, SC-8. References: OMB Memoranda 04-04, 11-11, 10-06-2011; FICAM Roadmap and Implementation Guidance; FIPS Publication 201; NIST Special Publications 800-63, 800-116; National Strategy for Trusted Identities in Cyberspace; Web: http://idmanagement.gov. | link | count: 001 Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-8(1) | FedRAMP_High_R4_IA-8(1) | FedRAMP High IA-8 (1) | Identification And Authentication | Acceptance Of Piv Credentials From Other Agencies | Shared | n/a | The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials from other federal agencies. Supplemental Guidance: This control enhancement applies to logical access control systems (LACS) and physical access control systems (PACS). Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 requires federal agencies to continue implementing the requirements specified in HSPD-12 to enable agency-wide use of PIV credentials. Related controls: AU-2, PE-3, SA-4. | link | count: 001 Accept PIV credentials (55be3260-a7a2-3c06-7fe6-072d07525ab7) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-8(2) | FedRAMP_High_R4_IA-8(2) | FedRAMP High IA-8 (2) | Identification And Authentication | Acceptance Of Third-Party Credentials | Shared | n/a | The information system accepts only FICAM-approved third-party credentials. Supplemental Guidance: This control enhancement typically applies to organizational information systems that are accessible to the general public, for example, public-facing websites. Third-party credentials are those credentials issued by nonfederal government entities approved by the Federal Identity, Credential, and Access Management (FICAM) Trust Framework Solutions initiative. Approved third-party credentials meet or exceed the set of minimum federal government-wide technical, security, privacy, and organizational maturity requirements. This allows federal government relying parties to trust such credentials at their approved assurance levels. Related control: AU-2. | link | count: 001 Accept only FICAM-approved third-party credentials (2d2ca910-7957-23ee-2945-33f401606efc) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-8(3) | FedRAMP_High_R4_IA-8(3) | FedRAMP High IA-8 (3) | Identification And Authentication | Use Of Ficam-Approved Products | Shared | n/a | The organization employs only FICAM-approved information system components in [Assignment: organization-defined information systems] to accept third-party credentials. Supplemental Guidance: This control enhancement typically applies to information systems that are accessible to the general public, for example, public-facing websites. FICAM-approved information system components include, for example, information technology products and software libraries that have been approved by the Federal Identity, Credential, and Access Management conformance program. Related control: SA-4. | link | count: 001 Employ FICAM-approved resources to accept third-party credentials (db8b35d6-8adb-3f51-44ff-c648ab5b1530) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IA-8(4) | FedRAMP_High_R4_IA-8(4) | FedRAMP High IA-8 (4) | Identification And Authentication | Use Of Ficam-Issued Profiles | Shared | n/a | The information system conforms to FICAM-issued profiles. Supplemental Guidance: This control enhancement addresses open identity management standards. To ensure that these standards are viable, robust, reliable, sustainable (e.g., available in commercial information technology products), and interoperable as documented, the United States Government assesses and scopes identity management standards and technology implementations against applicable federal legislation, directives, policies, and requirements. The result is FICAM-issued implementation profiles of approved protocols (e.g., FICAM authentication protocols such as SAML 2.0 and OpenID 2.0, as well as other protocols such as the FICAM Backend Attribute Exchange). Related control: SA-4. | link | count: 001 Conform to FICAM-issued profiles (a8df9c78-4044-98be-2c05-31a315ac8957) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-1 | FedRAMP_High_R4_IR-1 | FedRAMP High IR-1 | Incident Response | Incident Response Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An incident response policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the incident response policy and associated incident response controls; and b. Reviews and updates the current: 1. Incident response policy [Assignment: organization-defined frequency]; and 2. Incident response procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the IR family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-61, 800-83, 800-100. | link | count: 001 Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-2 | FedRAMP_High_R4_IR-2 | FedRAMP High IR-2 | Incident Response | Incident Response Training | Shared | n/a | The organization provides incident response training to information system users consistent with assigned roles and responsibilities: a. Within [Assignment: organization-defined time period] of assuming an incident response role or responsibility; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Incident response training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure the appropriate content and level of detail is included in such training. For example, regular users may only need to know who to call or how to recognize an incident on the information system; system administrators may require additional training on how to handle/remediate incidents; and incident responders may receive more specific training on forensics, reporting, system recovery, and restoration. Incident response training includes user training in the identification and reporting of suspicious activities, both from external and internal sources. Related controls: AT-3, CP-3, IR-8. References: NIST Special Publications 800-16, 800-50. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-2(1) | FedRAMP_High_R4_IR-2(1) | FedRAMP High IR-2 (1) | Incident Response | Simulated Events | Shared | n/a | The organization incorporates simulated events into incident response training to facilitate effective response by personnel in crisis situations. | link | count: 001 Incorporate simulated events into incident response training (1fdeb7c4-4c93-8271-a135-17ebe85f1cc7) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-2(2) | FedRAMP_High_R4_IR-2(2) | FedRAMP High IR-2 (2) | Incident Response | Automated Training Environments | Shared | n/a | The organization employs automated mechanisms to provide a more thorough and realistic incident response training environment. | link | count: 001 Employ automated training environment (c8aa992d-76b7-7ca0-07b3-31a58d773fa9) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-3 | FedRAMP_High_R4_IR-3 | FedRAMP High IR-3 | Incident Response | Incident Response Testing | Shared | n/a | The organization tests the incident response capability for the information system [Assignment: organization-defined frequency] using [Assignment: organization-defined tests] to determine the incident response effectiveness and documents the results. Supplemental Guidance: Organizations test incident response capabilities to determine the overall effectiveness of the capabilities and to identify potential weaknesses or deficiencies. Incident response testing includes, for example, the use of checklists, walk-through or tabletop exercises, simulations (parallel/full interrupt), and comprehensive exercises. Incident response testing can also include a determination of the effects on organizational operations (e.g., reduction in mission capabilities), organizational assets, and individuals due to incident response. Related controls: CP-4, IR-8. References: NIST Special Publications 800-84, 800-115. | link | count: 003 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-3(2) | FedRAMP_High_R4_IR-3(2) | FedRAMP High IR-3 (2) | Incident Response | Coordination With Related Plans | Shared | n/a | The organization coordinates incident response testing with organizational elements responsible for related plans. Supplemental Guidance: Organizational plans related to incident response testing include, for example, Business Continuity Plans, Contingency Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, and Occupant Emergency Plans. | link | count: 003 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-4 | FedRAMP_High_R4_IR-4 | FedRAMP High IR-4 | Incident Response | Incident Handling | Shared | n/a | The organization: a. Implements an incident handling capability for security incidents that includes preparation, detection and analysis, containment, eradication, and recovery; b. Coordinates incident handling activities with contingency planning activities; and c. Incorporates lessons learned from ongoing incident handling activities into incident response procedures, training, and testing/exercises, and implements the resulting changes accordingly. Supplemental Guidance: Organizations recognize that incident response capability is dependent on the capabilities of organizational information systems and the mission/business processes being supported by those systems. Therefore, organizations consider incident response as part of the definition, design, and development of mission/business processes and information systems. Incident-related information can be obtained from a variety of sources including, for example, audit monitoring, network monitoring, physical access monitoring, user/administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including, for example, mission/business owners, information system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive (function). Related controls: AU-6, CM-6, CP-2, CP-4, IR-2, IR-3, IR-8, PE-6, SC-5, SC-7, SI-3, SI-4, SI-7. References: Executive Order 13587; NIST Special Publication 800-61. | link | count: 024 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance, Security Center, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-4(1) | FedRAMP_High_R4_IR-4(1) | FedRAMP High IR-4 (1) | Incident Response | Automated Incident Handling Processes | Shared | n/a | The organization employs automated mechanisms to support the incident handling process. Supplemental Guidance: Automated mechanisms supporting incident handling processes include, for example, online incident management systems. | link | count: 003 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-4(2) | FedRAMP_High_R4_IR-4(2) | FedRAMP High IR-4 (2) | Incident Response | Dynamic Reconfiguration | Shared | n/a | The organization includes dynamic reconfiguration of [Assignment: organization-defined information system components] as part of the incident response capability. Supplemental Guidance: Dynamic reconfiguration includes, for example, changes to router rules, access control lists, intrusion detection/prevention system parameters, and filter rules for firewalls and gateways. Organizations perform dynamic reconfiguration of information systems, for example, to stop attacks, to misdirect attackers, and to isolate components of systems, thus limiting the extent of the damage from breaches or compromises. Organizations include time frames for achieving the reconfiguration of information systems in the definition of the reconfiguration capability, considering the potential need for rapid response in order to effectively address sophisticated cyber threats. Related controls: AC-2, AC-4, AC-16, CM-2, CM-3, CM-4. | link | count: 001 Include dynamic reconfig of customer deployed resources (1e0d5ba8-a433-01aa-829c-86b06c9631ec) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-4(3) | FedRAMP_High_R4_IR-4(3) | FedRAMP High IR-4 (3) | Incident Response | Continuity Of Operations | Shared | n/a | The organization identifies [Assignment: organization-defined classes of incidents] and [Assignment: organization-defined actions to take in response to classes of incidents] to ensure continuation of organizational missions and business functions. Supplemental Guidance: Classes of incidents include, for example, malfunctions due to design/implementation errors and omissions, targeted malicious attacks, and untargeted malicious attacks. Appropriate incident response actions include, for example, graceful degradation, information system shutdown, fall back to manual mode/alternative technology whereby the system operates differently, employing deceptive measures, alternate information flows, or operating in a mode that is reserved solely for when systems are under attack. | link | count: 001 Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-4(4) | FedRAMP_High_R4_IR-4(4) | FedRAMP High IR-4 (4) | Incident Response | Information Correlation | Shared | n/a | The organization correlates incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response. Supplemental Guidance: Sometimes the nature of a threat event, for example, a hostile cyber attack, is such that it can only be observed by bringing together information from different sources including various reports and reporting procedures established by organizations. | link | count: 001 Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-4(6) | FedRAMP_High_R4_IR-4(6) | FedRAMP High IR-4 (6) | Incident Response | Insider Threats - Specific Capabilities | Shared | n/a | The organization implements incident handling capability for insider threats. Supplemental Guidance: While many organizations address insider threat incidents as an inherent part of their organizational incident response capability, this control enhancement provides additional emphasis on this type of threat and the need for specific incident handling capabilities (as defined within organizations) to provide appropriate and timely responses. | link | count: 001 Implement Incident handling capability (98e33927-8d7f-6d5f-44f5-2469b40b7215) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-4(8) | FedRAMP_High_R4_IR-4(8) | FedRAMP High IR-4 (8) | Incident Response | Correlation With External Organizations | Shared | n/a | The organization coordinates with [Assignment: organization-defined external organizations] to correlate and share [Assignment: organization-defined incident information] to achieve a cross- organization perspective on incident awareness and more effective incident responses. Supplemental Guidance: The coordination of incident information with external organizations including, for example, mission/business partners, military/coalition partners, customers, and multitiered developers, can provide significant benefits. Cross-organizational coordination with respect to incident handling can serve as an important risk management capability. This capability allows organizations to leverage critical information from a variety of sources to effectively respond to information security-related incidents potentially affecting the organization’s operations, assets, and individuals. | link | count: 001 Coordinate with external organizations to achieve cross org perspective (d4e6a629-28eb-79a9-000b-88030e4823ca) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-5 | FedRAMP_High_R4_IR-5 | FedRAMP High IR-5 | Incident Response | Incident Monitoring | Shared | n/a | The organization tracks and documents information system security incidents. Supplemental Guidance: Documenting information system security incidents includes, for example, maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics, evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources including, for example, incident reports, incident response teams, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports. Related controls: AU-6, IR-8, PE-6, SC-5, SC-7, SI-3, SI-4, SI-7. References: NIST Special Publication 800-61. | link | count: 013 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-6(1) | FedRAMP_High_R4_IR-6(1) | FedRAMP High IR-6 (1) | Incident Response | Automated Reporting | Shared | n/a | The organization employs automated mechanisms to assist in the reporting of security incidents. Supplemental Guidance: Related control: IR-7. | link | count: 001 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-7 | FedRAMP_High_R4_IR-7 | FedRAMP High IR-7 | Incident Response | Incident Response Assistance | Shared | n/a | The organization provides an incident response support resource, integral to the organizational incident response capability that offers advice and assistance to users of the information system for the handling and reporting of security incidents. Supplemental Guidance: Incident response support resources provided by organizations include, for example, help desks, assistance groups, and access to forensics services, when required. Related controls: AT-2, IR-4, IR-6, IR-8, SA-9. | link | count: 001 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-7(1) | FedRAMP_High_R4_IR-7(1) | FedRAMP High IR-7 (1) | Incident Response | Automation Support For Availability Of Information / Support | Shared | n/a | The organization employs automated mechanisms to increase the availability of incident response- related information and support. Supplemental Guidance: Automated mechanisms can provide a push and/or pull capability for users to obtain incident response assistance. For example, individuals might have access to a website to query the assistance capability, or conversely, the assistance capability may have the ability to proactively send information to users (general distribution or targeted) as part of increasing understanding of current response capabilities and support. | link | count: 007 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-7(2) | FedRAMP_High_R4_IR-7(2) | FedRAMP High IR-7 (2) | Incident Response | Coordination With External Providers | Shared | n/a | The organization: (a) Establishes a direct, cooperative relationship between its incident response capability and external providers of information system protection capability; and (b) Identifies organizational incident response team members to the external providers. Supplemental Guidance: External providers of information system protection capability include, for example, the Computer Network Defense program within the U.S. Department of Defense. External providers help to protect, monitor, analyze, detect, and respond to unauthorized activity within organizational information systems and networks. | link | count: 002 Establish relationship between incident response capability and external providers (b470a37a-7a47-3792-34dd-7a793140702e), Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-8 | FedRAMP_High_R4_IR-8 | FedRAMP High IR-8 | Incident Response | Incident Response Plan | Shared | n/a | The organization: a. Develops an incident response plan that: 1. Provides the organization with a roadmap for implementing its incident response capability; 2. Describes the structure and organization of the incident response capability; 3. Provides a high-level approach for how the incident response capability fits into the overall organization; 4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions; 5. Defines reportable incidents; 6. Provides metrics for measuring the incident response capability within the organization; 7. Defines the resources and management support needed to effectively maintain and mature an incident response capability; and 8. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; b. Distributes copies of the incident response plan to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; c. Reviews the incident response plan [Assignment: organization-defined frequency]; d. Updates the incident response plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing; e. Communicates incident response plan changes to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and f. Protects the incident response plan from unauthorized disclosure and modification. Supplemental Guidance: It is important that organizations develop and implement a coordinated approach to incident response. Organizational missions, business functions, strategies, goals, and objectives for incident response help to determine the structure of incident response capabilities. As part of a comprehensive incident response capability, organizations consider the coordination and sharing of information with external organizations, including, for example, external service providers and organizations involved in the supply chain for organizational information systems. Related controls: MP-2, MP-4, MP-5. Control Enhancements: None. References: NIST Special Publication 800-61. | link | count: 006 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-9 | FedRAMP_High_R4_IR-9 | FedRAMP High IR-9 | Incident Response | Information Spillage Response | Shared | n/a | The organization responds to information spills by: a. Identifying the specific information involved in the information system contamination; b. Alerting [Assignment: organization-defined personnel or roles] of the information spill using a method of communication not associated with the spill; c. Isolating the contaminated information system or system component; d. Eradicating the information from the contaminated information system or component; e. Identifying other information systems or system components that may have been subsequently contaminated; and f. Performing other [Assignment: organization-defined actions]. Supplemental Guidance: Information spillage refers to instances where either classified or sensitive information is inadvertently placed on information systems that are not authorized to process such information. Such information spills often occur when information that is initially thought to be of lower sensitivity is transmitted to an information system and then is subsequently determined to be of higher sensitivity. At that point, corrective action is required. The nature of the organizational response is generally based upon the degree of sensitivity of the spilled information (e.g., security category or classification level), the security capabilities of the information system, the specific nature of contaminated storage media, and the access authorizations (e.g., security clearances) of individuals with authorized access to the contaminated system. The methods used to communicate information about the spill after the fact do not involve methods directly associated with the actual spill to minimize the risk of further spreading the contamination before such contamination is isolated and eradicated. References: None. | link | count: 007 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify contaminated systems and components (279052a0-8238-694d-9661-bf649f951747), Identify spilled information (69d90ee6-9f9f-262a-2038-d909fb4e5723), Isolate information spills (22457e81-3ec6-5271-a786-c3ca284601dd) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-9(1) | FedRAMP_High_R4_IR-9(1) | FedRAMP High IR-9 (1) | Incident Response | Responsible Personnel | Shared | n/a | The organization assigns [Assignment: organization-defined personnel or roles] with responsibility for responding to information spills. | link | count: 001 Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-9(2) | FedRAMP_High_R4_IR-9(2) | FedRAMP High IR-9 (2) | Incident Response | Training | Shared | n/a | The organization provides information spillage response training [Assignment: organization- defined frequency]. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-9(3) | FedRAMP_High_R4_IR-9(3) | FedRAMP High IR-9 (3) | Incident Response | Post-Spill Operations | Shared | n/a | The organization implements [Assignment: organization-defined procedures] to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions. Supplemental Guidance: Correction actions for information systems contaminated due to information spillages may be very time-consuming. During those periods, personnel may not have access to the contaminated systems, which may potentially affect their ability to conduct organizational business. | link | count: 001 Develop spillage response procedures (bb048641-6017-7272-7772-a008f285a520) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | IR-9(4) | FedRAMP_High_R4_IR-9(4) | FedRAMP High IR-9 (4) | Incident Response | Exposure To Unauthorized Personnel | Shared | n/a | The organization employs [Assignment: organization-defined security safeguards] for personnel exposed to information not within assigned access authorizations. Supplemental Guidance: Security safeguards include, for example, making personnel exposed to spilled information aware of the federal laws, directives, policies, and/or regulations regarding the information and the restrictions imposed based on exposure to such information. | link | count: 001 Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-1 | FedRAMP_High_R4_MA-1 | FedRAMP High MA-1 | Maintenance | System Maintenance Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls; and b. Reviews and updates the current: 1. System maintenance policy [Assignment: organization-defined frequency]; and 2. System maintenance procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the MA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-2 | FedRAMP_High_R4_MA-2 | FedRAMP High MA-2 | Maintenance | Controlled Maintenance | Shared | n/a | The organization: a. Schedules, performs, documents, and reviews records of maintenance and repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements; b. Approves and monitors all maintenance activities, whether performed on site or remotely and whether the equipment is serviced on site or removed to another location; c. Requires that [Assignment: organization-defined personnel or roles] explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs; d. Sanitizes equipment to remove all information from associated media prior to removal from organizational facilities for off-site maintenance or repairs; e. Checks all potentially impacted security controls to verify that the controls are still functioning properly following maintenance or repair actions; and f. Includes [Assignment: organization-defined maintenance-related information] in organizational maintenance records. Supplemental Guidance: This control addresses the information security aspects of the information system maintenance program and applies to all types of maintenance to any system component (including applications) conducted by any local or nonlocal entity (e.g., in-contract, warranty, in- house, software maintenance agreement). System maintenance also includes those components not directly associated with information processing and/or data/information retention such as scanners, copiers, and printers. Information necessary for creating effective maintenance records includes, for example: (i) date and time of maintenance; (ii) name of individuals or group performing the maintenance; (iii) name of escort, if necessary; (iv) a description of the maintenance performed; and (v) information system components/equipment removed or replaced (including identification numbers, if applicable). The level of detail included in maintenance records can be informed by the security categories of organizational information systems. Organizations consider supply chain issues associated with replacement components for information systems. Related controls: CM-3, CM-4, MA-4, MP-6, PE-16, SA-12, SI-2. References: None. | link | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-2(2) | FedRAMP_High_R4_MA-2(2) | FedRAMP High MA-2 (2) | Maintenance | Automated Maintenance Activities | Shared | n/a | The organization: (a) Employs automated mechanisms to schedule, conduct, and document maintenance and repairs; and (b) Produces up-to date, accurate, and complete records of all maintenance and repair actions requested, scheduled, in process, and completed. Supplemental Guidance: Related controls: CA-7, MA-3. References: None. | link | count: 002 Automate remote maintenance activities (b8587fce-138f-86e8-33a3-c60768bf1da6), Produce complete records of remote maintenance activities (74041cfe-3f87-1d17-79ec-34ca5f895542) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-3 | FedRAMP_High_R4_MA-3 | FedRAMP High MA-3 | Maintenance | Maintenance Tools | Shared | n/a | The organization approves, controls, and monitors information system maintenance tools. Supplemental Guidance: This control addresses security-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems. Maintenance tools can include hardware, software, and firmware items. Maintenance tools are potential vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and subsequently into organizational information systems. Maintenance tools can include, for example, hardware/software diagnostic test equipment and hardware/software packet sniffers. This control does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing “ping,” “ls,” “ipconfig,” or the hardware and software implementing the monitoring port of an Ethernet switch. Related controls: MA-2, MA-5, MP-6. References: NIST Special Publication 800-88. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-3(1) | FedRAMP_High_R4_MA-3(1) | FedRAMP High MA-3 (1) | Maintenance | Inspect Tools | Shared | n/a | The organization inspects the maintenance tools carried into a facility by maintenance personnel for improper or unauthorized modifications. Supplemental Guidance: If, upon inspection of maintenance tools, organizations determine that the tools have been modified in an improper/unauthorized manner or contain malicious code, the incident is handled consistent with organizational policies and procedures for incident handling. Related control: SI-7. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-3(2) | FedRAMP_High_R4_MA-3(2) | FedRAMP High MA-3 (2) | Maintenance | Inspect Media | Shared | n/a | The organization checks media containing diagnostic and test programs for malicious code before the media are used in the information system. Supplemental Guidance: If, upon inspection of media containing maintenance diagnostic and test programs, organizations determine that the media contain malicious code, the incident is handled consistent with organizational incident handling policies and procedures. Related control: SI-3. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-3(3) | FedRAMP_High_R4_MA-3(3) | FedRAMP High MA-3 (3) | Maintenance | Prevent Unauthorized Removal | Shared | n/a | The organization prevents the unauthorized removal of maintenance equipment containing organizational information by: (a) Verifying that there is no organizational information contained on the equipment; (b) Sanitizing or destroying the equipment; (c) Retaining the equipment within the facility; or (d) Obtaining an exemption from [Assignment: organization-defined personnel or roles] explicitly authorizing removal of the equipment from the facility. Supplemental Guidance: Organizational information includes all information specifically owned by organizations and information provided to organizations in which organizations serve as information stewards. | link | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-4 | FedRAMP_High_R4_MA-4 | FedRAMP High MA-4 | Maintenance | Nonlocal Maintenance | Shared | n/a | The organization: a. Approves and monitors nonlocal maintenance and diagnostic activities; b. Allows the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the information system; c. Employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions; d. Maintains records for nonlocal maintenance and diagnostic activities; and e. Terminates session and network connections when nonlocal maintenance is completed. Supplemental Guidance: Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Authentication techniques used in the establishment of nonlocal maintenance and diagnostic sessions reflect the network access requirements in IA-2. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric. Enforcing requirements in MA-4 is accomplished in part by other controls. Related controls: AC-2, AC-3, AC-6, AC-17, AU-2, AU-3, IA-2, IA-4, IA-5, IA-8, MA-2, MA-5, MP-6, PL-2, SC-7, SC-10, SC-17. References: FIPS Publications 140-2, 197, 201; NIST Special Publications 800-63, 800-88; CNSS Policy 15. | link | count: 001 Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-4(2) | FedRAMP_High_R4_MA-4(2) | FedRAMP High MA-4 (2) | Maintenance | Document Nonlocal Maintenance | Shared | n/a | The organization documents in the security plan for the information system, the policies and procedures for the establishment and use of nonlocal maintenance and diagnostic connections. | link | count: 001 Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-4(3) | FedRAMP_High_R4_MA-4(3) | FedRAMP High MA-4 (3) | Maintenance | Comparable Security / Sanitization | Shared | n/a | The organization: (a) Requires that nonlocal maintenance and diagnostic services be performed from an information system that implements a security capability comparable to the capability implemented on the system being serviced; or (b) Removes the component to be serviced from the information system and prior to nonlocal maintenance or diagnostic services, sanitizes the component (with regard to organizational information) before removal from organizational facilities, and after the service is performed, inspects and sanitizes the component (with regard to potentially malicious software) before reconnecting the component to the information system. Supplemental Guidance: Comparable security capability on information systems, diagnostic tools, and equipment providing maintenance services implies that the implemented security controls on those systems, tools, and equipment are at least as comprehensive as the controls on the information system being serviced. Related controls: MA-3, SA-12, SI-3, SI-7. | link | count: 001 Perform all non-local maintenance (5bac5fb7-7735-357b-767d-02264bfe5c3b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-4(6) | FedRAMP_High_R4_MA-4(6) | FedRAMP High MA-4 (6) | Maintenance | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications. Supplemental Guidance: Related controls: SC-8, SC-13. | link | count: 001 Implement cryptographic mechanisms (10c3a1b1-29b0-a2d5-8f4c-a284b0f07830) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-5 | FedRAMP_High_R4_MA-5 | FedRAMP High MA-5 | Maintenance | Maintenance Personnel | Shared | n/a | The organization: a. Establishes a process for maintenance personnel authorization and maintains a list of authorized maintenance organizations or personnel; b. Ensures that non-escorted personnel performing maintenance on the information system have required access authorizations; and c. Designates organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations. Supplemental Guidance: This control applies to individuals performing hardware or software maintenance on organizational information systems, while PE-2 addresses physical access for individuals whose maintenance duties place them within the physical protection perimeter of the systems (e.g., custodial staff, physical plant maintenance personnel). Technical competence of supervising individuals relates to the maintenance performed on the information systems while having required access authorizations refers to maintenance on and near the systems. Individuals not previously identified as authorized maintenance personnel, such as information technology manufacturers, vendors, systems integrators, and consultants, may require privileged access to organizational information systems, for example, when required to conduct maintenance activities with little or no notice. Based on organizational assessments of risk, organizations may issue temporary credentials to these individuals. Temporary credentials may be for one-time use or for very limited time periods. Related controls: AC-2, IA-8, MP-2, PE-2, PE-3, PE-4, RA-3. References: None. | link | count: 003 Designate personnel to supervise unauthorized maintenance activities (7a489c62-242c-5db9-74df-c073056d6fa3), Maintain list of authorized remote maintenance personnel (4ce91e4e-6dab-3c46-011a-aa14ae1561bf), Manage maintenance personnel (b273f1e3-79e7-13ee-5b5d-dca6c66c3d5d) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-5(1) | FedRAMP_High_R4_MA-5(1) | FedRAMP High MA-5 (1) | Maintenance | Individuals Without Appropriate Access | Shared | n/a | The organization: (a) Implements procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements: (1) Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the information system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified; (2) Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the information system are sanitized and all nonvolatile storage media are removed or physically disconnected from the system and secured; and (b) Develops and implements alternate security safeguards in the event an information system component cannot be sanitized, removed, or disconnected from the system. Supplemental Guidance: This control enhancement denies individuals who lack appropriate security clearances (i.e., individuals who do not possess security clearances or possess security clearances at a lower level than required) or who are not U.S. citizens, visual and electronic access to any classified information, Controlled Unclassified Information (CUI), or any other sensitive information contained on organizational information systems. Procedures for the use of maintenance personnel can be documented in security plans for the information systems. Related controls: MP-6, PL-2. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MA-6 | FedRAMP_High_R4_MA-6 | FedRAMP High MA-6 | Maintenance | Timely Maintenance | Shared | n/a | The organization obtains maintenance support and/or spare parts for [Assignment: organization-defined information system components] within [Assignment: organization-defined time period] of failure. Supplemental Guidance: Organizations specify the information system components that result in increased risk to organizational operations and assets, individuals, other organizations, or the Nation when the functionality provided by those components is not operational. Organizational actions to obtain maintenance support typically include having appropriate contracts in place. Related controls: CM-8, CP-2, CP-7, SA-14, SA-15. References: None. | link | count: 001 Provide timely maintenance support (eb598832-4bcc-658d-4381-3ecbe17b9866) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-1 | FedRAMP_High_R4_MP-1 | FedRAMP High MP-1 | Media Protection | Media Protection Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A media protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the media protection policy and associated media protection controls; and b. Reviews and updates the current: 1. Media protection policy [Assignment: organization-defined frequency]; and 2. Media protection procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the MP family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-2 | FedRAMP_High_R4_MP-2 | FedRAMP High MP-2 | Media Protection | Media Access | Shared | n/a | The organization restricts access to [Assignment: organization-defined types of digital and/or non-digital media] to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Restricting non-digital media access includes, for example, denying access to patient medical records in a community hospital unless the individuals seeking access to such records are authorized healthcare providers. Restricting access to digital media includes, for example, limiting access to design specifications stored on compact disks in the media library to the project leader and the individuals on the development team. Related controls: AC-3, IA-2, MP-4, PE-2, PE-3, PL-2. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-3 | FedRAMP_High_R4_MP-3 | FedRAMP High MP-3 | Media Protection | Media Marking | Shared | n/a | The organization: a. Marks information system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and b. Exempts [Assignment: organization-defined types of information system media] from marking as long as the media remain within [Assignment: organization-defined controlled areas]. Supplemental Guidance: The term security marking refers to the application/use of human-readable security attributes. The term security labeling refers to the application/use of security attributes with regard to internal data structures within information systems (see AC-16). Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Security marking is generally not required for media containing information determined by organizations to be in the public domain or to be publicly releasable. However, some organizations may require markings for public information indicating that the information is publicly releasable. Marking of information system media reflects applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Related controls: AC-16, PL-2, RA-3. Control Enhancements: None. References: FIPS Publication 199. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-4 | FedRAMP_High_R4_MP-4 | FedRAMP High MP-4 | Media Protection | Media Storage | Shared | n/a | The organization: a. Physically controls and securely stores [Assignment: organization-defined types of digital and/or non-digital media] within [Assignment: organization-defined controlled areas]; and b. Protects information system media until the media are destroyed or sanitized using approved equipment, techniques, and procedures. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Physically controlling information system media includes, for example, conducting inventories, ensuring procedures are in place to allow individuals to check out and return media to the media library, and maintaining accountability for all stored media. Secure storage includes, for example, a locked drawer, desk, or cabinet, or a controlled media library. The type of media storage is commensurate with the security category and/or classification of the information residing on the media. Controlled areas are areas for which organizations provide sufficient physical and procedural safeguards to meet the requirements established for protecting information and/or information systems. For media containing information determined by organizations to be in the public domain, to be publicly releasable, or to have limited or no adverse impact on organizations or individuals if accessed by other than authorized personnel, fewer safeguards may be needed. In these situations, physical access controls provide adequate protection. Related controls: CP-6, CP-9, MP-2, MP-7, PE-3. References: FIPS Publication 199; NIST Special Publications 800-56, 800-57, 800-111. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-5 | FedRAMP_High_R4_MP-5 | FedRAMP High MP-5 | Media Protection | Media Transport | Shared | n/a | The organization: a. Protects and controls [Assignment: organization-defined types of information system media] during transport outside of controlled areas using [Assignment: organization-defined security safeguards]; b. Maintains accountability for information system media during transport outside of controlled areas; c. Documents activities associated with the transport of information system media; and d. Restricts the activities associated with the transport of information system media to authorized personnel. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. This control also applies to mobile devices with information storage capability (e.g., smart phones, tablets, E-readers), that are transported outside of controlled areas. Controlled areas are areas or spaces for which organizations provide sufficient physical and/or procedural safeguards to meet the requirements established for protecting information and/or information systems. Physical and technical safeguards for media are commensurate with the security category or classification of the information residing on the media. Safeguards to protect media during transport include, for example, locked containers and cryptography. Cryptographic mechanisms can provide confidentiality and integrity protections depending upon the mechanisms used. Activities associated with transport include the actual transport as well as those activities such as releasing media for transport and ensuring that media enters the appropriate transport processes. For the actual transport, authorized transport and courier personnel may include individuals from outside the organization (e.g., U.S. Postal Service or a commercial transport or delivery service). Maintaining accountability of media during transport includes, for example, restricting transport activities to authorized personnel, and tracking and/or obtaining explicit records of transport activities as the media moves through the transportation system to prevent and detect loss, destruction, or tampering. Organizations establish documentation requirements for activities associated with the transport of information system media in accordance with organizational assessments of risk to include the flexibility to define different record-keeping methods for the different types of media transport as part of an overall system of transport-related records. Related controls: AC-19, CP-9, MP-3, MP-4, RA-3, SC-8, SC-13, SC-28. References: FIPS Publication 199; NIST Special Publication 800-60. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-5(4) | FedRAMP_High_R4_MP-5(4) | FedRAMP High MP-5 (4) | Media Protection | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to protect the confidentiality and integrity of information stored on digital media during transport outside of controlled areas. Supplemental Guidance: This control enhancement applies to both portable storage devices (e.g., USB memory sticks, compact disks, digital video disks, external/removable hard disk drives) and mobile devices with storage capability (e.g., smart phones, tablets, E-readers). Related control: MP-2. References: FIPS Publication 199; NIST Special Publication 800-60. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-6 | FedRAMP_High_R4_MP-6 | FedRAMP High MP-6 | Media Protection | Media Sanitization | Shared | n/a | The organization: a. Sanitizes [Assignment: organization-defined information system media] prior to disposal, release out of organizational control, or release for reuse using [Assignment: organization- defined sanitization techniques and procedures] in accordance with applicable federal and organizational standards and policies; and b. Employs sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information. Supplemental Guidance: This control applies to all information system media, both digital and non- digital, subject to disposal or reuse, whether or not the media is considered removable. Examples include media found in scanners, copiers, printers, notebook computers, workstations, network components, and mobile devices. The sanitization process removes information from the media such that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, cryptographic erase, and destruction, prevent the disclosure of information to unauthorized individuals when such media is reused or released for disposal. Organizations determine the appropriate sanitization methods recognizing that destruction is sometimes necessary when other methods cannot be applied to media requiring sanitization. Organizations use discretion on the employment of approved sanitization techniques and procedures for media containing information deemed to be in the public domain or publicly releasable, or deemed to have no adverse impact on organizations or individuals if released for reuse or disposal. Sanitization of non-digital media includes, for example, removing a classified appendix from an otherwise unclassified document, or redacting selected sections or words from a document by obscuring the redacted sections/words in a manner equivalent in effectiveness to removing them from the document. NSA standards and policies control the sanitization process for media containing classified information. Related controls: MA-2, MA-4, RA-3, SC-4. References: FIPS Publication 199; NIST Special Publications 800-60, 800-88; Web: http://www.nsa.gov/ia/mitigation_guidance/media_destruction_guidance/index.shtml. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-6(1) | FedRAMP_High_R4_MP-6(1) | FedRAMP High MP-6 (1) | Media Protection | Review / Approve / Track / Document / Verify | Shared | n/a | The organization reviews, approves, tracks, documents, and verifies media sanitization and disposal actions. Supplemental Guidance: Organizations review and approve media to be sanitized to ensure compliance with records-retention policies. Tracking/documenting actions include, for example, listing personnel who reviewed and approved sanitization and disposal actions, types of media sanitized, specific files stored on the media, sanitization methods used, date and time of the sanitization actions, personnel who performed the sanitization, verification actions taken, personnel who performed the verification, and disposal action taken. Organizations verify that the sanitization of the media was effective prior to disposal. Related control: SI-12. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-6(2) | FedRAMP_High_R4_MP-6(2) | FedRAMP High MP-6 (2) | Media Protection | Equipment Testing | Shared | n/a | The organization tests sanitization equipment and procedures [Assignment: organization-defined frequency] to verify that the intended sanitization is being achieved. Supplemental Guidance: Testing of sanitization equipment and procedures may be conducted by qualified and authorized external entities (e.g., other federal agencies or external service providers). | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-7 | FedRAMP_High_R4_MP-7 | FedRAMP High MP-7 | Media Protection | Media Use | Shared | n/a | The organization [Selection: restricts; prohibits] the use of [Assignment: organization- defined types of information system media] on [Assignment: organization-defined information systems or system components] using [Assignment: organization-defined security safeguards]. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. This control also applies to mobile devices with information storage capability (e.g., smart phones, tablets, E-readers). In contrast to MP-2, which restricts user access to media, this control restricts the use of certain types of media on information systems, for example, restricting/prohibiting the use of flash drives or external hard disk drives. Organizations can employ technical and nontechnical safeguards (e.g., policies, procedures, rules of behavior) to restrict the use of information system media. Organizations may restrict the use of portable storage devices, for example, by using physical cages on workstations to prohibit access to certain external ports, or disabling/removing the ability to insert, read or write to such devices. Organizations may also limit the use of portable storage devices to only approved devices including, for example, devices provided by the organization, devices provided by other approved organizations, and devices that are not personally owned. Finally, organizations may restrict the use of portable storage devices based on the type of device, for example, prohibiting the use of writeable, portable storage devices, and implementing this restriction by disabling or removing the capability to write to such devices. Related controls: AC-19, PL-4. References: None. | link | count: 004 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | MP-7(1) | FedRAMP_High_R4_MP-7(1) | FedRAMP High MP-7 (1) | Media Protection | Prohibit Use Without Owner | Shared | n/a | The organization prohibits the use of portable storage devices in organizational information systems when such devices have no identifiable owner. Supplemental Guidance: Requiring identifiable owners (e.g., individuals, organizations, or projects) for portable storage devices reduces the risk of using such technologies by allowing organizations to assign responsibility and accountability for addressing known vulnerabilities in the devices (e.g., malicious code insertion). Related control: PL-4. | link | count: 004 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-1 | FedRAMP_High_R4_PE-1 | FedRAMP High PE-1 | Physical And Environmental Protection | Physical And Environmental Protection Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A physical and environmental protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls; and b. Reviews and updates the current: 1. Physical and environmental protection policy [Assignment: organization-defined frequency]; and 2. Physical and environmental protection procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PE family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-12 | FedRAMP_High_R4_PE-12 | FedRAMP High PE-12 | Physical And Environmental Protection | Emergency Lighting | Shared | n/a | The organization employs and maintains automatic emergency lighting for the information system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Related controls: CP-2, CP-7. References: None. | link | count: 001 Employ automatic emergency lighting (aa892c0d-2c40-200c-0dd8-eac8c4748ede) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-13 | FedRAMP_High_R4_PE-13 | FedRAMP High PE-13 | Physical And Environmental Protection | Fire Protection | Shared | n/a | The organization employs and maintains fire suppression and detection devices/systems for the information system that are supported by an independent energy source. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Fire suppression and detection devices/systems include, for example, sprinkler systems, handheld fire extinguishers, fixed fire hoses, and smoke detectors. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-13(1) | FedRAMP_High_R4_PE-13(1) | FedRAMP High PE-13 (1) | Physical And Environmental Protection | Detection Devices / Systems | Shared | n/a | The organization employs fire detection devices/systems for the information system that activate automatically and notify [Assignment: organization-defined personnel or roles] and [Assignment: organization-defined emergency responders] in the event of a fire. Supplemental Guidance: Organizations can identify specific personnel, roles, and emergency responders in the event that individuals on the notification list must have appropriate access authorizations and/or clearances, for example, to obtain access to facilities where classified operations are taking place or where there are information systems containing classified information. | link | count: 003 Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-13(2) | FedRAMP_High_R4_PE-13(2) | FedRAMP High PE-13 (2) | Physical And Environmental Protection | Suppression Devices / Systems | Shared | n/a | The organization employs fire suppression devices/systems for the information system that provide automatic notification of any activation to Assignment: organization-defined personnel or roles] and [Assignment: organization-defined emergency responders]. Supplemental Guidance: Organizations can identify specific personnel, roles, and emergency responders in the event that individuals on the notification list must have appropriate access authorizations and/or clearances, for example, to obtain access to facilities where classified operations are taking place or where there are information systems containing classified information. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-13(3) | FedRAMP_High_R4_PE-13(3) | FedRAMP High PE-13 (3) | Physical And Environmental Protection | Automatic Fire Suppression | Shared | n/a | The organization employs an automatic fire suppression capability for the information system when the facility is not staffed on a continuous basis. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-14 | FedRAMP_High_R4_PE-14 | FedRAMP High PE-14 | Physical And Environmental Protection | Temperature And Humidity Controls | Shared | n/a | The organization: a. Maintains temperature and humidity levels within the facility where the information system resides at [Assignment: organization-defined acceptable levels]; and b. Monitors temperature and humidity levels [Assignment: organization-defined frequency]. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources, for example, data centers, server rooms, and mainframe computer rooms. Related control: AT-3. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-14(2) | FedRAMP_High_R4_PE-14(2) | FedRAMP High PE-14 (2) | Physical And Environmental Protection | Monitoring With Alarms / Notifications | Shared | n/a | The organization employs temperature and humidity monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment. | link | count: 002 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-15 | FedRAMP_High_R4_PE-15 | FedRAMP High PE-15 | Physical And Environmental Protection | Water Damage Protection | Shared | n/a | The organization protects the information system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible, working properly, and known to key personnel. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Isolation valves can be employed in addition to or in lieu of master shutoff valves to shut off water supplies in specific areas of concern, without affecting entire organizations. Related control: AT-3. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-16 | FedRAMP_High_R4_PE-16 | FedRAMP High PE-16 | Physical And Environmental Protection | Delivery And Removal | Shared | n/a | The organization authorizes, monitors, and controls [Assignment: organization-defined types of information system components] entering and exiting the facility and maintains records of those items. Supplemental Guidance: Effectively enforcing authorizations for entry and exit of information system components may require restricting access to delivery areas and possibly isolating the areas from the information system and media libraries. Related controls: CM-3, MA-2, MA-3, MP-5, SA-12. References: None. | link | count: 002 Define requirements for managing assets (25a1f840-65d0-900a-43e4-bee253de04de), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-17 | FedRAMP_High_R4_PE-17 | FedRAMP High PE-17 | Physical And Environmental Protection | Alternate Work Site | Shared | n/a | The organization: a. Employs [Assignment: organization-defined security controls] at alternate work sites; b. Assesses as feasible, the effectiveness of security controls at alternate work sites; and c. Provides a means for employees to communicate with information security personnel in case of security incidents or problems. Supplemental Guidance: Alternate work sites may include, for example, government facilities or private residences of employees. While commonly distinct from alternative processing sites, alternate work sites may provide readily available alternate locations as part of contingency operations. Organizations may define different sets of security controls for specific alternate work sites or types of sites depending on the work-related activities conducted at those sites. This control supports the contingency planning activities of organizations and the federal telework initiative. Related controls: AC-17, CP-7. Control Enhancements: None. References: NIST Special Publication 800-46. | link | count: 001 Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-18 | FedRAMP_High_R4_PE-18 | FedRAMP High PE-18 | Physical And Environmental Protection | Location Of Information System Components | Shared | n/a | The organization positions information system components within the facility to minimize potential damage from [Assignment: organization-defined physical and environmental hazards] and to minimize the opportunity for unauthorized access. Supplemental Guidance: Physical and environmental hazards include, for example, flooding, fire, tornados, earthquakes, hurricanes, acts of terrorism, vandalism, electromagnetic pulse, electrical interference, and other forms of incoming electromagnetic radiation. In addition, organizations consider the location of physical entry points where unauthorized individuals, while not being granted access, might nonetheless be in close proximity to information systems and therefore increase the potential for unauthorized access to organizational communications (e.g., through the use of wireless sniffers or microphones). Related controls: CP-2, PE-19, RA-3. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-2 | FedRAMP_High_R4_PE-2 | FedRAMP High PE-2 | Physical And Environmental Protection | Physical Access Authorizations | Shared | n/a | The organization: a. Develops, approves, and maintains a list of individuals with authorized access to the facility where the information system resides; b. Issues authorization credentials for facility access; c. Reviews the access list detailing authorized facility access by individuals [Assignment: organization-defined frequency]; and d. Removes individuals from the facility access list when access is no longer required. Supplemental Guidance: This control applies to organizational employees and visitors. Individuals (e.g., employees, contractors, and others) with permanent physical access authorization credentials are not considered visitors. Authorization credentials include, for example, badges, identification cards, and smart cards. Organizations determine the strength of authorization credentials needed (including level of forge-proof badges, smart cards, or identification cards) consistent with federal standards, policies, and procedures. This control only applies to areas within facilities that have not been designated as publicly accessible. Related controls: PE-3, PE-4, PS-3. References: None | link | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-3 | FedRAMP_High_R4_PE-3 | FedRAMP High PE-3 | Physical And Environmental Protection | Physical Access Control | Shared | n/a | The organization: a. Enforces physical access authorizations at [Assignment: organization-defined entry/exit points to the facility where the information system resides] by; 1. Verifying individual access authorizations before granting access to the facility; and 2. Controlling ingress/egress to the facility using [Selection (one or more): [Assignment: organization-defined physical access control systems/devices]; guards]; b. Maintains physical access audit logs for [Assignment: organization-defined entry/exit points]; c. Provides [Assignment: organization-defined security safeguards] to control access to areas within the facility officially designated as publicly accessible; d. Escorts visitors and monitors visitor activity [Assignment: organization-defined circumstances requiring visitor escorts and monitoring]; e. Secures keys, combinations, and other physical access devices; f. Inventories [Assignment: organization-defined physical access devices] every [Assignment: organization-defined frequency]; and g. Changes combinations and keys [Assignment: organization-defined frequency] and/or when keys are lost, combinations are compromised, or individuals are transferred or terminated. Supplemental Guidance: This control applies to organizational employees and visitors. Individuals (e.g., employees, contractors, and others) with permanent physical access authorization credentials are not considered visitors. Organizations determine the types of facility guards needed including, for example, professional physical security staff or other personnel such as administrative staff or information system users. Physical access devices include, for example, keys, locks, combinations, and card readers. Safeguards for publicly accessible areas within organizational facilities include, for example, cameras, monitoring by guards, and isolating selected information systems and/or system components in secured areas. Physical access control systems comply with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The Federal Identity, Credential, and Access Management Program provides implementation guidance for identity, credential, and access management capabilities for physical access control systems. Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural (e.g., a written log of individuals accessing the facility and when such access occurred), automated (e.g., capturing ID provided by a PIV card), or some combination thereof. Physical access points can include facility access points, interior access points to information systems and/or components requiring supplemental access controls, or both. Components of organizational information systems (e.g., workstations, terminals) may be located in areas designated as publicly accessible with organizations safeguarding access to such devices. Related controls: AU-2, AU-6, MP-2, MP-4, PE-2, PE-4, PE-5, PS-3, RA-3. Supplemental Guidance: Related controls: CA-2, CA-7. | link | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-4 | FedRAMP_High_R4_PE-4 | FedRAMP High PE-4 | Physical And Environmental Protection | Access Control For Transmission Medium | Shared | n/a | The organization controls physical access to [Assignment: organization-defined information system distribution and transmission lines] within organizational facilities using [Assignment: organization-defined security safeguards]. Supplemental Guidance: Physical security safeguards applied to information system distribution and transmission lines help to prevent accidental damage, disruption, and physical tampering. In addition, physical safeguards may be necessary to help prevent eavesdropping or in transit modification of unencrypted transmissions. Security safeguards to control physical access to system distribution and transmission lines include, for example: (i) locked wiring closets; (ii) disconnected or locked spare jacks; and/or (iii) protection of cabling by conduit or cable trays. Related controls: MP-2, MP-4, PE-2, PE-3, PE-5, SC-7, SC-8. Control Enhancements: None. References: NSTISSI No. 7003. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-5 | FedRAMP_High_R4_PE-5 | FedRAMP High PE-5 | Physical And Environmental Protection | Access Control For Output Devices | Shared | n/a | The organization controls physical access to information system output devices to prevent unauthorized individuals from obtaining the output. Supplemental Guidance: Controlling physical access to output devices includes, for example, placing output devices in locked rooms or other secured areas and allowing access to authorized individuals only, and placing output devices in locations that can be monitored by organizational personnel. Monitors, printers, copiers, scanners, facsimile machines, and audio devices are examples of information system output devices. Related controls: PE-2, PE-3, PE-4, PE-18. References: None. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-6(1) | FedRAMP_High_R4_PE-6(1) | FedRAMP High PE-6 (1) | Physical And Environmental Protection | Intrusion Alarms / Surveillance Equipment | Shared | n/a | The organization monitors physical intrusion alarms and surveillance equipment. | link | count: 002 Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PE-8 | FedRAMP_High_R4_PE-8 | FedRAMP High PE-8 | Physical And Environmental Protection | Visitor Access Records | Shared | n/a | The organization: a. Maintains visitor access records to the facility where the information system resides for [Assignment: organization-defined time period]; and b. Reviews visitor access records [Assignment: organization-defined frequency]. Supplemental Guidance: Visitor access records include, for example, names and organizations of persons visiting, visitor signatures, forms of identification, dates of access, entry and departure times, purposes of visits, and names and organizations of persons visited. Visitor access records are not required for publicly accessible areas. References: None. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PL-1 | FedRAMP_High_R4_PL-1 | FedRAMP High PL-1 | Planning | Security Planning Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A security planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the security planning policy and associated security planning controls; and b. Reviews and updates the current: 1. Security planning policy [Assignment: organization-defined frequency]; and 2. Security planning procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PL family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-18, 800-100. | link | count: 001 Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PL-2 | FedRAMP_High_R4_PL-2 | FedRAMP High PL-2 | Planning | System Security Plan | Shared | n/a | The organization: a. Develops a security plan for the information system that: 1. Is consistent with the organization’s enterprise architecture; 2. Explicitly defines the authorization boundary for the system; 3. Describes the operational context of the information system in terms of missions and business processes; 4. Provides the security categorization of the information system including supporting rationale; 5. Describes the operational environment for the information system and relationships with or connections to other information systems; 6. Provides an overview of the security requirements for the system; 7. Identifies any relevant overlays, if applicable; 8. Describes the security controls in place or planned for meeting those requirements including a rationale for the tailoring and supplementation decisions; and 9. Is reviewed and approved by the authorizing official or designated representative prior to plan implementation; b. Distributes copies of the security plan and communicates subsequent changes to the plan to [Assignment: organization-defined personnel or roles]; c. Reviews the security plan for the information system [Assignment: organization-defined frequency]; d. Updates the plan to address changes to the information system/environment of operation or problems identified during plan implementation or security control assessments; and e. Protects the security plan from unauthorized disclosure and modification. Supplemental Guidance: Security plans relate security requirements to a set of security controls and control enhancements. Security plans also describe, at a high level, how the security controls and control enhancements meet those security requirements, but do not provide detailed, technical descriptions of the specific design or implementation of the controls/enhancements. Security plans contain sufficient information (including the specification of parameter values for assignment and selection statements either explicitly or by reference) to enable a design and implementation that is unambiguously compliant with the intent of the plans and subsequent determinations of risk to organizational operations and assets, individuals, other organizations, and the Nation if the plan is implemented as intended. Organizations can also apply tailoring guidance to the security control baselines in Appendix D and CNSS Instruction 1253 to develop overlays for community-wide use or to address specialized requirements, technologies, or missions/environments of operation (e.g., DoD-tactical, Federal Public Key Infrastructure, or Federal Identity, Credential, and Access Management, space operations). Appendix I provides guidance on developing overlays. Security plans need not be single documents; the plans can be a collection of various documents including documents that already exist. Effective security plans make extensive use of references to policies, procedures, and additional documents (e.g., design and implementation specifications) where more detailed information can be obtained. This reduces the documentation requirements associated with security programs and maintains security-related information in other established management/operational areas related to enterprise architecture, system development life cycle, systems engineering, and acquisition. For example, security plans do not contain detailed contingency plan or incident response plan information but instead provide explicitly or by reference, sufficient information to define what needs to be accomplished by those plans. Related controls: AC-2, AC-6, AC-14, AC-17, AC-20, CA-2, CA-3, CA-7, CM-9, CP-2, IR-8, MA-4, MA-5, MP-2, MP-4, MP-5, PL-7, PM-1, PM-7, PM-8, PM-9, PM-11, SA-5, SA-17. References: NIST Special Publication 800-18. | link | count: 006 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PL-2(3) | FedRAMP_High_R4_PL-2(3) | FedRAMP High PL-2 (3) | Planning | Plan / Coordinate With Other Organizational Entities | Shared | n/a | The organization plans and coordinates security-related activities affecting the information system with [Assignment: organization-defined individuals or groups] before conducting such activities in order to reduce the impact on other organizational entities. Supplemental Guidance: Security-related activities include, for example, security assessments, audits, hardware and software maintenance, patch management, and contingency plan testing. Advance planning and coordination includes emergency and nonemergency (i.e., planned or nonurgent unplanned) situations. The process defined by organizations to plan and coordinate security-related activities can be included in security plans for information systems or other documents, as appropriate. Related controls: CP-4, IR-4. | link | count: 003 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PL-4 | FedRAMP_High_R4_PL-4 | FedRAMP High PL-4 | Planning | Rules Of Behavior | Shared | n/a | The organization: a. Establishes and makes readily available to individuals requiring access to the information system, the rules that describe their responsibilities and expected behavior with regard to information and information system usage; b. Receives a signed acknowledgment from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the information system; c. Reviews and updates the rules of behavior [Assignment: organization-defined frequency]; and d. Requires individuals who have signed a previous version of the rules of behavior to read and resign when the rules of behavior are revised/updated. Supplemental Guidance: This control enhancement applies to organizational users. Organizations consider rules of behavior based on individual user roles and responsibilities, differentiating, for example, between rules that apply to privileged users and rules that apply to general users. Establishing rules of behavior for some types of non-organizational users including, for example, individuals who simply receive data/information from federal information systems, is often not feasible given the large number of such users and the limited nature of their interactions with the systems. Rules of behavior for both organizational and non-organizational users can also be established in AC-8, System Use Notification. PL-4 b. (the signed acknowledgment portion of this control) may be satisfied by the security awareness training and role-based security training programs conducted by organizations if such training includes rules of behavior. Organizations can use electronic signatures for acknowledging rules of behavior. Related controls: AC-2, AC-6, AC-8, AC-9, AC-17, AC-18, AC-19, AC-20, AT-2, AT-3, CM-11, IA-2, IA-4, IA-5, MP-7, PS-6, PS-8, SA-5. References: NIST Special Publication 800-18. | link | count: 009 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PL-4(1) | FedRAMP_High_R4_PL-4(1) | FedRAMP High PL-4 (1) | Planning | Social Media And Networking Restrictions | Shared | n/a | The organization includes in the rules of behavior, explicit restrictions on the use of social media/networking sites and posting organizational information on public websites. Supplemental Guidance: This control enhancement addresses rules of behavior related to the use of social media/networking sites: (i) when organizational personnel are using such sites for official duties or in the conduct of official business; (ii) when organizational information is involved in social media/networking transactions; and (iii) when personnel are accessing social media/networking sites from organizational information systems. Organizations also address specific rules that prevent unauthorized entities from obtaining and/or inferring non- public organizational information (e.g., system account information, personally identifiable information) from social media/networking sites. | link | count: 001 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PL-8 | FedRAMP_High_R4_PL-8 | FedRAMP High PL-8 | Planning | Information Security Architecture | Shared | n/a | The organization: a. Develops an information security architecture for the information system that: 1. Describes the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information; 2. Describes how the information security architecture is integrated into and supports the enterprise architecture; and 3. Describes any information security assumptions about, and dependencies on, external services; b. Reviews and updates the information security architecture [Assignment: organization-defined frequency] to reflect updates in the enterprise architecture; and c. Ensures that planned information security architecture changes are reflected in the security plan, the security Concept of Operations (CONOPS), and organizational procurements/acquisitions. Supplemental Guidance: This control addresses actions taken by organizations in the design and development of information systems. The information security architecture at the individual information system level is consistent with and complements the more global, organization-wide information security architecture described in PM-7 that is integral to and developed as part of the enterprise architecture. The information security architecture includes an architectural description, the placement/allocation of security functionality (including security controls), security-related information for external interfaces, information being exchanged across the interfaces, and the protection mechanisms associated with each interface. In addition, the security architecture can include other important security-related information, for example, user roles and access privileges assigned to each role, unique security requirements, the types of information processed, stored, and transmitted by the information system, restoration priorities of information and information system services, and any other specific protection needs. In today’s modern architecture, it is becoming less common for organizations to control all information resources. There are going to be key dependencies on external information services and service providers. Describing such dependencies in the information security architecture is important to developing a comprehensive mission/business protection strategy. Establishing, developing, documenting, and maintaining under configuration control, a baseline configuration for organizational information systems is critical to implementing and maintaining an effective information security architecture. The development of the information security architecture is coordinated with the Senior Agency Official for Privacy (SAOP)/Chief Privacy Officer (CPO) to ensure that security controls needed to support privacy requirements are identified and effectively implemented. PL-8 is primarily directed at organizations (i.e., internally focused) to help ensure that organizations develop an information security architecture for the information system, and that the security architecture is integrated with or tightly coupled to the enterprise architecture through the organization-wide information security architecture. In contrast, SA-17 is primarily directed at external information technology product/system developers and integrators (although SA-17 could be used internally within organizations for in-house system development). SA-17, which is complementary to PL-8, is selected when organizations outsource the development of information systems or information system components to external entities, and there is a need to demonstrate/show consistency with the organization’s enterprise architecture and information security architecture. Related controls: CM-2, CM-6, PL-2, PM-7, SA-5, SA-17, Appendix J. References: None. | link | count: 002 Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-1 | FedRAMP_High_R4_PS-1 | FedRAMP High PS-1 | Personnel Security | Personnel Security Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A personnel security policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the personnel security policy and associated personnel security controls; and b. Reviews and updates the current: 1. Personnel security policy [Assignment: organization-defined frequency]; and 2. Personnel security procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PS family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-2 | FedRAMP_High_R4_PS-2 | FedRAMP High PS-2 | Personnel Security | Position Risk Designation | Shared | n/a | The organization: a. Assigns a risk designation to all organizational positions; b. Establishes screening criteria for individuals filling those positions; and c. Reviews and updates position risk designations [Assignment: organization-defined frequency]. Supplemental Guidance: Position risk designations reflect Office of Personnel Management policy and guidance. Risk designations can guide and inform the types of authorizations individuals receive when accessing organizational information and information systems. Position screening criteria include explicit information security role appointment requirements (e.g., training, security clearances). Related controls: AT-3, PL-2, PS-3. Control Enhancements: None. References: 5 C.F.R. 731.106(a). | link | count: 001 Assign risk designations (b7897ddc-9716-2460-96f7-7757ad038cc4) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-3 | FedRAMP_High_R4_PS-3 | FedRAMP High PS-3 | Personnel Security | Personnel Screening | Shared | n/a | The organization: a. Screens individuals prior to authorizing access to the information system; and b. Rescreens individuals according to [Assignment: organization-defined conditions requiring rescreening and, where rescreening is so indicated, the frequency of such rescreening]. Supplemental Guidance: Personnel screening and rescreening activities reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, guidance, and specific criteria established for the risk designations of assigned positions. Organizations may define different rescreening conditions and frequencies for personnel accessing information systems based on types of information processed, stored, or transmitted by the systems. Related controls: AC-2, IA-4, PE-2, PS-2. References: 5 C.F.R. 731.106; FIPS Publications 199, 201; NIST Special Publications 800-60, 800-73, 800-76, 800-78; ICD 704. | link | count: 003 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Rescreen individuals at a defined frequency (c6aeb800-0b19-944d-92dc-59b893722329) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-3(3) | FedRAMP_High_R4_PS-3(3) | FedRAMP High PS-3 (3) | Personnel Security | Information With Special Protection Measures | Shared | n/a | The organization ensures that individuals accessing an information system processing, storing, or transmitting information requiring special protection: (a) Have valid access authorizations that are demonstrated by assigned official government duties; and (b) Satisfy [Assignment: organization-defined additional personnel screening criteria]. Supplemental Guidance: Organizational information requiring special protection includes, for example, Controlled Unclassified Information (CUI) and Sources and Methods Information (SAMI). Personnel security criteria include, for example, position sensitivity background screening requirements. | link | count: 001 Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-4 | FedRAMP_High_R4_PS-4 | FedRAMP High PS-4 | Personnel Security | Personnel Termination | Shared | n/a | The organization, upon termination of individual employment: a. Disables information system access within [Assignment: organization-defined time period]; b. Terminates/revokes any authenticators/credentials associated with the individual; c. Conducts exit interviews that include a discussion of [Assignment: organization-defined information security topics]; d. Retrieves all security-related organizational information system-related property; e. Retains access to organizational information and information systems formerly controlled by terminated individual; and f. Notifies [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period]. Supplemental Guidance: Information system-related property includes, for example, hardware authentication tokens, system administration technical manuals, keys, identification cards, and building passes. Exit interviews ensure that terminated individuals understand the security constraints imposed by being former employees and that proper accountability is achieved for information system-related property. Security topics of interest at exit interviews can include, for example, reminding terminated individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not be possible for some terminated individuals, for example, in cases related to job abandonment, illnesses, and nonavailability of supervisors. Exit interviews are important for individuals with security clearances. Timely execution of termination actions is essential for individuals terminated for cause. In certain situations, organizations consider disabling the information system accounts of individuals that are being terminated prior to the individuals being notified. Related controls: AC-2, IA-4, PE-2, PS-5, PS-6. References: None. | link | count: 005 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-4(2) | FedRAMP_High_R4_PS-4(2) | FedRAMP High PS-4 (2) | Personnel Security | Automated Notification | Shared | n/a | The organization employs automated mechanisms to notify [Assignment: organization-defined personnel or roles] upon termination of an individual. Supplemental Guidance: In organizations with a large number of employees, not all personnel who need to know about termination actions receive the appropriate notifications—or, if such notifications are received, they may not occur in a timely manner. Automated mechanisms can be used to send automatic alerts or notifications to specific organizational personnel or roles (e.g., management personnel, supervisors, personnel security officers, information security officers, systems administrators, or information technology administrators) when individuals are terminated. Such automatic alerts or notifications can be conveyed in a variety of ways, including, for example, telephonically, via electronic mail, via text message, or via websites. | link | count: 001 Automate notification of employee termination (729c8708-2bec-093c-8427-2e87d2cd426d) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-5 | FedRAMP_High_R4_PS-5 | FedRAMP High PS-5 | Personnel Security | Personnel Transfer | Shared | n/a | The organization: a. Reviews and confirms ongoing operational need for current logical and physical access authorizations to information systems/facilities when individuals are reassigned or transferred to other positions within the organization; b. Initiates [Assignment: organization-defined transfer or reassignment actions] within [Assignment: organization-defined time period following the formal transfer action]; c. Modifies access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and d. Notifies [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period]. Supplemental Guidance: This control applies when reassignments or transfers of individuals are permanent or of such extended durations as to make the actions warranted. Organizations define actions appropriate for the types of reassignments or transfers, whether permanent or extended. Actions that may be required for personnel transfers or reassignments to other positions within organizations include, for example: (i) returning old and issuing new keys, identification cards, and building passes; (ii) closing information system accounts and establishing new accounts; (iii) changing information system access authorizations (i.e., privileges); and (iv) providing for access to official records to which individuals had access at previous work locations and in previous information system accounts. Related controls: AC-2, IA-4, PE-2, PS-4. Control Enhancements: None. References: None. | link | count: 004 Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-6 | FedRAMP_High_R4_PS-6 | FedRAMP High PS-6 | Personnel Security | Access Agreements | Shared | n/a | The organization: a. Develops and documents access agreements for organizational information systems; b. Reviews and updates the access agreements [Assignment: organization-defined frequency]; and c. Ensures that individuals requiring access to organizational information and information systems: 1. Sign appropriate access agreements prior to being granted access; and 2. Re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or [Assignment: organization-defined frequency]. Supplemental Guidance: Access agreements include, for example, nondisclosure agreements, acceptable use agreements, rules of behavior, and conflict-of-interest agreements. Signed access agreements include an acknowledgement that individuals have read, understand, and agree to abide by the constraints associated with organizational information systems to which access is authorized. Organizations can use electronic signatures to acknowledge access agreements unless specifically prohibited by organizational policy. Related control: PL-4, PS-2, PS-3, PS-4, PS-8. References: None. | link | count: 005 Document organizational access agreements (c981fa70-2e58-8141-1457-e7f62ebc2ade), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Ensure access agreements are signed or resigned timely (e7589f4e-1e8b-72c2-3692-1e14d7f3699f), Require users to sign access agreement (3af53f59-979f-24a8-540f-d7cdbc366607), Update organizational access agreements (e21f91d1-2803-0282-5f2d-26ebc4b170ef) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-7 | FedRAMP_High_R4_PS-7 | FedRAMP High PS-7 | Personnel Security | Third-Party Personnel Security | Shared | n/a | The organization: a. Establishes personnel security requirements including security roles and responsibilities for third-party providers; b. Requires third-party providers to comply with personnel security policies and procedures established by the organization; c. Documents personnel security requirements; d. Requires third-party providers to notify [Assignment: organization-defined personnel or roles] of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges within [Assignment: organization-defined time period]; and e. Monitors provider compliance. Supplemental Guidance: Third-party providers include, for example, service bureaus, contractors, and other organizations providing information system development, information technology services, outsourced applications, and network and security management. Organizations explicitly include personnel security requirements in acquisition-related documents. Third-party providers may have personnel working at organizational facilities with credentials, badges, or information system privileges issued by organizations. Notifications of third-party personnel changes ensure appropriate termination of privileges and credentials. Organizations define the transfers and terminations deemed reportable by security-related characteristics that include, for example, functions, roles, and nature of credentials/privileges associated with individuals transferred or terminated. Related controls: PS-2, PS-3, PS-4, PS-5, PS-6, SA-9, SA-21. Control Enhancements: None. References: NIST Special Publication 800-35. | link | count: 005 Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | PS-8 | FedRAMP_High_R4_PS-8 | FedRAMP High PS-8 | Personnel Security | Personnel Sanctions | Shared | n/a | The organization: a. Employs a formal sanctions process for individuals failing to comply with established information security policies and procedures; and b. Notifies [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period] when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction. Supplemental Guidance: Organizational sanctions processes reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Sanctions processes are described in access agreements and can be included as part of general personnel policies and procedures for organizations. Organizations consult with the Office of the General Counsel regarding matters of employee sanctions. Related controls: PL-4, PS-6. Control Enhancements: None. References: None. | link | count: 002 Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-1 | FedRAMP_High_R4_RA-1 | FedRAMP High RA-1 | Risk Assessment | Risk Assessment Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A risk assessment policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls; and b. Reviews and updates the current: 1. Risk assessment policy [Assignment: organization-defined frequency]; and 2. Risk assessment procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the RA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-30, 800-100. | link | count: 001 Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-2 | FedRAMP_High_R4_RA-2 | FedRAMP High RA-2 | Risk Assessment | Security Categorization | Shared | n/a | The organization: a. Categorizes information and the information system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance; b. Documents the security categorization results (including supporting rationale) in the security plan for the information system; and c. Ensures that the security categorization decision is reviewed and approved by the authorizing official or authorizing official designated representative. Supplemental Guidance: Clearly defined authorization boundaries are a prerequisite for effective security categorization decisions. Security categories describe the potential adverse impacts to organizational operations, organizational assets, and individuals if organizational information and information systems are comprised through a loss of confidentiality, integrity, or availability. Organizations conduct the security categorization process as an organization-wide activity with the involvement of chief information officers, senior information security officers, information system owners, mission/business owners, and information owners/stewards. Organizations also consider the potential adverse impacts to other organizations and, in accordance with the USA PATRIOT Act of 2001 and Homeland Security Presidential Directives, potential national-level adverse impacts. Security categorization processes carried out by organizations facilitate the development of inventories of information assets, and along with CM-8, mappings to specific information system components where information is processed, stored, or transmitted. Related controls: CM-8, MP-4, RA-3, SC-7. Control Enhancements: None. References: FIPS Publication 199; NIST Special Publications 800-30, 800-39, 800-60. | link | count: 004 Categorize information (93fa357f-2e38-22a9-5138-8cc5124e1923), Develop business classification schemes (11ba0508-58a8-44de-5f3a-9e05d80571da), Ensure security categorization is approved (6c79c3e5-5f7b-a48a-5c7b-8c158bc01115), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-3 | FedRAMP_High_R4_RA-3 | FedRAMP High RA-3 | Risk Assessment | Risk Assessment | Shared | n/a | The organization: a. Conducts an assessment of risk, including the likelihood and magnitude of harm, from the unauthorized access, use, disclosure, disruption, modification, or destruction of the information system and the information it processes, stores, or transmits; b. Documents risk assessment results in [Selection: security plan; risk assessment report; [Assignment: organization-defined document]]; c. Reviews risk assessment results [Assignment: organization-defined frequency]; d. Disseminates risk assessment results to [Assignment: organization-defined personnel or roles]; and e. Updates the risk assessment [Assignment: organization-defined frequency] or whenever there are significant changes to the information system or environment of operation (including the identification of new threats and vulnerabilities), or other conditions that may impact the security state of the system. Supplemental Guidance: Clearly defined authorization boundaries are a prerequisite for effective risk assessments. Risk assessments take into account threats, vulnerabilities, likelihood, and impact to organizational operations and assets, individuals, other organizations, and the Nation based on the operation and use of information systems. Risk assessments also take into account risk from external parties (e.g., service providers, contractors operating information systems on behalf of the organization, individuals accessing organizational information systems, outsourcing entities). In accordance with OMB policy and related E-authentication initiatives, authentication of public users accessing federal information systems may also be required to protect nonpublic or privacy-related information. As such, organizational assessments of risk also address public access to federal information systems. Risk assessments (either formal or informal) can be conducted at all three tiers in the risk management hierarchy (i.e., organization level, mission/business process level, or information system level) and at any phase in the system development life cycle. Risk assessments can also be conducted at various steps in the Risk Management Framework, including categorization, security control selection, security control implementation, security control assessment, information system authorization, and security control monitoring. RA-3 is noteworthy in that the control must be partially implemented prior to the implementation of other controls in order to complete the first two steps in the Risk Management Framework. Risk assessments can play an important role in security control selection processes, particularly during the application of tailoring guidance, which includes security control supplementation. Related controls: RA-2, PM-9. Control Enhancements: None. References: OMB Memorandum 04-04; NIST Special Publication 800-30, 800-39; Web:idmanagement.gov. | link | count: 004 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-5 | FedRAMP_High_R4_RA-5 | FedRAMP High RA-5 | Risk Assessment | Vulnerability Scanning | Shared | n/a | The organization: a. Scans for vulnerabilities in the information system and hosted applications [Assignment: organization-defined frequency and/or randomly in accordance with organization-defined process] and when new vulnerabilities potentially affecting the system/applications are identified and reported; b. Employs vulnerability scanning tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: 1. Enumerating platforms, software flaws, and improper configurations; 2. Formatting checklists and test procedures; and 3. Measuring vulnerability impact; c. Analyzes vulnerability scan reports and results from security control assessments; d. Remediates legitimate vulnerabilities [Assignment: organization-defined response times], in accordance with an organizational assessment of risk; and e. Shares information obtained from the vulnerability scanning process and security control assessments with [Assignment: organization-defined personnel or roles] to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies). Supplemental Guidance: Security categorization of information systems guides the frequency and comprehensiveness of vulnerability scans. Organizations determine the required vulnerability scanning for all information system components, ensuring that potential sources of vulnerabilities such as networked printers, scanners, and copiers are not overlooked. Vulnerability analyses for custom software applications may require additional approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can employ these analysis approaches in a variety of tools (e.g., web-based application scanners, static analysis tools, binary analyzers) and in source code reviews. Vulnerability scanning includes, for example: (i) scanning for patch levels; (ii) scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and (iii) scanning for improperly configured or incorrectly operating information flow control mechanisms. Organizations consider using tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention and that use the Open Vulnerability Assessment Language (OVAL) to determine/test for the presence of vulnerabilities. Suggested sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). In addition, security control assessments such as red team exercises provide other sources of potential vulnerabilities for which to scan. Organizations also consider using tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS). Related controls: CA-2, CA-7, CM-4, CM-6, RA-2, RA-3, SA-11, SI-2. References: NIST Special Publications 800-40, 800-70, 800-115; Web: http://cwe.mitre.org, http://nvd.nist.gov. | link | count: 021 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Regulatory Compliance, Security Center, SQL, Synapse | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-5(1) | FedRAMP_High_R4_RA-5(1) | FedRAMP High RA-5 (1) | Risk Assessment | Update Tool Capability | Shared | n/a | The organization employs vulnerability scanning tools that include the capability to readily update the information system vulnerabilities to be scanned. Supplemental Guidance: The vulnerabilities to be scanned need to be readily updated as new vulnerabilities are discovered, announced, and scanning methods developed. This updating process helps to ensure that potential vulnerabilities in the information system are identified and addressed as quickly as possible. Related controls: SI-3, SI-7. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-5(10) | FedRAMP_High_R4_RA-5(10) | FedRAMP High RA-5 (10) | Risk Assessment | Correlate Scanning Information | Shared | n/a | The organization correlates the output from vulnerability scanning tools to determine the presence of multi-vulnerability/multi-hop attack vectors. | link | count: 001 Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-5(2) | FedRAMP_High_R4_RA-5(2) | FedRAMP High RA-5 (2) | Risk Assessment | Update By Frequency / Prior To New Scan / When Identified | Shared | n/a | The organization updates the information system vulnerabilities scanned [Selection (one or more): [Assignment: organization-defined frequency]; prior to a new scan; when new vulnerabilities are identified and reported]. Supplemental Guidance: Related controls: SI-3, SI-5. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-5(3) | FedRAMP_High_R4_RA-5(3) | FedRAMP High RA-5 (3) | Risk Assessment | Breadth / Depth Of Coverage | Shared | n/a | The organization employs vulnerability scanning procedures that can identify the breadth and depth of coverage (i.e., information system components scanned and vulnerabilities checked). | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-5(4) | FedRAMP_High_R4_RA-5(4) | FedRAMP High RA-5 (4) | Risk Assessment | Discoverable Information | Shared | n/a | The organization determines what information about the information system is discoverable by adversaries and subsequently takes [Assignment: organization-defined corrective actions]. Supplemental Guidance: Discoverable information includes information that adversaries could obtain without directly compromising or breaching the information system, for example, by collecting information the system is exposing or by conducting extensive searches of the web. Corrective actions can include, for example, notifying appropriate organizational personnel, removing designated information, or changing the information system to make designated information less relevant or attractive to adversaries. Related control: AU-13. | link | count: 001 Take action in response to customer information (d25cbded-121e-0ed6-1857-dc698c9095b1) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-5(5) | FedRAMP_High_R4_RA-5(5) | FedRAMP High RA-5 (5) | Risk Assessment | Privileged Access | Shared | n/a | The information system implements privileged access authorization to [Assignment: organization- identified information system components] for selected [Assignment: organization-defined vulnerability scanning activities]. Supplemental Guidance: In certain situations, the nature of the vulnerability scanning may be more intrusive or the information system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system components facilitates more thorough vulnerability scanning and also protects the sensitive nature of such scanning. | link | count: 001 Implement privileged access for executing vulnerability scanning activities (5b802722-71dd-a13d-2e7e-231e09589efb) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-5(6) | FedRAMP_High_R4_RA-5(6) | FedRAMP High RA-5 (6) | Risk Assessment | Automated Trend Analyses | Shared | n/a | The organization employs automated mechanisms to compare the results of vulnerability scans over time to determine trends in information system vulnerabilities. Supplemental Guidance: Related controls: IR-4, IR-5, SI-4. | link | count: 005 Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | RA-5(8) | FedRAMP_High_R4_RA-5(8) | FedRAMP High RA-5 (8) | Risk Assessment | Review Historic Audit Logs | Shared | n/a | The organization reviews historic audit logs to determine if a vulnerability identified in the information system has been previously exploited. Supplemental Guidance: Related control: AU-6. | link | count: 015 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review exploit protection events (a30bd8e9-7064-312a-0e1f-e1b485d59f6e), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-1 | FedRAMP_High_R4_SA-1 | FedRAMP High SA-1 | System And Services Acquisition | System And Services Acquisition Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system and services acquisition policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls; and b. Reviews and updates the current: 1. System and services acquisition policy [Assignment: organization-defined frequency]; and 2. System and services acquisition procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-10 | FedRAMP_High_R4_SA-10 | FedRAMP High SA-10 | System And Services Acquisition | Developer Configuration Management | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to: a. Perform configuration management during system, component, or service [Selection (one or more): design; development; implementation; operation]; b. Document, manage, and control the integrity of changes to [Assignment: organization-defined configuration items under configuration management]; c. Implement only organization-approved changes to the system, component, or service; d. Document approved changes to the system, component, or service and the potential security impacts of such changes; and e. Track security flaws and flaw resolution within the system, component, or service and report findings to [Assignment: organization-defined personnel]. Supplemental Guidance: This control also applies to organizations conducting internal information systems development and integration. Organizations consider the quality and completeness of the configuration management activities conducted by developers as evidence of applying effective security safeguards. Safeguards include, for example, protecting from unauthorized modification or destruction, the master copies of all material used to generate security-relevant portions of the system hardware, software, and firmware. Maintaining the integrity of changes to the information system, information system component, or information system service requires configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes. Configuration items that are placed under configuration management (if existence/use is required by other security controls) include: the formal model; the functional, high-level, and low-level design specifications; other design data; implementation documentation; source code and hardware schematics; the running version of the object code; tools for comparing new versions of security-relevant hardware descriptions and software/firmware source code with previous versions; and test fixtures and documentation. Depending on the mission/business needs of organizations and the nature of the contractual relationships in place, developers may provide configuration management support during the operations and maintenance phases of the life cycle. Related controls: CM-3, CM-4, CM-9, SA-12, SI-2. References: NIST Special Publication 800-128. | link | count: 009 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-10(1) | FedRAMP_High_R4_SA-10(1) | FedRAMP High SA-10 (1) | System And Services Acquisition | Software / Firmware Integrity Verification | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to enable integrity verification of software and firmware components. Supplemental Guidance: This control enhancement allows organizations to detect unauthorized changes to software and firmware components through the use of tools, techniques, and/or mechanisms provided by developers. Integrity checking mechanisms can also address counterfeiting of software and firmware components. Organizations verify the integrity of software and firmware components, for example, through secure one-way hashes provided by developers. Delivered software and firmware components also include any updates to such components. Related control: SI-7. | link | count: 001 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-11 | FedRAMP_High_R4_SA-11 | FedRAMP High SA-11 | System And Services Acquisition | Developer Security Testing And Evaluation | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to: a. Create and implement a security assessment plan; b. Perform [Selection (one or more): unit; integration; system; regression] testing/evaluation at [Assignment: organization-defined depth and coverage]; c. Produce evidence of the execution of the security assessment plan and the results of the security testing/evaluation; d. Implement a verifiable flaw remediation process; and e. Correct flaws identified during security testing/evaluation. Supplemental Guidance: Developmental security testing/evaluation occurs at all post‐design phases of the system development life cycle. Such testing/evaluation confirms that the required security controls are implemented correctly, operating as intended, enforcing the desired security policy, and meeting established security requirements. Security properties of information systems may be affected by the interconnection of system components or changes to those components. These interconnections or changes (e.g., upgrading or replacing applications and operating systems) may adversely affect previously implemented security controls. This control provides additional types of security testing/evaluation that developers can conduct to reduce or eliminate potential flaws. Testing custom software applications may require approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Developers can employ these analysis approaches in a variety of tools (e.g., web-based application scanners, static analysis tools, binary analyzers) and in source code reviews. Security assessment plans provide the specific activities that developers plan to carry out including the types of analyses, testing, evaluation, and reviews of software and firmware components, the degree of rigor to be applied, and the types of artifacts produced during those processes. The depth of security testing/evaluation refers to the rigor and level of detail associated with the assessment process (e.g., black box, gray box, or white box testing). The coverage of security testing/evaluation refers to the scope (i.e., number and type) of the artifacts included in the assessment process. Contracts specify the acceptance criteria for security assessment plans, flaw remediation processes, and the evidence that the plans/processes have been diligently applied. Methods for reviewing and protecting assessment plans, evidence, and documentation are commensurate with the security category or classification level of the information system. Contracts may specify documentation protection requirements. Related controls: CA-2, CM-4, SA-3, SA-4, SA-5, SI-2. References: ISO/IEC 15408; NIST Special Publication 800-53A; Web: http://nvd.nist.gov, http://cwe.mitre.org, http://cve.mitre.org, http://capec.mitre.org. | link | count: 003 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-12 | FedRAMP_High_R4_SA-12 | FedRAMP High SA-12 | System And Services Acquisition | Supply Chain Protection | Shared | n/a | The organization protects against supply chain threats to the information system, system component, or information system service by employing [Assignment: organization-defined security safeguards] as part of a comprehensive, defense-in-breadth information security strategy. Supplemental Guidance: Information systems (including system components that compose those systems) need to be protected throughout the system development life cycle (i.e., during design, development, manufacturing, packaging, assembly, distribution, system integration, operations, maintenance, and retirement). Protection of organizational information systems is accomplished through threat awareness, by the identification, management, and reduction of vulnerabilities at each phase of the life cycle and the use of complementary, mutually reinforcing strategies to respond to risk. Organizations consider implementing a standardized process to address supply chain risk with respect to information systems and system components, and to educate the acquisition workforce on threats, risk, and required security controls. Organizations use the acquisition/procurement processes to require supply chain entities to implement necessary security safeguards to: (i) reduce the likelihood of unauthorized modifications at each stage in the supply chain; and (ii) protect information systems and information system components, prior to taking delivery of such systems/components. This control enhancement also applies to information system services. Security safeguards include, for example: (i) security controls for development systems, development facilities, and external connections to development systems; (ii) vetting development personnel; and (iii) use of tamper-evident packaging during shipping/warehousing. Methods for reviewing and protecting development plans, evidence, and documentation are commensurate with the security category or classification level of the information system. Contracts may specify documentation protection requirements. Related controls: AT-3, CM-8, IR- 4, PE-16, PL-8, SA-3, SA-4, SA-8, SA-10, SA-14, SA-15, SA-18, SA-19, SC-29, SC-30, SC-38, SI-7. References: NIST Special Publication 800-161; NIST Interagency Report 7622. | link | count: 004 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-15 | FedRAMP_High_R4_SA-15 | FedRAMP High SA-15 | System And Services Acquisition | Development Process, Standards, And Tools | Shared | n/a | The organization: a. Requires the developer of the information system, system component, or information system service to follow a documented development process that: 1. Explicitly addresses security requirements; 2. Identifies the standards and tools used in the development process; 3. Documents the specific tool options and tool configurations used in the development process; and 4. Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and b. Reviews the development process, standards, tools, and tool options/configurations [Assignment: organization-defined frequency] to determine if the process, standards, tools, and tool options/configurations selected and employed can satisfy [Assignment: organization- defined security requirements]. Supplemental Guidance: Development tools include, for example, programming languages and computer-aided design (CAD) systems. Reviews of development processes can include, for example, the use of maturity models to determine the potential effectiveness of such processes. Maintaining the integrity of changes to tools and processes enables accurate supply chain risk assessment and mitigation, and requires robust configuration control throughout the life cycle (including design, development, transport, delivery, integration, and maintenance) to track authorized changes and prevent unauthorized changes. Related controls: SA-3, SA-8. References: None. | link | count: 001 Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-16 | FedRAMP_High_R4_SA-16 | FedRAMP High SA-16 | System And Services Acquisition | Developer-Provided Training | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to provide [Assignment: organization-defined training] on the correct use and operation of the implemented security functions, controls, and/or mechanisms. Supplemental Guidance: This control applies to external and internal (in-house) developers. Training of personnel is an essential element to ensure the effectiveness of security controls implemented within organizational information systems. Training options include, for example, classroom-style training, web-based/computer-based training, and hands-on training. Organizations can also request sufficient training materials from developers to conduct in-house training or offer self- training to organizational personnel. Organizations determine the type of training necessary and may require different types of training for different security functions, controls, or mechanisms. Related controls: AT-2, AT-3, SA-5. References: None. | link | count: 001 Require developers to provide training (676c3c35-3c36-612c-9523-36d266a65000) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-17 | FedRAMP_High_R4_SA-17 | FedRAMP High SA-17 | System And Services Acquisition | Developer Security Architecture And Design | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to produce a design specification and security architecture that: a. Is consistent with and supportive of the organization’s security architecture which is established within and is an integrated part of the organization’s enterprise architecture; b. Accurately and completely describes the required security functionality, and the allocation of security controls among physical and logical components; and c. Expresses how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection. Supplemental Guidance: This control is primarily directed at external developers, although it could also be used for internal (in-house) development. In contrast, PL-8 is primarily directed at internal developers to help ensure that organizations develop an information security architecture and such security architecture is integrated or tightly coupled to the enterprise architecture. This distinction is important if/when organizations outsource the development of information systems, information system components, or information system services to external entities, and there is a requirement to demonstrate consistency with the organization’s enterprise architecture and information security architecture. Related controls: PL-8, PM-7, SA-3, SA-8. References: None. | link | count: 003 Require developers to build security architecture (f131c8c5-a54a-4888-1efc-158928924bc1), Require developers to describe accurate security functionality (3e37c891-840c-3eb4-78d2-e2e0bb5063e0), Require developers to provide unified security protection approach (7a114735-a420-057d-a651-9a73cd0416ef) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-2 | FedRAMP_High_R4_SA-2 | FedRAMP High SA-2 | System And Services Acquisition | Allocation Of Resources | Shared | n/a | The organization: a. Determines information security requirements for the information system or information system service in mission/business process planning; b. Determines, documents, and allocates the resources required to protect the information system or information system service as part of its capital planning and investment control process; and c. Establishes a discrete line item for information security in organizational programming and budgeting documentation. Supplemental Guidance: Resource allocation for information security includes funding for the initial information system or information system service acquisition and funding for the sustainment of the system/service. Related controls: PM-3, PM-11. Control Enhancements: None. References: NIST Special Publication 800-65. | link | count: 006 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Allocate resources in determining information system requirements (90a156a6-49ed-18d1-1052-69aac27c05cd), Establish a discrete line item in budgeting documentation (06af77de-02ca-0f3e-838a-a9420fe466f5), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-3 | FedRAMP_High_R4_SA-3 | FedRAMP High SA-3 | System And Services Acquisition | System Development Life Cycle | Shared | n/a | The organization: a. Manages the information system using [Assignment: organization-defined system development life cycle] that incorporates information security considerations; b. Defines and documents information security roles and responsibilities throughout the system development life cycle; c. Identifies individuals having information security roles and responsibilities; and d. Integrates the organizational information security risk management process into system development life cycle activities. Supplemental Guidance: A well-defined system development life cycle provides the foundation for the successful development, implementation, and operation of organizational information systems. To apply the required security controls within the system development life cycle requires a basic understanding of information security, threats, vulnerabilities, adverse impacts, and risk to critical missions/business functions. The security engineering principles in SA-8 cannot be properly applied if individuals that design, code, and test information systems and system components (including information technology products) do not understand security. Therefore, organizations include qualified personnel, for example, chief information security officers, security architects, security engineers, and information system security officers in system development life cycle activities to ensure that security requirements are incorporated into organizational information systems. It is equally important that developers include individuals on the development team that possess the requisite security expertise and skills to ensure that needed security capabilities are effectively integrated into the information system. Security awareness and training programs can help ensure that individuals having key security roles and responsibilities have the appropriate experience, skills, and expertise to conduct assigned system development life cycle activities. The effective integration of security requirements into enterprise architecture also helps to ensure that important security considerations are addressed early in the system development life cycle and that those considerations are directly related to the organizational mission/business processes. This process also facilitates the integration of the information security architecture into the enterprise architecture, consistent with organizational risk management and information security strategies. Related controls: AT-3, PM-7, SA-8. Control Enhancements: None. References: NIST Special Publications 800-37, 800-64. | link | count: 003 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-4 | FedRAMP_High_R4_SA-4 | FedRAMP High SA-4 | System And Services Acquisition | Acquisition Process | Shared | n/a | The organization includes the following requirements, descriptions, and criteria, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs: a. Security functional requirements; b. Security strength requirements; c. Security assurance requirements; d. Security-related documentation requirements; e. Requirements for protecting security-related documentation; f. Description of the information system development environment and environment in which the system is intended to operate; and g. Acceptance criteria. Supplemental Guidance: Information system components are discrete, identifiable information technology assets (e.g., hardware, software, or firmware) that represent the building blocks of an information system. Information system components include commercial information technology products. Security functional requirements include security capabilities, security functions, and security mechanisms. Security strength requirements associated with such capabilities, functions, and mechanisms include degree of correctness, completeness, resistance to direct attack, and resistance to tampering or bypass. Security assurance requirements include: (i) development processes, procedures, practices, and methodologies; and (ii) evidence from development and assessment activities providing grounds for confidence that the required security functionality has been implemented and the required security strength has been achieved. Security documentation requirements address all phases of the system development life cycle. Security functionality, assurance, and documentation requirements are expressed in terms of security controls and control enhancements that have been selected through the tailoring process. The security control tailoring process includes, for example, the specification of parameter values through the use of assignment and selection statements and the specification of platform dependencies and implementation information. Security documentation provides user and administrator guidance regarding the implementation and operation of security controls. The level of detail required in security documentation is based on the security category or classification level of the information system and the degree to which organizations depend on the stated security capability, functions, or mechanisms to meet overall risk response expectations (as defined in the organizational risk management strategy). Security requirements can also include organizationally mandated configuration settings specifying allowed functions, ports, protocols, and services. Acceptance criteria for information systems, information system components, and information system services are defined in the same manner as such criteria for any organizational acquisition or procurement. The Federal Acquisition Regulation (FAR) Section 7.103 contains information security requirements from FISMA. Related controls: CM-6, PL-2, PS-7, SA-3, SA-5, SA-8, SA-11, SA-12. References: HSPD-12; ISO/IEC 15408; FIPS Publications 140-2, 201; NIST Special Publications 800-23, 800-35, 800-36, 800-37, 800-64, 800-70, 800-137; Federal Acquisition Regulation; Web: http://www.niap-ccevs.org, http://fips201ep.cio.gov, http://www.acquisition.gov/far. | link | count: 011 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-4(1) | FedRAMP_High_R4_SA-4(1) | FedRAMP High SA-4 (1) | System And Services Acquisition | Functional Properties Of Security Controls | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to provide a description of the functional properties of the security controls to be employed. Supplemental Guidance: Functional properties of security controls describe the functionality (i.e., security capability, functions, or mechanisms) visible at the interfaces of the controls and specifically exclude functionality and data structures internal to the operation of the controls. Related control: SA-5. | link | count: 001 Obtain functional properties of security controls (44b71aa8-099d-8b97-1557-0e853ec38e0d) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-4(10) | FedRAMP_High_R4_SA-4(10) | FedRAMP High SA-4 (10) | System And Services Acquisition | Use Of Approved Piv Products | Shared | n/a | The organization employs only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational information systems. Supplemental Guidance: Related controls: IA-2; IA-8. | link | count: 001 Employ FIPS 201-approved technology for PIV (8b333332-6efd-7c0d-5a9f-d1eb95105214) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-4(2) | FedRAMP_High_R4_SA-4(2) | FedRAMP High SA-4 (2) | System And Services Acquisition | Design / Implementation Information For Security Controls | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to provide design and implementation information for the security controls to be employed that includes: [Selection (one or more): security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [Assignment: organization-defined design/implementation information]] at [Assignment: organization-defined level of detail]. Supplemental Guidance: Organizations may require different levels of detail in design and implementation documentation for security controls employed in organizational information systems, system components, or information system services based on mission/business requirements, requirements for trustworthiness/resiliency, and requirements for analysis and testing. Information systems can be partitioned into multiple subsystems. Each subsystem within the system can contain one or more modules. The high-level design for the system is expressed in terms of multiple subsystems and the interfaces between subsystems providing security-relevant functionality. The low-level design for the system is expressed in terms of modules with particular emphasis on software and firmware (but not excluding hardware) and the interfaces between modules providing security-relevant functionality. Source code and hardware schematics are typically referred to as the implementation representation of the information system. Related control: SA-5. | link | count: 001 Obtain design and implementation information for the security controls (22a02c9a-49e4-5dc9-0d14-eb35ad717154) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-4(8) | FedRAMP_High_R4_SA-4(8) | FedRAMP High SA-4 (8) | System And Services Acquisition | Continuous Monitoring Plan | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to produce a plan for the continuous monitoring of security control effectiveness that contains [Assignment: organization-defined level of detail]. Supplemental Guidance: The objective of continuous monitoring plans is to determine if the complete set of planned, required, and deployed security controls within the information system, system component, or information system service continue to be effective over time based on the inevitable changes that occur. Developer continuous monitoring plans include a sufficient level of detail such that the information can be incorporated into the continuous monitoring strategies and programs implemented by organizations. Related control: CA-7. | link | count: 001 Obtain continuous monitoring plan for security controls (ca6d7878-3189-1833-4620-6c7254ed1607) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-4(9) | FedRAMP_High_R4_SA-4(9) | FedRAMP High SA-4 (9) | System And Services Acquisition | Functions / Ports / Protocols / Services In Use | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to identify early in the system development life cycle, the functions, ports, protocols, and services intended for organizational use. Supplemental Guidance: The identification of functions, ports, protocols, and services early in the system development life cycle (e.g., during the initial requirements definition and design phases) allows organizations to influence the design of the information system, information system component, or information system service. This early involvement in the life cycle helps organizations to avoid or minimize the use of functions, ports, protocols, or services that pose unnecessarily high risks and understand the trade-offs involved in blocking specific ports, protocols, or services (or when requiring information system service providers to do so). Early identification of functions, ports, protocols, and services avoids costly retrofitting of security controls after the information system, system component, or information system service has been implemented. SA-9 describes requirements for external information system services with organizations identifying which functions, ports, protocols, and services are provided from external sources. Related controls: CM-7, SA-9. | link | count: 001 Require developer to identify SDLC ports, protocols, and services (f6da5cca-5795-60ff-49e1-4972567815fe) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-5 | FedRAMP_High_R4_SA-5 | FedRAMP High SA-5 | System And Services Acquisition | Information System Documentation | Shared | n/a | The organization: a. Obtains administrator documentation for the information system, system component, or information system service that describes: 1. Secure configuration, installation, and operation of the system, component, or service; 2. Effective use and maintenance of security functions/mechanisms; and 3. Known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions; b. Obtains user documentation for the information system, system component, or information system service that describes: 1. User-accessible security functions/mechanisms and how to effectively use those security functions/mechanisms; 2. Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner; and 3. User responsibilities in maintaining the security of the system, component, or service; c. Documents attempts to obtain information system, system component, or information system service documentation when such documentation is either unavailable or nonexistent and [Assignment: organization-defined actions] in response; d. Protects documentation as required, in accordance with the risk management strategy; and e. Distributes documentation to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: This control helps organizational personnel understand the implementation and operation of security controls associated with information systems, system components, and information system services. Organizations consider establishing specific measures to determine the quality/completeness of the content provided. The inability to obtain needed documentation may occur, for example, due to the age of the information system/component or lack of support from developers and contractors. In those situations, organizations may need to recreate selected documentation if such documentation is essential to the effective implementation or operation of security controls. The level of protection provided for selected information system, component, or service documentation is commensurate with the security category or classification of the system. For example, documentation associated with a key DoD weapons system or command and control system would typically require a higher level of protection than a routine administrative system. Documentation that addresses information system vulnerabilities may also require an increased level of protection. Secure operation of the information system, includes, for example, initially starting the system and resuming secure system operation after any lapse in system operation. Related controls: CM-6, CM-8, PL-2, PL-4, PS-2, SA-3, SA-4. References: None. | link | count: 005 Distribute information system documentation (84a01872-5318-049e-061e-d56734183e84), Document customer-defined actions (8c44a0ea-9b09-4d9c-0e91-f9bee3d05bfb), Obtain Admin documentation (3f1216b0-30ee-1ac9-3899-63eb744e85f5), Obtain user security function documentation (be1c34ab-295a-07a6-785c-36f63c1d223e), Protect administrator and user documentation (09960521-759e-5d12-086f-4192a72a5e92) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-9 | FedRAMP_High_R4_SA-9 | FedRAMP High SA-9 | System And Services Acquisition | External Information System Services | Shared | n/a | The organization: a. Requires that providers of external information system services comply with organizational information security requirements and employ [Assignment: organization-defined security controls] in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance; b. Defines and documents government oversight and user roles and responsibilities with regard to external information system services; and c. Employs [Assignment: organization-defined processes, methods, and techniques] to monitor security control compliance by external service providers on an ongoing basis. Supplemental Guidance: External information system services are services that are implemented outside of the authorization boundaries of organizational information systems. This includes services that are used by, but not a part of, organizational information systems. FISMA and OMB policy require that organizations using external service providers that are processing, storing, or transmitting federal information or operating information systems on behalf of the federal government ensure that such providers meet the same security requirements that federal agencies are required to meet. Organizations establish relationships with external service providers in a variety of ways including, for example, through joint ventures, business partnerships, contracts, interagency agreements, lines of business arrangements, licensing agreements, and supply chain exchanges. The responsibility for managing risks from the use of external information system services remains with authorizing officials. For services external to organizations, a chain of trust requires that organizations establish and retain a level of confidence that each participating provider in the potentially complex consumer-provider relationship provides adequate protection for the services rendered. The extent and nature of this chain of trust varies based on the relationships between organizations and the external providers. Organizations document the basis for trust relationships so the relationships can be monitored over time. External information system services documentation includes government, service providers, end user security roles and responsibilities, and service-level agreements. Service-level agreements define expectations of performance for security controls, describe measurable outcomes, and identify remedies and response requirements for identified instances of noncompliance. Related controls: CA-3, IR-7, PS-7. References: NIST Special Publication 800-35. | link | count: 004 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-9(1) | FedRAMP_High_R4_SA-9(1) | FedRAMP High SA-9 (1) | System And Services Acquisition | Risk Assessments / Organizational Approvals | Shared | n/a | The organization: (a) Conducts an organizational assessment of risk prior to the acquisition or outsourcing of dedicated information security services; and (b) Ensures that the acquisition or outsourcing of dedicated information security services is approved by [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Dedicated information security services include, for example, incident monitoring, analysis and response, operation of information security-related devices such as firewalls, or key management services. Related controls: CA-6, RA-3. | link | count: 002 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Obtain approvals for acquisitions and outsourcing (92b94485-1c49-3350-9ada-dffe94f08e87) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-9(2) | FedRAMP_High_R4_SA-9(2) | FedRAMP High SA-9 (2) | System And Services Acquisition | Identification Of Functions / Ports / Protocols / Services | Shared | n/a | The organization requires providers of [Assignment: organization-defined external information system services] to identify the functions, ports, protocols, and other services required for the use of such services. Supplemental Guidance: Information from external service providers regarding the specific functions, ports, protocols, and services used in the provision of such services can be particularly useful when the need arises to understand the trade-offs involved in restricting certain functions/services or blocking certain ports/protocols. Related control: CM-7. | link | count: 001 Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-9(4) | FedRAMP_High_R4_SA-9(4) | FedRAMP High SA-9 (4) | System And Services Acquisition | Consistent Interests Of Consumers And Providers | Shared | n/a | The organization employs [Assignment: organization-defined security safeguards] to ensure that the interests of [Assignment: organization-defined external service providers] are consistent with and reflect organizational interests. Supplemental Guidance: As organizations increasingly use external service providers, the possibility exists that the interests of the service providers may diverge from organizational interests. In such situations, simply having the correct technical, procedural, or operational safeguards in place may not be sufficient if the service providers that implement and control those safeguards are not operating in a manner consistent with the interests of the consuming organizations. Possible actions that organizations might take to address such concerns include, for example, requiring background checks for selected service provider personnel, examining ownership records, employing only trustworthy service providers (i.e., providers with which organizations have had positive experiences), and conducting periodic/unscheduled visits to service provider facilities. | link | count: 001 Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SA-9(5) | FedRAMP_High_R4_SA-9(5) | FedRAMP High SA-9 (5) | System And Services Acquisition | Processing, Storage, And Service Location | Shared | n/a | The organization restricts the location of [Selection (one or more): information processing; information/data; information system services] to [Assignment: organization-defined locations] based on [Assignment: organization-defined requirements or conditions]. Supplemental Guidance: The location of information processing, information/data storage, or information system services that are critical to organizations can have a direct impact on the ability of those organizations to successfully execute their missions/business functions. This situation exists when external providers control the location of processing, storage or services. The criteria external providers use for the selection of processing, storage, or service locations may be different from organizational criteria. For example, organizations may want to ensure that data/information storage locations are restricted to certain locations to facilitate incident response activities (e.g., forensic analyses, after-the-fact investigations) in case of information security breaches/compromises. Such incident response activities may be adversely affected by the governing laws or protocols in the locations where processing and storage occur and/or the locations from which information system services emanate. | link | count: 001 Restrict location of information processing, storage and services (0040d2e5-2779-170d-6a2c-1f5fca353335) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-1 | FedRAMP_High_R4_SC-1 | FedRAMP High SC-1 | System And Communications Protection | System And Communications Protection Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system and communications protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls; and b. Reviews and updates the current: 1. System and communications protection policy [Assignment: organization-defined frequency]; and 2. System and communications protection procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SC family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-10 | FedRAMP_High_R4_SC-10 | FedRAMP High SC-10 | System And Communications Protection | Network Disconnect | Shared | n/a | The information system terminates the network connection associated with a communications session at the end of the session or after [Assignment: organization-defined time period] of inactivity. Supplemental Guidance: This control applies to both internal and external networks. Terminating network connections associated with communications sessions include, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. Time periods of inactivity may be established by organizations and include, for example, time periods by type of network access or for specific network accesses. Control Enhancements: None. References: None. | link | count: 001 Reauthenticate or terminate a user session (d6653f89-7cb5-24a4-9d71-51581038231b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-12 | FedRAMP_High_R4_SC-12 | FedRAMP High SC-12 | System And Communications Protection | Cryptographic Key Establishment And Management | Shared | n/a | The organization establishes and manages cryptographic keys for required cryptography employed within the information system in accordance with [Assignment: organization-defined requirements for key generation, distribution, storage, access, and destruction]. Supplemental Guidance: Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. Organizations define key management requirements in accordance with applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance, specifying appropriate options, levels, and parameters. Organizations manage trust stores to ensure that only approved trust anchors are in such trust stores. This includes certificates with visibility external to organizational information systems and certificates related to the internal operations of systems. Related controls: SC-13, SC-17. References: NIST Special Publications 800-56, 800-57. | link | count: 040 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) (47031206-ce96-41f8-861b-6a915f3de284), Azure API for FHIR should use a customer-managed key to encrypt data at rest (051cba44-2429-45b9-9649-46cec11c7119), Azure Automation accounts should use customer-managed keys to encrypt data at rest (56a5ee18-2ae6-4810-86f7-18e39ce5629b), Azure Batch account should use customer-managed keys to encrypt data (99e9ccd8-3db9-4592-b0d1-14b1715a4d8a), Azure Container Instance container group should use customer-managed key for encryption (0aa61e00-0a01-4a3c-9945-e93cffedf0e6), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password (86efb160-8de7-451d-bc08-5d475b0aadae), Azure Data Explorer encryption at rest should use a customer-managed key (81e74cea-30fd-40d5-802f-d72103c2aaaa), Azure data factories should be encrypted with a customer-managed key (4ec52d6d-beb7-40c4-9a9e-fe753254690e), Azure HDInsight clusters should use customer-managed keys to encrypt data at rest (64d314f6-6062-4780-a861-c23e8951bee5), Azure HDInsight clusters should use encryption at host to encrypt data at rest (1fd32ebd-e4c3-4e13-a54a-d7422d4d95f6), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Stream Analytics jobs should use customer-managed keys to encrypt data (87ba29ef-1ab3-4d82-b763-87fcd4f531f7), Azure Synapse workspaces should use customer-managed keys to encrypt data at rest (f7d52b2d-e161-4dfa-a82b-55e564167385), Bot Service should be encrypted with a customer-managed key (51522a96-0869-4791-82f3-981000c2c67f), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Event Hub namespaces should use a customer-managed key for encryption (a1ad735a-e96f-45d2-a7b2-9a4932cab7ec), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Logic Apps Integration Service Environment should be encrypted with customer-managed keys (1fafeaf6-7927-4059-a50a-8eb2a7a6f2b5), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), OS and data disks should be encrypted with a customer-managed key (702dd420-7fcc-42c5-afe8-4026edd20fe0), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Service Bus Premium namespaces should use a customer-managed key for encryption (295fc8b1-dc9f-4f53-9c61-3f313ceab40a), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
API for FHIR, Automation, Azure Data Explorer, Backup, Batch, Bot Service, Cognitive Services, Compute, Container Instance, Container Registry, Cosmos DB, Data Box, Data Factory, Event Hub, HDInsight, Internet of Things, Kubernetes, Logic Apps, Machine Learning, Monitoring, Regulatory Compliance, Service Bus, SQL, Storage, Stream Analytics, Synapse | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-12(1) | FedRAMP_High_R4_SC-12(1) | FedRAMP High SC-12 (1) | System And Communications Protection | Availability | Shared | n/a | The organization maintains availability of information in the event of the loss of cryptographic keys by users. Supplemental Guidance: Escrowing of encryption keys is a common practice for ensuring availability in the event of loss of keys (e.g., due to forgotten passphrase). | link | count: 001 Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-12(2) | FedRAMP_High_R4_SC-12(2) | FedRAMP High SC-12 (2) | System And Communications Protection | Symmetric Keys | Shared | n/a | The organization produces, controls, and distributes symmetric cryptographic keys using [Selection: NIST FIPS-compliant; NSA-approved] key management technology and processes. | link | count: 001 Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-12(3) | FedRAMP_High_R4_SC-12(3) | FedRAMP High SC-12 (3) | System And Communications Protection | Asymmetric Keys | Shared | n/a | The organization produces, controls, and distributes asymmetric cryptographic keys using [Selection: NSA-approved key management technology and processes; approved PKI Class 3 certificates or prepositioned keying material; approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user’s private key]. | link | count: 001 Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-13 | FedRAMP_High_R4_SC-13 | FedRAMP High SC-13 | System And Communications Protection | Cryptographic Protection | Shared | n/a | The information system implements [Assignment: organization-defined cryptographic uses and type of cryptography required for each use] in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Supplemental Guidance: Cryptography can be employed to support a variety of security solutions including, for example, the protection of classified and Controlled Unclassified Information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Generally applicable cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. This control does not impose any requirements on organizations to use cryptography. However, if cryptography is required based on the selection of other security controls, organizations define each type of cryptographic use and the type of cryptography required (e.g., protection of classified information: NSA-approved cryptography; provision of digital signatures: FIPS-validated cryptography). Related controls: AC-2, AC-3, AC-7, AC-17, AC-18, AU-9, AU-10, CM-11, CP-9, IA-3, IA-7, MA-4, MP-2, MP-4, MP-5, SA-4, SC-8, SC-12, SC-28, SI-7. References: FIPS Publication 140; Web: http://csrc.nist.gov/cryptval, http://www.cnss.gov. | link | count: 001 Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-15 | FedRAMP_High_R4_SC-15 | FedRAMP High SC-15 | System And Communications Protection | Collaborative Computing Devices | Shared | n/a | The information system: a. Prohibits remote activation of collaborative computing devices with the following exceptions: [Assignment: organization-defined exceptions where remote activation is to be allowed]; and b. Provides an explicit indication of use to users physically present at the devices. Supplemental Guidance: Collaborative computing devices include, for example, networked white boards, cameras, and microphones. Explicit indication of use includes, for example, signals to users when collaborative computing devices are activated. Related control: AC-21. References: None. | link | count: 002 Explicitly notify use of collaborative computing devices (62fa14f0-4cbe-762d-5469-0899a99b98aa), Prohibit remote activation of collaborative computing devices (678ca228-042d-6d8e-a598-c58d5670437d) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-17 | FedRAMP_High_R4_SC-17 | FedRAMP High SC-17 | System And Communications Protection | Public Key Infrastructure Certificates | Shared | n/a | The organization issues public key certificates under an [Assignment: organization- defined certificate policy] or obtains public key certificates from an approved service provider. Supplemental Guidance: For all certificates, organizations manage information system trust stores to ensure only approved trust anchors are in the trust stores. This control addresses both certificates with visibility external to organizational information systems and certificates related to the internal operations of systems, for example, application-specific time services. Related control: SC-12. Control Enhancements: None. References: OMB Memorandum 05-24; NIST Special Publications 800-32, 800-63. | link | count: 001 Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-18 | FedRAMP_High_R4_SC-18 | FedRAMP High SC-18 | System And Communications Protection | Mobile Code | Shared | n/a | The organization: a. Defines acceptable and unacceptable mobile code and mobile code technologies; b. Establishes usage restrictions and implementation guidance for acceptable mobile code and mobile code technologies; and c. Authorizes, monitors, and controls the use of mobile code within the information system. Supplemental Guidance: Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include, for example, Java, JavaScript, ActiveX, Postscript, PDF, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices (e.g., smart phones). Mobile code policy and procedures address preventing the development, acquisition, or introduction of unacceptable mobile code within organizational information systems. Related controls: AU-2, AU-12, CM-2, CM-6, SI-3. References: NIST Special Publication 800-28; DoD Instruction 8552.01. | link | count: 003 Authorize, monitor, and control usage of mobile code technologies (291f20d4-8d93-1d73-89f3-6ce28b825563), Define acceptable and unacceptable mobile code technologies (1afada58-8b34-7ac2-a38a-983218635201), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-19 | FedRAMP_High_R4_SC-19 | FedRAMP High SC-19 | System And Communications Protection | Voice Over Internet Protocol | Shared | n/a | The organization: a. Establishes usage restrictions and implementation guidance for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously; and b. Authorizes, monitors, and controls the use of VoIP within the information system. Supplemental Guidance: Related controls: CM-6, SC-7, SC-15. References: NIST Special Publication 800-58. | link | count: 002 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Establish voip usage restrictions (68a39c2b-0f17-69ee-37a3-aa10f9853a08) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-2 | FedRAMP_High_R4_SC-2 | FedRAMP High SC-2 | System And Communications Protection | Application Partitioning | Shared | n/a | The information system separates user functionality (including user interface services) from information system management functionality. Supplemental Guidance: Information system management functionality includes, for example, functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical. Organizations implement separation of system management-related functionality from user functionality by using different computers, different central processing units, different instances of operating systems, different network addresses, virtualization techniques, or combinations of these or other methods, as appropriate. This type of separation includes, for example, web administrative interfaces that use separate authentication methods for users of any other information system resources. Separation of system and user functionality may include isolating administrative interfaces on different domains and with additional access controls. Related controls: SA-4, SA-8, SC-3. References: None. | link | count: 003 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-20 | FedRAMP_High_R4_SC-20 | FedRAMP High SC-20 | System And Communications Protection | Secure Name / Address Resolution Service (Authoritative Source) | Shared | n/a | The information system: a. Provides additional data origin and integrity artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries; and b. Provides the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace. Supplemental Guidance: This control enables external clients including, for example, remote Internet clients, to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. Information systems that provide name and address resolution services include, for example, domain name system (DNS) servers. Additional artifacts include, for example, DNS Security (DNSSEC) digital signatures and cryptographic keys. DNS resource records are examples of authoritative data. The means to indicate the security status of child zones includes, for example, the use of delegation signer resource records in the DNS. The DNS security controls reflect (and are referenced from) OMB Memorandum 08-23. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to assure the authenticity and integrity of response data. Related controls: AU-10, SC-8, SC-12, SC-13, SC-21, SC-22. References: OMB Memorandum 08-23; NIST Special Publication 800-81. | link | count: 002 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-21 | FedRAMP_High_R4_SC-21 | FedRAMP High SC-21 | System And Communications Protection | Secure Name / Address Resolution Service (Recursive Or Caching Resolver) | Shared | n/a | The information system requests and performs data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources. Supplemental Guidance: Each client of name resolution services either performs this validation on its own, or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching domain name system (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to enable clients to verify the authenticity and integrity of response data. Related controls: SC-20, SC-22. References: NIST Special Publication 800-81. | link | count: 002 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-22 | FedRAMP_High_R4_SC-22 | FedRAMP High SC-22 | System And Communications Protection | Architecture And Provisioning For Name / Address Resolution Service | Shared | n/a | The information systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal/external role separation. Supplemental Guidance: Information systems that provide name and address resolution services include, for example, domain name system (DNS) servers. To eliminate single points of failure and to enhance redundancy, organizations employ at least two authoritative domain name system servers, one configured as the primary server and the other configured as the secondary server. Additionally, organizations typically deploy the servers in two geographically separated network subnetworks (i.e., not located in the same physical facility). For role separation, DNS servers with internal roles only process name and address resolution requests from within organizations (i.e., from internal clients). DNS servers with external roles only process name and address resolution information requests from clients external to organizations (i.e., on external networks including the Internet). Organizations specify clients that can access authoritative DNS servers in particular roles (e.g., by address ranges, explicit lists). Related controls: SC-2, SC-20, SC-21, SC-24. Control Enhancements: None. References: NIST Special Publication 800-81. | link | count: 001 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-23 | FedRAMP_High_R4_SC-23 | FedRAMP High SC-23 | System And Communications Protection | Session Authenticity | Shared | n/a | The information system protects the authenticity of communications sessions. Supplemental Guidance: This control addresses communications protection at the session, versus packet level (e.g., sessions in service-oriented architectures providing web-based services) and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. Authenticity protection includes, for example, protecting against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. Related controls: SC-8, SC-10, SC-11. References: NIST Special Publications 800-52, 800-77, 800-95. | link | count: 002 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce random unique session identifiers (c7d57a6a-7cc2-66c0-299f-83bf90558f5d) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-23(1) | FedRAMP_High_R4_SC-23(1) | FedRAMP High SC-23 (1) | System And Communications Protection | Invalidate Session Identifiers At Logout | Shared | n/a | The information system invalidates session identifiers upon user logout or other session termination. Supplemental Guidance: This control enhancement curtails the ability of adversaries from capturing and continuing to employ previously valid session IDs. | link | count: 001 Invalidate session identifiers at logout (396f465d-375e-57de-58ba-021adb008191) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-24 | FedRAMP_High_R4_SC-24 | FedRAMP High SC-24 | System And Communications Protection | Fail In Known State | Shared | n/a | The information system fails to a [Assignment: organization-defined known-state] for [Assignment: organization-defined types of failures] preserving [Assignment: organization-defined system state information] in failure. Supplemental Guidance: Failure in a known state addresses security concerns in accordance with the mission/business needs of organizations. Failure in a known secure state helps to prevent the loss of confidentiality, integrity, or availability of information in the event of failures of organizational information systems or system components. Failure in a known safe state helps to prevent systems from failing to a state that may cause injury to individuals or destruction to property. Preserving information system state information facilitates system restart and return to the operational mode of organizations with less disruption of mission/business processes. Related controls: CP-2, CP- 10, CP-12, SC-7, SC-22. Control Enhancements: None. References: None. | link | count: 001 Ensure information system fails in known state (12af7c7a-92af-9e96-0d0c-5e732d1a3751) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-28 | FedRAMP_High_R4_SC-28 | FedRAMP High SC-28 | System And Communications Protection | Protection Of Information At Rest | Shared | n/a | The information system protects the [Selection (one or more): confidentiality; integrity] of [Assignment: organization-defined information at rest]. Supplemental Guidance: This control addresses the confidentiality and integrity of information at rest and covers user information and system information. Information at rest refers to the state of information when it is located on storage devices as specific components of information systems. System-related information requiring protection includes, for example, configurations or rule sets for firewalls, gateways, intrusion detection/prevention systems, filtering routers, and authenticator content. Organizations may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms and file share scanning. Integrity protection can be achieved, for example, by implementing Write-Once-Read-Many (WORM) technologies. Organizations may also employ other security controls including, for example, secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved and/or continuous monitoring to identify malicious code at rest. Related controls: AC-3, AC-6, CA-7, CM-3, CM-5, CM-6, PE-3, SC-8, SC-13, SI-3, SI-7. References: NIST Special Publications 800-56, 800-57, 800-111. | link | count: 017 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-28(1) | FedRAMP_High_R4_SC-28(1) | FedRAMP High SC-28 (1) | System And Communications Protection | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to prevent unauthorized disclosure and modification of [Assignment: organization-defined information] on [Assignment: organization-defined information system components]. Supplemental Guidance: Selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of organizational information. The strength of mechanism is commensurate with the security category and/or classification of the information. This control enhancement applies to significant concentrations of digital media in organizational areas designated for media storage and also to limited quantities of media generally associated with information system components in operational environments (e.g., portable storage devices, mobile devices). Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). Organizations employing cryptographic mechanisms to protect information at rest also consider cryptographic key management solutions. Related controls: AC-19, SC-12. | link | count: 017 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-3 | FedRAMP_High_R4_SC-3 | FedRAMP High SC-3 | System And Communications Protection | Security Function Isolation | Shared | n/a | The information system isolates security functions from nonsecurity functions. Supplemental Guidance: The information system isolates security functions from nonsecurity functions by means of an isolation boundary (implemented via partitions and domains). Such isolation controls access to and protects the integrity of the hardware, software, and firmware that perform those security functions. Information systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including, for example, through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk, and address space protections that protect executing code. Information systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities. While the ideal is for all of the code within the security function isolation boundary to only contain security-relevant code, it is sometimes necessary to include nonsecurity functions within the isolation boundary as an exception. Related controls: AC- 3, AC-6, SA-4, SA-5, SA-8, SA-13, SC-2, SC-7, SC-39. References: None. | link | count: 004 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-39 | FedRAMP_High_R4_SC-39 | FedRAMP High SC-39 | System And Communications Protection | Process Isolation | Shared | n/a | The information system maintains a separate execution domain for each executing process. Supplemental Guidance: Information systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each information system process has a distinct address space so that communication between processes is performed in a manner controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces. This capability is available in most commercial operating systems that employ multi-state processor technologies. Related controls: AC-3, AC-4, AC-6, SA-4, SA-5, SA-8, SC-2, SC-3. References: None. | link | count: 001 Maintain separate execution domains for running processes (bfc540fe-376c-2eef-4355-121312fa4437) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-5 | FedRAMP_High_R4_SC-5 | FedRAMP High SC-5 | System And Communications Protection | Denial Of Service Protection | Shared | n/a | The information system protects against or limits the effects of the following types of denial of service attacks: [Assignment: organization-defined types of denial of service attacks or reference to source for such information] by employing [Assignment: organization-defined security safeguards]. Supplemental Guidance: A variety of technologies exist to limit, or in some cases, eliminate the effects of denial of service attacks. For example, boundary protection devices can filter certain types of packets to protect information system components on internal organizational networks from being directly affected by denial of service attacks. Employing increased capacity and bandwidth combined with service redundancy may also reduce the susceptibility to denial of service attacks. Related controls: SC-6, SC-7. References: None. | link | count: 005 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Develop and document a DDoS response plan (b7306e73-0494-83a2-31f5-280e934a8f70), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Network, Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-6 | FedRAMP_High_R4_SC-6 | FedRAMP High SC-6 | System And Communications Protection | Resource Availability | Shared | n/a | The information system protects the availability of resources by allocating [Assignment: organization-defined resources] by [Selection (one or more); priority; quota; [Assignment: organization-defined security safeguards]]. Supplemental Guidance: Priority protection helps prevent lower-priority processes from delaying or interfering with the information system servicing any higher-priority processes. Quotas prevent users or processes from obtaining more than predetermined amounts of resources. This control does not apply to information system components for which there are only single users/roles. Control Enhancements: None. References: None. | link | count: 003 Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Manage availability and capacity (edcc36f1-511b-81e0-7125-abee29752fe7), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7 | FedRAMP_High_R4_SC-7 | FedRAMP High SC-7 | System And Communications Protection | Boundary Protection | Shared | n/a | The information system: a. Monitors and controls communications at the external boundary of the system and at key internal boundaries within the system; b. Implements subnetworks for publicly accessible system components that are [Selection: physically; logically] separated from internal organizational networks; and c. Connects to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture. Supplemental Guidance: Managed interfaces include, for example, gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within a security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational information systems includes, for example, restricting external web traffic to designated web servers within managed interfaces and prohibiting external traffic that appears to be spoofing internal addresses. Organizations consider the shared nature of commercial telecommunications services in the implementation of security controls associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers, and may also include third party-provided access lines and other service elements. Such transmission services may represent sources of increased risk despite contract security provisions. Related controls: AC-4, AC-17, CA-3, CM-7, CP-8, IR-4, RA-3, SC-5, SC-13. References: FIPS Publication 199; NIST Special Publications 800-41, 800-77. | link | count: 053 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Regulatory Compliance, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7(12) | FedRAMP_High_R4_SC-7(12) | FedRAMP High SC-7 (12) | System And Communications Protection | Host-Based Protection | Shared | n/a | The organization implements [Assignment: organization-defined host-based boundary protection mechanisms] at [Assignment: organization-defined information system components]. Supplemental Guidance: Host-based boundary protection mechanisms include, for example, host-based firewalls. Information system components employing host-based boundary protection mechanisms include, for example, servers, workstations, and mobile devices. | link | count: 001 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7(13) | FedRAMP_High_R4_SC-7(13) | FedRAMP High SC-7 (13) | System And Communications Protection | Isolation Of Security Tools / Mechanisms / Support Components | Shared | n/a | The organization isolates [Assignment: organization-defined information security tools, mechanisms, and support components] from other internal information system components by implementing physically separate subnetworks with managed interfaces to other components of the system. Supplemental Guidance: Physically separate subnetworks with managed interfaces are useful, for example, in isolating computer network defenses from critical operational processing networks to prevent adversaries from discovering the analysis and forensics techniques of organizations. Related controls: SA-8, SC-2, SC-3. | link | count: 001 Isolate SecurID systems, Security Incident Management systems (dd6d00a8-701a-5935-a22b-c7b9c0c698b2) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7(18) | FedRAMP_High_R4_SC-7(18) | FedRAMP High SC-7 (18) | System And Communications Protection | Fail Secure | Shared | n/a | The information system fails securely in the event of an operational failure of a boundary protection device. Supplemental Guidance: Fail secure is a condition achieved by employing information system mechanisms to ensure that in the event of operational failures of boundary protection devices at managed interfaces (e.g., routers, firewalls, guards, and application gateways residing on protected subnetworks commonly referred to as demilitarized zones), information systems do not enter into unsecure states where intended security properties no longer hold. Failures of boundary protection devices cannot lead to, or cause information external to the devices to enter the devices, nor can failures permit unauthorized information releases. Related controls: CP-2, SC-24. | link | count: 002 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage transfers between standby and active system components (df54d34f-65f3-39f1-103c-a0464b8615df) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7(20) | FedRAMP_High_R4_SC-7(20) | FedRAMP High SC-7 (20) | System And Communications Protection | Dynamic Isolation / Segregation | Shared | n/a | The information system provides the capability to dynamically isolate/segregate [Assignment: organization-defined information system components] from other components of the system. Supplemental Guidance: The capability to dynamically isolate or segregate certain internal components of organizational information systems is useful when it is necessary to partition or separate certain components of dubious origin from those components possessing greater trustworthiness. Component isolation reduces the attack surface of organizational information systems. Isolation of selected information system components is also a means of limiting the damage from successful cyber attacks when those attacks occur. | link | count: 001 Ensure system capable of dynamic isolation of resources (83eea3d3-0d2c-9ccd-1021-2111b29b2a62) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7(21) | FedRAMP_High_R4_SC-7(21) | FedRAMP High SC-7 (21) | System And Communications Protection | Isolation Of Information System Components | Shared | n/a | The organization employs boundary protection mechanisms to separate [Assignment: organization-defined information system components] supporting [Assignment: organization- defined missions and/or business functions]. Supplemental Guidance: Organizations can isolate information system components performing different missions and/or business functions. Such isolation limits unauthorized information flows among system components and also provides the opportunity to deploy greater levels of protection for selected components. Separating system components with boundary protection mechanisms provides the capability for increased protection of individual components and to more effectively control information flows between those components. This type of enhanced protection limits the potential harm from cyber attacks and errors. The degree of separation provided varies depending upon the mechanisms chosen. Boundary protection mechanisms include, for example, routers, gateways, and firewalls separating system components into physically separate networks or subnetworks, cross-domain devices separating subnetworks, virtualization techniques, and encrypting information flows among system components using distinct encryption keys. Related controls: CA-9, SC-3. | link | count: 001 Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7(3) | FedRAMP_High_R4_SC-7(3) | FedRAMP High SC-7 (3) | System And Communications Protection | Access Points | Shared | n/a | The organization limits the number of external network connections to the information system. Supplemental Guidance: Limiting the number of external network connections facilitates more comprehensive monitoring of inbound and outbound communications traffic. The Trusted Internet Connection (TIC) initiative is an example of limiting the number of external network connections. | link | count: 052 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7(4) | FedRAMP_High_R4_SC-7(4) | FedRAMP High SC-7 (4) | System And Communications Protection | External Telecommunications Services | Shared | n/a | The organization: (a) Implements a managed interface for each external telecommunication service; (b) Establishes a traffic flow policy for each managed interface; (c) Protects the confidentiality and integrity of the information being transmitted across each interface; (d) Documents each exception to the traffic flow policy with a supporting mission/business need and duration of that need; and (e) Reviews exceptions to the traffic flow policy [Assignment: organization-defined frequency] and removes exceptions that are no longer supported by an explicit mission/business need. Supplemental Guidance: Related control: SC-8. | link | count: 003 Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7(7) | FedRAMP_High_R4_SC-7(7) | FedRAMP High SC-7 (7) | System And Communications Protection | Prevent Split Tunneling For Remote Devices | Shared | n/a | The information system, in conjunction with a remote device, prevents the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks. Supplemental Guidance: This control enhancement is implemented within remote devices (e.g., notebook computers) through configuration settings to disable split tunneling in those devices, and by preventing those configuration settings from being readily configurable by users. This control enhancement is implemented within the information system by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling. Split tunneling might be desirable by remote users to communicate with local information system resources such as printers/file servers. However, split tunneling would in effect allow unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. The use of VPNs for remote connections, when adequately provisioned with appropriate security controls, may provide the organization with sufficient assurance that it can effectively treat such connections as non-remote connections from the confidentiality and integrity perspective. VPNs thus provide a means for allowing non-remote communications paths from remote devices. The use of an adequately provisioned VPN does not eliminate the need for preventing split tunneling. | link | count: 001 Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-7(8) | FedRAMP_High_R4_SC-7(8) | FedRAMP High SC-7 (8) | System And Communications Protection | Route Traffic To Authenticated Proxy Servers | Shared | n/a | The information system routes [Assignment: organization-defined internal communications traffic] to [Assignment: organization-defined external networks] through authenticated proxy servers at managed interfaces. Supplemental Guidance: External networks are networks outside of organizational control. A proxy server is a server (i.e., information system or application) that acts as an intermediary for clients requesting information system resources (e.g., files, connections, web pages, or services) from other organizational servers. Client requests established through an initial connection to the proxy server are evaluated to manage complexity and to provide additional protection by limiting direct connectivity. Web content filtering devices are one of the most common proxy servers providing access to the Internet. Proxy servers support logging individual Transmission Control Protocol (TCP) sessions and blocking specific Uniform Resource Locators (URLs), domain names, and Internet Protocol (IP) addresses. Web proxies can be configured with organization-defined lists of authorized and unauthorized websites. Related controls: AC-3, AU-2. | link | count: 001 Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-8 | FedRAMP_High_R4_SC-8 | FedRAMP High SC-8 | System And Communications Protection | Transmission Confidentiality And Integrity | Shared | n/a | The information system protects the [Selection (one or more): confidentiality; integrity] of transmitted information. Supplemental Guidance: This control applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and/or integrity of organizational information can be accomplished by physical means (e.g., by employing physical distribution systems) or by logical means (e.g., employing encryption techniques). Organizations relying on commercial providers offering transmission services as commodity services rather than as fully dedicated services (i.e., services which can be highly specialized to individual customer needs), may find it difficult to obtain the necessary assurances regarding the implementation of needed security controls for transmission confidentiality/integrity. In such situations, organizations determine what types of confidentiality/integrity services are available in standard, commercial telecommunication service packages. If it is infeasible or impractical to obtain the necessary security controls and assurances of control effectiveness through appropriate contracting vehicles, organizations implement appropriate compensating security controls or explicitly accept the additional risk. Related controls: AC-17, PE-4. References: FIPS Publications 140-2, 197; NIST Special Publications 800-52, 800-77, 800-81, 800-113; CNSS Policy 15; NSTISSI No. 7003. | link | count: 015 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, Regulatory Compliance, SQL, Storage | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SC-8(1) | FedRAMP_High_R4_SC-8(1) | FedRAMP High SC-8 (1) | System And Communications Protection | Cryptographic Or Alternate Physical Protection | Shared | n/a | The information system implements cryptographic mechanisms to [Selection (one or more): prevent unauthorized disclosure of information; detect changes to information] during transmission unless otherwise protected by [Assignment: organization-defined alternative physical safeguards]. Supplemental Guidance: Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions which have common application in digital signatures, checksums, and message authentication codes. Alternative physical security safeguards include, for example, protected distribution systems. Related control: SC-13. | link | count: 014 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, Regulatory Compliance, SQL, Storage | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-1 | FedRAMP_High_R4_SI-1 | FedRAMP High SI-1 | System And Information Integrity | System And Information Integrity Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system and information integrity policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls; and b. Reviews and updates the current: 1. System and information integrity policy [Assignment: organization-defined frequency]; and 2. System and information integrity procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SI family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-10 | FedRAMP_High_R4_SI-10 | FedRAMP High SI-10 | System And Information Integrity | Information Input Validation | Shared | n/a | The information system checks the validity of [Assignment: organization-defined information inputs]. Supplemental Guidance: Checking the valid syntax and semantics of information system inputs (e.g., character set, length, numerical range, and acceptable values) verifies that inputs match specified definitions for format and content. Software applications typically follow well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If software applications use attacker- supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the tainted output will perform the wrong operations or otherwise interpret the data incorrectly. Prescreening inputs prior to passing to interpreters prevents the content from being unintentionally interpreted as commands. Input validation helps to ensure accurate and correct inputs and prevent attacks such as cross-site scripting and a variety of injection attacks. References: None. | link | count: 001 Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-11 | FedRAMP_High_R4_SI-11 | FedRAMP High SI-11 | System And Information Integrity | Error Handling | Shared | n/a | The information system: a. Generates error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries; and b. Reveals error messages only to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information such as account numbers, social security numbers, and credit card numbers. In addition, error messages may provide a covert channel for transmitting information. Related controls: AU-2, AU-3, SC-31. Control Enhancements: None. References: None. | link | count: 002 Generate error messages (c2cb4658-44dc-9d11-3dad-7c6802dd5ba3), Reveal error messages (20762f1e-85fb-31b0-a600-e833633f10fe) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-12 | FedRAMP_High_R4_SI-12 | FedRAMP High SI-12 | System And Information Integrity | Information Handling And Retention | Shared | n/a | The organization handles and retains information within the information system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements. Supplemental Guidance: Information handling and retention requirements cover the full life cycle of information, in some cases extending beyond the disposal of information systems. The National Archives and Records Administration provides guidance on records retention. Related controls: AC-16, AU-5, AU-11, MP-2, MP-4. Control Enhancements: None. References: None. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-16 | FedRAMP_High_R4_SI-16 | FedRAMP High SI-16 | System And Information Integrity | Memory Protection | Shared | n/a | The information system implements [Assignment: organization-defined security safeguards] to protect its memory from unauthorized code execution. Supplemental Guidance: Some adversaries launch attacks with the intent of executing code in non- executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. Related controls: AC-25, SC-3. Control Enhancements: None. References: None. | link | count: 002 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-2 | FedRAMP_High_R4_SI-2 | FedRAMP High SI-2 | System And Information Integrity | Flaw Remediation | Shared | n/a | The organization: a. Identifies, reports, and corrects information system flaws; b. Tests software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation; c. Installs security-relevant software and firmware updates within [Assignment: organization- defined time period] of the release of the updates; and d. Incorporates flaw remediation into the organizational configuration management process. Supplemental Guidance: Organizations identify information systems affected by announced software flaws including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security responsibilities. Security-relevant software updates include, for example, patches, service packs, hot fixes, and anti-virus signatures. Organizations also address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations take advantage of available resources such as the Common Weakness Enumeration (CWE) or Common Vulnerabilities and Exposures (CVE) databases in remediating flaws discovered in organizational information systems. By incorporating flaw remediation into ongoing configuration management processes, required/anticipated remediation actions can be tracked and verified. Flaw remediation actions that can be tracked and verified include, for example, determining whether organizations follow US-CERT guidance and Information Assurance Vulnerability Alerts. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types. Organizations determine the degree and type of testing needed for the specific type of flaw remediation activity under consideration and also the types of changes that are to be configuration-managed. In some situations, organizations may determine that the testing of software and/or firmware updates is not necessary or practical, for example, when implementing simple anti-virus signature updates. Organizations may also consider in testing decisions, whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures. Related controls: CA-2, CA-7, CM-3, CM-5, CM-8, MA-2, IR-4, RA-5, SA-10, SA-11, SI-11. | link | count: 019 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
App Service, Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-2(2) | FedRAMP_High_R4_SI-2(2) | FedRAMP High SI-2 (2) | System And Information Integrity | Automated Flaw Remediation Status | Shared | n/a | The organization employs automated mechanisms [Assignment: organization-defined frequency] to determine the state of information system components with regard to flaw remediation. Supplemental Guidance: Related controls: CM-6, SI-4. | link | count: 002 Automate flaw remediation (a90c4d44-7fac-8e02-6d5b-0d92046b20e6), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-2(3) | FedRAMP_High_R4_SI-2(3) | FedRAMP High SI-2 (3) | System And Information Integrity | Time To Remediate Flaws / Benchmarks For Corrective Actions | Shared | n/a | The organization: (a) Measures the time between flaw identification and flaw remediation; and (b) Establishes [Assignment: organization-defined benchmarks] for taking corrective actions. Supplemental Guidance: This control enhancement requires organizations to determine the current time it takes on the average to correct information system flaws after such flaws have been identified, and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by type of flaw and/or severity of the potential vulnerability if the flaw can be exploited. | link | count: 002 Establish benchmarks for flaw remediation (dd2523d5-2db3-642b-a1cf-83ac973b32c2), Measure the time between flaw identification and flaw remediation (dad1887d-161b-7b61-2e4d-5124a7b5724e) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-3 | FedRAMP_High_R4_SI-3 | FedRAMP High SI-3 | System And Information Integrity | Malicious Code Protection | Shared | n/a | The organization: a. Employs malicious code protection mechanisms at information system entry and exit points to detect and eradicate malicious code; b. Updates malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures; c. Configures malicious code protection mechanisms to: 1. Perform periodic scans of the information system [Assignment: organization-defined frequency] and real-time scans of files from external sources at [Selection (one or more); endpoint; network entry/exit points] as the files are downloaded, opened, or executed in accordance with organizational security policy; and 2. [Selection (one or more): block malicious code; quarantine malicious code; send alert to administrator; [Assignment: organization-defined action]] in response to malicious code detection; and d. Addresses the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the information system. Supplemental Guidance: Information system entry and exit points include, for example, firewalls, electronic mail servers, web servers, proxy servers, remote-access servers, workstations, notebook computers, and mobile devices. Malicious code includes, for example, viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using steganography. Malicious code can be transported by different means including, for example, web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of information system vulnerabilities. Malicious code protection mechanisms include, for example, anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include, for example, logic bombs, back doors, and other types of cyber attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including, for example, secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. Organizations may determine that in response to the detection of malicious code, different actions may be warranted. For example, organizations can define actions in response to malicious code detection during periodic scans, actions in response to detection of malicious downloads, and/or actions in response to detection of maliciousness when attempting to open or execute files. Related controls: CM-3, MP-2, SA-4, SA-8, SA-12, SA-13, SC-7, SC-26, SC-44, SI-2, SI-4, SI-7. References: NIST Special Publication 800-83. | link | count: 011 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-3(1) | FedRAMP_High_R4_SI-3(1) | FedRAMP High SI-3 (1) | System And Information Integrity | Central Management | Shared | n/a | The organization centrally manages malicious code protection mechanisms. Supplemental Guidance: Central management is the organization-wide management and implementation of malicious code protection mechanisms. Central management includes planning, implementing, assessing, authorizing, and monitoring the organization-defined, centrally managed flaw malicious code protection security controls. Related controls: AU-2, SI-8. | link | count: 010 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Regulatory Compliance, Security Center | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-3(2) | FedRAMP_High_R4_SI-3(2) | FedRAMP High SI-3 (2) | System And Information Integrity | Automatic Updates | Shared | n/a | The information system automatically updates malicious code protection mechanisms. Supplemental Guidance: Malicious code protection mechanisms include, for example, signature definitions. Due to information system integrity and availability concerns, organizations give careful consideration to the methodology used to carry out automatic updates. Related control: SI-8. | link | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-3(7) | FedRAMP_High_R4_SI-3(7) | FedRAMP High SI-3 (7) | System And Information Integrity | Nonsignature-Based Detection | Shared | n/a | The information system implements nonsignature-based malicious code detection mechanisms. Supplemental Guidance: Nonsignature-based detection mechanisms include, for example, the use of heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide safeguards against malicious code for which signatures do not yet exist or for which existing signatures may not be effective. This includes polymorphic malicious code (i.e., code that changes signatures when it replicates). This control enhancement does not preclude the use of signature-based detection mechanisms. | link | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-4 | FedRAMP_High_R4_SI-4 | FedRAMP High SI-4 | System And Information Integrity | Information System Monitoring | Shared | n/a | The organization: a. Monitors the information system to detect: 1. Attacks and indicators of potential attacks in accordance with [Assignment: organization- defined monitoring objectives]; and 2. Unauthorized local, network, and remote connections; b. Identifies unauthorized use of the information system through [Assignment: organization- defined techniques and methods]; c. Deploys monitoring devices: (i) strategically within the information system to collect organization-determined essential information; and (ii) at ad hoc locations within the system to track specific types of transactions of interest to the organization; d. Protects information obtained from intrusion-monitoring tools from unauthorized access, modification, and deletion; e. Heightens the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information; f. Obtains legal opinion with regard to information system monitoring activities in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations; and g. Provides [Assignment: or ganization-defined information system monitoring information] to [Assignment: organization-defined personnel or roles] [Selection (one or more): as needed; [Assignment: organization-defined frequency]]. Supplemental Guidance: Information system monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at the information system boundary (i.e., part of perimeter defense and boundary protection). Internal monitoring includes the observation of events occurring within the information system. Organizations can monitor information systems, for example, by observing audit activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives may guide determination of the events. Information system monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Strategic locations for monitoring devices include, for example, selected perimeter locations and near server farms supporting critical applications, with such devices typically being employed at the managed interfaces associated with controls SC-7 and AC-17. Einstein network monitoring devices from the Department of Homeland Security can also be included as monitoring devices. The granularity of monitoring information collected is based on organizational monitoring objectives and the capability of information systems to support such objectives. Specific types of transactions of interest include, for example, Hyper Text Transfer Protocol (HTTP) traffic that bypasses HTTP proxies. Information system monitoring is an integral part of organizational continuous monitoring and incident response programs. Output from system monitoring serves as input to continuous monitoring and incident response programs. A network connection is any connection with a device that communicates through a network (e.g., local area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Local, network, and remote connections can be either wired or wireless. Related controls: AC-3, AC-4, AC-8, AC-17, AU-2, AU-6, AU-7, AU-9, AU-12, CA-7, IR-4, PE-3, RA-5, SC-7, SC-26, SC-35, SI-3, SI-7. References: NIST Special Publications 800-61, 800-83, 800-92, 800-94, 800-137. | link | count: 025 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-4(14) | FedRAMP_High_R4_SI-4(14) | FedRAMP High SI-4 (14) | System And Information Integrity | Wireless Intrusion Detection | Shared | n/a | The organization employs a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises/breaches to the information system. Supplemental Guidance: Wireless signals may radiate beyond the confines of organization- controlled facilities. Organizations proactively search for unauthorized wireless connections including the conduct of thorough scans for unauthorized wireless access points. Scans are not limited to those areas within facilities containing information systems, but also include areas outside of facilities as needed, to verify that unauthorized wireless access points are not connected to the systems. Related controls: AC-18, IA-3. | link | count: 001 Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-4(2) | FedRAMP_High_R4_SI-4(2) | FedRAMP High SI-4 (2) | System And Information Integrity | Automated Tools For Real-Time Analysis | Shared | n/a | The organization employs automated tools to support near real-time analysis of events. Supplemental Guidance: Automated tools include, for example, host-based, network-based, transport-based, or storage-based event monitoring tools or Security Information and Event Management (SIEM) technologies that provide real time analysis of alerts and/or notifications generated by organizational information systems. | link | count: 002 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-4(22) | FedRAMP_High_R4_SI-4(22) | FedRAMP High SI-4 (22) | System And Information Integrity | Unauthorized Network Services | Shared | n/a | The information system detects network services that have not been authorized or approved by [Assignment: organization-defined authorization or approval processes] and [Selection (one or more): audits; alerts [Assignment: organization-defined personnel or roles]]. Supplemental Guidance: Unauthorized or unapproved network services include, for example, services in service-oriented architectures that lack organizational verification or validation and therefore may be unreliable or serve as malicious rogues for valid services. Related controls: AC-6, CM-7, SA-5, SA-9. | link | count: 001 Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-4(24) | FedRAMP_High_R4_SI-4(24) | FedRAMP High SI-4 (24) | System And Information Integrity | Indicators Of Compromise | Shared | n/a | The information system discovers, collects, distributes, and uses indicators of compromise. Supplemental Guidance: Indicators of compromise (IOC) are forensic artifacts from intrusions that are identified on organizational information systems (at the host or network level). IOCs provide organizations with valuable information on objects or information systems that have been compromised. IOCs for the discovery of compromised hosts can include for example, the creation of registry key values. IOCs for network traffic include, for example, Universal Resource Locator (URL) or protocol elements that indicate malware command and control servers. The rapid distribution and adoption of IOCs can improve information security by reducing the time that information systems and organizations are vulnerable to the same exploit or attack. | link | count: 001 Discover any indicators of compromise (07b42fb5-027e-5a3c-4915-9d9ef3020ec7) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-4(4) | FedRAMP_High_R4_SI-4(4) | FedRAMP High SI-4 (4) | System And Information Integrity | Inbound And Outbound Communications Traffic | Shared | n/a | The information system monitors inbound and outbound communications traffic [Assignment: organization-defined frequency] for unusual or unauthorized activities or conditions. Supplemental Guidance: Unusual/unauthorized activities or conditions related to information system inbound and outbound communications traffic include, for example, internal traffic that indicates the presence of malicious code within organizational information systems or propagating among system components, the unauthorized exporting of information, or signaling to external information systems. Evidence of malicious code is used to identify potentially compromised information systems or information system components. | link | count: 004 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-4(5) | FedRAMP_High_R4_SI-4(5) | FedRAMP High SI-4 (5) | System And Information Integrity | System-Generated Alerts | Shared | n/a | The information system alerts [Assignment: organization-defined personnel or roles] when the following indications of compromise or potential compromise occur: [Assignment: organization- defined compromise indicators]. Supplemental Guidance: Alerts may be generated from a variety of sources, including, for example, audit records or inputs from malicious code protection mechanisms, intrusion detection or prevention mechanisms, or boundary protection devices such as firewalls, gateways, and routers. Alerts can be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. Organizational personnel on the notification list can include, for example, system administrators, mission/business owners, system owners, or information system security officers. Related controls: AU-5, PE-6. | link | count: 003 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-5 | FedRAMP_High_R4_SI-5 | FedRAMP High SI-5 | System And Information Integrity | Security Alerts, Advisories, And Directives | Shared | n/a | The organization: a. Receives information system security alerts, advisories, and directives from [Assignment: organization-defined external organizations] on an ongoing basis; b. Generates internal security alerts, advisories, and directives as deemed necessary; c. Disseminates security alerts, advisories, and directives to: [Selection (one or more): [Assignment: organization-defined personnel or roles]; [Assignment: organization-defined elements within the organization]; [Assignment: organization-defined external organizations]]; and d. Implements security directives in accordance with established time frames, or notifies the issuing organization of the degree of noncompliance. Supplemental Guidance: The United States Computer Emergency Readiness Team (US-CERT) generates security alerts and advisories to maintain situational awareness across the federal government. Security directives are issued by OMB or other designated organizations with the responsibility and authority to issue such directives. Compliance to security directives is essential due to the critical nature of many of these directives and the potential immediate adverse effects on organizational operations and assets, individuals, other organizations, and the Nation should the directives not be implemented in a timely manner. External organizations include, for example, external mission/business partners, supply chain partners, external service providers, and other peer/supporting organizations. Related control: SI-2. References: NIST Special Publication 800-40. | link | count: 004 Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Generate internal security alerts (171e377b-5224-4a97-1eaa-62a3b5231dac), Implement security directives (26d178a4-9261-6f04-a100-47ed85314c6e) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-5(1) | FedRAMP_High_R4_SI-5(1) | FedRAMP High SI-5 (1) | System And Information Integrity | Automated Alerts And Advisories | Shared | n/a | The organization employs automated mechanisms to make security alert and advisory information available throughout the organization. Supplemental Guidance: The significant number of changes to organizational information systems and the environments in which those systems operate requires the dissemination of security-related information to a variety of organizational entities that have a direct interest in the success of organizational missions and business functions. Based on the information provided by the security alerts and advisories, changes may be required at one or more of the three tiers related to the management of information security risk including the governance level, mission/business process/enterprise architecture level, and the information system level. | link | count: 001 Use automated mechanisms for security alerts (b8689b2e-4308-a58b-a0b4-6f3343a000df) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-6 | FedRAMP_High_R4_SI-6 | FedRAMP High SI-6 | System And Information Integrity | Security Function Verification | Shared | n/a | The information system: a. Verifies the correct operation of [Assignment: organization-defined security functions]; b. Performs this verification [Selection (one or more): [Assignment: organization-defined system transitional states]; upon command by user with appropriate privilege; [Assignment: organization-defined frequency]]; c. Notifies [Assignment: organization-defined personnel or roles] of failed security verification tests; and d. [Selection (one or more): shuts the information system down; restarts the information system; [Assignment: organization-defined alternative action(s)]] when anomalies are discovered. Supplemental Guidance: Transitional states for information systems include, for example, system startup, restart, shutdown, and abort. Notifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications such as lights. Related controls: CA-7, CM-6. References: None. | link | count: 004 Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Notify personnel of any failed security verification tests (18e9d748-73d4-0c96-55ab-b108bfbd5bc3), Perform security function verification at a defined frequency (f30edfad-4e1d-1eef-27ee-9292d6d89842), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-7 | FedRAMP_High_R4_SI-7 | FedRAMP High SI-7 | System And Information Integrity | Software, Firmware, And Information Integrity | Shared | n/a | The organization employs integrity verification tools to detect unauthorized changes to [Assignment: organization-defined software, firmware, and information]. Supplemental Guidance: Unauthorized changes to software, firmware, and information can occur due to errors or malicious activity (e.g., tampering). Software includes, for example, operating systems (with key internal components such as kernels, drivers), middleware, and applications. Firmware includes, for example, the Basic Input Output System (BIOS). Information includes metadata such as security attributes associated with information. State-of-the-practice integrity- checking mechanisms (e.g., parity checks, cyclical redundancy checks, cryptographic hashes) and associated tools can automatically monitor the integrity of information systems and hosted applications. Related controls: SA-12, SC-8, SC-13, SI-3. References: NIST Special Publications 800-147, 800-155. | link | count: 001 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-7(1) | FedRAMP_High_R4_SI-7(1) | FedRAMP High SI-7 (1) | System And Information Integrity | Integrity Checks | Shared | n/a | The information system performs an integrity check of [Assignment: organization-defined software, firmware, and information] [Selection (one or more): at startup; at [Assignment: organization-defined transitional states or security-relevant events]; [Assignment: organization- defined frequency]]. Supplemental Guidance: Security-relevant events include, for example, the identification of a new threat to which organizational information systems are susceptible, and the installation of new hardware, software, or firmware. Transitional states include, for example, system startup, restart, shutdown, and abort. | link | count: 002 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-7(14) | FedRAMP_High_R4_SI-7(14) | FedRAMP High SI-7 (14) | System And Information Integrity | Binary Or Machine Executable Code | Shared | n/a | The organization: (a) Prohibits the use of binary or machine-executable code from sources with limited or no warranty and without the provision of source code; and (b) Provides exceptions to the source code requirement only for compelling mission/operational requirements and with the approval of the authorizing official. Supplemental Guidance: This control enhancement applies to all sources of binary or machine- executable code including, for example, commercial software/firmware and open source software. Organizations assess software products without accompanying source code from sources with limited or no warranty for potential security impacts. The assessments address the fact that these types of software products may be very difficult to review, repair, or extend, given that organizations, in most cases, do not have access to the original source code, and there may be no owners who could make such repairs on behalf of organizations. Related control: SA-5. | link | count: 001 Prohibit binary/machine-executable code (8e920169-739d-40b5-3f99-c4d855327bb2) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_High_R4 | SI-7(5) | FedRAMP_High_R4_SI-7(5) | FedRAMP High SI-7 (5) | System And Information Integrity | Automated Response To Integrity Violations | Shared | n/a | The information system automatically [Selection (one or more): shuts the information system down; restarts the information system; implements [Assignment: organization-defined security safeguards]] when integrity violations are discovered. Supplemental Guidance: Organizations may define different integrity checking and anomaly responses: (i) by type of information (e.g., firmware, software, user data); (ii) by specific information (e.g., boot firmware, boot firmware for a specific types of machines); or (iii) a combination of both. Automatic implementation of specific safeguards within organizational information systems includes, for example, reversing the changes, halting the information system, or triggering audit alerts when unauthorized modifications to critical security files occur. | link | count: 001 Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4) |
Regulatory Compliance | FedRAMP High (d5264498-16f4-418a-b659-fa7ef418175f) |
| FedRAMP_Moderate_R4 | AC-1 | FedRAMP_Moderate_R4_AC-1 | FedRAMP Moderate AC-1 | Access Control | Access Control Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the access control policy and associated access controls; and b. Reviews and updates the current: 1. Access control policy [Assignment: organization-defined frequency]; and 2. Access control procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AC family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-10 | FedRAMP_Moderate_R4_AC-10 | FedRAMP Moderate AC-10 | Access Control | Concurrent Session Control | Shared | n/a | The information system limits the number of concurrent sessions for each [Assignment: organization-defined account and/or account type] to [Assignment: organization-defined number]. Supplemental Guidance: Organizations may define the maximum number of concurrent sessions for information system accounts globally, by account type (e.g., privileged user, non-privileged user, domain, specific application), by account, or a combination. For example, organizations may limit the number of concurrent sessions for system administrators or individuals working in particularly sensitive domains or mission-critical applications. This control addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. Control Enhancements: None. References: None. | link | count: 001 Define and enforce the limit of concurrent sessions (d8350d4c-9314-400b-288f-20ddfce04fbd) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-12 | FedRAMP_Moderate_R4_AC-12 | FedRAMP Moderate AC-12 | Access Control | Session Termination | Shared | n/a | The information system automatically terminates a user session after [Assignment: organization-defined conditions or trigger events requiring session disconnect]. Supplemental Guidance: This control addresses the termination of user-initiated logical sessions in contrast to SC-10 which addresses the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user’s logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, time-of-day restrictions on information system use. Related controls: SC-10, SC-23. References: None. | link | count: 001 Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-14 | FedRAMP_Moderate_R4_AC-14 | FedRAMP Moderate AC-14 | Access Control | Permitted Actions Without Identification Or Authentication | Shared | n/a | The organization: a. Identifies [Assignment: organization-defined user actions] that can be performed on the information system without identification or authentication consistent with organizational missions/business functions; and b. Documents and provides supporting rationale in the security plan for the information system, user actions not requiring identification or authentication. Supplemental Guidance: This control addresses situations in which organizations determine that no identification or authentication is required in organizational information systems. Organizations may allow a limited number of user actions without identification or authentication including, for example, when individuals access public websites or other publicly accessible federal information systems, when individuals use mobile phones to receive calls, or when facsimiles are received. Organizations also identify actions that normally require identification or authentication but may under certain circumstances (e.g., emergencies), allow identification or authentication mechanisms to be bypassed. Such bypasses may occur, for example, via a software-readable physical switch that commands bypass of the logon functionality and is protected from accidental or unmonitored use. This control does not apply to situations where identification and authentication have already occurred and are not repeated, but rather to situations where identification and authentication have not yet occurred. Organizations may decide that there are no user actions that can be performed on organizational information systems without identification and authentication and thus, the values for assignment statements can be none. Related controls: CP-2, IA-2. Control Enhancements: None. (1) PERMITTED ACTIONS WITHOUT IDENTIFICATION OR AUTHENTICATION | NECESSARY USES [Withdrawn: Incorporated into AC-14]. References: None. | link | count: 001 Identify actions allowed without authentication (92a7591f-73b3-1173-a09c-a08882d84c70) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-17 | FedRAMP_Moderate_R4_AC-17 | FedRAMP Moderate AC-17 | Access Control | Remote Access | Shared | n/a | The organization: a. Establishes and documents usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and b. Authorizes remote access to the information system prior to allowing such connections. Supplemental Guidance: Remote access is access to organizational information systems by users (or processes acting on behalf of users) communicating through external networks (e.g., the Internet). Remote access methods include, for example, dial-up, broadband, and wireless. Organizations often employ encrypted virtual private networks (VPNs) to enhance confidentiality and integrity over remote connections. The use of encrypted VPNs does not make the access non-remote; however, the use of VPNs, when adequately provisioned with appropriate security controls (e.g., employing appropriate encryption techniques for confidentiality and integrity protection) may provide sufficient assurance to the organization that it can effectively treat such connections as internal networks. Still, VPN connections traverse external networks, and the encrypted VPN does not enhance the availability of remote connections. Also, VPNs with encrypted tunnels can affect the organizational capability to adequately monitor network communications traffic for malicious code. Remote access controls apply to information systems other than public web servers or systems designed for public access. This control addresses authorization prior to allowing remote access without specifying the formats for such authorization. While organizations may use interconnection security agreements to authorize remote access connections, such agreements are not required by this control. Enforcing access restrictions for remote connections is addressed in AC-3. Related controls: AC-2, AC-3, AC-18, AC-19, AC-20, CA-3, CA-7, CM-8, IA-2, IA-3, IA-8, MA-4, PE-17, PL-4, SC-10, SI-4. References: NIST Special Publications 800-46, 800-77, 800-113, 800-114, 800-121. | link | count: 041 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-17(1) | FedRAMP_Moderate_R4_AC-17(1) | FedRAMP Moderate AC-17 (1) | Access Control | Automated Monitoring / Control | Shared | n/a | The information system monitors and controls remote access methods. Supplemental Guidance: Automated monitoring and control of remote access sessions allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote users on a variety of information system components (e.g., servers, workstations, notebook computers, smart phones, and tablets). Related controls: AU-2, AU-12. | link | count: 037 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-17(2) | FedRAMP_Moderate_R4_AC-17(2) | FedRAMP Moderate AC-17 (2) | Access Control | Protection Of Confidentiality / Integrity Using Encryption | Shared | n/a | The information system implements cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions. Supplemental Guidance: The encryption strength of mechanism is selected based on the security categorization of the information. Related controls: SC-8, SC-12, SC-13. | link | count: 002 Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-17(3) | FedRAMP_Moderate_R4_AC-17(3) | FedRAMP Moderate AC-17 (3) | Access Control | Managed Access Control Points | Shared | n/a | The information system routes all remote accesses through [Assignment: organization-defined number] managed network access control points. Supplemental Guidance: Limiting the number of access control points for remote accesses reduces the attack surface for organizations. Organizations consider the Trusted Internet Connections (TIC) initiative requirements for external network connections. Related control: SC-7. | link | count: 001 Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-17(4) | FedRAMP_Moderate_R4_AC-17(4) | FedRAMP Moderate AC-17 (4) | Access Control | Privileged Commands / Access | Shared | n/a | The organization: (a) Authorizes the execution of privileged commands and access to security-relevant information via remote access only for [Assignment: organization-defined needs]; and (b) Documents the rationale for such access in the security plan for the information system. Supplemental Guidance: Related control: AC-6. | link | count: 005 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Authorize remote access to privileged commands (01c387ea-383d-4ca9-295a-977fab516b03), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-17(9) | FedRAMP_Moderate_R4_AC-17(9) | FedRAMP Moderate AC-17 (9) | Access Control | Disconnect / Disable Access | Shared | n/a | The organization provides the capability to expeditiously disconnect or disable remote access to the information system within [Assignment: organization-defined time period]. Supplemental Guidance: This control enhancement requires organizations to have the capability to rapidly disconnect current users remotely accessing the information system and/or disable further remote access. The speed of disconnect or disablement varies based on the criticality of missions/business functions and the need to eliminate immediate or future remote access to organizational information systems. | link | count: 001 Provide capability to disconnect or disable remote access (4edaca8c-0912-1ac5-9eaa-6a1057740fae) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-18 | FedRAMP_Moderate_R4_AC-18 | FedRAMP Moderate AC-18 | Access Control | Wireless Access | Shared | n/a | The organization: a. Establishes usage restrictions, configuration/connection requirements, and implementation guidance for wireless access; and b. Authorizes wireless access to the information system prior to allowing such connections. Supplemental Guidance: Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual authentication. Related controls: AC-2, AC-3, AC-17, AC-19, CA-3, CA-7, CM-8, IA-2, IA-3, IA-8, PL-4, SI-4. References: NIST Special Publications 800-48, 800-94, 800-97. | link | count: 002 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-18(1) | FedRAMP_Moderate_R4_AC-18(1) | FedRAMP Moderate AC-18 (1) | Access Control | Authentication And Encryption | Shared | n/a | The information system protects wireless access to the system using authentication of [Selection (one or more): users; devices] and encryption. Supplemental Guidance: Related controls: SC-8, SC-13. | link | count: 003 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-19 | FedRAMP_Moderate_R4_AC-19 | FedRAMP Moderate AC-19 | Access Control | Access Control For Mobile Devices | Shared | n/a | The organization: a. Establishes usage restrictions, configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices; and b. Authorizes the connection of mobile devices to organizational information systems. Supplemental Guidance: A mobile device is a computing device that: (i) has a small form factor such that it can easily be carried by a single individual; (ii) is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); (iii) possesses local, non- removable or removable data storage; and (iv) includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones, E-readers, and tablets. Mobile devices are typically associated with a single individual and the device is usually in close proximity to the individual; however, the degree of proximity can vary depending upon on the form factor and size of the device. The processing, storage, and transmission capability of the mobile device may be comparable to or merely a subset of desktop systems, depending upon the nature and intended purpose of the device. Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different classes/types of such devices. Usage restrictions and specific implementation guidance for mobile devices include, for example, configuration management, device identification and authentication, implementation of mandatory protective software (e.g., malicious code detection, firewall), scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting primary operating system (and possibly other resident software) integrity checks, and disabling unnecessary hardware (e.g., wireless, infrared). Organizations are cautioned that the need to provide adequate security for mobile devices goes beyond the requirements in this control. Many safeguards and countermeasures for mobile devices are reflected in other security controls in the catalog allocated in the initial control baselines as starting points for the development of security plans and overlays using the tailoring process. There may also be some degree of overlap in the requirements articulated by the security controls within the different families of controls. AC-20 addresses mobile devices that are not organization-controlled. Related controls: AC-3, AC-7, AC-18, AC-20, CA-9, CM-2, IA-2, IA-3, MP-2, MP-4, MP-5, PL-4, SC-7, SC-43, SI-3, SI-4. References: OMB Memorandum 06-16; NIST Special Publications 800-114, 800-124, 800-164. | link | count: 001 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-19(5) | FedRAMP_Moderate_R4_AC-19(5) | FedRAMP Moderate AC-19 (5) | Access Control | Full Device / Container-Based Encryption | Shared | n/a | The organization employs [Selection: full-device encryption; container encryption] to protect the confidentiality and integrity of information on [Assignment: organization-defined mobile devices]. Supplemental Guidance: Container-based encryption provides a more fine-grained approach to the encryption of data/information on mobile devices, including for example, encrypting selected data structures such as files, records, or fields. Related controls: MP-5, SC-13, SC-28. References: OMB Memorandum 06-16; NIST Special Publications 800-114, 800-124, 800-164. | link | count: 002 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-2 | FedRAMP_Moderate_R4_AC-2 | FedRAMP Moderate AC-2 | Access Control | Account Management | Shared | n/a | The organization: a. Identifies and selects the following types of information system accounts to support organizational missions/business functions: [Assignment: organization-defined information system account types]; b. Assigns account managers for information system accounts; c. Establishes conditions for group and role membership; d. Specifies authorized users of the information system, group and role membership, and access authorizations (i.e., privileges) and other attributes (as required) for each account; e. Requires approvals by [Assignment: organization-defined personnel or roles] for requests to create information system accounts; f. Creates, enables, modifies, disables, and removes information system accounts in accordance with [Assignment: organization-defined procedures or conditions]; g. Monitors the use of, information system accounts; h. Notifies account managers: 1. When accounts are no longer required; 2. When users are terminated or transferred; and 3. When individual information system usage or need-to-know changes; i. Authorizes access to the information system based on: 1. A valid access authorization; 2. Intended system usage; and 3. Other attributes as required by the organization or associated missions/business functions; j. Reviews accounts for compliance with account management requirements [Assignment: organization-defined frequency]; and k. Establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group. Supplemental Guidance: Information system account types include individual, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service. Some of the account management requirements listed above can be implemented by organizational information systems. The identification of authorized users of the information system and the specification of access privileges reflects the requirements in other security controls in the security plan. Users requiring administrative privileges on information system accounts receive additional scrutiny by appropriate organizational personnel (e.g., system owner, mission/business owner, or chief information security officer) responsible for approving such accounts and privileged access. Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. Other attributes required for authorizing access include, for example, restrictions on time-of-day, day-of-week, and point-of-origin. In defining other account attributes, organizations consider system-related requirements (e.g., scheduled maintenance, system upgrades) and mission/business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements). Failure to consider these factors could affect information system availability. Temporary and emergency accounts are accounts intended for short-term use. Organizations establish temporary accounts as a part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. Organizations establish emergency accounts in response to crisis situations and with the need for rapid account activation. Therefore, emergency account activation may bypass normal account authorization processes. Emergency and temporary accounts are not to be confused with infrequently used accounts (e.g., local logon accounts used for special tasks defined by organizations or when network resources are unavailable). Such accounts remain available and are not subject to automatic disabling or removal dates. Conditions for disabling or deactivating accounts include, for example: (i) when shared/group, emergency, or temporary accounts are no longer required; or (ii) when individuals are transferred or terminated. Some types of information system accounts may require specialized training. Related controls: AC-3, AC-4, AC-5, AC-6, AC-10, AC-17, AC-19, AC-20, AU-9, IA-2, IA-4, IA-5, IA-8, CM-5, CM-6, CM-11, MA-3, MA-4, MA-5, PL-4, SC-13. References: None. | link | count: 025 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, General, Regulatory Compliance, Security Center, Service Fabric, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-2(1) | FedRAMP_Moderate_R4_AC-2(1) | FedRAMP Moderate AC-2 (1) | Access Control | Automated System Account Management | Shared | n/a | The organization employs automated mechanisms to support the management of information system accounts. Supplemental Guidance: The use of automated mechanisms can include, for example: using email or text messaging to automatically notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using telephonic notification to report atypical system account usage. | link | count: 007 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-2(10) | FedRAMP_Moderate_R4_AC-2(10) | FedRAMP Moderate AC-2 (10) | Access Control | Shared / Group Account Credential Termination | Shared | n/a | The information system terminates shared/group account credentials when members leave the group. | link | count: 001 Terminate customer controlled account credentials (76d66b5c-85e4-93f5-96a5-ebb2fad61dc6) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-2(12) | FedRAMP_Moderate_R4_AC-2(12) | FedRAMP Moderate AC-2 (12) | Access Control | Account Monitoring / Atypical Usage | Shared | n/a | The organization: (a) Monitors information system accounts for [Assignment: organization-defined atypical use]; and (b) Reports atypical usage of information system accounts to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Atypical usage includes, for example, accessing information systems at certain times of the day and from locations that are not consistent with the normal usage patterns of individuals working in organizations. Related control: CA-7. | link | count: 013 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81) |
Kubernetes, Regulatory Compliance, Security Center, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-2(3) | FedRAMP_Moderate_R4_AC-2(3) | FedRAMP Moderate AC-2 (3) | Access Control | Disable Inactive Accounts | Shared | n/a | The information system automatically disables inactive accounts after [Assignment: organization-defined time period]. | link | count: 002 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-2(4) | FedRAMP_Moderate_R4_AC-2(4) | FedRAMP Moderate AC-2 (4) | Access Control | Automated Audit Actions | Shared | n/a | The information system automatically audits account creation, modification, enabling, disabling, and removal actions, and notifies [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Related controls: AU-2, AU-12. | link | count: 005 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-2(5) | FedRAMP_Moderate_R4_AC-2(5) | FedRAMP Moderate AC-2 (5) | Access Control | Inactivity Logout | Shared | n/a | The organization requires that users log out when [Assignment: organization-defined time-period of expected inactivity or description of when to log out]. Supplemental Guidance: Related control: SC-23. | link | count: 001 Define and enforce inactivity log policy (2af4640d-11a6-a64b-5ceb-a468f4341c0c) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-2(7) | FedRAMP_Moderate_R4_AC-2(7) | FedRAMP Moderate AC-2 (7) | Access Control | Role-Based Schemes | Shared | n/a | The organization: (a) Establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles; (b) Monitors privileged role assignments; and (c) Takes [Assignment: organization-defined actions] when privileged role assignments are no longer appropriate. Supplemental Guidance: Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. These privileged roles include, for example, key management, account management, network and system administration, database administration, and web administration. | link | count: 010 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Azure Ai Services, General, Regulatory Compliance, Service Fabric, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-2(9) | FedRAMP_Moderate_R4_AC-2(9) | FedRAMP Moderate AC-2 (9) | Access Control | Restrictions On Use Of Shared Groups / Accounts | Shared | n/a | The organization only permits the use of shared/group accounts that meet [Assignment: organization-defined conditions for establishing shared/group accounts]. | link | count: 001 Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-20 | FedRAMP_Moderate_R4_AC-20 | FedRAMP Moderate AC-20 | Access Control | Use Of External Information Systems | Shared | n/a | The organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to: a. Access the information system from external information systems; and b. Process, store, or transmit organization-controlled information using external information systems. Supplemental Guidance: External information systems are information systems or components of information systems that are outside of the authorization boundary established by organizations and for which organizations typically have no direct supervision and authority over the application of required security controls or the assessment of control effectiveness. External information systems include, for example: (i) personally owned information systems/devices (e.g., notebook computers, smart phones, tablets, personal digital assistants); (ii) privately owned computing and communications devices resident in commercial or public facilities (e.g., hotels, train stations, convention centers, shopping malls, or airports); (iii) information systems owned or controlled by nonfederal governmental organizations; and (iv) federal information systems that are not owned by, operated by, or under the direct supervision and authority of organizations. This control also addresses the use of external information systems for the processing, storage, or transmission of organizational information, including, for example, accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational information systems. For some external information systems (i.e., information systems operated by other federal agencies, including organizations subordinate to those agencies), the trust relationships that have been established between those organizations and the originating organization may be such, that no explicit terms and conditions are required. Information systems within these organizations would not be considered external. These situations occur when, for example, there are pre-existing sharing/trust agreements (either implicit or explicit) established between federal agencies or organizations subordinate to those agencies, or when such trust agreements are specified by applicable laws, Executive Orders, directives, or policies. Authorized individuals include, for example, organizational personnel, contractors, or other individuals with authorized access to organizational information systems and over which organizations have the authority to impose rules of behavior with regard to system access. Restrictions that organizations impose on authorized individuals need not be uniform, as those restrictions may vary depending upon the trust relationships between organizations. Therefore, organizations may choose to impose different security restrictions on contractors than on state, local, or tribal governments. This control does not apply to the use of external information systems to access public interfaces to organizational information systems (e.g., individuals accessing federal information through www.usa.gov). Organizations establish terms and conditions for the use of external information systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum: types of applications that can be accessed on organizational information systems from external information systems; and the highest security category of information that can be processed, stored, or transmitted on external information systems. If terms and conditions with the owners of external information systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems. Related controls: AC-3, AC-17, AC-19, CA-3, PL-4, SA-9. References: FIPS Publication 199. | link | count: 002 Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-20(1) | FedRAMP_Moderate_R4_AC-20(1) | FedRAMP Moderate AC-20 (1) | Access Control | Limits On Authorized Use | Shared | n/a | The organization permits authorized individuals to use an external information system to access the information system or to process, store, or transmit organization-controlled information only when the organization: (a) Verifies the implementation of required security controls on the external system as specified in the organization’s information security policy and security plan; or (b) Retains approved information system connection or processing agreements with the organizational entity hosting the external information system. Supplemental Guidance: This control enhancement recognizes that there are circumstances where individuals using external information systems (e.g., contractors, coalition partners) need to access organizational information systems. In those situations, organizations need confidence that the external information systems contain the necessary security safeguards (i.e., security controls), so as not to compromise, damage, or otherwise harm organizational information systems. Verification that the required security controls have been implemented can be achieved, for example, by third-party, independent assessments, attestations, or other means, depending on the confidence level required by organizations. Related control: CA-2. | link | count: 001 Verify security controls for external information systems (dc7ec756-221c-33c8-0afe-c48e10e42321) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-20(2) | FedRAMP_Moderate_R4_AC-20(2) | FedRAMP Moderate AC-20 (2) | Access Control | Portable Storage Devices | Shared | n/a | The organization [Selection: restricts; prohibits] the use of organization-controlled portable storage devices by authorized individuals on external information systems. Supplemental Guidance: Limits on the use of organization-controlled portable storage devices in external information systems include, for example, complete prohibition of the use of such devices or restrictions on how the devices may be used and under what conditions the devices may be used. | link | count: 003 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-21 | FedRAMP_Moderate_R4_AC-21 | FedRAMP Moderate AC-21 | Access Control | Information Sharing | Shared | n/a | The organization: a. Facilitates information sharing by enabling authorized users to determine whether access authorizations assigned to the sharing partner match the access restrictions on the information for [Assignment: organization-defined information sharing circumstances where user discretion is required]; and b. Employs [Assignment: organization-defined automated mechanisms or manual processes] to assist users in making information sharing/collaboration decisions. Supplemental Guidance: This control applies to information that may be restricted in some manner (e.g., privileged medical information, contract-sensitive information, proprietary information, personally identifiable information, classified information related to special access programs or compartments) based on some formal or administrative determination. Depending on the particular information-sharing circumstances, sharing partners may be defined at the individual, group, or organizational level. Information may be defined by content, type, security category, or special access program/compartment. Related control: AC-3. References: None. | link | count: 002 Automate information sharing decisions (e54901fe-42c2-7f3b-3c5f-327aa5320a69), Facilitate information sharing (a44c9fba-43f8-4b7b-7ee6-db52c96b4366) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-22 | FedRAMP_Moderate_R4_AC-22 | FedRAMP Moderate AC-22 | Access Control | Publicly Accessible Content | Shared | n/a | The organization: a. Designates individuals authorized to post information onto a publicly accessible information system; b. Trains authorized individuals to ensure that publicly accessible information does not contain nonpublic information; c. Reviews the proposed content of information prior to posting onto the publicly accessible information system to ensure that nonpublic information is not included; and d. Reviews the content on the publicly accessible information system for nonpublic information [Assignment: organization-defined frequency] and removes such information, if discovered. Supplemental Guidance: In accordance with federal laws, Executive Orders, directives, policies, regulations, standards, and/or guidance, the general public is not authorized access to nonpublic information (e.g., information protected under the Privacy Act and proprietary information). This control addresses information systems that are controlled by the organization and accessible to the general public, typically without identification or authentication. The posting of information on non-organization information systems is covered by organizational policy. Related controls: AC-3, AC-4, AT-2, AT-3, AU-13. Control Enhancements: None. References: None. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Review content prior to posting publicly accessible information (9e3c505e-7aeb-2096-3417-b132242731fc), Review publicly accessible content for nonpublic information (b5244f81-6cab-3188-2412-179162294996), Train personnel on disclosure of nonpublic information (97f0d974-1486-01e2-2088-b888f46c0589) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-3 | FedRAMP_Moderate_R4_AC-3 | FedRAMP Moderate AC-3 | Access Control | Access Enforcement | Shared | n/a | The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. Supplemental Guidance: Access control policies (e.g., identity-based policies, role-based policies, attribute-based policies) and access enforcement mechanisms (e.g., access control lists, access control matrices, cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, domains) in information systems. In addition to enforcing authorized access at the information system level and recognizing that information systems can host many applications and services in support of organizational missions and business operations, access enforcement mechanisms can also be employed at the application and service level to provide increased information security. Related controls: AC-2, AC-4, AC-5, AC-6, AC-16, AC-17, AC-18, AC-19, AC-20, AC-21, AC-22, AU-9, CM-5, CM-6, CM-11, MA-3, MA-4, MA-5, PE-3. References: None. | link | count: 021 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
App Service, Azure Ai Services, Compute, Guest Configuration, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-4 | FedRAMP_Moderate_R4_AC-4 | FedRAMP Moderate AC-4 | Access Control | Information Flow Enforcement | Shared | n/a | The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems based on [Assignment: organization-defined information flow control policies]. Supplemental Guidance: Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. Flow control restrictions include, for example, keeping export-controlled information from being transmitted in the clear to the Internet, blocking outside traffic that claims to be from within the organization, restricting web requests to the Internet that are not from the internal web proxy server, and limiting information transfers between organizations based on data structures and content. Transferring information between information systems representing different security domains with different security policies introduces risk that such transfers violate one or more domain security policies. In such situations, information owners/stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes, for example: (i) prohibiting information transfers between interconnected systems (i.e., allowing access only); (ii) employing hardware mechanisms to enforce one-way information flows; and (iii) implementing trustworthy regarding mechanisms to reassign security attributes and security labels. Organizations commonly employ information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path. Enforcement occurs, for example, in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, firewalls) that employ rule sets or establish configuration settings that restrict information system services, provide a packet-filtering capability based on header information, or message- filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Organizations also consider the trustworthiness of filtering/inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Control enhancements 3 through 22 primarily address cross-domain solution needs which focus on more advanced filtering techniques, in-depth analysis, and stronger flow enforcement mechanisms implemented in cross-domain products, for example, high-assurance guards. Such capabilities are generally not available in commercial off-the-shelf information technology products. Related controls: AC-3, AC-17, AC-19, AC-21, CM-6, CM-7, SA-8, SC-2, SC-5, SC-7, SC-18. References: None. | link | count: 053 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, API Management, App Configuration, App Service, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Regulatory Compliance, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-4(21) | FedRAMP_Moderate_R4_AC-4(21) | FedRAMP Moderate AC-4 (21) | Access Control | Physical / Logical Separation Of Information Flows | Shared | n/a | The information system separates information flows logically or physically using [Assignment: organization-defined mechanisms and/or techniques] to accomplish [Assignment: organization- defined required separations by types of information]. Supplemental Guidance: Enforcing the separation of information flows by type can enhance protection by ensuring that information is not commingled while in transit and by enabling flow control by transmission paths perhaps not otherwise achievable. Types of separable information include, for example, inbound and outbound communications traffic, service requests and responses, and information of differing security categories. | link | count: 004 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-5 | FedRAMP_Moderate_R4_AC-5 | FedRAMP Moderate AC-5 | Access Control | Separation Of Duties | Shared | n/a | The organization: a. Separates [Assignment: organization-defined duties of individuals]; b. Documents separation of duties of individuals; and c. Defines information system access authorizations to support separation of duties. Supplemental Guidance: Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes, for example: (i) dividing mission functions and information system support functions among different individuals and/or roles; (ii) conducting information system support functions with different individuals (e.g., system management, programming, configuration management, quality assurance and testing, and network security); and (iii) ensuring security personnel administering access control functions do not also administer audit functions. Related controls: AC-3, AC-6, PE-3, PE-4, PS-2. Control Enhancements: None. References: None. | link | count: 004 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Regulatory Compliance, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-6 | FedRAMP_Moderate_R4_AC-6 | FedRAMP Moderate AC-6 | Access Control | Least Privilege | Shared | n/a | The organization employs the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions. Supplemental Guidance: Organizations employ least privilege for specific duties and information systems. The principle of least privilege is also applied to information system processes, ensuring that the processes operate at privilege levels no higher than necessary to accomplish required organizational missions/business functions. Organizations consider the creation of additional processes, roles, and information system accounts as necessary, to achieve least privilege. Organizations also apply least privilege to the development, implementation, and operation of organizational information systems. Related controls: AC-2, AC-3, AC-5, CM-6, CM-7, PL-2. References: None. | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f) |
General, Regulatory Compliance, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-6(1) | FedRAMP_Moderate_R4_AC-6(1) | FedRAMP Moderate AC-6 (1) | Access Control | Authorize Access To Security Functions | Shared | n/a | The organization explicitly authorizes access to [Assignment: organization-defined security functions (deployed in hardware, software, and firmware) and security-relevant information]. Supplemental Guidance: Security functions include, for example, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Security-relevant information includes, for example, filtering rules for routers/firewalls, cryptographic key management information, configuration parameters for security services, and access control lists. Explicitly authorized personnel include, for example, security administrators, system and network administrators, system security officers, system maintenance personnel, system programmers, and other privileged users. Related controls: AC-17, AC-18, AC-19. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-6(5) | FedRAMP_Moderate_R4_AC-6(5) | FedRAMP Moderate AC-6 (5) | Access Control | Privileged Accounts | Shared | n/a | The organization restricts privileged accounts on the information system to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from having access to privileged information/functions. Organizations may differentiate in the application of this control enhancement between allowed privileges for local accounts and for domain accounts provided organizations retain the ability to control information system configurations for key security parameters and as otherwise necessary to sufficiently mitigate risk. Related control: CM-6. | link | count: 001 Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-6(9) | FedRAMP_Moderate_R4_AC-6(9) | FedRAMP Moderate AC-6 (9) | Access Control | Auditing Use Of Privileged Functions | Shared | n/a | The information system audits the execution of privileged functions. Supplemental Guidance: Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat (APT). Related control: AU-2. | link | count: 006 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AC-7 | FedRAMP_Moderate_R4_AC-7 | FedRAMP Moderate AC-7 | Access Control | Unsuccessful Logon Attempts | Shared | n/a | The information system: a. Enforces a limit of [Assignment: organization-defined number] consecutive invalid logon attempts by a user during a [Assignment: organization-defined time period]; and b. Automatically [Selection: locks the account/node for an [Assignment: organization-defined time period]; locks the account/node until released by an administrator; delays next logon prompt according to [Assignment: organization-defined delay algorithm]] when the maximum number of unsuccessful attempts is exceeded. Supplemental Guidance: This control applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by information systems are usually temporary and automatically release after a predetermined time period established by organizations. If a delay algorithm is selected, organizations may choose to employ different algorithms for different information system components based on the capabilities of those components. Responses to unsuccessful logon attempts may be implemented at both the operating system and the application levels. Related controls: AC-2, AC-9, AC-14, IA-5. References: None. | link | count: 001 Enforce a limit of consecutive failed login attempts (b4409bff-2287-8407-05fd-c73175a68302) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AT-1 | FedRAMP_Moderate_R4_AT-1 | FedRAMP Moderate AT-1 | Awareness And Training | Security Awareness And Training Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A security awareness and training policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the security awareness and training policy and associated security awareness and training controls; and b. Reviews and updates the current: 1. Security awareness and training policy [Assignment: organization-defined frequency]; and 2. Security awareness and training procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AT family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-16, 800-50, 800-100. | link | count: 002 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AT-2 | FedRAMP_Moderate_R4_AT-2 | FedRAMP Moderate AT-2 | Awareness And Training | Security Awareness Training | Shared | n/a | The organization provides basic security awareness training to information system users (including managers, senior executives, and contractors): a. As part of initial training for new users; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Organizations determine the appropriate content of security awareness training and security awareness techniques based on the specific organizational requirements and the information systems to which personnel have authorized access. The content includes a basic understanding of the need for information security and user actions to maintain security and to respond to suspected security incidents. The content also addresses awareness of the need for operations security. Security awareness techniques can include, for example, displaying posters, offering supplies inscribed with security reminders, generating email advisories/notices from senior organizational officials, displaying logon screen messages, and conducting information security awareness events. Related controls: AT-3, AT-4, PL-4. References: C.F.R. Part 5 Subpart C (5 C.F.R. 930.301); Executive Order 13587; NIST Special Publication 800-50. | link | count: 003 Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AT-2(2) | FedRAMP_Moderate_R4_AT-2(2) | FedRAMP Moderate AT-2 (2) | Awareness And Training | Insider Threat | Shared | n/a | The organization includes security awareness training on recognizing and reporting potential indicators of insider threat. Supplemental Guidance: Potential indicators and possible precursors of insider threat can include behaviors such as inordinate, long-term job dissatisfaction, attempts to gain access to information not required for job performance, unexplained access to financial resources, bullying or sexual harassment of fellow employees, workplace violence, and other serious violations of organizational policies, procedures, directives, rules, or practices. Security awareness training includes how to communicate employee and management concerns regarding potential indicators of insider threat through appropriate organizational channels in accordance with established organizational policies and procedures. Related controls: PL-4, PM-12, PS-3, PS-6. References: C.F.R. Part 5 Subpart C (5 C.F.R 930.301); Executive Order 13587; NIST Special Publication 800-50. | link | count: 001 Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AT-3 | FedRAMP_Moderate_R4_AT-3 | FedRAMP Moderate AT-3 | Awareness And Training | Role-Based Security Training | Shared | n/a | The organization provides role-based security training to personnel with assigned security roles and responsibilities: a. Before authorizing access to the information system or performing assigned duties; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Organizations determine the appropriate content of security training based on the assigned roles and responsibilities of individuals and the specific security requirements of organizations and the information systems to which personnel have authorized access. In addition, organizations provide enterprise architects, information system developers, software developers, acquisition/procurement officials, information system managers, system/network administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation activities, security control assessors, and other personnel having access to system-level software, adequate security-related technical training specifically tailored for their assigned duties. Comprehensive role-based training addresses management, operational, and technical roles and responsibilities covering physical, personnel, and technical safeguards and countermeasures. Such training can include for example, policies, procedures, tools, and artifacts for the organizational security roles defined. Organizations also provide the training necessary for individuals to carry out their responsibilities related to operations and supply chain security within the context of organizational information security programs. Role-based security training also applies to contractors providing services to federal agencies. Related controls: AT-2, AT-4, PL-4, PS-7, SA-3, SA-12, SA-16. References: C.F.R. Part 5 Subpart C (5 C.F.R. 930.301); NIST Special Publications 800-16, 800-50. | link | count: 003 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AT-4 | FedRAMP_Moderate_R4_AT-4 | FedRAMP Moderate AT-4 | Awareness And Training | Security Training Records | Shared | n/a | The organization: a. Documents and monitors individual information system security training activities including basic security awareness training and specific information system security training; and b. Retains individual training records for [Assignment: organization-defined time period]. Supplemental Guidance: Documentation for specialized training may be maintained by individual supervisors at the option of the organization. Related controls: AT-2, AT-3, PM-14. Control Enhancements: None. References: None. | link | count: 003 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a), Retain training records (3153d9c0-2584-14d3-362d-578b01358aeb) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-1 | FedRAMP_Moderate_R4_AU-1 | FedRAMP Moderate AU-1 | Audit And Accountability | Audit And Accountability Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls; and b. Reviews and updates the current: 1. Audit and accountability policy [Assignment: organization-defined frequency]; and 2. Audit and accountability procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AU family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 004 Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-11 | FedRAMP_Moderate_R4_AU-11 | FedRAMP Moderate AU-11 | Audit And Accountability | Audit Record Retention | Shared | n/a | The organization retains audit records for [Assignment: organization-defined time period consistent with records retention policy] to provide support for after-the-fact investigations of security incidents and to meet regulatory and organizational information retention requirements. Supplemental Guidance: Organizations retain audit records until it is determined that they are no longer needed for administrative, legal, audit, or other operational purposes. This includes, for example, retention and availability of audit records relative to Freedom of Information Act (FOIA) requests, subpoenas, and law enforcement actions. Organizations develop standard categories of audit records relative to such types of actions and standard response processes for each type of action. The National Archives and Records Administration (NARA) General Records Schedules provide federal policy on record retention. Related controls: AU-4, AU-5, AU-9, MP-6. References: None. | link | count: 004 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
Regulatory Compliance, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-12 | FedRAMP_Moderate_R4_AU-12 | FedRAMP Moderate AU-12 | Audit And Accountability | Audit Generation | Shared | n/a | The information system: a. Provides audit record generation capability for the auditable events defined in AU-2 a. at [Assignment: organization-defined information system components]; b. Allows [Assignment: organization-defined personnel or roles] to select which auditable events are to be audited by specific components of the information system; and c. Generates audit records for the events defined in AU-2 d. with the content defined in AU-3. Supplemental Guidance: Audit records can be generated from many different information system components. The list of audited events is the set of events for which audits are to be generated. These events are typically a subset of all events for which the information system is capable of generating audit records. Related controls: AC-3, AU-2, AU-3, AU-6, AU-7. References: None. | link | count: 037 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-2 | FedRAMP_Moderate_R4_AU-2 | FedRAMP Moderate AU-2 | Audit And Accountability | Audit Events | Shared | n/a | The organization: a. Determines that the information system is capable of auditing the following events: [Assignment: organization-defined auditable events]; b. Coordinates the security audit function with other organizational entities requiring audit- related information to enhance mutual support and to help guide the selection of auditable events; c. Provides a rationale for why the auditable events are deemed to be adequate to support after- the-fact investigations of security incidents; and d. Determines that the following events are to be audited within the information system: [Assignment: organization-defined audited events (the subset of the auditable events defined in AU-2 a.) along with the frequency of (or situation requiring) auditing for each identified event]. Supplemental Guidance: An event is any observable occurrence in an organizational information system. Organizations identify audit events as those events which are significant and relevant to the security of information systems and the environments in which those systems operate in order to meet specific and ongoing audit needs. Audit events can include, for example, password changes, failed logons, or failed accesses related to information systems, administrative privilege usage, PIV credential usage, or third-party credential usage. In determining the set of auditable events, organizations consider the auditing appropriate for each of the security controls to be implemented. To balance auditing requirements with other information system needs, this control also requires identifying that subset of auditable events that are audited at a given point in time. For example, organizations may determine that information systems must have the capability to log every file access both successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. Auditing requirements, including the need for auditable events, may be referenced in other security controls and control enhancements. Organizations also include auditable events that are required by applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit capability and can facilitate the identification of root causes to problems. Organizations consider in the definition of auditable events, the auditing necessary to cover related events such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across multiple organizations) and actions that occur in service-oriented architectures. Related controls: AC-6, AC-17, AU-3, AU-12, MA-4, MP-2, MP-4, SI-4. References: NIST Special Publication 800-92; Web: http://idmanagement.gov. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-2(3) | FedRAMP_Moderate_R4_AU-2(3) | FedRAMP Moderate AU-2 (3) | Audit And Accountability | Reviews And Updates | Shared | n/a | The organization reviews and updates the audited events [Assignment: organization-defined frequency]. Supplemental Guidance: Over time, the events that organizations believe should be audited may change. Reviewing and updating the set of audited events periodically is necessary to ensure that the current set is still necessary and sufficient. | link | count: 001 Review and update the events defined in AU-02 (a930f477-9dcb-2113-8aa7-45bb6fc90861) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-3 | FedRAMP_Moderate_R4_AU-3 | FedRAMP Moderate AU-3 | Audit And Accountability | Content Of Audit Records | Shared | n/a | The information system generates audit records containing information that establishes what type of event occurred, when the event occurred, where the event occurred, the source of the event, the outcome of the event, and the identity of any individuals or subjects associated with the event. Supplemental Guidance: Audit record content that may be necessary to satisfy the requirement of this control, includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred). Related controls: AU-2, AU-8, AU-12, SI-11. References: None. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-3(1) | FedRAMP_Moderate_R4_AU-3(1) | FedRAMP Moderate AU-3 (1) | Audit And Accountability | Additional Audit Information | Shared | n/a | The information system generates audit records containing the following additional information: [Assignment: organization-defined additional, more detailed information]. Supplemental Guidance: Detailed information that organizations may consider in audit records includes, for example, full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. | link | count: 001 Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-4 | FedRAMP_Moderate_R4_AU-4 | FedRAMP Moderate AU-4 | Audit And Accountability | Audit Storage Capacity | Shared | n/a | The organization allocates audit record storage capacity in accordance with [Assignment: organization-defined audit record storage requirements]. Supplemental Guidance: Organizations consider the types of auditing to be performed and the audit processing requirements when allocating audit storage capacity. Allocating sufficient audit storage capacity reduces the likelihood of such capacity being exceeded and resulting in the potential loss or reduction of auditing capability. Related controls: AU-2, AU-5, AU-6, AU-7, AU-11, SI-4. References: None. | link | count: 001 Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-5 | FedRAMP_Moderate_R4_AU-5 | FedRAMP Moderate AU-5 | Audit And Accountability | Response To Audit Processing Failures | Shared | n/a | The information system: a. Alerts [Assignment: organization-defined personnel or roles] in the event of an audit processing failure; and b. Takes the following additional actions: [Assignment: organization-defined actions to be taken (e.g., shut down information system, overwrite oldest audit records, stop generating audit records)]. Supplemental Guidance: Audit processing failures include, for example, software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. Organizations may choose to define additional actions for different audit processing failures (e.g., by type, by location, by severity, or a combination of such factors). This control applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the total audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both. Related controls: AU-4, SI-12. References: None. | link | count: 001 Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-6 | FedRAMP_Moderate_R4_AU-6 | FedRAMP Moderate AU-6 | Audit And Accountability | Audit Review, Analysis, And Reporting | Shared | n/a | The organization: a. Reviews and analyzes information system audit records [Assignment: organization-defined frequency] for indications of [Assignment: organization-defined inappropriate or unusual activity]; and b. Reports findings to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Audit review, analysis, and reporting covers information security-related auditing performed by organizations including, for example, auditing that results from monitoring of account usage, remote access, wireless connectivity, mobile device connection, configuration settings, system component inventory, use of maintenance tools and nonlocal maintenance, physical access, temperature and humidity, equipment delivery and removal, communications at the information system boundaries, use of mobile code, and use of VoIP. Findings can be reported to organizational entities that include, for example, incident response team, help desk, information security group/department. If organizations are prohibited from reviewing and analyzing audit information or unable to conduct such activities (e.g., in certain national security applications or systems), the review/analysis may be carried out by other organizations granted such authority. Related controls: AC-2, AC-3, AC-6, AC-17, AT-3, AU-7, AU-16, CA-7, CM-5, CM-10, CM-11, IA-3, IA-5, IR-5, IR-6, MA-4, MP-4, PE-3, PE-6, PE-14, PE-16, RA-5, SC-7, SC-18, SC-19, SI-3, SI-4, SI-7. References: None. | link | count: 025 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-6(1) | FedRAMP_Moderate_R4_AU-6(1) | FedRAMP Moderate AU-6 (1) | Audit And Accountability | Process Integration | Shared | n/a | The organization employs automated mechanisms to integrate audit review, analysis, and reporting processes to support organizational processes for investigation and response to suspicious activities. Supplemental Guidance: Organizational processes benefiting from integrated audit review, analysis, and reporting include, for example, incident response, continuous monitoring, contingency planning, and Inspector General audits. Related controls: AU-12, PM-7. | link | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-6(3) | FedRAMP_Moderate_R4_AU-6(3) | FedRAMP Moderate AU-6 (3) | Audit And Accountability | Correlate Audit Repositories | Shared | n/a | The organization analyzes and correlates audit records across different repositories to gain organization-wide situational awareness. Supplemental Guidance: Organization-wide situational awareness includes awareness across all three tiers of risk management (i.e., organizational, mission/business process, and information system) and supports cross-organization awareness. Related controls: AU-12, IR-4. | link | count: 002 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-7 | FedRAMP_Moderate_R4_AU-7 | FedRAMP Moderate AU-7 | Audit And Accountability | Audit Reduction And Report Generation | Shared | n/a | The information system provides an audit reduction and report generation capability that: a. Supports on-demand audit review, analysis, and reporting requirements and after-the-fact investigations of security incidents; and b. Does not alter the original content or time ordering of audit records. Supplemental Guidance: Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Audit reduction and report generation capabilities do not always emanate from the same information system or from the same organizational entities conducting auditing activities. Audit reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the information system can generate customizable reports. Time ordering of audit records can be a significant issue if the granularity of the timestamp in the record is insufficient. Related control: AU-6. References: None. | link | count: 002 Ensure audit records are not altered (27ce30dd-3d56-8b54-6144-e26d9a37a541), Provide audit review, analysis, and reporting capability (44f8a42d-739f-8030-89a8-4c2d5b3f6af3) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-7(1) | FedRAMP_Moderate_R4_AU-7(1) | FedRAMP Moderate AU-7 (1) | Audit And Accountability | Automatic Processing | Shared | n/a | The information system provides the capability to process audit records for events of interest based on [Assignment: organization-defined audit fields within audit records]. Supplemental Guidance: Events of interest can be identified by the content of specific audit record fields including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations may define audit event criteria to any degree of granularity required, for example, locations selectable by general networking location (e.g., by network or subnetwork) or selectable by specific information system component. Related controls: AU-2, AU-12. | link | count: 001 Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-8 | FedRAMP_Moderate_R4_AU-8 | FedRAMP Moderate AU-8 | Audit And Accountability | Time Stamps | Shared | n/a | The information system: a. Uses internal system clocks to generate time stamps for audit records; and b. Records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT) and meets [Assignment: organization-defined granularity of time measurement]. Supplemental Guidance: Time stamps generated by the information system include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Granularity of time measurements refers to the degree of synchronization between information system clocks and reference clocks, for example, clocks synchronizing within hundreds of milliseconds or within tens of milliseconds. Organizations may define different time granularities for different system components. Time service can also be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities. Related controls: AU-3, AU-12. References: None. | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-8(1) | FedRAMP_Moderate_R4_AU-8(1) | FedRAMP Moderate AU-8 (1) | Audit And Accountability | Synchronization With Authoritative Time Source | Shared | n/a | The information system: (a) Compares the internal information system clocks [Assignment: organization-defined frequency] with [Assignment: organization-defined authoritative time source]; and (b) Synchronizes the internal system clocks to the authoritative time source when the time difference is greater than [Assignment: organization-defined time period]. Supplemental Guidance: This control enhancement provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-9 | FedRAMP_Moderate_R4_AU-9 | FedRAMP Moderate AU-9 | Audit And Accountability | Protection Of Audit Information | Shared | n/a | The information system protects audit information and audit tools from unauthorized access, modification, and deletion. Supplemental Guidance: Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. This control focuses on technical protection of audit information. Physical protection of audit information is addressed by media protection controls and physical and environmental protection controls. Related controls: AC-3, AC-6, MP-2, MP-4, PE-2, PE-3, PE-6. References: None. | link | count: 002 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-9(2) | FedRAMP_Moderate_R4_AU-9(2) | FedRAMP Moderate AU-9 (2) | Audit And Accountability | Audit Backup On Separate Physical Systems / Components | Shared | n/a | The information system backs up audit records [Assignment: organization-defined frequency] onto a physically different system or system component than the system or component being audited. Supplemental Guidance: This control enhancement helps to ensure that a compromise of the information system being audited does not also result in a compromise of the audit records. Related controls: AU-4, AU-5, AU-11. | link | count: 001 Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | AU-9(4) | FedRAMP_Moderate_R4_AU-9(4) | FedRAMP Moderate AU-9 (4) | Audit And Accountability | Access By Subset Of Privileged Users | Shared | n/a | The organization authorizes access to management of audit functionality to only [Assignment: organization-defined subset of privileged users]. Supplemental Guidance: Individuals with privileged access to an information system and who are also the subject of an audit by that system, may affect the reliability of audit information by inhibiting audit activities or modifying audit records. This control enhancement requires that privileged access be further defined between audit-related privileges and other privileges, thus limiting the users with audit-related privileges. Related control: AC-5. | link | count: 001 Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-1 | FedRAMP_Moderate_R4_CA-1 | FedRAMP Moderate CA-1 | Security Assessment And Authorization | Security Assessment And Authorization Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A security assessment and authorization policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the security assessment and authorization policy and associated security assessment and authorization controls; and b. Reviews and updates the current: 1. Security assessment and authorization policy [Assignment: organization-defined frequency]; and 2. Security assessment and authorization procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-37, 800-53A, 800-100. | link | count: 001 Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-2 | FedRAMP_Moderate_R4_CA-2 | FedRAMP Moderate CA-2 | Security Assessment And Authorization | Security Assessments | Shared | n/a | The organization: a. Develops a security assessment plan that describes the scope of the assessment including: 1. Security controls and control enhancements under assessment; 2. Assessment procedures to be used to determine security control effectiveness; and 3. Assessment environment, assessment team, and assessment roles and responsibilities; b. Assesses the security controls in the information system and its environment of operation [Assignment: organization-defined frequency] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security requirements; c. Produces a security assessment report that documents the results of the assessment; and d. Provides the results of the security control assessment to [Assignment: organization-defined individuals or roles]. Supplemental Guidance: Organizations assess security controls in organizational information systems and the environments in which those systems operate as part of: (i) initial and ongoing security authorizations; (ii) FISMA annual assessments; (iii) continuous monitoring; and (iv) system development life cycle activities. Security assessments: (i) ensure that information security is built into organizational information systems; (ii) identify weaknesses and deficiencies early in the development process; (iii) provide essential information needed to make risk-based decisions as part of security authorization processes; and (iv) ensure compliance to vulnerability mitigation procedures. Assessments are conducted on the implemented security controls from Appendix F (main catalog) and Appendix G (Program Management controls) as documented in System Security Plans and Information Security Program Plans. Organizations can use other types of assessment activities such as vulnerability scanning and system monitoring to maintain the security posture of information systems during the entire life cycle. Security assessment reports document assessment results in sufficient detail as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the security controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting security requirements. The FISMA requirement for assessing security controls at least annually does not require additional assessment activities to those activities already in place in organizational security authorization processes. Security assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. For example, assessments conducted in support of security authorization decisions are provided to authorizing officials or authorizing official designated representatives. To satisfy annual assessment requirements, organizations can use assessment results from the following sources: (i) initial or ongoing information system authorizations; (ii) continuous monitoring; or (iii) system development life cycle activities. Organizations ensure that security assessment results are current, relevant to the determination of security control effectiveness, and obtained with the appropriate level of assessor independence. Existing security control assessment results can be reused to the extent that the results are still valid and can also be supplemented with additional assessments as needed. Subsequent to initial authorizations and in accordance with OMB policy, organizations assess security controls during continuous monitoring. Organizations establish the frequency for ongoing security control assessments in accordance with organizational continuous monitoring strategies. Information Assurance Vulnerability Alerts provide useful examples of vulnerability mitigation procedures. External audits (e.g., audits by external entities such as regulatory agencies) are outside the scope of this control. Related controls: CA-5, CA-6, CA-7, PM-9, RA-5, SA-11, SA-12, SI-4. References: Executive Order 13587; FIPS Publication 199; NIST Special Publications 800-37, 800-39, 800-53A, 800-115, 800-137. | link | count: 004 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-2(1) | FedRAMP_Moderate_R4_CA-2(1) | FedRAMP Moderate CA-2 (1) | Security Assessment And Authorization | Independent Assessors | Shared | n/a | The organization employs assessors or assessment teams with [Assignment: organization-defined level of independence] to conduct security control assessments. Supplemental Guidance: Independent assessors or assessment teams are individuals or groups who conduct impartial assessments of organizational information systems. Impartiality implies that assessors are free from any perceived or actual conflicts of interest with regard to the development, operation, or management of the organizational information systems under assessment or to the determination of security control effectiveness. To achieve impartiality, assessors should not: (i) create a mutual or conflicting interest with the organizations where the assessments are being conducted; (ii) assess their own work; (iii) act as management or employees of the organizations they are serving; or (iv) place themselves in positions of advocacy for the organizations acquiring their services. Independent assessments can be obtained from elements within organizations or can be contracted to public or private sector entities outside of organizations. Authorizing officials determine the required level of independence based on the security categories of information systems and/or the ultimate risk to organizational operations, organizational assets, or individuals. Authorizing officials also determine if the level of assessor independence provides sufficient assurance that the results are sound and can be used to make credible, risk-based decisions. This includes determining whether contracted security assessment services have sufficient independence, for example, when information system owners are not directly involved in contracting processes or cannot unduly influence the impartiality of assessors conducting assessments. In special situations, for example, when organizations that own the information systems are small or organizational structures require that assessments are conducted by individuals that are in the developmental, operational, or management chain of system owners, independence in assessment processes can be achieved by ensuring that assessment results are carefully reviewed and analyzed by independent teams of experts to validate the completeness, accuracy, integrity, and reliability of the results. Organizations recognize that assessments performed for purposes other than direct support to authorization decisions are, when performed by assessors with sufficient independence, more likely to be useable for such decisions, thereby reducing the need to repeat assessments. | link | count: 001 Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-2(2) | FedRAMP_Moderate_R4_CA-2(2) | FedRAMP Moderate CA-2 (2) | Security Assessment And Authorization | Specialized Assessments | Shared | n/a | The organization includes as part of security control assessments, [Assignment: organization- defined frequency], [Selection: announced; unannounced], [Selection (one or more): in-depth monitoring; vulnerability scanning; malicious user testing; insider threat assessment; performance/load testing; [Assignment: organization-defined other forms of security assessment]]. Supplemental Guidance: Organizations can employ information system monitoring, insider threat assessments, malicious user testing, and other forms of testing (e.g., verification and validation) to improve readiness by exercising organizational capabilities and indicating current performance levels as a means of focusing actions to improve security. Organizations conduct assessment activities in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Authorizing officials approve the assessment methods in coordination with the organizational risk executive function. Organizations can incorporate vulnerabilities uncovered during assessments into vulnerability remediation processes. Related controls: PE-3, SI-2. | link | count: 001 Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-2(3) | FedRAMP_Moderate_R4_CA-2(3) | FedRAMP Moderate CA-2 (3) | Security Assessment And Authorization | External Organizations | Shared | n/a | The organization accepts the results of an assessment of [Assignment: organization-defined information system] performed by [Assignment: organization-defined external organization] when the assessment meets [Assignment: organization-defined requirements]. Supplemental Guidance: Organizations may often rely on assessments of specific information systems by other (external) organizations. Utilizing such existing assessments (i.e., reusing existing assessment evidence) can significantly decrease the time and resources required for organizational assessments by limiting the amount of independent assessment activities that organizations need to perform. The factors that organizations may consider in determining whether to accept assessment results from external organizations can vary. Determinations for accepting assessment results can be based on, for example, past assessment experiences one organization has had with another organization, the reputation that organizations have with regard to assessments, the level of detail of supporting assessment documentation provided, or mandates imposed upon organizations by federal legislation, policies, or directives. | link | count: 001 Accept assessment results (3054c74b-9b45-2581-56cf-053a1a716c39) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-3 | FedRAMP_Moderate_R4_CA-3 | FedRAMP Moderate CA-3 | Security Assessment And Authorization | System Interconnections | Shared | n/a | The organization: a. Authorizes connections from the information system to other information systems through the use of Interconnection Security Agreements; b. Documents, for each interconnection, the interface characteristics, security requirements, and the nature of the information communicated; and c. Reviews and updates Interconnection Security Agreements [Assignment: organization-defined frequency]. Supplemental Guidance: This control applies to dedicated connections between information systems (i.e., system interconnections) and does not apply to transitory, user-controlled connections such as email and website browsing. Organizations carefully consider the risks that may be introduced when information systems are connected to other systems with different security requirements and security controls, both within organizations and external to organizations. Authorizing officials determine the risk associated with information system connections and the appropriate controls employed. If interconnecting systems have the same authorizing official, organizations do not need to develop Interconnection Security Agreements. Instead, organizations can describe the interface characteristics between those interconnecting systems in their respective security plans. If interconnecting systems have different authorizing officials within the same organization, organizations can either develop Interconnection Security Agreements or describe the interface characteristics between systems in the security plans for the respective systems. Organizations may also incorporate Interconnection Security Agreement information into formal contracts, especially for interconnections established between federal agencies and nonfederal (i.e., private sector) organizations. Risk considerations also include information systems sharing the same networks. For certain technologies (e.g., space, unmanned aerial vehicles, and medical devices), there may be specialized connections in place during preoperational testing. Such connections may require Interconnection Security Agreements and be subject to additional security controls. Related controls: AC-3, AC-4, AC-20, AU-2, AU-12, AU-16, CA-7, IA-3, SA-9, SC-7, SI-4. References: FIPS Publication 199; NIST Special Publication 800-47. | link | count: 002 Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-3(3) | FedRAMP_Moderate_R4_CA-3(3) | FedRAMP Moderate CA-3 (3) | Security Assessment And Authorization | Unclassified Non-National Security System Connections | Shared | n/a | The organization prohibits the direct connection of an [Assignment: organization-defined unclassified, non-national security system] to an external network without the use of [Assignment; organization-defined boundary protection device]. Supplemental Guidance: Organizations typically do not have control over external networks (e.g., the Internet). Approved boundary protection devices (e.g., routers, firewalls) mediate communications (i.e., information flows) between unclassified non-national security systems and external networks. This control enhancement is required for organizations processing, storing, or transmitting Controlled Unclassified Information (CUI). | link | count: 001 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-3(5) | FedRAMP_Moderate_R4_CA-3(5) | FedRAMP Moderate CA-3 (5) | Security Assessment And Authorization | Restrictions On External System Connections | Shared | n/a | The organization employs [Selection: allow-all, deny-by-exception; deny-all, permit-by-exception] policy for allowing [Assignment: organization-defined information systems] to connect to external information systems. Supplemental Guidance: Organizations can constrain information system connectivity to external domains (e.g., websites) by employing one of two policies with regard to such connectivity: (i) allow-all, deny by exception, also known as blacklisting (the weaker of the two policies); or (ii) deny-all, allow by exception, also known as whitelisting (the stronger of the two policies). For either policy, organizations determine what exceptions, if any, are acceptable. Related control: CM-7. | link | count: 001 Employ restrictions on external system interconnections (80029bc5-834f-3a9c-a2d8-acbc1aab4e9f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-5 | FedRAMP_Moderate_R4_CA-5 | FedRAMP Moderate CA-5 | Security Assessment And Authorization | Plan Of Action And Milestones | Shared | n/a | The organization: a. Develops a plan of action and milestones for the information system to document the organization’s planned remedial actions to correct weaknesses or deficiencies noted during the assessment of the security controls and to reduce or eliminate known vulnerabilities in the system; and b. Updates existing plan of action and milestones [Assignment: organization-defined frequency] based on the findings from security controls assessments, security impact analyses, and continuous monitoring activities. Supplemental Guidance: Plans of action and milestones are key documents in security authorization packages and are subject to federal reporting requirements established by OMB. Related controls: CA-2, CA-7, CM-4, PM-4. References: OMB Memorandum 02-01; NIST Special Publication 800-37. | link | count: 002 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-6 | FedRAMP_Moderate_R4_CA-6 | FedRAMP Moderate CA-6 | Security Assessment And Authorization | Security Authorization | Shared | n/a | The organization: a. Assigns a senior-level executive or manager as the authorizing official for the information system; b. Ensures that the authorizing official authorizes the information system for processing before commencing operations; and c. Updates the security authorization [Assignment: organization-defined frequency]. Supplemental Guidance: Security authorizations are official management decisions, conveyed through authorization decision documents, by senior organizational officials or executives (i.e., authorizing officials) to authorize operation of information systems and to explicitly accept the risk to organizational operations and assets, individuals, other organizations, and the Nation based on the implementation of agreed-upon security controls. Authorizing officials provide budgetary oversight for organizational information systems or assume responsibility for the mission/business operations supported by those systems. The security authorization process is an inherently federal responsibility and therefore, authorizing officials must be federal employees. Through the security authorization process, authorizing officials assume responsibility and are accountable for security risks associated with the operation and use of organizational information systems. Accordingly, authorizing officials are in positions with levels of authority commensurate with understanding and accepting such information security-related risks. OMB policy requires that organizations conduct ongoing authorizations of information systems by implementing continuous monitoring programs. Continuous monitoring programs can satisfy three-year reauthorization requirements, so separate reauthorization processes are not necessary. Through the employment of comprehensive continuous monitoring processes, critical information contained in authorization packages (i.e., security plans, security assessment reports, and plans of action and milestones) is updated on an ongoing basis, providing authorizing officials and information system owners with an up-to-date status of the security state of organizational information systems and environments of operation. To reduce the administrative cost of security reauthorization, authorizing officials use the results of continuous monitoring processes to the maximum extent possible as the basis for rendering reauthorization decisions. Related controls: CA-2, CA-7, PM-9, PM-10. Control Enhancements: None. References: OMB Circular A-130; OMB Memorandum 11-33; NIST Special Publications 800-37, 800-137. | link | count: 003 Assign an authorizing official (AO) (e29a8f1b-149b-2fa3-969d-ebee1baa9472), Ensure resources are authorized (0716f0f5-4955-2ccb-8d5e-c6be14d57c0f), Update the security authorization (449ebb52-945b-36e5-3446-af6f33770f8f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-7 | FedRAMP_Moderate_R4_CA-7 | FedRAMP Moderate CA-7 | Security Assessment And Authorization | Continuous Monitoring | Shared | n/a | The organization develops a continuous monitoring strategy and implements a continuous monitoring program that includes: a. Establishment of [Assignment: organization-defined metrics] to be monitored; b. Establishment of [Assignment: organization-defined frequencies] for monitoring and [Assignment: organization-defined frequencies] for assessments supporting such monitoring; c. Ongoing security control assessments in accordance with the organizational continuous monitoring strategy; d. Ongoing security status monitoring of organization-defined metrics in accordance with the organizational continuous monitoring strategy; e. Correlation and analysis of security-related information generated by assessments and monitoring; f. Response actions to address results of the analysis of security-related information; and g. Reporting the security status of organization and the information system to [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency]. Supplemental Guidance: Continuous monitoring programs facilitate ongoing awareness of threats, vulnerabilities, and information security to support organizational risk management decisions. The terms continuous and ongoing imply that organizations assess/analyze security controls and information security-related risks at a frequency sufficient to support organizational risk-based decisions. The results of continuous monitoring programs generate appropriate risk response actions by organizations. Continuous monitoring programs also allow organizations to maintain the security authorizations of information systems and common controls over time in highly dynamic environments of operation with changing mission/business needs, threats, vulnerabilities, and technologies. Having access to security-related information on a continuing basis through reports/dashboards gives organizational officials the capability to make more effective and timely risk management decisions, including ongoing security authorization decisions. Automation supports more frequent updates to security authorization packages, hardware/software/firmware inventories, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Continuous monitoring activities are scaled in accordance with the security categories of information systems. Related controls: CA-2, CA-5, CA-6, CM-3, CM-4, PM-6, PM-9, RA-5, SA-11, SA-12, SI-2, SI-4. References: OMB Memorandum 11-33; NIST Special Publications 800-37, 800-39, 800-53A, 800-115, 800-137; US-CERT Technical Cyber Security Alerts; DoD Information Assurance Vulnerability Alerts. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-7(1) | FedRAMP_Moderate_R4_CA-7(1) | FedRAMP Moderate CA-7 (1) | Security Assessment And Authorization | Independent Assessment | Shared | n/a | The organization employs assessors or assessment teams with [Assignment: organization-defined level of independence] to monitor the security controls in the information system on an ongoing basis. Supplemental Guidance: Organizations can maximize the value of assessments of security controls during the continuous monitoring process by requiring that such assessments be conducted by assessors or assessment teams with appropriate levels of independence based on continuous monitoring strategies. Assessor independence provides a degree of impartiality to the monitoring process. To achieve such impartiality, assessors should not: (i) create a mutual or conflicting interest with the organizations where the assessments are being conducted; (ii) assess their own work; (iii) act as management or employees of the organizations they are serving; or (iv) place themselves in advocacy positions for the organizations acquiring their services. | link | count: 001 Employ independent assessors for continuous monitoring (3baee3fd-30f5-882c-018c-cc78703a0106) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-8(1) | FedRAMP_Moderate_R4_CA-8(1) | FedRAMP Moderate CA-8 (1) | Security Assessment And Authorization | Independent Penetration Agent Or Team | Shared | n/a | The organization employs an independent penetration agent or penetration team to perform penetration testing on the information system or system components. Supplemental Guidance: Independent penetration agents or teams are individuals or groups who conduct impartial penetration testing of organizational information systems. Impartiality implies that penetration agents or teams are free from any perceived or actual conflicts of interest with regard to the development, operation, or management of the information systems that are the targets of the penetration testing. Supplemental guidance for CA-2 (1) provides additional information regarding independent assessments that can be applied to penetration testing. Related control: CA-2. | link | count: 001 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CA-9 | FedRAMP_Moderate_R4_CA-9 | FedRAMP Moderate CA-9 | Security Assessment And Authorization | Internal System Connections | Shared | n/a | The organization: a. Authorizes internal connections of [Assignment: organization-defined information system components or classes of components] to the information system; and b. Documents, for each internal connection, the interface characteristics, security requirements, and the nature of the information communicated. Supplemental Guidance: This control applies to connections between organizational information systems and (separate) constituent system components (i.e., intra-system connections) including, for example, system connections with mobile devices, notebook/desktop computers, printers, copiers, facsimile machines, scanners, sensors, and servers. Instead of authorizing each individual internal connection, organizations can authorize internal connections for a class of components with common characteristics and/or configurations, for example, all digital printers, scanners, and copiers with a specified processing, storage, and transmission capability or all smart phones with a specific baseline configuration. Related controls: AC-3, AC-4, AC-18, AC-19, AU-2, AU-12, CA-7, CM-2, IA-3, SC-7, SI-4. References: None. | link | count: 001 Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-1 | FedRAMP_Moderate_R4_CM-1 | FedRAMP Moderate CM-1 | Configuration Management | Configuration Management Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the configuration management policy and associated configuration management controls; and b. Reviews and updates the current: 1. Configuration management policy [Assignment: organization-defined frequency]; and 2. Configuration management procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CM family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-10 | FedRAMP_Moderate_R4_CM-10 | FedRAMP Moderate CM-10 | Configuration Management | Software Usage Restrictions | Shared | n/a | The organization: a. Uses software and associated documentation in accordance with contract agreements and copyright laws; b. Tracks the use of software and associated documentation protected by quantity licenses to control copying and distribution; and c. Controls and documents the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work. Supplemental Guidance: Software license tracking can be accomplished by manual methods (e.g., simple spreadsheets) or automated methods (e.g., specialized tracking applications) depending on organizational needs. Related controls: AC-17, CM-8, SC-7. References: None. | link | count: 004 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Require compliance with intellectual property rights (725164e5-3b21-1ec2-7e42-14f077862841), Track software license usage (77cc89bb-774f-48d7-8a84-fb8c322c3000) |
Regulatory Compliance, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-10(1) | FedRAMP_Moderate_R4_CM-10(1) | FedRAMP Moderate CM-10 (1) | Configuration Management | Open Source Software | Shared | n/a | The organization establishes the following restrictions on the use of open source software: [Assignment: organization-defined restrictions]. Supplemental Guidance: Open source software refers to software that is available in source code form. Certain software rights normally reserved for copyright holders are routinely provided under software license agreements that permit individuals to study, change, and improve the software. From a security perspective, the major advantage of open source software is that it provides organizations with the ability to examine the source code. However, there are also various licensing issues associated with open source software including, for example, the constraints on derivative use of such software. | link | count: 001 Restrict use of open source software (08c11b48-8745-034d-1c1b-a144feec73b9) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-11 | FedRAMP_Moderate_R4_CM-11 | FedRAMP Moderate CM-11 | Configuration Management | User-Installed Software | Shared | n/a | The organization: a. Establishes [Assignment: organization-defined policies] governing the installation of software by users; b. Enforces software installation policies through [Assignment: organization-defined methods]; and c. Monitors policy compliance at [Assignment: organization-defined frequency]. Supplemental Guidance: If provided the necessary privileges, users have the ability to install software in organizational information systems. To maintain control over the types of software installed, organizations identify permitted and prohibited actions regarding software installation. Permitted software installations may include, for example, updates and security patches to existing software and downloading applications from organization-approved “app stores.” Prohibited software installations may include, for example, software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods (e.g., periodic examination of user accounts), automated methods (e.g., configuration settings implemented on organizational information systems), or both. Related controls: AC-3, CM-2, CM-3, CM-5, CM-6, CM-7, PL-4. References: None. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-2 | FedRAMP_Moderate_R4_CM-2 | FedRAMP Moderate CM-2 | Configuration Management | Baseline Configuration | Shared | n/a | The organization develops, documents, and maintains under configuration control, a current baseline configuration of the information system. Supplemental Guidance: This control establishes baseline configurations for information systems and system components including communications and connectivity-related aspects of systems. Baseline configurations are documented, formally reviewed and agreed-upon sets of specifications for information systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, and/or changes to information systems. Baseline configurations include information about information system components (e.g., standard software packages installed on workstations, notebook computers, servers, network components, or mobile devices; current version numbers and patch information on operating systems and applications; and configuration settings/parameters), network topology, and the logical placement of those components within the system architecture. Maintaining baseline configurations requires creating new baselines as organizational information systems change over time. Baseline configurations of information systems reflect the current enterprise architecture. Related controls: CM-3, CM-6, CM-8, CM-9, SA-10, PM-5, PM-7. References: NIST Special Publication 800-128. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-2(2) | FedRAMP_Moderate_R4_CM-2(2) | FedRAMP Moderate CM-2 (2) | Configuration Management | Automation Support For Accuracy / Currency | Shared | n/a | The organization employs automated mechanisms to maintain an up-to-date, complete, accurate, and readily available baseline configuration of the information system. Supplemental Guidance: Automated mechanisms that help organizations maintain consistent baseline configurations for information systems include, for example, hardware and software inventory tools, configuration management tools, and network management tools. Such tools can be deployed and/or allocated as common controls, at the information system level, or at the operating system or component level (e.g., on workstations, servers, notebook computers, network components, or mobile devices). Tools can be used, for example, to track version numbers on operating system applications, types of software installed, and current patch levels. This control enhancement can be satisfied by the implementation of CM-8 (2) for organizations that choose to combine information system component inventory and baseline configuration activities. Related controls: CM-7, RA-5. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-2(3) | FedRAMP_Moderate_R4_CM-2(3) | FedRAMP Moderate CM-2 (3) | Configuration Management | Retention Of Previous Configurations | Shared | n/a | The organization retains [Assignment: organization-defined previous versions of baseline configurations of the information system] to support rollback. Supplemental Guidance: Retaining previous versions of baseline configurations to support rollback may include, for example, hardware, software, firmware, configuration files, and configuration records. | link | count: 001 Retain previous versions of baseline configs (5e4e9685-3818-5934-0071-2620c4fa2ca5) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-2(7) | FedRAMP_Moderate_R4_CM-2(7) | FedRAMP Moderate CM-2 (7) | Configuration Management | Configure Systems, Components, Or Devices For High-Risk Areas | Shared | n/a | The organization: (a) Issues [Assignment: organization-defined information systems, system components, or devices] with [Assignment: organization-defined configurations] to individuals traveling to locations that the organization deems to be of significant risk; and (b) Applies [Assignment: organization-defined security safeguards] to the devices when the individuals return. Supplemental Guidance: When it is known that information systems, system components, or devices (e.g., notebook computers, mobile devices) will be located in high-risk areas, additional security controls may be implemented to counter the greater threat in such areas coupled with the lack of physical security relative to organizational-controlled areas. For example, organizational policies and procedures for notebook computers used by individuals departing on and returning from travel include, for example, determining which locations are of concern, defining required configurations for the devices, ensuring that the devices are configured as intended before travel is initiated, and applying specific safeguards to the device after travel is completed. Specially configured notebook computers include, for example, computers with sanitized hard drives, limited applications, and additional hardening (e.g., more stringent configuration settings). Specified safeguards applied to mobile devices upon return from travel include, for example, examining the device for signs of physical tampering and purging/reimaging the hard disk drive. Protecting information residing on mobile devices is covered in the media protection family..\ | link | count: 002 Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-3 | FedRAMP_Moderate_R4_CM-3 | FedRAMP Moderate CM-3 | Configuration Management | Configuration Change Control | Shared | n/a | The organization: a. Determines the types of changes to the information system that are configuration-controlled; b. Reviews proposed configuration-controlled changes to the information system and approves or disapproves such changes with explicit consideration for security impact analyses; c. Documents configuration change decisions associated with the information system; d. Implements approved configuration-controlled changes to the information system; e. Retains records of configuration-controlled changes to the information system for [Assignment: organization-defined time period]; f. Audits and reviews activities associated with configuration-controlled changes to the information system; and g. Coordinates and provides oversight for configuration change control activities through [Assignment: organization-defined configuration change control element (e.g., committee, board] that convenes [Selection (one or more): [Assignment: organization-defined frequency]; [Assignment: organization-defined configuration change conditions]]. Supplemental Guidance: Configuration change controls for organizational information systems involve the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications. Configuration change control includes changes to baseline configurations for components and configuration items of information systems, changes to configuration settings for information technology products (e.g., operating systems, applications, firewalls, routers, and mobile devices), unscheduled/unauthorized changes, and changes to remediate vulnerabilities. Typical processes for managing configuration changes to information systems include, for example, Configuration Control Boards that approve proposed changes to systems. For new development information systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards. Auditing of changes includes activities before and after changes are made to organizational information systems and the auditing activities required to implement such changes. Related controls: CM-2, CM-4, CM-5, CM-6, CM-9, SA-10, SI-2, SI-12. References: NIST Special Publication 800-128. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-4 | FedRAMP_Moderate_R4_CM-4 | FedRAMP Moderate CM-4 | Configuration Management | Security Impact Analysis | Shared | n/a | The organization analyzes changes to the information system to determine potential security impacts prior to change implementation. Supplemental Guidance: Organizational personnel with information security responsibilities (e.g., Information System Administrators, Information System Security Officers, Information System Security Managers, and Information System Security Engineers) conduct security impact analyses. Individuals conducting security impact analyses possess the necessary skills/technical expertise to analyze the changes to information systems and the associated security ramifications. Security impact analysis may include, for example, reviewing security plans to understand security control requirements and reviewing system design documentation to understand control implementation and how specific changes might affect the controls. Security impact analyses may also include assessments of risk to better understand the impact of the changes and to determine if additional security controls are required. Security impact analyses are scaled in accordance with the security categories of the information systems. Related controls: CA-2, CA-7, CM-3, CM-9, SA-4, SA-5, SA-10, SI-2. References: NIST Special Publication 800-128. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-5 | FedRAMP_Moderate_R4_CM-5 | FedRAMP Moderate CM-5 | Configuration Management | Access Restrictions For Change | Shared | n/a | The organization defines, documents, approves, and enforces physical and logical access restrictions associated with changes to the information system. Supplemental Guidance: Any changes to the hardware, software, and/or firmware components of information systems can potentially have significant effects on the overall security of the systems. Therefore, organizations permit only qualified and authorized individuals to access information systems for purposes of initiating changes, including upgrades and modifications. Organizations maintain records of access to ensure that configuration change control is implemented and to support after-the-fact actions should organizations discover any unauthorized changes. Access restrictions for change also include software libraries. Access restrictions include, for example, physical and logical access controls (see AC-3 and PE-3), workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into information systems), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover). Related controls: AC-3, AC-6, PE-3. References: None. | link | count: 001 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-5(1) | FedRAMP_Moderate_R4_CM-5(1) | FedRAMP Moderate CM-5 (1) | Configuration Management | Automated Access Enforcement / Auditing | Shared | n/a | The information system enforces access restrictions and supports auditing of the enforcement actions. Supplemental Guidance: Related controls: AU-2, AU-12, AU-6, CM-3, CM-6. | link | count: 001 Enforce and audit access restrictions (8cd815bf-97e1-5144-0735-11f6ddb50a59) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-5(3) | FedRAMP_Moderate_R4_CM-5(3) | FedRAMP Moderate CM-5 (3) | Configuration Management | Signed Components | Shared | n/a | The information system prevents the installation of [Assignment: organization-defined software and firmware components] without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization. Supplemental Guidance: Software and firmware components prevented from installation unless signed with recognized and approved certificates include, for example, software and firmware version updates, patches, service packs, device drivers, and basic input output system (BIOS) updates. Organizations can identify applicable software and firmware components by type, by specific items, or a combination of both. Digital signatures and organizational verification of such signatures, is a method of code authentication. Related controls: CM-7, SC-13, SI-7. | link | count: 001 Restrict unauthorized software and firmware installation (4ee5975d-2507-5530-a20a-83a725889c6f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-5(5) | FedRAMP_Moderate_R4_CM-5(5) | FedRAMP Moderate CM-5 (5) | Configuration Management | Limit Production / Operational Privileges | Shared | n/a | The organization: (a) Limits privileges to change information system components and system-related information within a production or operational environment; and (b) Reviews and reevaluates privileges [Assignment: organization-defined frequency]. Supplemental Guidance: In many organizations, information systems support multiple core missions/business functions. Limiting privileges to change information system components with respect to operational systems is necessary because changes to a particular information system component may have far-reaching effects on mission/business processes supported by the system where the component resides. The complex, many-to-many relationships between systems and mission/business processes are in some cases, unknown to developers. Related control: AC-2. | link | count: 002 Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-6 | FedRAMP_Moderate_R4_CM-6 | FedRAMP Moderate CM-6 | Configuration Management | Configuration Settings | Shared | n/a | The organization: a. Establishes and documents configuration settings for information technology products employed within the information system using [Assignment: organization-defined security configuration checklists] that reflect the most restrictive mode consistent with operational requirements; b. Implements the configuration settings; c. Identifies, documents, and approves any deviations from established configuration settings for [Assignment: organization-defined information system components] based on [Assignment: organization-defined operational requirements]; and d. Monitors and controls changes to the configuration settings in accordance with organizational policies and procedures. Supplemental Guidance: Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the information system that affect the security posture and/or functionality of the system. Information technology products for which security- related configuration settings can be defined include, for example, mainframe computers, servers (e.g., database, electronic mail, authentication, web, proxy, file, domain name), workstations, input/output devices (e.g., scanners, copiers, and printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications. Security-related parameters are those parameters impacting the security state of information systems including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: (i) registry settings; (ii) account, file, directory permission settings; and (iii) settings for functions, ports, protocols, services, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific settings for information systems. The established settings become part of the systems configuration baseline. Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those information system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations including, for example, information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors. Common secure configurations include the United States Government Configuration Baseline (USGCB) which affects the implementation of CM-6 and other controls such as AC-19 and CM-7. The Security Content Automation Protocol (SCAP) and the defined standards within the protocol (e.g., Common Configuration Enumeration) provide an effective method to uniquely identify, track, and control configuration settings. OMB establishes federal policy on configuration requirements for federal information systems. Related controls: AC-19, CM-2, CM-3, CM-7, SI-4. References: OMB Memoranda 07-11, 07-18, 08-22; NIST Special Publications 800-70, 800-128; Web: http://nvd.nist.gov, http://checklists.nist.gov, http://www.nsa.gov. | link | count: 023 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Guest Configuration, Kubernetes, Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-6(1) | FedRAMP_Moderate_R4_CM-6(1) | FedRAMP Moderate CM-6 (1) | Configuration Management | Automated Central Management / Application / Verification | Shared | n/a | The organization employs automated mechanisms to centrally manage, apply, and verify configuration settings for [Assignment: organization-defined information system components]. Supplemental Guidance: Related controls: CA-7, CM-4. | link | count: 003 Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-7 | FedRAMP_Moderate_R4_CM-7 | FedRAMP Moderate CM-7 | Configuration Management | Least Functionality | Shared | n/a | The organization: a. Configures the information system to provide only essential capabilities; and b. Prohibits or restricts the use of the following functions, ports, protocols, and/or services: [Assignment: organization-defined prohibited or restricted functions, ports, protocols, and/or services]. Supplemental Guidance: Information systems can provide a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Additionally, it is sometimes convenient to provide multiple services from single information system components, but doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per device (e.g., email servers or web servers, but not both). Organizations review functions and services provided by information systems or individual components of information systems, to determine which functions and services are candidates for elimination (e.g., Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing). Organizations consider disabling unused or unnecessary physical and logical ports/protocols (e.g., Universal Serial Bus, File Transfer Protocol, and Hyper Text Transfer Protocol) on information systems to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services. Related controls: AC-6, CM-2, RA-5, SA-5, SC-7. References: DoD Instruction 8551.01. | link | count: 003 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-7(2) | FedRAMP_Moderate_R4_CM-7(2) | FedRAMP Moderate CM-7 (2) | Configuration Management | Prevent Program Execution | Shared | n/a | The information system prevents program execution in accordance with [Selection (one or more): [Assignment: organization-defined policies regarding software program usage and restrictions]; rules authorizing the terms and conditions of software program usage]. Supplemental Guidance: Related controls: CM-8, PM-5. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-7(5) | FedRAMP_Moderate_R4_CM-7(5) | FedRAMP Moderate CM-7 (5) | Configuration Management | Authorized Software / Whitelisting | Shared | n/a | The organization: (a) Identifies [Assignment: organization-defined software programs authorized to execute on the information system]; (b) Employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the information system; and (c) Reviews and updates the list of authorized software programs [Assignment: organization- defined frequency]. Supplemental Guidance: The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting. In addition to whitelisting, organizations consider verifying the integrity of white-listed software programs using, for example, cryptographic checksums, digital signatures, or hash functions. Verification of white-listed software can occur either prior to execution or at system startup. Related controls: CM-2, CM-6, CM-8, PM-5, SA-10, SC-34, SI-7. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-8 | FedRAMP_Moderate_R4_CM-8 | FedRAMP Moderate CM-8 | Configuration Management | Information System Component Inventory | Shared | n/a | The organization: a. Develops and documents an inventory of information system components that: 1. Accurately reflects the current information system; 2. Includes all components within the authorization boundary of the information system; 3. Is at the level of granularity deemed necessary for tracking and reporting; and 4. Includes [Assignment: organization-defined information deemed necessary to achieve effective information system component accountability]; and b. Reviews and updates the information system component inventory [Assignment: organization-defined frequency]. Supplemental Guidance: Organizations may choose to implement centralized information system component inventories that include components from all organizational information systems. In such situations, organizations ensure that the resulting inventories include system-specific information required for proper component accountability (e.g., information system association, information system owner). Information deemed necessary for effective accountability of information system components includes, for example, hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include, for example, manufacturer, device type, model, serial number, and physical location. Related controls: CM-2, CM-6, PM-5. References: NIST Special Publication 800-128. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-8(1) | FedRAMP_Moderate_R4_CM-8(1) | FedRAMP Moderate CM-8 (1) | Configuration Management | Updates During Installations / Removals | Shared | n/a | The organization updates the inventory of information system components as an integral part of component installations, removals, and information system updates. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-8(3) | FedRAMP_Moderate_R4_CM-8(3) | FedRAMP Moderate CM-8 (3) | Configuration Management | Automated Unauthorized Component Detection | Shared | n/a | The organization: (a) Employs automated mechanisms [Assignment: organization-defined frequency] to detect the presence of unauthorized hardware, software, and firmware components within the information system; and (b) Takes the following actions when unauthorized components are detected: [Selection (one or more): disables network access by such components; isolates the components; notifies [Assignment: organization-defined personnel or roles]]. Supplemental Guidance: This control enhancement is applied in addition to the monitoring for unauthorized remote connections and mobile devices. Monitoring for unauthorized system components may be accomplished on an ongoing basis or by the periodic scanning of systems for that purpose. Automated mechanisms can be implemented within information systems or in other separate devices. Isolation can be achieved, for example, by placing unauthorized information system components in separate domains or subnets or otherwise quarantining such components. This type of component isolation is commonly referred to as sandboxing. Related controls: AC-17, AC-18, AC-19, CA-7, SI-3, SI-4, SI-7, RA-5. | link | count: 002 Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CM-9 | FedRAMP_Moderate_R4_CM-9 | FedRAMP Moderate CM-9 | Configuration Management | Configuration Management Plan | Shared | n/a | The organization develops, documents, and implements a configuration management plan for the information system that: a. Addresses roles, responsibilities, and configuration management processes and procedures; b. Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items; c. Defines the configuration items for the information system and places the configuration items under configuration management; and d. Protects the configuration management plan from unauthorized disclosure and modification. Supplemental Guidance: Configuration management plans satisfy the requirements in configuration management policies while being tailored to individual information systems. Such plans define detailed processes and procedures for how configuration management is used to support system development life cycle activities at the information system level. Configuration management plans are typically developed during the development/acquisition phase of the system development life cycle. The plans describe how to move changes through change management processes, how to update configuration settings and baselines, how to maintain information system component inventories, how to control development, test, and operational environments, and how to develop, release, and update key documents. Organizations can employ templates to help ensure consistent and timely development and implementation of configuration management plans. Such templates can represent a master configuration management plan for the organization at large with subsets of the plan implemented on a system by system basis. Configuration management approval processes include designation of key management stakeholders responsible for reviewing and approving proposed changes to information systems, and personnel that conduct security impact analyses prior to the implementation of changes to the systems. Configuration items are the information system items (hardware, software, firmware, and documentation) to be configuration-managed. As information systems continue through the system development life cycle, new configuration items may be identified and some existing configuration items may no longer need to be under configuration control. Related controls: CM-2, CM-3, CM-4, CM-5, CM-8, SA-10. References: NIST Special Publication 800-128. | link | count: 006 Create configuration plan protection (874a6f2e-2098-53bc-3a16-20dcdc425a7e), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-1 | FedRAMP_Moderate_R4_CP-1 | FedRAMP Moderate CP-1 | Contingency Planning | Contingency Planning Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A contingency planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls; and b. Reviews and updates the current: 1. Contingency planning policy [Assignment: organization-defined frequency]; and 2. Contingency planning procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CP family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: Federal Continuity Directive 1; NIST Special Publications 800-12, 800-34, 800-100. | link | count: 001 Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-10 | FedRAMP_Moderate_R4_CP-10 | FedRAMP Moderate CP-10 | Contingency Planning | Information System Recovery And Reconstitution | Shared | n/a | The organization provides for the recovery and reconstitution of the information system to a known state after a disruption, compromise, or failure. Supplemental Guidance: Recovery is executing information system contingency plan activities to restore organizational missions/business functions. Reconstitution takes place following recovery and includes activities for returning organizational information systems to fully operational states. Recovery and reconstitution operations reflect mission and business priorities, recovery point/time and reconstitution objectives, and established organizational metrics consistent with contingency plan requirements. Reconstitution includes the deactivation of any interim information system capabilities that may have been needed during recovery operations. Reconstitution also includes assessments of fully restored information system capabilities, reestablishment of continuous monitoring activities, potential information system reauthorizations, and activities to prepare the systems against future disruptions, compromises, or failures. Recovery/reconstitution capabilities employed by organizations can include both automated mechanisms and manual procedures. Related controls: CA-2, CA-6, CA-7, CP-2, CP-6, CP-7, CP-9, SC-24. References: Federal Continuity Directive 1; NIST Special Publication 800-34. | link | count: 001 Recover and reconstitute resources after any disruption (f33c3238-11d2-508c-877c-4262ec1132e1) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-10(2) | FedRAMP_Moderate_R4_CP-10(2) | FedRAMP Moderate CP-10 (2) | Contingency Planning | Transaction Recovery | Shared | n/a | The information system implements transaction recovery for systems that are transaction-based. Supplemental Guidance: Transaction-based information systems include, for example, database management systems and transaction processing systems. Mechanisms supporting transaction recovery include, for example, transaction rollback and transaction journaling. | link | count: 001 Implement transaction based recovery (ba02d0a0-566a-25dc-73f1-101c726a19c5) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-2 | FedRAMP_Moderate_R4_CP-2 | FedRAMP Moderate CP-2 | Contingency Planning | Contingency Plan | Shared | n/a | The organization: a. Develops a contingency plan for the information system that: 1. Identifies essential missions and business functions and associated contingency requirements; 2. Provides recovery objectives, restoration priorities, and metrics; 3. Addresses contingency roles, responsibilities, assigned individuals with contact information; 4. Addresses maintaining essential missions and business functions despite an information system disruption, compromise, or failure; 5. Addresses eventual, full information system restoration without deterioration of the security safeguards originally planned and implemented; and 6. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; b. Distributes copies of the contingency plan to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements]; c. Coordinates contingency planning activities with incident handling activities; d. Reviews the contingency plan for the information system [Assignment: organization-defined frequency]; e. Updates the contingency plan to address changes to the organization, information system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing; f. Communicates contingency plan changes to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements]; and g. Protects the contingency plan from unauthorized disclosure and modification. Supplemental Guidance: Contingency planning for information systems is part of an overall organizational program for achieving continuity of operations for mission/business functions. Contingency planning addresses both information system restoration and implementation of alternative mission/business processes when systems are compromised. The effectiveness of contingency planning is maximized by considering such planning throughout the phases of the system development life cycle. Performing contingency planning on hardware, software, and firmware development can be an effective means of achieving information system resiliency. Contingency plans reflect the degree of restoration required for organizational information systems since not all systems may need to fully recover to achieve the level of continuity of operations desired. Information system recovery objectives reflect applicable laws, Executive Orders, directives, policies, standards, regulations, and guidelines. In addition to information system availability, contingency plans also address other security-related events resulting in a reduction in mission and/or business effectiveness, such as malicious attacks compromising the confidentiality or integrity of information systems. Actions addressed in contingency plans include, for example, orderly/graceful degradation, information system shutdown, fallback to a manual mode, alternate information flows, and operating in modes reserved for when systems are under attack. By closely coordinating contingency planning with incident handling activities, organizations can ensure that the necessary contingency planning activities are in place and activated in the event of a security incident. Related controls: AC-14, CP-6, CP-7, CP-8, CP-9, CP-10, IR-4, IR-8, MP-2, MP-4, MP-5, PM-8, PM-11. References: Federal Continuity Directive 1; NIST Special Publication 800-34. | link | count: 008 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82), Review contingency plan (53fc1282-0ee3-2764-1319-e20143bb0ea5), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-2(1) | FedRAMP_Moderate_R4_CP-2(1) | FedRAMP Moderate CP-2 (1) | Contingency Planning | Coordinate With Related Plans | Shared | n/a | The organization coordinates contingency plan development with organizational elements responsible for related plans. Supplemental Guidance: Plans related to contingency plans for organizational information systems include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, Insider Threat Implementation Plan, and Occupant Emergency Plans. | link | count: 001 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-2(2) | FedRAMP_Moderate_R4_CP-2(2) | FedRAMP Moderate CP-2 (2) | Contingency Planning | Capacity Planning | Shared | n/a | The organization conducts capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations. Supplemental Guidance: Capacity planning is needed because different types of threats (e.g., natural disasters, targeted cyber attacks) can result in a reduction of the available processing, telecommunications, and support services originally intended to support the organizational missions/business functions. Organizations may need to anticipate degraded operations during contingency operations and factor such degradation into capacity planning. | link | count: 001 Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-2(3) | FedRAMP_Moderate_R4_CP-2(3) | FedRAMP Moderate CP-2 (3) | Contingency Planning | Resume Essential Missions / Business Functions | Shared | n/a | The organization plans for the resumption of essential missions and business functions within [Assignment: organization-defined time period] of contingency plan activation. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. The time period for resumption of essential missions/business functions may be dependent on the severity/extent of disruptions to the information system and its supporting infrastructure. Related control: PE-12. | link | count: 001 Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-2(8) | FedRAMP_Moderate_R4_CP-2(8) | FedRAMP Moderate CP-2 (8) | Contingency Planning | Identify Critical Assets | Shared | n/a | The organization identifies critical information system assets supporting essential missions and business functions. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. Organizations identify critical information system assets so that additional safeguards and countermeasures can be employed (above and beyond those safeguards and countermeasures routinely implemented) to help ensure that organizational missions/business functions can continue to be conducted during contingency operations. In addition, the identification of critical information assets facilitates the prioritization of organizational resources. Critical information system assets include technical and operational aspects. Technical aspects include, for example, information technology services, information system components, information technology products, and mechanisms. Operational aspects include, for example, procedures (manually executed operations) and personnel (individuals operating technical safeguards and/or executing manual procedures). Organizational program protection plans can provide assistance in identifying critical assets. Related controls: SA-14, SA-15. | link | count: 001 Perform a business impact assessment and application criticality assessment (cb8841d4-9d13-7292-1d06-ba4d68384681) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-3 | FedRAMP_Moderate_R4_CP-3 | FedRAMP Moderate CP-3 | Contingency Planning | Contingency Training | Shared | n/a | The organization provides contingency training to information system users consistent with assigned roles and responsibilities: a. Within [Assignment: organization-defined time period] of assuming a contingency role or responsibility; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Contingency training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, regular users may only need to know when and where to report for duty during contingency operations and if normal duties are affected; system administrators may require additional training on how to set up information systems at alternate processing and storage sites; and managers/senior leaders may receive more specific training on how to conduct mission-essential functions in designated off-site locations and how to establish communications with other governmental entities for purposes of coordination on contingency-related activities. Training for contingency roles/responsibilities reflects the specific continuity requirements in the contingency plan. Related controls: AT-2, AT-3, CP-2, IR-2. References: Federal Continuity Directive 1; NIST Special Publications 800-16, 800-50. | link | count: 001 Provide contingency training (de936662-13dc-204c-75ec-1af80f994088) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-4 | FedRAMP_Moderate_R4_CP-4 | FedRAMP Moderate CP-4 | Contingency Planning | Contingency Plan Testing | Shared | n/a | The organization: a. Tests the contingency plan for the information system [Assignment: organization-defined frequency] using [Assignment: organization-defined tests] to determine the effectiveness of the plan and the organizational readiness to execute the plan; b. Reviews the contingency plan test results; and c. Initiates corrective actions, if needed. Supplemental Guidance: Methods for testing contingency plans to determine the effectiveness of the plans and to identify potential weaknesses in the plans include, for example, walk-through and tabletop exercises, checklists, simulations (parallel, full interrupt), and comprehensive exercises. Organizations conduct testing based on the continuity requirements in contingency plans and include a determination of the effects on organizational operations, assets, and individuals arising due to contingency operations. Organizations have flexibility and discretion in the breadth, depth, and timelines of corrective actions. Related controls: CP-2, CP-3, IR-3. References: Federal Continuity Directive 1; FIPS Publication 199; NIST Special Publications 800-34, 800-84. | link | count: 003 Initiate contingency plan testing corrective actions (8bfdbaa6-6824-3fec-9b06-7961bf7389a6), Review the results of contingency plan testing (5d3abfea-a130-1208-29c0-e57de80aa6b0), Test the business continuity and disaster recovery plan (58a51cde-008b-1a5d-61b5-d95849770677) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-4(1) | FedRAMP_Moderate_R4_CP-4(1) | FedRAMP Moderate CP-4 (1) | Contingency Planning | Coordinate With Related Plans | Shared | n/a | The organization coordinates contingency plan testing with organizational elements responsible for related plans. Supplemental Guidance: Plans related to contingency plans for organizational information systems include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, and Occupant Emergency Plans. This control enhancement does not require organizations to create organizational elements to handle related plans or to align such elements with specific plans. It does require, however, that if such organizational elements are responsible for related plans, organizations should coordinate with those elements. Related controls: IR-8, PM-8. | link | count: 001 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-6 | FedRAMP_Moderate_R4_CP-6 | FedRAMP Moderate CP-6 | Contingency Planning | Alternate Storage Site | Shared | n/a | The organization: a. Establishes an alternate storage site including necessary agreements to permit the storage and retrieval of information system backup information; and b. Ensures that the alternate storage site provides information security safeguards equivalent to that of the primary site. Supplemental Guidance: Alternate storage sites are sites that are geographically distinct from primary storage sites. An alternate storage site maintains duplicate copies of information and data in the event that the primary storage site is not available. Items covered by alternate storage site agreements include, for example, environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and coordination of delivery/retrieval of backup media. Alternate storage sites reflect the requirements in contingency plans so that organizations can maintain essential missions/business functions despite disruption, compromise, or failure in organizational information systems. Related controls: CP-2, CP-7, CP-9, CP-10, MP-4. References: NIST Special Publication 800-34. | link | count: 007 Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Regulatory Compliance, SQL, Storage | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-6(1) | FedRAMP_Moderate_R4_CP-6(1) | FedRAMP Moderate CP-6 (1) | Contingency Planning | Separation From Primary Site | Shared | n/a | The organization identifies an alternate storage site that is separated from the primary storage site to reduce susceptibility to the same threats. Supplemental Guidance: Threats that affect alternate storage sites are typically defined in organizational assessments of risk and include, for example, natural disasters, structural failures, hostile cyber attacks, and errors of omission/commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate storage sites based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites is less relevant. Related control: RA-3. | link | count: 006 Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Regulatory Compliance, SQL, Storage | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-6(3) | FedRAMP_Moderate_R4_CP-6(3) | FedRAMP Moderate CP-6 (3) | Contingency Planning | Accessibility | Shared | n/a | The organization identifies potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions. Supplemental Guidance: Area-wide disruptions refer to those types of disruptions that are broad in geographic scope (e.g., hurricane, regional power outage) with such determinations made by organizations based on organizational assessments of risk. Explicit mitigation actions include, for example: (i) duplicating backup information at other alternate storage sites if access problems occur at originally designated alternate sites; or (ii) planning for physical access to retrieve backup information if electronic accessibility to the alternate site is disrupted. Related control: RA-3. | link | count: 001 Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-7 | FedRAMP_Moderate_R4_CP-7 | FedRAMP Moderate CP-7 | Contingency Planning | Alternate Processing Site | Shared | n/a | The organization: a. Establishes an alternate processing site including necessary agreements to permit the transfer and resumption of [Assignment: organization-defined information system operations] for essential missions/business functions within [Assignment: organization-defined time period consistent with recovery time and recovery point objectives] when the primary processing capabilities are unavailable; b. Ensures that equipment and supplies required to transfer and resume operations are available at the alternate processing site or contracts are in place to support delivery to the site within the organization-defined time period for transfer/resumption; and c. Ensures that the alternate processing site provides information security safeguards equivalent to that of the primary site. Supplemental Guidance: Alternate processing sites are sites that are geographically distinct from primary processing sites. An alternate processing site provides processing capability in the event that the primary processing site is not available. Items covered by alternate processing site agreements include, for example, environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and coordination for the transfer/assignment of personnel. Requirements are specifically allocated to alternate processing sites that reflect the requirements in contingency plans to maintain essential missions/business functions despite disruption, compromise, or failure in organizational information systems. Related controls: CP-2, CP-6, CP-8, CP-9, CP-10, MA-6. References: NIST Special Publication 800-34. | link | count: 002 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Compute, Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-7(1) | FedRAMP_Moderate_R4_CP-7(1) | FedRAMP Moderate CP-7 (1) | Contingency Planning | Separation From Primary Site | Shared | n/a | The organization identifies an alternate processing site that is separated from the primary processing site to reduce susceptibility to the same threats. Supplemental Guidance: Threats that affect alternate processing sites are typically defined in organizational assessments of risk and include, for example, natural disasters, structural failures, hostile cyber attacks, and errors of omission/commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate processing sites based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites is less relevant. Related control: RA-3. | link | count: 001 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-7(2) | FedRAMP_Moderate_R4_CP-7(2) | FedRAMP Moderate CP-7 (2) | Contingency Planning | Accessibility | Shared | n/a | The organization identifies potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions. Supplemental Guidance: Area-wide disruptions refer to those types of disruptions that are broad in geographic scope (e.g., hurricane, regional power outage) with such determinations made by organizations based on organizational assessments of risk. Related control: RA-3. | link | count: 001 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-7(3) | FedRAMP_Moderate_R4_CP-7(3) | FedRAMP Moderate CP-7 (3) | Contingency Planning | Priority Of Service | Shared | n/a | The organization develops alternate processing site agreements that contain priority-of-service provisions in accordance with organizational availability requirements (including recovery time objectives). Supplemental Guidance: Priority-of-service agreements refer to negotiated agreements with service providers that ensure that organizations receive priority treatment consistent with their availability requirements and the availability of information resources at the alternate processing site. | link | count: 002 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-8(1) | FedRAMP_Moderate_R4_CP-8(1) | FedRAMP Moderate CP-8 (1) | Contingency Planning | Priority Of Service Provisions | Shared | n/a | The organization: (a) Develops primary and alternate telecommunications service agreements that contain priority- of-service provisions in accordance with organizational availability requirements (including recovery time objectives); and (b) Requests Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness in the event that the primary and/or alternate telecommunications services are provided by a common carrier. Supplemental Guidance: Organizations consider the potential mission/business impact in situations where telecommunications service providers are servicing other organizations with similar priority-of-service provisions. | link | count: 001 Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-9 | FedRAMP_Moderate_R4_CP-9 | FedRAMP Moderate CP-9 | Contingency Planning | Information System Backup | Shared | n/a | The organization: a. Conducts backups of user-level information contained in the information system [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; b. Conducts backups of system-level information contained in the information system [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; c. Conducts backups of information system documentation including security-related documentation [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; and d. Protects the confidentiality, integrity, and availability of backup information at storage locations. Supplemental Guidance: System-level information includes, for example, system-state information, operating system and application software, and licenses. User-level information includes any information other than system-level information. Mechanisms employed by organizations to protect the integrity of information system backups include, for example, digital signatures and cryptographic hashes. Protection of system backup information while in transit is beyond the scope of this control. Information system backups reflect the requirements in contingency plans as well as other organizational requirements for backing up information. Related controls: CP-2, CP-6, MP-4, MP-5, SC-13. References: NIST Special Publication 800-34. | link | count: 009 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Backup, Key Vault, Regulatory Compliance, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | CP-9(3) | FedRAMP_Moderate_R4_CP-9(3) | FedRAMP Moderate CP-9 (3) | Contingency Planning | Separate Storage For Critical Information | Shared | n/a | The organization stores backup copies of [Assignment: organization-defined critical information system software and other security-related information] in a separate facility or in a fire-rated container that is not collocated with the operational system. Supplemental Guidance: Critical information system software includes, for example, operating systems, cryptographic key management systems, and intrusion detection/prevention systems. Security-related information includes, for example, organizational inventories of hardware, software, and firmware components. Alternate storage sites typically serve as separate storage facilities for organizations. Related controls: CM-2, CM-8. | link | count: 001 Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-1 | FedRAMP_Moderate_R4_IA-1 | FedRAMP Moderate IA-1 | Identification And Authentication | Identification And Authentication Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls; and b. Reviews and updates the current: 1. Identification and authentication policy [Assignment: organization-defined frequency]; and 2. Identification and authentication procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the IA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: FIPS Publication 201; NIST Special Publications 800-12, 800-63, 800-73, 800-76, 800-78, 800-100. | link | count: 001 Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-2 | FedRAMP_Moderate_R4_IA-2 | FedRAMP Moderate IA-2 | Identification And Authentication | Identification And Authentication (Organizational Users) | Shared | n/a | The information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users). Supplemental Guidance: Organizational users include employees or individuals that organizations deem to have equivalent status of employees (e.g., contractors, guest researchers). This control applies to all accesses other than: (i) accesses that are explicitly identified and documented in AC-14; and (ii) accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity. Organizations employ passwords, tokens, or biometrics to authenticate user identities, or in the case multifactor authentication, or some combination thereof. Access to organizational information systems is defined as either local access or network access. Local access is any access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained by direct connections without the use of networks. Network access is access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks (e.g., the Internet). Internal networks include local area networks and wide area networks. In addition, the use of encrypted virtual private networks (VPNs) for network connections between organization- controlled endpoints and non-organization controlled endpoints may be treated as internal networks from the perspective of protecting the confidentiality and integrity of information traversing the network. Organizations can satisfy the identification and authentication requirements in this control by complying with the requirements in Homeland Security Presidential Directive 12 consistent with the specific organizational implementation plans. Multifactor authentication requires the use of two or more different factors to achieve authentication. The factors are defined as: (i) something you know (e.g., password, personal identification number [PIN]); (ii) something you have (e.g., cryptographic identification device, token); or (iii) something you are (e.g., biometric). Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card. In addition to identifying and authenticating users at the information system level (i.e., at logon), organizations also employ identification and authentication mechanisms at the application level, when necessary, to provide increased information security. Identification and authentication requirements for other than organizational users are described in IA-8. Related controls: AC-2, AC-3, AC-14, AC-17, AC-18, IA-4, IA-5, IA-8. References: HSPD-12; OMB Memoranda 04-04, 06-16, 11-11; FIPS Publication 201; NIST Special Publications 800-63, 800-73, 800-76, 800-78; FICAM Roadmap and Implementation Guidance; Web: http://idmanagement.gov. | link | count: 010 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
App Service, Azure Ai Services, Regulatory Compliance, Security Center, Service Fabric, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-2(1) | FedRAMP_Moderate_R4_IA-2(1) | FedRAMP Moderate IA-2 (1) | Identification And Authentication | Network Access To Privileged Accounts | Shared | n/a | The information system implements multifactor authentication for network access to privileged accounts. Supplemental Guidance: Related control: AC-6. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-2(11) | FedRAMP_Moderate_R4_IA-2(11) | FedRAMP Moderate IA-2 (11) | Identification And Authentication | Remote Access - Separate Device | Shared | n/a | The information system implements multifactor authentication for remote access to privileged and non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access and the device meets [Assignment: organization-defined strength of mechanism requirements]. Supplemental Guidance: For remote access to privileged/non-privileged accounts, the purpose of requiring a device that is separate from the information system gaining access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authentication credentials stored on the system. For example, adversaries deploying malicious code on organizational information systems can potentially compromise such credentials resident on the system and subsequently impersonate authorized users. Related control: AC-6. | link | count: 002 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-2(12) | FedRAMP_Moderate_R4_IA-2(12) | FedRAMP Moderate IA-2 (12) | Identification And Authentication | Acceptance Of Piv Credentials | Shared | n/a | The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials. Supplemental Guidance: This control enhancement applies to organizations implementing logical access control systems (LACS) and physical access control systems (PACS). Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 requires federal agencies to continue implementing the requirements specified in HSPD-12 to enable agency-wide use of PIV credentials. Related controls: AU-2, PE-3, SA-4. | link | count: 001 Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-2(2) | FedRAMP_Moderate_R4_IA-2(2) | FedRAMP Moderate IA-2 (2) | Identification And Authentication | Network Access To Non-Privileged Accounts | Shared | n/a | The information system implements multifactor authentication for network access to non- privileged accounts. | link | count: 002 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-2(3) | FedRAMP_Moderate_R4_IA-2(3) | FedRAMP Moderate IA-2 (3) | Identification And Authentication | Local Access To Privileged Accounts | Shared | n/a | The information system implements multifactor authentication for local access to privileged accounts. Supplemental Guidance: Related control: AC-6. | link | count: 001 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-2(5) | FedRAMP_Moderate_R4_IA-2(5) | FedRAMP Moderate IA-2 (5) | Identification And Authentication | Group Authentication | Shared | n/a | The organization requires individuals to be authenticated with an individual authenticator when a group authenticator is employed. Supplemental Guidance: Requiring individuals to use individual authenticators as a second level of authentication helps organizations to mitigate the risk of using group authenticators. | link | count: 001 Require use of individual authenticators (08ad71d0-52be-6503-4908-e015460a16ae) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-4 | FedRAMP_Moderate_R4_IA-4 | FedRAMP Moderate IA-4 | Identification And Authentication | Identifier Management | Shared | n/a | The organization manages information system identifiers by: a. Receiving authorization from [Assignment: organization-defined personnel or roles] to assign an individual, group, role, or device identifier; b. Selecting an identifier that identifies an individual, group, role, or device; c. Assigning the identifier to the intended individual, group, role, or device; d. Preventing reuse of identifiers for [Assignment: organization-defined time period]; and e. Disabling the identifier after [Assignment: organization-defined time period of inactivity]. Supplemental Guidance: Common device identifiers include, for example, media access control (MAC), Internet protocol (IP) addresses, or device-unique token identifiers. Management of individual identifiers is not applicable to shared information system accounts (e.g., guest and anonymous accounts). Typically, individual identifiers are the user names of the information system accounts assigned to those individuals. In such instances, the account management activities of AC-2 use account names provided by IA-4. This control also addresses individual identifiers not necessarily associated with information system accounts (e.g., identifiers used in physical security control databases accessed by badge reader systems for access to information systems). Preventing reuse of identifiers implies preventing the assignment of previously used individual, group, role, or device identifiers to different individuals, groups, roles, or devices. Related controls: AC-2, IA-2, IA-3, IA-5, IA-8, SC-37. References: FIPS Publication 201; NIST Special Publications 800-73, 800-76, 800-78. | link | count: 007 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Prevent identifier reuse for the defined time period (4781e5fd-76b8-7d34-6df3-a0a7fca47665), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-4(4) | FedRAMP_Moderate_R4_IA-4(4) | FedRAMP Moderate IA-4 (4) | Identification And Authentication | Identify User Status | Shared | n/a | The organization manages individual identifiers by uniquely identifying each individual as [Assignment: organization-defined characteristic identifying individual status]. Supplemental Guidance: Characteristics identifying the status of individuals include, for example, contractors and foreign nationals. Identifying the status of individuals by specific characteristics provides additional information about the people with whom organizational personnel are communicating. For example, it might be useful for a government employee to know that one of the individuals on an email message is a contractor. Related control: AT-2. | link | count: 001 Identify status of individual users (ca748dfe-3e28-1d18-4221-89aea30aa0a5) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-5 | FedRAMP_Moderate_R4_IA-5 | FedRAMP Moderate IA-5 | Identification And Authentication | Authenticator Management | Shared | n/a | The organization manages information system authenticators by: a. Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, or device receiving the authenticator; b. Establishing initial authenticator content for authenticators defined by the organization; c. Ensuring that authenticators have sufficient strength of mechanism for their intended use; d. Establishing and implementing administrative procedures for initial authenticator distribution, for lost/compromised or damaged authenticators, and for revoking authenticators; e. Changing default content of authenticators prior to information system installation; f. Establishing minimum and maximum lifetime restrictions and reuse conditions for authenticators; g. Changing/refreshing authenticators [Assignment: organization-defined time period by authenticator type]; h. Protecting authenticator content from unauthorized disclosure and modification; i. Requiring individuals to take, and having devices implement, specific security safeguards to protect authenticators; and j. Changing authenticators for group/role accounts when membership to those accounts changes. Supplemental Guidance: Individual authenticators include, for example, passwords, tokens, biometrics, PKI certificates, and key cards. Initial authenticator content is the actual content (e.g., the initial password) as opposed to requirements about authenticator content (e.g., minimum password length). In many cases, developers ship information system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant security risk. The requirement to protect individual authenticators may be implemented via control PL-4 or PS-6 for authenticators in the possession of individuals and by controls AC-3, AC-6, and SC-28 for authenticators stored within organizational information systems (e.g., passwords stored in hashed or encrypted formats, files containing encrypted or hashed passwords accessible with administrator privileges). Information systems support individual authenticator management by organization-defined settings and restrictions for various authenticator characteristics including, for example, minimum password length, password composition, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication. Specific actions that can be taken to safeguard authenticators include, for example, maintaining possession of individual authenticators, not loaning or sharing individual authenticators with others, and reporting lost, stolen, or compromised authenticators immediately. Authenticator management includes issuing and revoking, when no longer needed, authenticators for temporary access such as that required for remote maintenance. Device authenticators include, for example, certificates and passwords. Related controls: AC-2, AC-3, AC-6, CM-6, IA-2, IA-4, IA-8, PL-4, PS-5, PS-6, SC-12, SC-13, SC-17, SC-28. References: OMB Memoranda 04-04, 11-11; FIPS Publication 201; NIST Special Publications 800-73, 800-63, 800-76, 800-78; FICAM Roadmap and Implementation Guidance | link | count: 018 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Guest Configuration, Key Vault, Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-5(1) | FedRAMP_Moderate_R4_IA-5(1) | FedRAMP Moderate IA-5 (1) | Identification And Authentication | Password-Based Authentication | Shared | n/a | The information system, for password-based authentication: (a) Enforces minimum password complexity of [Assignment: organization-defined requirements for case sensitivity, number of characters, mix of upper-case letters, lower-case letters, numbers, and special characters, including minimum requirements for each type]; (b) Enforces at least the following number of changed characters when new passwords are created: [Assignment: organization-defined number]; (c) Stores and transmits only encrypted representations of passwords; (d) Enforces password minimum and maximum lifetime restrictions of [Assignment: organization- defined numbers for lifetime minimum, lifetime maximum]; (e) Prohibits password reuse for [Assignment: organization-defined number] generations; and (f) Allows the use of a temporary password for system logons with an immediate change to a permanent password. Supplemental Guidance: This control enhancement applies to single-factor authentication of individuals using passwords as individual or group authenticators, and in a similar manner, when passwords are part of multifactor authenticators. This control enhancement does not apply when passwords are used to unlock hardware authenticators (e.g., Personal Identity Verification cards). The implementation of such password mechanisms may not meet all of the requirements in the enhancement. Encrypted representations of passwords include, for example, encrypted versions of passwords and one-way cryptographic hashes of passwords. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. Password lifetime restrictions do not apply to temporary passwords. Related control: IA-6. | link | count: 015 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Guest Configuration, Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-5(11) | FedRAMP_Moderate_R4_IA-5(11) | FedRAMP Moderate IA-5 (11) | Identification And Authentication | Hardware Token-Based Authentication | Shared | n/a | The information system, for hardware token-based authentication, employs mechanisms that satisfy [Assignment: organization-defined token quality requirements]. Supplemental Guidance: Hardware token-based authentication typically refers to the use of PKI-based tokens, such as the U.S. Government Personal Identity Verification (PIV) card. Organizations define specific requirements for tokens, such as working with a particular PKI. | link | count: 001 Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-5(2) | FedRAMP_Moderate_R4_IA-5(2) | FedRAMP Moderate IA-5 (2) | Identification And Authentication | Pki-Based Authentication | Shared | n/a | The information system, for PKI-based authentication: (a) Validates certifications by constructing and verifying a certification path to an accepted trust anchor including checking certificate status information; (b) Enforces authorized access to the corresponding private key; (c) Maps the authenticated identity to the account of the individual or group; and (d) Implements a local cache of revocation data to support path discovery and validation in case of inability to access revocation information via the network. Supplemental Guidance: Status information for certification paths includes, for example, certificate revocation lists or certificate status protocol responses. For PIV cards, validation of certifications involves the construction and verification of a certification path to the Common Policy Root trust anchor including certificate policy processing. Related control: IA-6. | link | count: 007 Bind authenticators and identities dynamically (6f311b49-9b0d-8c67-3d6e-db80ae528173), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish parameters for searching secret authenticators and verifiers (0065241c-72e9-3b2c-556f-75de66332a94), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Map authenticated identities to individuals (4012c2b7-4e0e-a7ab-1688-4aab43f14420), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-5(3) | FedRAMP_Moderate_R4_IA-5(3) | FedRAMP Moderate IA-5 (3) | Identification And Authentication | In-Person Or Trusted Third-Party Registration | Shared | n/a | The organization requires that the registration process to receive [Assignment: organization- defined types of and/or specific authenticators] be conducted [Selection: in person; by a trusted third party] before [Assignment: organization-defined registration authority] with authorization by [Assignment: organization-defined personnel or roles]. | link | count: 001 Distribute authenticators (098dcde7-016a-06c3-0985-0daaf3301d3a) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-5(4) | FedRAMP_Moderate_R4_IA-5(4) | FedRAMP Moderate IA-5 (4) | Identification And Authentication | Automated Support For Password Strength Determination | Shared | n/a | The organization employs automated tools to determine if password authenticators are sufficiently strong to satisfy [Assignment: organization-defined requirements]. Supplemental Guidance: This control enhancement focuses on the creation of strong passwords and the characteristics of such passwords (e.g., complexity) prior to use, the enforcement of which is carried out by organizational information systems in IA-5 (1). Related controls: CA-2, CA-7, RA-5. | link | count: 003 Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-5(6) | FedRAMP_Moderate_R4_IA-5(6) | FedRAMP Moderate IA-5 (6) | Identification And Authentication | Protection Of Authenticators | Shared | n/a | The organization protects authenticators commensurate with the security category of the information to which use of the authenticator permits access. Supplemental Guidance: For information systems containing multiple security categories of information without reliable physical or logical separation between categories, authenticators used to grant access to the systems are protected commensurate with the highest security category of information on the systems. | link | count: 001 Ensure authorized users protect provided authenticators (37dbe3dc-0e9c-24fa-36f2-11197cbfa207) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-5(7) | FedRAMP_Moderate_R4_IA-5(7) | FedRAMP Moderate IA-5 (7) | Identification And Authentication | No Embedded Unencrypted Static Authenticators | Shared | n/a | The organization ensures that unencrypted static authenticators are not embedded in applications or access scripts or stored on function keys. Supplemental Guidance: Organizations exercise caution in determining whether embedded or stored authenticators are in encrypted or unencrypted form. If authenticators are used in the manner stored, then those representations are considered unencrypted authenticators. This is irrespective of whether that representation is perhaps an encrypted version of something else (e.g., a password). | link | count: 001 Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-6 | FedRAMP_Moderate_R4_IA-6 | FedRAMP Moderate IA-6 | Identification And Authentication | Authenticator Feedback | Shared | n/a | The information system obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. Supplemental Guidance: The feedback from information systems does not provide information that would allow unauthorized individuals to compromise authentication mechanisms. For some types of information systems or system components, for example, desktops/notebooks with relatively large monitors, the threat (often referred to as shoulder surfing) may be significant. For other types of systems or components, for example, mobile devices with 2-4 inch screens, this threat may be less significant, and may need to be balanced against the increased likelihood of typographic input errors due to the small keyboards. Therefore, the means for obscuring the authenticator feedback is selected accordingly. Obscuring the feedback of authentication information includes, for example, displaying asterisks when users type passwords into input devices, or displaying feedback for a very limited time before fully obscuring it. Related control: PE-18. Control Enhancements: None. References: None. | link | count: 001 Obscure feedback information during authentication process (1ff03f2a-974b-3272-34f2-f6cd51420b30) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-7 | FedRAMP_Moderate_R4_IA-7 | FedRAMP Moderate IA-7 | Identification And Authentication | Cryptographic Module Authentication | Shared | n/a | The information system implements mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication. Supplemental Guidance: Authentication mechanisms may be required within a cryptographic module to authenticate an operator accessing the module and to verify that the operator is authorized to assume the requested role and perform services within that role. Related controls: SC-12, SC-13. Control Enhancements: None. References: FIPS Publication 140; Web: csrc.nist.gov/groups/STM/cmvp/index.html. | link | count: 001 Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-8 | FedRAMP_Moderate_R4_IA-8 | FedRAMP Moderate IA-8 | Identification And Authentication | Identification And Authentication (Non- Organizational Users) | Shared | n/a | The information system uniquely identifies and authenticates non-organizational users (or processes acting on behalf of non-organizational users). Supplemental Guidance: Non-organizational users include information system users other than organizational users explicitly covered by IA-2. These individuals are uniquely identified and authenticated for accesses other than those accesses explicitly identified and documented in AC-14. In accordance with the E-Authentication E-Government initiative, authentication of non- organizational users accessing federal information systems may be required to protect federal, proprietary, or privacy-related information (with exceptions noted for national security systems). Organizations use risk assessments to determine authentication needs and consider scalability, practicality, and security in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk. IA-2 addresses identification and authentication requirements for access to information systems by organizational users. Related controls: AC-2, AC-14, AC-17, AC-18, IA-2, IA-4, IA-5, MA-4, RA-3, SA-12, SC-8. References: OMB Memoranda 04-04, 11-11, 10-06-2011; FICAM Roadmap and Implementation Guidance; FIPS Publication 201; NIST Special Publications 800-63, 800-116; National Strategy for Trusted Identities in Cyberspace; Web: http://idmanagement.gov. | link | count: 001 Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-8(1) | FedRAMP_Moderate_R4_IA-8(1) | FedRAMP Moderate IA-8 (1) | Identification And Authentication | Acceptance Of Piv Credentials From Other Agencies | Shared | n/a | The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials from other federal agencies. Supplemental Guidance: This control enhancement applies to logical access control systems (LACS) and physical access control systems (PACS). Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 requires federal agencies to continue implementing the requirements specified in HSPD-12 to enable agency-wide use of PIV credentials. Related controls: AU-2, PE-3, SA-4. | link | count: 001 Accept PIV credentials (55be3260-a7a2-3c06-7fe6-072d07525ab7) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-8(2) | FedRAMP_Moderate_R4_IA-8(2) | FedRAMP Moderate IA-8 (2) | Identification And Authentication | Acceptance Of Third-Party Credentials | Shared | n/a | The information system accepts only FICAM-approved third-party credentials. Supplemental Guidance: This control enhancement typically applies to organizational information systems that are accessible to the general public, for example, public-facing websites. Third-party credentials are those credentials issued by nonfederal government entities approved by the Federal Identity, Credential, and Access Management (FICAM) Trust Framework Solutions initiative. Approved third-party credentials meet or exceed the set of minimum federal government-wide technical, security, privacy, and organizational maturity requirements. This allows federal government relying parties to trust such credentials at their approved assurance levels. Related control: AU-2. | link | count: 001 Accept only FICAM-approved third-party credentials (2d2ca910-7957-23ee-2945-33f401606efc) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-8(3) | FedRAMP_Moderate_R4_IA-8(3) | FedRAMP Moderate IA-8 (3) | Identification And Authentication | Use Of Ficam-Approved Products | Shared | n/a | The organization employs only FICAM-approved information system components in [Assignment: organization-defined information systems] to accept third-party credentials. Supplemental Guidance: This control enhancement typically applies to information systems that are accessible to the general public, for example, public-facing websites. FICAM-approved information system components include, for example, information technology products and software libraries that have been approved by the Federal Identity, Credential, and Access Management conformance program. Related control: SA-4. | link | count: 001 Employ FICAM-approved resources to accept third-party credentials (db8b35d6-8adb-3f51-44ff-c648ab5b1530) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IA-8(4) | FedRAMP_Moderate_R4_IA-8(4) | FedRAMP Moderate IA-8 (4) | Identification And Authentication | Use Of Ficam-Issued Profiles | Shared | n/a | The information system conforms to FICAM-issued profiles. Supplemental Guidance: This control enhancement addresses open identity management standards. To ensure that these standards are viable, robust, reliable, sustainable (e.g., available in commercial information technology products), and interoperable as documented, the United States Government assesses and scopes identity management standards and technology implementations against applicable federal legislation, directives, policies, and requirements. The result is FICAM-issued implementation profiles of approved protocols (e.g., FICAM authentication protocols such as SAML 2.0 and OpenID 2.0, as well as other protocols such as the FICAM Backend Attribute Exchange). Related control: SA-4. | link | count: 001 Conform to FICAM-issued profiles (a8df9c78-4044-98be-2c05-31a315ac8957) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-1 | FedRAMP_Moderate_R4_IR-1 | FedRAMP Moderate IR-1 | Incident Response | Incident Response Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An incident response policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the incident response policy and associated incident response controls; and b. Reviews and updates the current: 1. Incident response policy [Assignment: organization-defined frequency]; and 2. Incident response procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the IR family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-61, 800-83, 800-100. | link | count: 001 Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-2 | FedRAMP_Moderate_R4_IR-2 | FedRAMP Moderate IR-2 | Incident Response | Incident Response Training | Shared | n/a | The organization provides incident response training to information system users consistent with assigned roles and responsibilities: a. Within [Assignment: organization-defined time period] of assuming an incident response role or responsibility; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Incident response training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure the appropriate content and level of detail is included in such training. For example, regular users may only need to know who to call or how to recognize an incident on the information system; system administrators may require additional training on how to handle/remediate incidents; and incident responders may receive more specific training on forensics, reporting, system recovery, and restoration. Incident response training includes user training in the identification and reporting of suspicious activities, both from external and internal sources. Related controls: AT-3, CP-3, IR-8. References: NIST Special Publications 800-16, 800-50. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-3 | FedRAMP_Moderate_R4_IR-3 | FedRAMP Moderate IR-3 | Incident Response | Incident Response Testing | Shared | n/a | The organization tests the incident response capability for the information system [Assignment: organization-defined frequency] using [Assignment: organization-defined tests] to determine the incident response effectiveness and documents the results. Supplemental Guidance: Organizations test incident response capabilities to determine the overall effectiveness of the capabilities and to identify potential weaknesses or deficiencies. Incident response testing includes, for example, the use of checklists, walk-through or tabletop exercises, simulations (parallel/full interrupt), and comprehensive exercises. Incident response testing can also include a determination of the effects on organizational operations (e.g., reduction in mission capabilities), organizational assets, and individuals due to incident response. Related controls: CP-4, IR-8. References: NIST Special Publications 800-84, 800-115. | link | count: 003 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-3(2) | FedRAMP_Moderate_R4_IR-3(2) | FedRAMP Moderate IR-3 (2) | Incident Response | Coordination With Related Plans | Shared | n/a | The organization coordinates incident response testing with organizational elements responsible for related plans. Supplemental Guidance: Organizational plans related to incident response testing include, for example, Business Continuity Plans, Contingency Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, and Occupant Emergency Plans. | link | count: 003 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-4 | FedRAMP_Moderate_R4_IR-4 | FedRAMP Moderate IR-4 | Incident Response | Incident Handling | Shared | n/a | The organization: a. Implements an incident handling capability for security incidents that includes preparation, detection and analysis, containment, eradication, and recovery; b. Coordinates incident handling activities with contingency planning activities; and c. Incorporates lessons learned from ongoing incident handling activities into incident response procedures, training, and testing/exercises, and implements the resulting changes accordingly. Supplemental Guidance: Organizations recognize that incident response capability is dependent on the capabilities of organizational information systems and the mission/business processes being supported by those systems. Therefore, organizations consider incident response as part of the definition, design, and development of mission/business processes and information systems. Incident-related information can be obtained from a variety of sources including, for example, audit monitoring, network monitoring, physical access monitoring, user/administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including, for example, mission/business owners, information system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive (function). Related controls: AU-6, CM-6, CP-2, CP-4, IR-2, IR-3, IR-8, PE-6, SC-5, SC-7, SI-3, SI-4, SI-7. References: Executive Order 13587; NIST Special Publication 800-61. | link | count: 024 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance, Security Center, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-4(1) | FedRAMP_Moderate_R4_IR-4(1) | FedRAMP Moderate IR-4 (1) | Incident Response | Automated Incident Handling Processes | Shared | n/a | The organization employs automated mechanisms to support the incident handling process. Supplemental Guidance: Automated mechanisms supporting incident handling processes include, for example, online incident management systems. | link | count: 003 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-5 | FedRAMP_Moderate_R4_IR-5 | FedRAMP Moderate IR-5 | Incident Response | Incident Monitoring | Shared | n/a | The organization tracks and documents information system security incidents. Supplemental Guidance: Documenting information system security incidents includes, for example, maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics, evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources including, for example, incident reports, incident response teams, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports. Related controls: AU-6, IR-8, PE-6, SC-5, SC-7, SI-3, SI-4, SI-7. References: NIST Special Publication 800-61. | link | count: 013 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-6(1) | FedRAMP_Moderate_R4_IR-6(1) | FedRAMP Moderate IR-6 (1) | Incident Response | Automated Reporting | Shared | n/a | The organization employs automated mechanisms to assist in the reporting of security incidents. Supplemental Guidance: Related control: IR-7. | link | count: 001 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-7 | FedRAMP_Moderate_R4_IR-7 | FedRAMP Moderate IR-7 | Incident Response | Incident Response Assistance | Shared | n/a | The organization provides an incident response support resource, integral to the organizational incident response capability that offers advice and assistance to users of the information system for the handling and reporting of security incidents. Supplemental Guidance: Incident response support resources provided by organizations include, for example, help desks, assistance groups, and access to forensics services, when required. Related controls: AT-2, IR-4, IR-6, IR-8, SA-9. | link | count: 001 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-7(1) | FedRAMP_Moderate_R4_IR-7(1) | FedRAMP Moderate IR-7 (1) | Incident Response | Automation Support For Availability Of Information / Support | Shared | n/a | The organization employs automated mechanisms to increase the availability of incident response- related information and support. Supplemental Guidance: Automated mechanisms can provide a push and/or pull capability for users to obtain incident response assistance. For example, individuals might have access to a website to query the assistance capability, or conversely, the assistance capability may have the ability to proactively send information to users (general distribution or targeted) as part of increasing understanding of current response capabilities and support. | link | count: 007 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-7(2) | FedRAMP_Moderate_R4_IR-7(2) | FedRAMP Moderate IR-7 (2) | Incident Response | Coordination With External Providers | Shared | n/a | The organization: (a) Establishes a direct, cooperative relationship between its incident response capability and external providers of information system protection capability; and (b) Identifies organizational incident response team members to the external providers. Supplemental Guidance: External providers of information system protection capability include, for example, the Computer Network Defense program within the U.S. Department of Defense. External providers help to protect, monitor, analyze, detect, and respond to unauthorized activity within organizational information systems and networks. | link | count: 002 Establish relationship between incident response capability and external providers (b470a37a-7a47-3792-34dd-7a793140702e), Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-8 | FedRAMP_Moderate_R4_IR-8 | FedRAMP Moderate IR-8 | Incident Response | Incident Response Plan | Shared | n/a | The organization: a. Develops an incident response plan that: 1. Provides the organization with a roadmap for implementing its incident response capability; 2. Describes the structure and organization of the incident response capability; 3. Provides a high-level approach for how the incident response capability fits into the overall organization; 4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions; 5. Defines reportable incidents; 6. Provides metrics for measuring the incident response capability within the organization; 7. Defines the resources and management support needed to effectively maintain and mature an incident response capability; and 8. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; b. Distributes copies of the incident response plan to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; c. Reviews the incident response plan [Assignment: organization-defined frequency]; d. Updates the incident response plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing; e. Communicates incident response plan changes to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and f. Protects the incident response plan from unauthorized disclosure and modification. Supplemental Guidance: It is important that organizations develop and implement a coordinated approach to incident response. Organizational missions, business functions, strategies, goals, and objectives for incident response help to determine the structure of incident response capabilities. As part of a comprehensive incident response capability, organizations consider the coordination and sharing of information with external organizations, including, for example, external service providers and organizations involved in the supply chain for organizational information systems. Related controls: MP-2, MP-4, MP-5. Control Enhancements: None. References: NIST Special Publication 800-61. | link | count: 006 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-9 | FedRAMP_Moderate_R4_IR-9 | FedRAMP Moderate IR-9 | Incident Response | Information Spillage Response | Shared | n/a | The organization responds to information spills by: a. Identifying the specific information involved in the information system contamination; b. Alerting [Assignment: organization-defined personnel or roles] of the information spill using a method of communication not associated with the spill; c. Isolating the contaminated information system or system component; d. Eradicating the information from the contaminated information system or component; e. Identifying other information systems or system components that may have been subsequently contaminated; and f. Performing other [Assignment: organization-defined actions]. Supplemental Guidance: Information spillage refers to instances where either classified or sensitive information is inadvertently placed on information systems that are not authorized to process such information. Such information spills often occur when information that is initially thought to be of lower sensitivity is transmitted to an information system and then is subsequently determined to be of higher sensitivity. At that point, corrective action is required. The nature of the organizational response is generally based upon the degree of sensitivity of the spilled information (e.g., security category or classification level), the security capabilities of the information system, the specific nature of contaminated storage media, and the access authorizations (e.g., security clearances) of individuals with authorized access to the contaminated system. The methods used to communicate information about the spill after the fact do not involve methods directly associated with the actual spill to minimize the risk of further spreading the contamination before such contamination is isolated and eradicated. References: None. | link | count: 007 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify contaminated systems and components (279052a0-8238-694d-9661-bf649f951747), Identify spilled information (69d90ee6-9f9f-262a-2038-d909fb4e5723), Isolate information spills (22457e81-3ec6-5271-a786-c3ca284601dd) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-9(1) | FedRAMP_Moderate_R4_IR-9(1) | FedRAMP Moderate IR-9 (1) | Incident Response | Responsible Personnel | Shared | n/a | The organization assigns [Assignment: organization-defined personnel or roles] with responsibility for responding to information spills. | link | count: 001 Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-9(2) | FedRAMP_Moderate_R4_IR-9(2) | FedRAMP Moderate IR-9 (2) | Incident Response | Training | Shared | n/a | The organization provides information spillage response training [Assignment: organization- defined frequency]. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-9(3) | FedRAMP_Moderate_R4_IR-9(3) | FedRAMP Moderate IR-9 (3) | Incident Response | Post-Spill Operations | Shared | n/a | The organization implements [Assignment: organization-defined procedures] to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions. Supplemental Guidance: Correction actions for information systems contaminated due to information spillages may be very time-consuming. During those periods, personnel may not have access to the contaminated systems, which may potentially affect their ability to conduct organizational business. | link | count: 001 Develop spillage response procedures (bb048641-6017-7272-7772-a008f285a520) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | IR-9(4) | FedRAMP_Moderate_R4_IR-9(4) | FedRAMP Moderate IR-9 (4) | Incident Response | Exposure To Unauthorized Personnel | Shared | n/a | The organization employs [Assignment: organization-defined security safeguards] for personnel exposed to information not within assigned access authorizations. Supplemental Guidance: Security safeguards include, for example, making personnel exposed to spilled information aware of the federal laws, directives, policies, and/or regulations regarding the information and the restrictions imposed based on exposure to such information. | link | count: 001 Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-1 | FedRAMP_Moderate_R4_MA-1 | FedRAMP Moderate MA-1 | Maintenance | System Maintenance Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls; and b. Reviews and updates the current: 1. System maintenance policy [Assignment: organization-defined frequency]; and 2. System maintenance procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the MA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-2 | FedRAMP_Moderate_R4_MA-2 | FedRAMP Moderate MA-2 | Maintenance | Controlled Maintenance | Shared | n/a | The organization: a. Schedules, performs, documents, and reviews records of maintenance and repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements; b. Approves and monitors all maintenance activities, whether performed on site or remotely and whether the equipment is serviced on site or removed to another location; c. Requires that [Assignment: organization-defined personnel or roles] explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs; d. Sanitizes equipment to remove all information from associated media prior to removal from organizational facilities for off-site maintenance or repairs; e. Checks all potentially impacted security controls to verify that the controls are still functioning properly following maintenance or repair actions; and f. Includes [Assignment: organization-defined maintenance-related information] in organizational maintenance records. Supplemental Guidance: This control addresses the information security aspects of the information system maintenance program and applies to all types of maintenance to any system component (including applications) conducted by any local or nonlocal entity (e.g., in-contract, warranty, in- house, software maintenance agreement). System maintenance also includes those components not directly associated with information processing and/or data/information retention such as scanners, copiers, and printers. Information necessary for creating effective maintenance records includes, for example: (i) date and time of maintenance; (ii) name of individuals or group performing the maintenance; (iii) name of escort, if necessary; (iv) a description of the maintenance performed; and (v) information system components/equipment removed or replaced (including identification numbers, if applicable). The level of detail included in maintenance records can be informed by the security categories of organizational information systems. Organizations consider supply chain issues associated with replacement components for information systems. Related controls: CM-3, CM-4, MA-4, MP-6, PE-16, SA-12, SI-2. References: None. | link | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-3 | FedRAMP_Moderate_R4_MA-3 | FedRAMP Moderate MA-3 | Maintenance | Maintenance Tools | Shared | n/a | The organization approves, controls, and monitors information system maintenance tools. Supplemental Guidance: This control addresses security-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems. Maintenance tools can include hardware, software, and firmware items. Maintenance tools are potential vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and subsequently into organizational information systems. Maintenance tools can include, for example, hardware/software diagnostic test equipment and hardware/software packet sniffers. This control does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing “ping,” “ls,” “ipconfig,” or the hardware and software implementing the monitoring port of an Ethernet switch. Related controls: MA-2, MA-5, MP-6. References: NIST Special Publication 800-88. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-3(1) | FedRAMP_Moderate_R4_MA-3(1) | FedRAMP Moderate MA-3 (1) | Maintenance | Inspect Tools | Shared | n/a | The organization inspects the maintenance tools carried into a facility by maintenance personnel for improper or unauthorized modifications. Supplemental Guidance: If, upon inspection of maintenance tools, organizations determine that the tools have been modified in an improper/unauthorized manner or contain malicious code, the incident is handled consistent with organizational policies and procedures for incident handling. Related control: SI-7. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-3(2) | FedRAMP_Moderate_R4_MA-3(2) | FedRAMP Moderate MA-3 (2) | Maintenance | Inspect Media | Shared | n/a | The organization checks media containing diagnostic and test programs for malicious code before the media are used in the information system. Supplemental Guidance: If, upon inspection of media containing maintenance diagnostic and test programs, organizations determine that the media contain malicious code, the incident is handled consistent with organizational incident handling policies and procedures. Related control: SI-3. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-3(3) | FedRAMP_Moderate_R4_MA-3(3) | FedRAMP Moderate MA-3 (3) | Maintenance | Prevent Unauthorized Removal | Shared | n/a | The organization prevents the unauthorized removal of maintenance equipment containing organizational information by: (a) Verifying that there is no organizational information contained on the equipment; (b) Sanitizing or destroying the equipment; (c) Retaining the equipment within the facility; or (d) Obtaining an exemption from [Assignment: organization-defined personnel or roles] explicitly authorizing removal of the equipment from the facility. Supplemental Guidance: Organizational information includes all information specifically owned by organizations and information provided to organizations in which organizations serve as information stewards. | link | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-4 | FedRAMP_Moderate_R4_MA-4 | FedRAMP Moderate MA-4 | Maintenance | Nonlocal Maintenance | Shared | n/a | The organization: a. Approves and monitors nonlocal maintenance and diagnostic activities; b. Allows the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the information system; c. Employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions; d. Maintains records for nonlocal maintenance and diagnostic activities; and e. Terminates session and network connections when nonlocal maintenance is completed. Supplemental Guidance: Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Authentication techniques used in the establishment of nonlocal maintenance and diagnostic sessions reflect the network access requirements in IA-2. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric. Enforcing requirements in MA-4 is accomplished in part by other controls. Related controls: AC-2, AC-3, AC-6, AC-17, AU-2, AU-3, IA-2, IA-4, IA-5, IA-8, MA-2, MA-5, MP-6, PL-2, SC-7, SC-10, SC-17. References: FIPS Publications 140-2, 197, 201; NIST Special Publications 800-63, 800-88; CNSS Policy 15. | link | count: 001 Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-4(2) | FedRAMP_Moderate_R4_MA-4(2) | FedRAMP Moderate MA-4 (2) | Maintenance | Document Nonlocal Maintenance | Shared | n/a | The organization documents in the security plan for the information system, the policies and procedures for the establishment and use of nonlocal maintenance and diagnostic connections. | link | count: 001 Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-5 | FedRAMP_Moderate_R4_MA-5 | FedRAMP Moderate MA-5 | Maintenance | Maintenance Personnel | Shared | n/a | The organization: a. Establishes a process for maintenance personnel authorization and maintains a list of authorized maintenance organizations or personnel; b. Ensures that non-escorted personnel performing maintenance on the information system have required access authorizations; and c. Designates organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations. Supplemental Guidance: This control applies to individuals performing hardware or software maintenance on organizational information systems, while PE-2 addresses physical access for individuals whose maintenance duties place them within the physical protection perimeter of the systems (e.g., custodial staff, physical plant maintenance personnel). Technical competence of supervising individuals relates to the maintenance performed on the information systems while having required access authorizations refers to maintenance on and near the systems. Individuals not previously identified as authorized maintenance personnel, such as information technology manufacturers, vendors, systems integrators, and consultants, may require privileged access to organizational information systems, for example, when required to conduct maintenance activities with little or no notice. Based on organizational assessments of risk, organizations may issue temporary credentials to these individuals. Temporary credentials may be for one-time use or for very limited time periods. Related controls: AC-2, IA-8, MP-2, PE-2, PE-3, PE-4, RA-3. References: None. | link | count: 003 Designate personnel to supervise unauthorized maintenance activities (7a489c62-242c-5db9-74df-c073056d6fa3), Maintain list of authorized remote maintenance personnel (4ce91e4e-6dab-3c46-011a-aa14ae1561bf), Manage maintenance personnel (b273f1e3-79e7-13ee-5b5d-dca6c66c3d5d) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-5(1) | FedRAMP_Moderate_R4_MA-5(1) | FedRAMP Moderate MA-5 (1) | Maintenance | Individuals Without Appropriate Access | Shared | n/a | The organization: (a) Implements procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements: (1) Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the information system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified; (2) Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the information system are sanitized and all nonvolatile storage media are removed or physically disconnected from the system and secured; and (b) Develops and implements alternate security safeguards in the event an information system component cannot be sanitized, removed, or disconnected from the system. Supplemental Guidance: This control enhancement denies individuals who lack appropriate security clearances (i.e., individuals who do not possess security clearances or possess security clearances at a lower level than required) or who are not U.S. citizens, visual and electronic access to any classified information, Controlled Unclassified Information (CUI), or any other sensitive information contained on organizational information systems. Procedures for the use of maintenance personnel can be documented in security plans for the information systems. Related controls: MP-6, PL-2. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MA-6 | FedRAMP_Moderate_R4_MA-6 | FedRAMP Moderate MA-6 | Maintenance | Timely Maintenance | Shared | n/a | The organization obtains maintenance support and/or spare parts for [Assignment: organization-defined information system components] within [Assignment: organization-defined time period] of failure. Supplemental Guidance: Organizations specify the information system components that result in increased risk to organizational operations and assets, individuals, other organizations, or the Nation when the functionality provided by those components is not operational. Organizational actions to obtain maintenance support typically include having appropriate contracts in place. Related controls: CM-8, CP-2, CP-7, SA-14, SA-15. References: None. | link | count: 001 Provide timely maintenance support (eb598832-4bcc-658d-4381-3ecbe17b9866) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-1 | FedRAMP_Moderate_R4_MP-1 | FedRAMP Moderate MP-1 | Media Protection | Media Protection Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A media protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the media protection policy and associated media protection controls; and b. Reviews and updates the current: 1. Media protection policy [Assignment: organization-defined frequency]; and 2. Media protection procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the MP family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-2 | FedRAMP_Moderate_R4_MP-2 | FedRAMP Moderate MP-2 | Media Protection | Media Access | Shared | n/a | The organization restricts access to [Assignment: organization-defined types of digital and/or non-digital media] to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Restricting non-digital media access includes, for example, denying access to patient medical records in a community hospital unless the individuals seeking access to such records are authorized healthcare providers. Restricting access to digital media includes, for example, limiting access to design specifications stored on compact disks in the media library to the project leader and the individuals on the development team. Related controls: AC-3, IA-2, MP-4, PE-2, PE-3, PL-2. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-3 | FedRAMP_Moderate_R4_MP-3 | FedRAMP Moderate MP-3 | Media Protection | Media Marking | Shared | n/a | The organization: a. Marks information system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and b. Exempts [Assignment: organization-defined types of information system media] from marking as long as the media remain within [Assignment: organization-defined controlled areas]. Supplemental Guidance: The term security marking refers to the application/use of human-readable security attributes. The term security labeling refers to the application/use of security attributes with regard to internal data structures within information systems (see AC-16). Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Security marking is generally not required for media containing information determined by organizations to be in the public domain or to be publicly releasable. However, some organizations may require markings for public information indicating that the information is publicly releasable. Marking of information system media reflects applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Related controls: AC-16, PL-2, RA-3. Control Enhancements: None. References: FIPS Publication 199. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-4 | FedRAMP_Moderate_R4_MP-4 | FedRAMP Moderate MP-4 | Media Protection | Media Storage | Shared | n/a | The organization: a. Physically controls and securely stores [Assignment: organization-defined types of digital and/or non-digital media] within [Assignment: organization-defined controlled areas]; and b. Protects information system media until the media are destroyed or sanitized using approved equipment, techniques, and procedures. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Physically controlling information system media includes, for example, conducting inventories, ensuring procedures are in place to allow individuals to check out and return media to the media library, and maintaining accountability for all stored media. Secure storage includes, for example, a locked drawer, desk, or cabinet, or a controlled media library. The type of media storage is commensurate with the security category and/or classification of the information residing on the media. Controlled areas are areas for which organizations provide sufficient physical and procedural safeguards to meet the requirements established for protecting information and/or information systems. For media containing information determined by organizations to be in the public domain, to be publicly releasable, or to have limited or no adverse impact on organizations or individuals if accessed by other than authorized personnel, fewer safeguards may be needed. In these situations, physical access controls provide adequate protection. Related controls: CP-6, CP-9, MP-2, MP-7, PE-3. References: FIPS Publication 199; NIST Special Publications 800-56, 800-57, 800-111. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-5 | FedRAMP_Moderate_R4_MP-5 | FedRAMP Moderate MP-5 | Media Protection | Media Transport | Shared | n/a | The organization: a. Protects and controls [Assignment: organization-defined types of information system media] during transport outside of controlled areas using [Assignment: organization-defined security safeguards]; b. Maintains accountability for information system media during transport outside of controlled areas; c. Documents activities associated with the transport of information system media; and d. Restricts the activities associated with the transport of information system media to authorized personnel. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. This control also applies to mobile devices with information storage capability (e.g., smart phones, tablets, E-readers), that are transported outside of controlled areas. Controlled areas are areas or spaces for which organizations provide sufficient physical and/or procedural safeguards to meet the requirements established for protecting information and/or information systems. Physical and technical safeguards for media are commensurate with the security category or classification of the information residing on the media. Safeguards to protect media during transport include, for example, locked containers and cryptography. Cryptographic mechanisms can provide confidentiality and integrity protections depending upon the mechanisms used. Activities associated with transport include the actual transport as well as those activities such as releasing media for transport and ensuring that media enters the appropriate transport processes. For the actual transport, authorized transport and courier personnel may include individuals from outside the organization (e.g., U.S. Postal Service or a commercial transport or delivery service). Maintaining accountability of media during transport includes, for example, restricting transport activities to authorized personnel, and tracking and/or obtaining explicit records of transport activities as the media moves through the transportation system to prevent and detect loss, destruction, or tampering. Organizations establish documentation requirements for activities associated with the transport of information system media in accordance with organizational assessments of risk to include the flexibility to define different record-keeping methods for the different types of media transport as part of an overall system of transport-related records. Related controls: AC-19, CP-9, MP-3, MP-4, RA-3, SC-8, SC-13, SC-28. References: FIPS Publication 199; NIST Special Publication 800-60. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-5(4) | FedRAMP_Moderate_R4_MP-5(4) | FedRAMP Moderate MP-5 (4) | Media Protection | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to protect the confidentiality and integrity of information stored on digital media during transport outside of controlled areas. Supplemental Guidance: This control enhancement applies to both portable storage devices (e.g., USB memory sticks, compact disks, digital video disks, external/removable hard disk drives) and mobile devices with storage capability (e.g., smart phones, tablets, E-readers). Related control: MP-2. References: FIPS Publication 199; NIST Special Publication 800-60. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-6 | FedRAMP_Moderate_R4_MP-6 | FedRAMP Moderate MP-6 | Media Protection | Media Sanitization | Shared | n/a | The organization: a. Sanitizes [Assignment: organization-defined information system media] prior to disposal, release out of organizational control, or release for reuse using [Assignment: organization- defined sanitization techniques and procedures] in accordance with applicable federal and organizational standards and policies; and b. Employs sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information. Supplemental Guidance: This control applies to all information system media, both digital and non- digital, subject to disposal or reuse, whether or not the media is considered removable. Examples include media found in scanners, copiers, printers, notebook computers, workstations, network components, and mobile devices. The sanitization process removes information from the media such that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, cryptographic erase, and destruction, prevent the disclosure of information to unauthorized individuals when such media is reused or released for disposal. Organizations determine the appropriate sanitization methods recognizing that destruction is sometimes necessary when other methods cannot be applied to media requiring sanitization. Organizations use discretion on the employment of approved sanitization techniques and procedures for media containing information deemed to be in the public domain or publicly releasable, or deemed to have no adverse impact on organizations or individuals if released for reuse or disposal. Sanitization of non-digital media includes, for example, removing a classified appendix from an otherwise unclassified document, or redacting selected sections or words from a document by obscuring the redacted sections/words in a manner equivalent in effectiveness to removing them from the document. NSA standards and policies control the sanitization process for media containing classified information. Related controls: MA-2, MA-4, RA-3, SC-4. References: FIPS Publication 199; NIST Special Publications 800-60, 800-88; Web: http://www.nsa.gov/ia/mitigation_guidance/media_destruction_guidance/index.shtml. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-6(2) | FedRAMP_Moderate_R4_MP-6(2) | FedRAMP Moderate MP-6 (2) | Media Protection | Equipment Testing | Shared | n/a | The organization tests sanitization equipment and procedures [Assignment: organization-defined frequency] to verify that the intended sanitization is being achieved. Supplemental Guidance: Testing of sanitization equipment and procedures may be conducted by qualified and authorized external entities (e.g., other federal agencies or external service providers). | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-7 | FedRAMP_Moderate_R4_MP-7 | FedRAMP Moderate MP-7 | Media Protection | Media Use | Shared | n/a | The organization [Selection: restricts; prohibits] the use of [Assignment: organization- defined types of information system media] on [Assignment: organization-defined information systems or system components] using [Assignment: organization-defined security safeguards]. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. This control also applies to mobile devices with information storage capability (e.g., smart phones, tablets, E-readers). In contrast to MP-2, which restricts user access to media, this control restricts the use of certain types of media on information systems, for example, restricting/prohibiting the use of flash drives or external hard disk drives. Organizations can employ technical and nontechnical safeguards (e.g., policies, procedures, rules of behavior) to restrict the use of information system media. Organizations may restrict the use of portable storage devices, for example, by using physical cages on workstations to prohibit access to certain external ports, or disabling/removing the ability to insert, read or write to such devices. Organizations may also limit the use of portable storage devices to only approved devices including, for example, devices provided by the organization, devices provided by other approved organizations, and devices that are not personally owned. Finally, organizations may restrict the use of portable storage devices based on the type of device, for example, prohibiting the use of writeable, portable storage devices, and implementing this restriction by disabling or removing the capability to write to such devices. Related controls: AC-19, PL-4. References: None. | link | count: 004 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | MP-7(1) | FedRAMP_Moderate_R4_MP-7(1) | FedRAMP Moderate MP-7 (1) | Media Protection | Prohibit Use Without Owner | Shared | n/a | The organization prohibits the use of portable storage devices in organizational information systems when such devices have no identifiable owner. Supplemental Guidance: Requiring identifiable owners (e.g., individuals, organizations, or projects) for portable storage devices reduces the risk of using such technologies by allowing organizations to assign responsibility and accountability for addressing known vulnerabilities in the devices (e.g., malicious code insertion). Related control: PL-4. | link | count: 004 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-1 | FedRAMP_Moderate_R4_PE-1 | FedRAMP Moderate PE-1 | Physical And Environmental Protection | Physical And Environmental Protection Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A physical and environmental protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls; and b. Reviews and updates the current: 1. Physical and environmental protection policy [Assignment: organization-defined frequency]; and 2. Physical and environmental protection procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PE family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-12 | FedRAMP_Moderate_R4_PE-12 | FedRAMP Moderate PE-12 | Physical And Environmental Protection | Emergency Lighting | Shared | n/a | The organization employs and maintains automatic emergency lighting for the information system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Related controls: CP-2, CP-7. References: None. | link | count: 001 Employ automatic emergency lighting (aa892c0d-2c40-200c-0dd8-eac8c4748ede) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-13 | FedRAMP_Moderate_R4_PE-13 | FedRAMP Moderate PE-13 | Physical And Environmental Protection | Fire Protection | Shared | n/a | The organization employs and maintains fire suppression and detection devices/systems for the information system that are supported by an independent energy source. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Fire suppression and detection devices/systems include, for example, sprinkler systems, handheld fire extinguishers, fixed fire hoses, and smoke detectors. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-13(2) | FedRAMP_Moderate_R4_PE-13(2) | FedRAMP Moderate PE-13 (2) | Physical And Environmental Protection | Suppression Devices / Systems | Shared | n/a | The organization employs fire suppression devices/systems for the information system that provide automatic notification of any activation to Assignment: organization-defined personnel or roles] and [Assignment: organization-defined emergency responders]. Supplemental Guidance: Organizations can identify specific personnel, roles, and emergency responders in the event that individuals on the notification list must have appropriate access authorizations and/or clearances, for example, to obtain access to facilities where classified operations are taking place or where there are information systems containing classified information. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-13(3) | FedRAMP_Moderate_R4_PE-13(3) | FedRAMP Moderate PE-13 (3) | Physical And Environmental Protection | Automatic Fire Suppression | Shared | n/a | The organization employs an automatic fire suppression capability for the information system when the facility is not staffed on a continuous basis. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-14 | FedRAMP_Moderate_R4_PE-14 | FedRAMP Moderate PE-14 | Physical And Environmental Protection | Temperature And Humidity Controls | Shared | n/a | The organization: a. Maintains temperature and humidity levels within the facility where the information system resides at [Assignment: organization-defined acceptable levels]; and b. Monitors temperature and humidity levels [Assignment: organization-defined frequency]. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources, for example, data centers, server rooms, and mainframe computer rooms. Related control: AT-3. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-14(2) | FedRAMP_Moderate_R4_PE-14(2) | FedRAMP Moderate PE-14 (2) | Physical And Environmental Protection | Monitoring With Alarms / Notifications | Shared | n/a | The organization employs temperature and humidity monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment. | link | count: 002 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-15 | FedRAMP_Moderate_R4_PE-15 | FedRAMP Moderate PE-15 | Physical And Environmental Protection | Water Damage Protection | Shared | n/a | The organization protects the information system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible, working properly, and known to key personnel. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Isolation valves can be employed in addition to or in lieu of master shutoff valves to shut off water supplies in specific areas of concern, without affecting entire organizations. Related control: AT-3. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-16 | FedRAMP_Moderate_R4_PE-16 | FedRAMP Moderate PE-16 | Physical And Environmental Protection | Delivery And Removal | Shared | n/a | The organization authorizes, monitors, and controls [Assignment: organization-defined types of information system components] entering and exiting the facility and maintains records of those items. Supplemental Guidance: Effectively enforcing authorizations for entry and exit of information system components may require restricting access to delivery areas and possibly isolating the areas from the information system and media libraries. Related controls: CM-3, MA-2, MA-3, MP-5, SA-12. References: None. | link | count: 002 Define requirements for managing assets (25a1f840-65d0-900a-43e4-bee253de04de), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-17 | FedRAMP_Moderate_R4_PE-17 | FedRAMP Moderate PE-17 | Physical And Environmental Protection | Alternate Work Site | Shared | n/a | The organization: a. Employs [Assignment: organization-defined security controls] at alternate work sites; b. Assesses as feasible, the effectiveness of security controls at alternate work sites; and c. Provides a means for employees to communicate with information security personnel in case of security incidents or problems. Supplemental Guidance: Alternate work sites may include, for example, government facilities or private residences of employees. While commonly distinct from alternative processing sites, alternate work sites may provide readily available alternate locations as part of contingency operations. Organizations may define different sets of security controls for specific alternate work sites or types of sites depending on the work-related activities conducted at those sites. This control supports the contingency planning activities of organizations and the federal telework initiative. Related controls: AC-17, CP-7. Control Enhancements: None. References: NIST Special Publication 800-46. | link | count: 001 Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-2 | FedRAMP_Moderate_R4_PE-2 | FedRAMP Moderate PE-2 | Physical And Environmental Protection | Physical Access Authorizations | Shared | n/a | The organization: a. Develops, approves, and maintains a list of individuals with authorized access to the facility where the information system resides; b. Issues authorization credentials for facility access; c. Reviews the access list detailing authorized facility access by individuals [Assignment: organization-defined frequency]; and d. Removes individuals from the facility access list when access is no longer required. Supplemental Guidance: This control applies to organizational employees and visitors. Individuals (e.g., employees, contractors, and others) with permanent physical access authorization credentials are not considered visitors. Authorization credentials include, for example, badges, identification cards, and smart cards. Organizations determine the strength of authorization credentials needed (including level of forge-proof badges, smart cards, or identification cards) consistent with federal standards, policies, and procedures. This control only applies to areas within facilities that have not been designated as publicly accessible. Related controls: PE-3, PE-4, PS-3. References: None | link | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-3 | FedRAMP_Moderate_R4_PE-3 | FedRAMP Moderate PE-3 | Physical And Environmental Protection | Physical Access Control | Shared | n/a | The organization: a. Enforces physical access authorizations at [Assignment: organization-defined entry/exit points to the facility where the information system resides] by; 1. Verifying individual access authorizations before granting access to the facility; and 2. Controlling ingress/egress to the facility using [Selection (one or more): [Assignment: organization-defined physical access control systems/devices]; guards]; b. Maintains physical access audit logs for [Assignment: organization-defined entry/exit points]; c. Provides [Assignment: organization-defined security safeguards] to control access to areas within the facility officially designated as publicly accessible; d. Escorts visitors and monitors visitor activity [Assignment: organization-defined circumstances requiring visitor escorts and monitoring]; e. Secures keys, combinations, and other physical access devices; f. Inventories [Assignment: organization-defined physical access devices] every [Assignment: organization-defined frequency]; and g. Changes combinations and keys [Assignment: organization-defined frequency] and/or when keys are lost, combinations are compromised, or individuals are transferred or terminated. Supplemental Guidance: This control applies to organizational employees and visitors. Individuals (e.g., employees, contractors, and others) with permanent physical access authorization credentials are not considered visitors. Organizations determine the types of facility guards needed including, for example, professional physical security staff or other personnel such as administrative staff or information system users. Physical access devices include, for example, keys, locks, combinations, and card readers. Safeguards for publicly accessible areas within organizational facilities include, for example, cameras, monitoring by guards, and isolating selected information systems and/or system components in secured areas. Physical access control systems comply with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The Federal Identity, Credential, and Access Management Program provides implementation guidance for identity, credential, and access management capabilities for physical access control systems. Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural (e.g., a written log of individuals accessing the facility and when such access occurred), automated (e.g., capturing ID provided by a PIV card), or some combination thereof. Physical access points can include facility access points, interior access points to information systems and/or components requiring supplemental access controls, or both. Components of organizational information systems (e.g., workstations, terminals) may be located in areas designated as publicly accessible with organizations safeguarding access to such devices. Related controls: AU-2, AU-6, MP-2, MP-4, PE-2, PE-4, PE-5, PS-3, RA-3. Supplemental Guidance: Related controls: CA-2, CA-7. | link | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-4 | FedRAMP_Moderate_R4_PE-4 | FedRAMP Moderate PE-4 | Physical And Environmental Protection | Access Control For Transmission Medium | Shared | n/a | The organization controls physical access to [Assignment: organization-defined information system distribution and transmission lines] within organizational facilities using [Assignment: organization-defined security safeguards]. Supplemental Guidance: Physical security safeguards applied to information system distribution and transmission lines help to prevent accidental damage, disruption, and physical tampering. In addition, physical safeguards may be necessary to help prevent eavesdropping or in transit modification of unencrypted transmissions. Security safeguards to control physical access to system distribution and transmission lines include, for example: (i) locked wiring closets; (ii) disconnected or locked spare jacks; and/or (iii) protection of cabling by conduit or cable trays. Related controls: MP-2, MP-4, PE-2, PE-3, PE-5, SC-7, SC-8. Control Enhancements: None. References: NSTISSI No. 7003. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-5 | FedRAMP_Moderate_R4_PE-5 | FedRAMP Moderate PE-5 | Physical And Environmental Protection | Access Control For Output Devices | Shared | n/a | The organization controls physical access to information system output devices to prevent unauthorized individuals from obtaining the output. Supplemental Guidance: Controlling physical access to output devices includes, for example, placing output devices in locked rooms or other secured areas and allowing access to authorized individuals only, and placing output devices in locations that can be monitored by organizational personnel. Monitors, printers, copiers, scanners, facsimile machines, and audio devices are examples of information system output devices. Related controls: PE-2, PE-3, PE-4, PE-18. References: None. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-6(1) | FedRAMP_Moderate_R4_PE-6(1) | FedRAMP Moderate PE-6 (1) | Physical And Environmental Protection | Intrusion Alarms / Surveillance Equipment | Shared | n/a | The organization monitors physical intrusion alarms and surveillance equipment. | link | count: 002 Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PE-8 | FedRAMP_Moderate_R4_PE-8 | FedRAMP Moderate PE-8 | Physical And Environmental Protection | Visitor Access Records | Shared | n/a | The organization: a. Maintains visitor access records to the facility where the information system resides for [Assignment: organization-defined time period]; and b. Reviews visitor access records [Assignment: organization-defined frequency]. Supplemental Guidance: Visitor access records include, for example, names and organizations of persons visiting, visitor signatures, forms of identification, dates of access, entry and departure times, purposes of visits, and names and organizations of persons visited. Visitor access records are not required for publicly accessible areas. References: None. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PL-1 | FedRAMP_Moderate_R4_PL-1 | FedRAMP Moderate PL-1 | Planning | Security Planning Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A security planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the security planning policy and associated security planning controls; and b. Reviews and updates the current: 1. Security planning policy [Assignment: organization-defined frequency]; and 2. Security planning procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PL family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-18, 800-100. | link | count: 001 Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PL-2 | FedRAMP_Moderate_R4_PL-2 | FedRAMP Moderate PL-2 | Planning | System Security Plan | Shared | n/a | The organization: a. Develops a security plan for the information system that: 1. Is consistent with the organization’s enterprise architecture; 2. Explicitly defines the authorization boundary for the system; 3. Describes the operational context of the information system in terms of missions and business processes; 4. Provides the security categorization of the information system including supporting rationale; 5. Describes the operational environment for the information system and relationships with or connections to other information systems; 6. Provides an overview of the security requirements for the system; 7. Identifies any relevant overlays, if applicable; 8. Describes the security controls in place or planned for meeting those requirements including a rationale for the tailoring and supplementation decisions; and 9. Is reviewed and approved by the authorizing official or designated representative prior to plan implementation; b. Distributes copies of the security plan and communicates subsequent changes to the plan to [Assignment: organization-defined personnel or roles]; c. Reviews the security plan for the information system [Assignment: organization-defined frequency]; d. Updates the plan to address changes to the information system/environment of operation or problems identified during plan implementation or security control assessments; and e. Protects the security plan from unauthorized disclosure and modification. Supplemental Guidance: Security plans relate security requirements to a set of security controls and control enhancements. Security plans also describe, at a high level, how the security controls and control enhancements meet those security requirements, but do not provide detailed, technical descriptions of the specific design or implementation of the controls/enhancements. Security plans contain sufficient information (including the specification of parameter values for assignment and selection statements either explicitly or by reference) to enable a design and implementation that is unambiguously compliant with the intent of the plans and subsequent determinations of risk to organizational operations and assets, individuals, other organizations, and the Nation if the plan is implemented as intended. Organizations can also apply tailoring guidance to the security control baselines in Appendix D and CNSS Instruction 1253 to develop overlays for community-wide use or to address specialized requirements, technologies, or missions/environments of operation (e.g., DoD-tactical, Federal Public Key Infrastructure, or Federal Identity, Credential, and Access Management, space operations). Appendix I provides guidance on developing overlays. Security plans need not be single documents; the plans can be a collection of various documents including documents that already exist. Effective security plans make extensive use of references to policies, procedures, and additional documents (e.g., design and implementation specifications) where more detailed information can be obtained. This reduces the documentation requirements associated with security programs and maintains security-related information in other established management/operational areas related to enterprise architecture, system development life cycle, systems engineering, and acquisition. For example, security plans do not contain detailed contingency plan or incident response plan information but instead provide explicitly or by reference, sufficient information to define what needs to be accomplished by those plans. Related controls: AC-2, AC-6, AC-14, AC-17, AC-20, CA-2, CA-3, CA-7, CM-9, CP-2, IR-8, MA-4, MA-5, MP-2, MP-4, MP-5, PL-7, PM-1, PM-7, PM-8, PM-9, PM-11, SA-5, SA-17. References: NIST Special Publication 800-18. | link | count: 006 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PL-2(3) | FedRAMP_Moderate_R4_PL-2(3) | FedRAMP Moderate PL-2 (3) | Planning | Plan / Coordinate With Other Organizational Entities | Shared | n/a | The organization plans and coordinates security-related activities affecting the information system with [Assignment: organization-defined individuals or groups] before conducting such activities in order to reduce the impact on other organizational entities. Supplemental Guidance: Security-related activities include, for example, security assessments, audits, hardware and software maintenance, patch management, and contingency plan testing. Advance planning and coordination includes emergency and nonemergency (i.e., planned or nonurgent unplanned) situations. The process defined by organizations to plan and coordinate security-related activities can be included in security plans for information systems or other documents, as appropriate. Related controls: CP-4, IR-4. | link | count: 003 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PL-4 | FedRAMP_Moderate_R4_PL-4 | FedRAMP Moderate PL-4 | Planning | Rules Of Behavior | Shared | n/a | The organization: a. Establishes and makes readily available to individuals requiring access to the information system, the rules that describe their responsibilities and expected behavior with regard to information and information system usage; b. Receives a signed acknowledgment from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the information system; c. Reviews and updates the rules of behavior [Assignment: organization-defined frequency]; and d. Requires individuals who have signed a previous version of the rules of behavior to read and resign when the rules of behavior are revised/updated. Supplemental Guidance: This control enhancement applies to organizational users. Organizations consider rules of behavior based on individual user roles and responsibilities, differentiating, for example, between rules that apply to privileged users and rules that apply to general users. Establishing rules of behavior for some types of non-organizational users including, for example, individuals who simply receive data/information from federal information systems, is often not feasible given the large number of such users and the limited nature of their interactions with the systems. Rules of behavior for both organizational and non-organizational users can also be established in AC-8, System Use Notification. PL-4 b. (the signed acknowledgment portion of this control) may be satisfied by the security awareness training and role-based security training programs conducted by organizations if such training includes rules of behavior. Organizations can use electronic signatures for acknowledging rules of behavior. Related controls: AC-2, AC-6, AC-8, AC-9, AC-17, AC-18, AC-19, AC-20, AT-2, AT-3, CM-11, IA-2, IA-4, IA-5, MP-7, PS-6, PS-8, SA-5. References: NIST Special Publication 800-18. | link | count: 009 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PL-4(1) | FedRAMP_Moderate_R4_PL-4(1) | FedRAMP Moderate PL-4 (1) | Planning | Social Media And Networking Restrictions | Shared | n/a | The organization includes in the rules of behavior, explicit restrictions on the use of social media/networking sites and posting organizational information on public websites. Supplemental Guidance: This control enhancement addresses rules of behavior related to the use of social media/networking sites: (i) when organizational personnel are using such sites for official duties or in the conduct of official business; (ii) when organizational information is involved in social media/networking transactions; and (iii) when personnel are accessing social media/networking sites from organizational information systems. Organizations also address specific rules that prevent unauthorized entities from obtaining and/or inferring non- public organizational information (e.g., system account information, personally identifiable information) from social media/networking sites. | link | count: 001 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PL-8 | FedRAMP_Moderate_R4_PL-8 | FedRAMP Moderate PL-8 | Planning | Information Security Architecture | Shared | n/a | The organization: a. Develops an information security architecture for the information system that: 1. Describes the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information; 2. Describes how the information security architecture is integrated into and supports the enterprise architecture; and 3. Describes any information security assumptions about, and dependencies on, external services; b. Reviews and updates the information security architecture [Assignment: organization-defined frequency] to reflect updates in the enterprise architecture; and c. Ensures that planned information security architecture changes are reflected in the security plan, the security Concept of Operations (CONOPS), and organizational procurements/acquisitions. Supplemental Guidance: This control addresses actions taken by organizations in the design and development of information systems. The information security architecture at the individual information system level is consistent with and complements the more global, organization-wide information security architecture described in PM-7 that is integral to and developed as part of the enterprise architecture. The information security architecture includes an architectural description, the placement/allocation of security functionality (including security controls), security-related information for external interfaces, information being exchanged across the interfaces, and the protection mechanisms associated with each interface. In addition, the security architecture can include other important security-related information, for example, user roles and access privileges assigned to each role, unique security requirements, the types of information processed, stored, and transmitted by the information system, restoration priorities of information and information system services, and any other specific protection needs. In today’s modern architecture, it is becoming less common for organizations to control all information resources. There are going to be key dependencies on external information services and service providers. Describing such dependencies in the information security architecture is important to developing a comprehensive mission/business protection strategy. Establishing, developing, documenting, and maintaining under configuration control, a baseline configuration for organizational information systems is critical to implementing and maintaining an effective information security architecture. The development of the information security architecture is coordinated with the Senior Agency Official for Privacy (SAOP)/Chief Privacy Officer (CPO) to ensure that security controls needed to support privacy requirements are identified and effectively implemented. PL-8 is primarily directed at organizations (i.e., internally focused) to help ensure that organizations develop an information security architecture for the information system, and that the security architecture is integrated with or tightly coupled to the enterprise architecture through the organization-wide information security architecture. In contrast, SA-17 is primarily directed at external information technology product/system developers and integrators (although SA-17 could be used internally within organizations for in-house system development). SA-17, which is complementary to PL-8, is selected when organizations outsource the development of information systems or information system components to external entities, and there is a need to demonstrate/show consistency with the organization’s enterprise architecture and information security architecture. Related controls: CM-2, CM-6, PL-2, PM-7, SA-5, SA-17, Appendix J. References: None. | link | count: 002 Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PS-1 | FedRAMP_Moderate_R4_PS-1 | FedRAMP Moderate PS-1 | Personnel Security | Personnel Security Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A personnel security policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the personnel security policy and associated personnel security controls; and b. Reviews and updates the current: 1. Personnel security policy [Assignment: organization-defined frequency]; and 2. Personnel security procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PS family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PS-2 | FedRAMP_Moderate_R4_PS-2 | FedRAMP Moderate PS-2 | Personnel Security | Position Risk Designation | Shared | n/a | The organization: a. Assigns a risk designation to all organizational positions; b. Establishes screening criteria for individuals filling those positions; and c. Reviews and updates position risk designations [Assignment: organization-defined frequency]. Supplemental Guidance: Position risk designations reflect Office of Personnel Management policy and guidance. Risk designations can guide and inform the types of authorizations individuals receive when accessing organizational information and information systems. Position screening criteria include explicit information security role appointment requirements (e.g., training, security clearances). Related controls: AT-3, PL-2, PS-3. Control Enhancements: None. References: 5 C.F.R. 731.106(a). | link | count: 001 Assign risk designations (b7897ddc-9716-2460-96f7-7757ad038cc4) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PS-3 | FedRAMP_Moderate_R4_PS-3 | FedRAMP Moderate PS-3 | Personnel Security | Personnel Screening | Shared | n/a | The organization: a. Screens individuals prior to authorizing access to the information system; and b. Rescreens individuals according to [Assignment: organization-defined conditions requiring rescreening and, where rescreening is so indicated, the frequency of such rescreening]. Supplemental Guidance: Personnel screening and rescreening activities reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, guidance, and specific criteria established for the risk designations of assigned positions. Organizations may define different rescreening conditions and frequencies for personnel accessing information systems based on types of information processed, stored, or transmitted by the systems. Related controls: AC-2, IA-4, PE-2, PS-2. References: 5 C.F.R. 731.106; FIPS Publications 199, 201; NIST Special Publications 800-60, 800-73, 800-76, 800-78; ICD 704. | link | count: 003 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Rescreen individuals at a defined frequency (c6aeb800-0b19-944d-92dc-59b893722329) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PS-3(3) | FedRAMP_Moderate_R4_PS-3(3) | FedRAMP Moderate PS-3 (3) | Personnel Security | Information With Special Protection Measures | Shared | n/a | The organization ensures that individuals accessing an information system processing, storing, or transmitting information requiring special protection: (a) Have valid access authorizations that are demonstrated by assigned official government duties; and (b) Satisfy [Assignment: organization-defined additional personnel screening criteria]. Supplemental Guidance: Organizational information requiring special protection includes, for example, Controlled Unclassified Information (CUI) and Sources and Methods Information (SAMI). Personnel security criteria include, for example, position sensitivity background screening requirements. | link | count: 001 Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PS-4 | FedRAMP_Moderate_R4_PS-4 | FedRAMP Moderate PS-4 | Personnel Security | Personnel Termination | Shared | n/a | The organization, upon termination of individual employment: a. Disables information system access within [Assignment: organization-defined time period]; b. Terminates/revokes any authenticators/credentials associated with the individual; c. Conducts exit interviews that include a discussion of [Assignment: organization-defined information security topics]; d. Retrieves all security-related organizational information system-related property; e. Retains access to organizational information and information systems formerly controlled by terminated individual; and f. Notifies [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period]. Supplemental Guidance: Information system-related property includes, for example, hardware authentication tokens, system administration technical manuals, keys, identification cards, and building passes. Exit interviews ensure that terminated individuals understand the security constraints imposed by being former employees and that proper accountability is achieved for information system-related property. Security topics of interest at exit interviews can include, for example, reminding terminated individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not be possible for some terminated individuals, for example, in cases related to job abandonment, illnesses, and nonavailability of supervisors. Exit interviews are important for individuals with security clearances. Timely execution of termination actions is essential for individuals terminated for cause. In certain situations, organizations consider disabling the information system accounts of individuals that are being terminated prior to the individuals being notified. Related controls: AC-2, IA-4, PE-2, PS-5, PS-6. References: None. | link | count: 005 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PS-5 | FedRAMP_Moderate_R4_PS-5 | FedRAMP Moderate PS-5 | Personnel Security | Personnel Transfer | Shared | n/a | The organization: a. Reviews and confirms ongoing operational need for current logical and physical access authorizations to information systems/facilities when individuals are reassigned or transferred to other positions within the organization; b. Initiates [Assignment: organization-defined transfer or reassignment actions] within [Assignment: organization-defined time period following the formal transfer action]; c. Modifies access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and d. Notifies [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period]. Supplemental Guidance: This control applies when reassignments or transfers of individuals are permanent or of such extended durations as to make the actions warranted. Organizations define actions appropriate for the types of reassignments or transfers, whether permanent or extended. Actions that may be required for personnel transfers or reassignments to other positions within organizations include, for example: (i) returning old and issuing new keys, identification cards, and building passes; (ii) closing information system accounts and establishing new accounts; (iii) changing information system access authorizations (i.e., privileges); and (iv) providing for access to official records to which individuals had access at previous work locations and in previous information system accounts. Related controls: AC-2, IA-4, PE-2, PS-4. Control Enhancements: None. References: None. | link | count: 004 Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PS-6 | FedRAMP_Moderate_R4_PS-6 | FedRAMP Moderate PS-6 | Personnel Security | Access Agreements | Shared | n/a | The organization: a. Develops and documents access agreements for organizational information systems; b. Reviews and updates the access agreements [Assignment: organization-defined frequency]; and c. Ensures that individuals requiring access to organizational information and information systems: 1. Sign appropriate access agreements prior to being granted access; and 2. Re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or [Assignment: organization-defined frequency]. Supplemental Guidance: Access agreements include, for example, nondisclosure agreements, acceptable use agreements, rules of behavior, and conflict-of-interest agreements. Signed access agreements include an acknowledgement that individuals have read, understand, and agree to abide by the constraints associated with organizational information systems to which access is authorized. Organizations can use electronic signatures to acknowledge access agreements unless specifically prohibited by organizational policy. Related control: PL-4, PS-2, PS-3, PS-4, PS-8. References: None. | link | count: 005 Document organizational access agreements (c981fa70-2e58-8141-1457-e7f62ebc2ade), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Ensure access agreements are signed or resigned timely (e7589f4e-1e8b-72c2-3692-1e14d7f3699f), Require users to sign access agreement (3af53f59-979f-24a8-540f-d7cdbc366607), Update organizational access agreements (e21f91d1-2803-0282-5f2d-26ebc4b170ef) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PS-7 | FedRAMP_Moderate_R4_PS-7 | FedRAMP Moderate PS-7 | Personnel Security | Third-Party Personnel Security | Shared | n/a | The organization: a. Establishes personnel security requirements including security roles and responsibilities for third-party providers; b. Requires third-party providers to comply with personnel security policies and procedures established by the organization; c. Documents personnel security requirements; d. Requires third-party providers to notify [Assignment: organization-defined personnel or roles] of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges within [Assignment: organization-defined time period]; and e. Monitors provider compliance. Supplemental Guidance: Third-party providers include, for example, service bureaus, contractors, and other organizations providing information system development, information technology services, outsourced applications, and network and security management. Organizations explicitly include personnel security requirements in acquisition-related documents. Third-party providers may have personnel working at organizational facilities with credentials, badges, or information system privileges issued by organizations. Notifications of third-party personnel changes ensure appropriate termination of privileges and credentials. Organizations define the transfers and terminations deemed reportable by security-related characteristics that include, for example, functions, roles, and nature of credentials/privileges associated with individuals transferred or terminated. Related controls: PS-2, PS-3, PS-4, PS-5, PS-6, SA-9, SA-21. Control Enhancements: None. References: NIST Special Publication 800-35. | link | count: 005 Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | PS-8 | FedRAMP_Moderate_R4_PS-8 | FedRAMP Moderate PS-8 | Personnel Security | Personnel Sanctions | Shared | n/a | The organization: a. Employs a formal sanctions process for individuals failing to comply with established information security policies and procedures; and b. Notifies [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period] when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction. Supplemental Guidance: Organizational sanctions processes reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Sanctions processes are described in access agreements and can be included as part of general personnel policies and procedures for organizations. Organizations consult with the Office of the General Counsel regarding matters of employee sanctions. Related controls: PL-4, PS-6. Control Enhancements: None. References: None. | link | count: 002 Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-1 | FedRAMP_Moderate_R4_RA-1 | FedRAMP Moderate RA-1 | Risk Assessment | Risk Assessment Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A risk assessment policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls; and b. Reviews and updates the current: 1. Risk assessment policy [Assignment: organization-defined frequency]; and 2. Risk assessment procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the RA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-30, 800-100. | link | count: 001 Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-2 | FedRAMP_Moderate_R4_RA-2 | FedRAMP Moderate RA-2 | Risk Assessment | Security Categorization | Shared | n/a | The organization: a. Categorizes information and the information system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance; b. Documents the security categorization results (including supporting rationale) in the security plan for the information system; and c. Ensures that the security categorization decision is reviewed and approved by the authorizing official or authorizing official designated representative. Supplemental Guidance: Clearly defined authorization boundaries are a prerequisite for effective security categorization decisions. Security categories describe the potential adverse impacts to organizational operations, organizational assets, and individuals if organizational information and information systems are comprised through a loss of confidentiality, integrity, or availability. Organizations conduct the security categorization process as an organization-wide activity with the involvement of chief information officers, senior information security officers, information system owners, mission/business owners, and information owners/stewards. Organizations also consider the potential adverse impacts to other organizations and, in accordance with the USA PATRIOT Act of 2001 and Homeland Security Presidential Directives, potential national-level adverse impacts. Security categorization processes carried out by organizations facilitate the development of inventories of information assets, and along with CM-8, mappings to specific information system components where information is processed, stored, or transmitted. Related controls: CM-8, MP-4, RA-3, SC-7. Control Enhancements: None. References: FIPS Publication 199; NIST Special Publications 800-30, 800-39, 800-60. | link | count: 004 Categorize information (93fa357f-2e38-22a9-5138-8cc5124e1923), Develop business classification schemes (11ba0508-58a8-44de-5f3a-9e05d80571da), Ensure security categorization is approved (6c79c3e5-5f7b-a48a-5c7b-8c158bc01115), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-3 | FedRAMP_Moderate_R4_RA-3 | FedRAMP Moderate RA-3 | Risk Assessment | Risk Assessment | Shared | n/a | The organization: a. Conducts an assessment of risk, including the likelihood and magnitude of harm, from the unauthorized access, use, disclosure, disruption, modification, or destruction of the information system and the information it processes, stores, or transmits; b. Documents risk assessment results in [Selection: security plan; risk assessment report; [Assignment: organization-defined document]]; c. Reviews risk assessment results [Assignment: organization-defined frequency]; d. Disseminates risk assessment results to [Assignment: organization-defined personnel or roles]; and e. Updates the risk assessment [Assignment: organization-defined frequency] or whenever there are significant changes to the information system or environment of operation (including the identification of new threats and vulnerabilities), or other conditions that may impact the security state of the system. Supplemental Guidance: Clearly defined authorization boundaries are a prerequisite for effective risk assessments. Risk assessments take into account threats, vulnerabilities, likelihood, and impact to organizational operations and assets, individuals, other organizations, and the Nation based on the operation and use of information systems. Risk assessments also take into account risk from external parties (e.g., service providers, contractors operating information systems on behalf of the organization, individuals accessing organizational information systems, outsourcing entities). In accordance with OMB policy and related E-authentication initiatives, authentication of public users accessing federal information systems may also be required to protect nonpublic or privacy-related information. As such, organizational assessments of risk also address public access to federal information systems. Risk assessments (either formal or informal) can be conducted at all three tiers in the risk management hierarchy (i.e., organization level, mission/business process level, or information system level) and at any phase in the system development life cycle. Risk assessments can also be conducted at various steps in the Risk Management Framework, including categorization, security control selection, security control implementation, security control assessment, information system authorization, and security control monitoring. RA-3 is noteworthy in that the control must be partially implemented prior to the implementation of other controls in order to complete the first two steps in the Risk Management Framework. Risk assessments can play an important role in security control selection processes, particularly during the application of tailoring guidance, which includes security control supplementation. Related controls: RA-2, PM-9. Control Enhancements: None. References: OMB Memorandum 04-04; NIST Special Publication 800-30, 800-39; Web:idmanagement.gov. | link | count: 004 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-5 | FedRAMP_Moderate_R4_RA-5 | FedRAMP Moderate RA-5 | Risk Assessment | Vulnerability Scanning | Shared | n/a | The organization: a. Scans for vulnerabilities in the information system and hosted applications [Assignment: organization-defined frequency and/or randomly in accordance with organization-defined process] and when new vulnerabilities potentially affecting the system/applications are identified and reported; b. Employs vulnerability scanning tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: 1. Enumerating platforms, software flaws, and improper configurations; 2. Formatting checklists and test procedures; and 3. Measuring vulnerability impact; c. Analyzes vulnerability scan reports and results from security control assessments; d. Remediates legitimate vulnerabilities [Assignment: organization-defined response times], in accordance with an organizational assessment of risk; and e. Shares information obtained from the vulnerability scanning process and security control assessments with [Assignment: organization-defined personnel or roles] to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies). Supplemental Guidance: Security categorization of information systems guides the frequency and comprehensiveness of vulnerability scans. Organizations determine the required vulnerability scanning for all information system components, ensuring that potential sources of vulnerabilities such as networked printers, scanners, and copiers are not overlooked. Vulnerability analyses for custom software applications may require additional approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can employ these analysis approaches in a variety of tools (e.g., web-based application scanners, static analysis tools, binary analyzers) and in source code reviews. Vulnerability scanning includes, for example: (i) scanning for patch levels; (ii) scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and (iii) scanning for improperly configured or incorrectly operating information flow control mechanisms. Organizations consider using tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention and that use the Open Vulnerability Assessment Language (OVAL) to determine/test for the presence of vulnerabilities. Suggested sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). In addition, security control assessments such as red team exercises provide other sources of potential vulnerabilities for which to scan. Organizations also consider using tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS). Related controls: CA-2, CA-7, CM-4, CM-6, RA-2, RA-3, SA-11, SI-2. References: NIST Special Publications 800-40, 800-70, 800-115; Web: http://cwe.mitre.org, http://nvd.nist.gov. | link | count: 021 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Regulatory Compliance, Security Center, SQL, Synapse | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-5(1) | FedRAMP_Moderate_R4_RA-5(1) | FedRAMP Moderate RA-5 (1) | Risk Assessment | Update Tool Capability | Shared | n/a | The organization employs vulnerability scanning tools that include the capability to readily update the information system vulnerabilities to be scanned. Supplemental Guidance: The vulnerabilities to be scanned need to be readily updated as new vulnerabilities are discovered, announced, and scanning methods developed. This updating process helps to ensure that potential vulnerabilities in the information system are identified and addressed as quickly as possible. Related controls: SI-3, SI-7. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-5(2) | FedRAMP_Moderate_R4_RA-5(2) | FedRAMP Moderate RA-5 (2) | Risk Assessment | Update By Frequency / Prior To New Scan / When Identified | Shared | n/a | The organization updates the information system vulnerabilities scanned [Selection (one or more): [Assignment: organization-defined frequency]; prior to a new scan; when new vulnerabilities are identified and reported]. Supplemental Guidance: Related controls: SI-3, SI-5. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-5(3) | FedRAMP_Moderate_R4_RA-5(3) | FedRAMP Moderate RA-5 (3) | Risk Assessment | Breadth / Depth Of Coverage | Shared | n/a | The organization employs vulnerability scanning procedures that can identify the breadth and depth of coverage (i.e., information system components scanned and vulnerabilities checked). | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-5(5) | FedRAMP_Moderate_R4_RA-5(5) | FedRAMP Moderate RA-5 (5) | Risk Assessment | Privileged Access | Shared | n/a | The information system implements privileged access authorization to [Assignment: organization- identified information system components] for selected [Assignment: organization-defined vulnerability scanning activities]. Supplemental Guidance: In certain situations, the nature of the vulnerability scanning may be more intrusive or the information system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system components facilitates more thorough vulnerability scanning and also protects the sensitive nature of such scanning. | link | count: 001 Implement privileged access for executing vulnerability scanning activities (5b802722-71dd-a13d-2e7e-231e09589efb) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-5(6) | FedRAMP_Moderate_R4_RA-5(6) | FedRAMP Moderate RA-5 (6) | Risk Assessment | Automated Trend Analyses | Shared | n/a | The organization employs automated mechanisms to compare the results of vulnerability scans over time to determine trends in information system vulnerabilities. Supplemental Guidance: Related controls: IR-4, IR-5, SI-4. | link | count: 005 Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | RA-5(8) | FedRAMP_Moderate_R4_RA-5(8) | FedRAMP Moderate RA-5 (8) | Risk Assessment | Review Historic Audit Logs | Shared | n/a | The organization reviews historic audit logs to determine if a vulnerability identified in the information system has been previously exploited. Supplemental Guidance: Related control: AU-6. | link | count: 015 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review exploit protection events (a30bd8e9-7064-312a-0e1f-e1b485d59f6e), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-1 | FedRAMP_Moderate_R4_SA-1 | FedRAMP Moderate SA-1 | System And Services Acquisition | System And Services Acquisition Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system and services acquisition policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls; and b. Reviews and updates the current: 1. System and services acquisition policy [Assignment: organization-defined frequency]; and 2. System and services acquisition procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-10 | FedRAMP_Moderate_R4_SA-10 | FedRAMP Moderate SA-10 | System And Services Acquisition | Developer Configuration Management | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to: a. Perform configuration management during system, component, or service [Selection (one or more): design; development; implementation; operation]; b. Document, manage, and control the integrity of changes to [Assignment: organization-defined configuration items under configuration management]; c. Implement only organization-approved changes to the system, component, or service; d. Document approved changes to the system, component, or service and the potential security impacts of such changes; and e. Track security flaws and flaw resolution within the system, component, or service and report findings to [Assignment: organization-defined personnel]. Supplemental Guidance: This control also applies to organizations conducting internal information systems development and integration. Organizations consider the quality and completeness of the configuration management activities conducted by developers as evidence of applying effective security safeguards. Safeguards include, for example, protecting from unauthorized modification or destruction, the master copies of all material used to generate security-relevant portions of the system hardware, software, and firmware. Maintaining the integrity of changes to the information system, information system component, or information system service requires configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes. Configuration items that are placed under configuration management (if existence/use is required by other security controls) include: the formal model; the functional, high-level, and low-level design specifications; other design data; implementation documentation; source code and hardware schematics; the running version of the object code; tools for comparing new versions of security-relevant hardware descriptions and software/firmware source code with previous versions; and test fixtures and documentation. Depending on the mission/business needs of organizations and the nature of the contractual relationships in place, developers may provide configuration management support during the operations and maintenance phases of the life cycle. Related controls: CM-3, CM-4, CM-9, SA-12, SI-2. References: NIST Special Publication 800-128. | link | count: 009 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-10(1) | FedRAMP_Moderate_R4_SA-10(1) | FedRAMP Moderate SA-10 (1) | System And Services Acquisition | Software / Firmware Integrity Verification | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to enable integrity verification of software and firmware components. Supplemental Guidance: This control enhancement allows organizations to detect unauthorized changes to software and firmware components through the use of tools, techniques, and/or mechanisms provided by developers. Integrity checking mechanisms can also address counterfeiting of software and firmware components. Organizations verify the integrity of software and firmware components, for example, through secure one-way hashes provided by developers. Delivered software and firmware components also include any updates to such components. Related control: SI-7. | link | count: 001 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-11 | FedRAMP_Moderate_R4_SA-11 | FedRAMP Moderate SA-11 | System And Services Acquisition | Developer Security Testing And Evaluation | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to: a. Create and implement a security assessment plan; b. Perform [Selection (one or more): unit; integration; system; regression] testing/evaluation at [Assignment: organization-defined depth and coverage]; c. Produce evidence of the execution of the security assessment plan and the results of the security testing/evaluation; d. Implement a verifiable flaw remediation process; and e. Correct flaws identified during security testing/evaluation. Supplemental Guidance: Developmental security testing/evaluation occurs at all post‐design phases of the system development life cycle. Such testing/evaluation confirms that the required security controls are implemented correctly, operating as intended, enforcing the desired security policy, and meeting established security requirements. Security properties of information systems may be affected by the interconnection of system components or changes to those components. These interconnections or changes (e.g., upgrading or replacing applications and operating systems) may adversely affect previously implemented security controls. This control provides additional types of security testing/evaluation that developers can conduct to reduce or eliminate potential flaws. Testing custom software applications may require approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Developers can employ these analysis approaches in a variety of tools (e.g., web-based application scanners, static analysis tools, binary analyzers) and in source code reviews. Security assessment plans provide the specific activities that developers plan to carry out including the types of analyses, testing, evaluation, and reviews of software and firmware components, the degree of rigor to be applied, and the types of artifacts produced during those processes. The depth of security testing/evaluation refers to the rigor and level of detail associated with the assessment process (e.g., black box, gray box, or white box testing). The coverage of security testing/evaluation refers to the scope (i.e., number and type) of the artifacts included in the assessment process. Contracts specify the acceptance criteria for security assessment plans, flaw remediation processes, and the evidence that the plans/processes have been diligently applied. Methods for reviewing and protecting assessment plans, evidence, and documentation are commensurate with the security category or classification level of the information system. Contracts may specify documentation protection requirements. Related controls: CA-2, CM-4, SA-3, SA-4, SA-5, SI-2. References: ISO/IEC 15408; NIST Special Publication 800-53A; Web: http://nvd.nist.gov, http://cwe.mitre.org, http://cve.mitre.org, http://capec.mitre.org. | link | count: 003 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-2 | FedRAMP_Moderate_R4_SA-2 | FedRAMP Moderate SA-2 | System And Services Acquisition | Allocation Of Resources | Shared | n/a | The organization: a. Determines information security requirements for the information system or information system service in mission/business process planning; b. Determines, documents, and allocates the resources required to protect the information system or information system service as part of its capital planning and investment control process; and c. Establishes a discrete line item for information security in organizational programming and budgeting documentation. Supplemental Guidance: Resource allocation for information security includes funding for the initial information system or information system service acquisition and funding for the sustainment of the system/service. Related controls: PM-3, PM-11. Control Enhancements: None. References: NIST Special Publication 800-65. | link | count: 006 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Allocate resources in determining information system requirements (90a156a6-49ed-18d1-1052-69aac27c05cd), Establish a discrete line item in budgeting documentation (06af77de-02ca-0f3e-838a-a9420fe466f5), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-3 | FedRAMP_Moderate_R4_SA-3 | FedRAMP Moderate SA-3 | System And Services Acquisition | System Development Life Cycle | Shared | n/a | The organization: a. Manages the information system using [Assignment: organization-defined system development life cycle] that incorporates information security considerations; b. Defines and documents information security roles and responsibilities throughout the system development life cycle; c. Identifies individuals having information security roles and responsibilities; and d. Integrates the organizational information security risk management process into system development life cycle activities. Supplemental Guidance: A well-defined system development life cycle provides the foundation for the successful development, implementation, and operation of organizational information systems. To apply the required security controls within the system development life cycle requires a basic understanding of information security, threats, vulnerabilities, adverse impacts, and risk to critical missions/business functions. The security engineering principles in SA-8 cannot be properly applied if individuals that design, code, and test information systems and system components (including information technology products) do not understand security. Therefore, organizations include qualified personnel, for example, chief information security officers, security architects, security engineers, and information system security officers in system development life cycle activities to ensure that security requirements are incorporated into organizational information systems. It is equally important that developers include individuals on the development team that possess the requisite security expertise and skills to ensure that needed security capabilities are effectively integrated into the information system. Security awareness and training programs can help ensure that individuals having key security roles and responsibilities have the appropriate experience, skills, and expertise to conduct assigned system development life cycle activities. The effective integration of security requirements into enterprise architecture also helps to ensure that important security considerations are addressed early in the system development life cycle and that those considerations are directly related to the organizational mission/business processes. This process also facilitates the integration of the information security architecture into the enterprise architecture, consistent with organizational risk management and information security strategies. Related controls: AT-3, PM-7, SA-8. Control Enhancements: None. References: NIST Special Publications 800-37, 800-64. | link | count: 003 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-4 | FedRAMP_Moderate_R4_SA-4 | FedRAMP Moderate SA-4 | System And Services Acquisition | Acquisition Process | Shared | n/a | The organization includes the following requirements, descriptions, and criteria, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs: a. Security functional requirements; b. Security strength requirements; c. Security assurance requirements; d. Security-related documentation requirements; e. Requirements for protecting security-related documentation; f. Description of the information system development environment and environment in which the system is intended to operate; and g. Acceptance criteria. Supplemental Guidance: Information system components are discrete, identifiable information technology assets (e.g., hardware, software, or firmware) that represent the building blocks of an information system. Information system components include commercial information technology products. Security functional requirements include security capabilities, security functions, and security mechanisms. Security strength requirements associated with such capabilities, functions, and mechanisms include degree of correctness, completeness, resistance to direct attack, and resistance to tampering or bypass. Security assurance requirements include: (i) development processes, procedures, practices, and methodologies; and (ii) evidence from development and assessment activities providing grounds for confidence that the required security functionality has been implemented and the required security strength has been achieved. Security documentation requirements address all phases of the system development life cycle. Security functionality, assurance, and documentation requirements are expressed in terms of security controls and control enhancements that have been selected through the tailoring process. The security control tailoring process includes, for example, the specification of parameter values through the use of assignment and selection statements and the specification of platform dependencies and implementation information. Security documentation provides user and administrator guidance regarding the implementation and operation of security controls. The level of detail required in security documentation is based on the security category or classification level of the information system and the degree to which organizations depend on the stated security capability, functions, or mechanisms to meet overall risk response expectations (as defined in the organizational risk management strategy). Security requirements can also include organizationally mandated configuration settings specifying allowed functions, ports, protocols, and services. Acceptance criteria for information systems, information system components, and information system services are defined in the same manner as such criteria for any organizational acquisition or procurement. The Federal Acquisition Regulation (FAR) Section 7.103 contains information security requirements from FISMA. Related controls: CM-6, PL-2, PS-7, SA-3, SA-5, SA-8, SA-11, SA-12. References: HSPD-12; ISO/IEC 15408; FIPS Publications 140-2, 201; NIST Special Publications 800-23, 800-35, 800-36, 800-37, 800-64, 800-70, 800-137; Federal Acquisition Regulation; Web: http://www.niap-ccevs.org, http://fips201ep.cio.gov, http://www.acquisition.gov/far. | link | count: 011 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-4(1) | FedRAMP_Moderate_R4_SA-4(1) | FedRAMP Moderate SA-4 (1) | System And Services Acquisition | Functional Properties Of Security Controls | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to provide a description of the functional properties of the security controls to be employed. Supplemental Guidance: Functional properties of security controls describe the functionality (i.e., security capability, functions, or mechanisms) visible at the interfaces of the controls and specifically exclude functionality and data structures internal to the operation of the controls. Related control: SA-5. | link | count: 001 Obtain functional properties of security controls (44b71aa8-099d-8b97-1557-0e853ec38e0d) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-4(10) | FedRAMP_Moderate_R4_SA-4(10) | FedRAMP Moderate SA-4 (10) | System And Services Acquisition | Use Of Approved Piv Products | Shared | n/a | The organization employs only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational information systems. Supplemental Guidance: Related controls: IA-2; IA-8. | link | count: 001 Employ FIPS 201-approved technology for PIV (8b333332-6efd-7c0d-5a9f-d1eb95105214) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-4(2) | FedRAMP_Moderate_R4_SA-4(2) | FedRAMP Moderate SA-4 (2) | System And Services Acquisition | Design / Implementation Information For Security Controls | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to provide design and implementation information for the security controls to be employed that includes: [Selection (one or more): security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [Assignment: organization-defined design/implementation information]] at [Assignment: organization-defined level of detail]. Supplemental Guidance: Organizations may require different levels of detail in design and implementation documentation for security controls employed in organizational information systems, system components, or information system services based on mission/business requirements, requirements for trustworthiness/resiliency, and requirements for analysis and testing. Information systems can be partitioned into multiple subsystems. Each subsystem within the system can contain one or more modules. The high-level design for the system is expressed in terms of multiple subsystems and the interfaces between subsystems providing security-relevant functionality. The low-level design for the system is expressed in terms of modules with particular emphasis on software and firmware (but not excluding hardware) and the interfaces between modules providing security-relevant functionality. Source code and hardware schematics are typically referred to as the implementation representation of the information system. Related control: SA-5. | link | count: 001 Obtain design and implementation information for the security controls (22a02c9a-49e4-5dc9-0d14-eb35ad717154) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-4(8) | FedRAMP_Moderate_R4_SA-4(8) | FedRAMP Moderate SA-4 (8) | System And Services Acquisition | Continuous Monitoring Plan | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to produce a plan for the continuous monitoring of security control effectiveness that contains [Assignment: organization-defined level of detail]. Supplemental Guidance: The objective of continuous monitoring plans is to determine if the complete set of planned, required, and deployed security controls within the information system, system component, or information system service continue to be effective over time based on the inevitable changes that occur. Developer continuous monitoring plans include a sufficient level of detail such that the information can be incorporated into the continuous monitoring strategies and programs implemented by organizations. Related control: CA-7. | link | count: 001 Obtain continuous monitoring plan for security controls (ca6d7878-3189-1833-4620-6c7254ed1607) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-4(9) | FedRAMP_Moderate_R4_SA-4(9) | FedRAMP Moderate SA-4 (9) | System And Services Acquisition | Functions / Ports / Protocols / Services In Use | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to identify early in the system development life cycle, the functions, ports, protocols, and services intended for organizational use. Supplemental Guidance: The identification of functions, ports, protocols, and services early in the system development life cycle (e.g., during the initial requirements definition and design phases) allows organizations to influence the design of the information system, information system component, or information system service. This early involvement in the life cycle helps organizations to avoid or minimize the use of functions, ports, protocols, or services that pose unnecessarily high risks and understand the trade-offs involved in blocking specific ports, protocols, or services (or when requiring information system service providers to do so). Early identification of functions, ports, protocols, and services avoids costly retrofitting of security controls after the information system, system component, or information system service has been implemented. SA-9 describes requirements for external information system services with organizations identifying which functions, ports, protocols, and services are provided from external sources. Related controls: CM-7, SA-9. | link | count: 001 Require developer to identify SDLC ports, protocols, and services (f6da5cca-5795-60ff-49e1-4972567815fe) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-5 | FedRAMP_Moderate_R4_SA-5 | FedRAMP Moderate SA-5 | System And Services Acquisition | Information System Documentation | Shared | n/a | The organization: a. Obtains administrator documentation for the information system, system component, or information system service that describes: 1. Secure configuration, installation, and operation of the system, component, or service; 2. Effective use and maintenance of security functions/mechanisms; and 3. Known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions; b. Obtains user documentation for the information system, system component, or information system service that describes: 1. User-accessible security functions/mechanisms and how to effectively use those security functions/mechanisms; 2. Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner; and 3. User responsibilities in maintaining the security of the system, component, or service; c. Documents attempts to obtain information system, system component, or information system service documentation when such documentation is either unavailable or nonexistent and [Assignment: organization-defined actions] in response; d. Protects documentation as required, in accordance with the risk management strategy; and e. Distributes documentation to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: This control helps organizational personnel understand the implementation and operation of security controls associated with information systems, system components, and information system services. Organizations consider establishing specific measures to determine the quality/completeness of the content provided. The inability to obtain needed documentation may occur, for example, due to the age of the information system/component or lack of support from developers and contractors. In those situations, organizations may need to recreate selected documentation if such documentation is essential to the effective implementation or operation of security controls. The level of protection provided for selected information system, component, or service documentation is commensurate with the security category or classification of the system. For example, documentation associated with a key DoD weapons system or command and control system would typically require a higher level of protection than a routine administrative system. Documentation that addresses information system vulnerabilities may also require an increased level of protection. Secure operation of the information system, includes, for example, initially starting the system and resuming secure system operation after any lapse in system operation. Related controls: CM-6, CM-8, PL-2, PL-4, PS-2, SA-3, SA-4. References: None. | link | count: 005 Distribute information system documentation (84a01872-5318-049e-061e-d56734183e84), Document customer-defined actions (8c44a0ea-9b09-4d9c-0e91-f9bee3d05bfb), Obtain Admin documentation (3f1216b0-30ee-1ac9-3899-63eb744e85f5), Obtain user security function documentation (be1c34ab-295a-07a6-785c-36f63c1d223e), Protect administrator and user documentation (09960521-759e-5d12-086f-4192a72a5e92) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-9 | FedRAMP_Moderate_R4_SA-9 | FedRAMP Moderate SA-9 | System And Services Acquisition | External Information System Services | Shared | n/a | The organization: a. Requires that providers of external information system services comply with organizational information security requirements and employ [Assignment: organization-defined security controls] in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance; b. Defines and documents government oversight and user roles and responsibilities with regard to external information system services; and c. Employs [Assignment: organization-defined processes, methods, and techniques] to monitor security control compliance by external service providers on an ongoing basis. Supplemental Guidance: External information system services are services that are implemented outside of the authorization boundaries of organizational information systems. This includes services that are used by, but not a part of, organizational information systems. FISMA and OMB policy require that organizations using external service providers that are processing, storing, or transmitting federal information or operating information systems on behalf of the federal government ensure that such providers meet the same security requirements that federal agencies are required to meet. Organizations establish relationships with external service providers in a variety of ways including, for example, through joint ventures, business partnerships, contracts, interagency agreements, lines of business arrangements, licensing agreements, and supply chain exchanges. The responsibility for managing risks from the use of external information system services remains with authorizing officials. For services external to organizations, a chain of trust requires that organizations establish and retain a level of confidence that each participating provider in the potentially complex consumer-provider relationship provides adequate protection for the services rendered. The extent and nature of this chain of trust varies based on the relationships between organizations and the external providers. Organizations document the basis for trust relationships so the relationships can be monitored over time. External information system services documentation includes government, service providers, end user security roles and responsibilities, and service-level agreements. Service-level agreements define expectations of performance for security controls, describe measurable outcomes, and identify remedies and response requirements for identified instances of noncompliance. Related controls: CA-3, IR-7, PS-7. References: NIST Special Publication 800-35. | link | count: 004 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-9(1) | FedRAMP_Moderate_R4_SA-9(1) | FedRAMP Moderate SA-9 (1) | System And Services Acquisition | Risk Assessments / Organizational Approvals | Shared | n/a | The organization: (a) Conducts an organizational assessment of risk prior to the acquisition or outsourcing of dedicated information security services; and (b) Ensures that the acquisition or outsourcing of dedicated information security services is approved by [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Dedicated information security services include, for example, incident monitoring, analysis and response, operation of information security-related devices such as firewalls, or key management services. Related controls: CA-6, RA-3. | link | count: 002 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Obtain approvals for acquisitions and outsourcing (92b94485-1c49-3350-9ada-dffe94f08e87) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-9(2) | FedRAMP_Moderate_R4_SA-9(2) | FedRAMP Moderate SA-9 (2) | System And Services Acquisition | Identification Of Functions / Ports / Protocols / Services | Shared | n/a | The organization requires providers of [Assignment: organization-defined external information system services] to identify the functions, ports, protocols, and other services required for the use of such services. Supplemental Guidance: Information from external service providers regarding the specific functions, ports, protocols, and services used in the provision of such services can be particularly useful when the need arises to understand the trade-offs involved in restricting certain functions/services or blocking certain ports/protocols. Related control: CM-7. | link | count: 001 Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-9(4) | FedRAMP_Moderate_R4_SA-9(4) | FedRAMP Moderate SA-9 (4) | System And Services Acquisition | Consistent Interests Of Consumers And Providers | Shared | n/a | The organization employs [Assignment: organization-defined security safeguards] to ensure that the interests of [Assignment: organization-defined external service providers] are consistent with and reflect organizational interests. Supplemental Guidance: As organizations increasingly use external service providers, the possibility exists that the interests of the service providers may diverge from organizational interests. In such situations, simply having the correct technical, procedural, or operational safeguards in place may not be sufficient if the service providers that implement and control those safeguards are not operating in a manner consistent with the interests of the consuming organizations. Possible actions that organizations might take to address such concerns include, for example, requiring background checks for selected service provider personnel, examining ownership records, employing only trustworthy service providers (i.e., providers with which organizations have had positive experiences), and conducting periodic/unscheduled visits to service provider facilities. | link | count: 001 Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SA-9(5) | FedRAMP_Moderate_R4_SA-9(5) | FedRAMP Moderate SA-9 (5) | System And Services Acquisition | Processing, Storage, And Service Location | Shared | n/a | The organization restricts the location of [Selection (one or more): information processing; information/data; information system services] to [Assignment: organization-defined locations] based on [Assignment: organization-defined requirements or conditions]. Supplemental Guidance: The location of information processing, information/data storage, or information system services that are critical to organizations can have a direct impact on the ability of those organizations to successfully execute their missions/business functions. This situation exists when external providers control the location of processing, storage or services. The criteria external providers use for the selection of processing, storage, or service locations may be different from organizational criteria. For example, organizations may want to ensure that data/information storage locations are restricted to certain locations to facilitate incident response activities (e.g., forensic analyses, after-the-fact investigations) in case of information security breaches/compromises. Such incident response activities may be adversely affected by the governing laws or protocols in the locations where processing and storage occur and/or the locations from which information system services emanate. | link | count: 001 Restrict location of information processing, storage and services (0040d2e5-2779-170d-6a2c-1f5fca353335) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-1 | FedRAMP_Moderate_R4_SC-1 | FedRAMP Moderate SC-1 | System And Communications Protection | System And Communications Protection Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system and communications protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls; and b. Reviews and updates the current: 1. System and communications protection policy [Assignment: organization-defined frequency]; and 2. System and communications protection procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SC family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-10 | FedRAMP_Moderate_R4_SC-10 | FedRAMP Moderate SC-10 | System And Communications Protection | Network Disconnect | Shared | n/a | The information system terminates the network connection associated with a communications session at the end of the session or after [Assignment: organization-defined time period] of inactivity. Supplemental Guidance: This control applies to both internal and external networks. Terminating network connections associated with communications sessions include, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. Time periods of inactivity may be established by organizations and include, for example, time periods by type of network access or for specific network accesses. Control Enhancements: None. References: None. | link | count: 001 Reauthenticate or terminate a user session (d6653f89-7cb5-24a4-9d71-51581038231b) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-12 | FedRAMP_Moderate_R4_SC-12 | FedRAMP Moderate SC-12 | System And Communications Protection | Cryptographic Key Establishment And Management | Shared | n/a | The organization establishes and manages cryptographic keys for required cryptography employed within the information system in accordance with [Assignment: organization-defined requirements for key generation, distribution, storage, access, and destruction]. Supplemental Guidance: Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. Organizations define key management requirements in accordance with applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance, specifying appropriate options, levels, and parameters. Organizations manage trust stores to ensure that only approved trust anchors are in such trust stores. This includes certificates with visibility external to organizational information systems and certificates related to the internal operations of systems. Related controls: SC-13, SC-17. References: NIST Special Publications 800-56, 800-57. | link | count: 040 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) (47031206-ce96-41f8-861b-6a915f3de284), Azure API for FHIR should use a customer-managed key to encrypt data at rest (051cba44-2429-45b9-9649-46cec11c7119), Azure Automation accounts should use customer-managed keys to encrypt data at rest (56a5ee18-2ae6-4810-86f7-18e39ce5629b), Azure Batch account should use customer-managed keys to encrypt data (99e9ccd8-3db9-4592-b0d1-14b1715a4d8a), Azure Container Instance container group should use customer-managed key for encryption (0aa61e00-0a01-4a3c-9945-e93cffedf0e6), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password (86efb160-8de7-451d-bc08-5d475b0aadae), Azure Data Explorer encryption at rest should use a customer-managed key (81e74cea-30fd-40d5-802f-d72103c2aaaa), Azure data factories should be encrypted with a customer-managed key (4ec52d6d-beb7-40c4-9a9e-fe753254690e), Azure HDInsight clusters should use customer-managed keys to encrypt data at rest (64d314f6-6062-4780-a861-c23e8951bee5), Azure HDInsight clusters should use encryption at host to encrypt data at rest (1fd32ebd-e4c3-4e13-a54a-d7422d4d95f6), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Stream Analytics jobs should use customer-managed keys to encrypt data (87ba29ef-1ab3-4d82-b763-87fcd4f531f7), Azure Synapse workspaces should use customer-managed keys to encrypt data at rest (f7d52b2d-e161-4dfa-a82b-55e564167385), Bot Service should be encrypted with a customer-managed key (51522a96-0869-4791-82f3-981000c2c67f), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Event Hub namespaces should use a customer-managed key for encryption (a1ad735a-e96f-45d2-a7b2-9a4932cab7ec), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Logic Apps Integration Service Environment should be encrypted with customer-managed keys (1fafeaf6-7927-4059-a50a-8eb2a7a6f2b5), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), OS and data disks should be encrypted with a customer-managed key (702dd420-7fcc-42c5-afe8-4026edd20fe0), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Service Bus Premium namespaces should use a customer-managed key for encryption (295fc8b1-dc9f-4f53-9c61-3f313ceab40a), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
API for FHIR, Automation, Azure Data Explorer, Backup, Batch, Bot Service, Cognitive Services, Compute, Container Instance, Container Registry, Cosmos DB, Data Box, Data Factory, Event Hub, HDInsight, Internet of Things, Kubernetes, Logic Apps, Machine Learning, Monitoring, Regulatory Compliance, Service Bus, SQL, Storage, Stream Analytics, Synapse | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-12(2) | FedRAMP_Moderate_R4_SC-12(2) | FedRAMP Moderate SC-12 (2) | System And Communications Protection | Symmetric Keys | Shared | n/a | The organization produces, controls, and distributes symmetric cryptographic keys using [Selection: NIST FIPS-compliant; NSA-approved] key management technology and processes. | link | count: 001 Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-12(3) | FedRAMP_Moderate_R4_SC-12(3) | FedRAMP Moderate SC-12 (3) | System And Communications Protection | Asymmetric Keys | Shared | n/a | The organization produces, controls, and distributes asymmetric cryptographic keys using [Selection: NSA-approved key management technology and processes; approved PKI Class 3 certificates or prepositioned keying material; approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user’s private key]. | link | count: 001 Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-13 | FedRAMP_Moderate_R4_SC-13 | FedRAMP Moderate SC-13 | System And Communications Protection | Cryptographic Protection | Shared | n/a | The information system implements [Assignment: organization-defined cryptographic uses and type of cryptography required for each use] in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Supplemental Guidance: Cryptography can be employed to support a variety of security solutions including, for example, the protection of classified and Controlled Unclassified Information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Generally applicable cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. This control does not impose any requirements on organizations to use cryptography. However, if cryptography is required based on the selection of other security controls, organizations define each type of cryptographic use and the type of cryptography required (e.g., protection of classified information: NSA-approved cryptography; provision of digital signatures: FIPS-validated cryptography). Related controls: AC-2, AC-3, AC-7, AC-17, AC-18, AU-9, AU-10, CM-11, CP-9, IA-3, IA-7, MA-4, MP-2, MP-4, MP-5, SA-4, SC-8, SC-12, SC-28, SI-7. References: FIPS Publication 140; Web: http://csrc.nist.gov/cryptval, http://www.cnss.gov. | link | count: 001 Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-15 | FedRAMP_Moderate_R4_SC-15 | FedRAMP Moderate SC-15 | System And Communications Protection | Collaborative Computing Devices | Shared | n/a | The information system: a. Prohibits remote activation of collaborative computing devices with the following exceptions: [Assignment: organization-defined exceptions where remote activation is to be allowed]; and b. Provides an explicit indication of use to users physically present at the devices. Supplemental Guidance: Collaborative computing devices include, for example, networked white boards, cameras, and microphones. Explicit indication of use includes, for example, signals to users when collaborative computing devices are activated. Related control: AC-21. References: None. | link | count: 002 Explicitly notify use of collaborative computing devices (62fa14f0-4cbe-762d-5469-0899a99b98aa), Prohibit remote activation of collaborative computing devices (678ca228-042d-6d8e-a598-c58d5670437d) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-17 | FedRAMP_Moderate_R4_SC-17 | FedRAMP Moderate SC-17 | System And Communications Protection | Public Key Infrastructure Certificates | Shared | n/a | The organization issues public key certificates under an [Assignment: organization- defined certificate policy] or obtains public key certificates from an approved service provider. Supplemental Guidance: For all certificates, organizations manage information system trust stores to ensure only approved trust anchors are in the trust stores. This control addresses both certificates with visibility external to organizational information systems and certificates related to the internal operations of systems, for example, application-specific time services. Related control: SC-12. Control Enhancements: None. References: OMB Memorandum 05-24; NIST Special Publications 800-32, 800-63. | link | count: 001 Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-18 | FedRAMP_Moderate_R4_SC-18 | FedRAMP Moderate SC-18 | System And Communications Protection | Mobile Code | Shared | n/a | The organization: a. Defines acceptable and unacceptable mobile code and mobile code technologies; b. Establishes usage restrictions and implementation guidance for acceptable mobile code and mobile code technologies; and c. Authorizes, monitors, and controls the use of mobile code within the information system. Supplemental Guidance: Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include, for example, Java, JavaScript, ActiveX, Postscript, PDF, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices (e.g., smart phones). Mobile code policy and procedures address preventing the development, acquisition, or introduction of unacceptable mobile code within organizational information systems. Related controls: AU-2, AU-12, CM-2, CM-6, SI-3. References: NIST Special Publication 800-28; DoD Instruction 8552.01. | link | count: 003 Authorize, monitor, and control usage of mobile code technologies (291f20d4-8d93-1d73-89f3-6ce28b825563), Define acceptable and unacceptable mobile code technologies (1afada58-8b34-7ac2-a38a-983218635201), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-19 | FedRAMP_Moderate_R4_SC-19 | FedRAMP Moderate SC-19 | System And Communications Protection | Voice Over Internet Protocol | Shared | n/a | The organization: a. Establishes usage restrictions and implementation guidance for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously; and b. Authorizes, monitors, and controls the use of VoIP within the information system. Supplemental Guidance: Related controls: CM-6, SC-7, SC-15. References: NIST Special Publication 800-58. | link | count: 002 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Establish voip usage restrictions (68a39c2b-0f17-69ee-37a3-aa10f9853a08) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-2 | FedRAMP_Moderate_R4_SC-2 | FedRAMP Moderate SC-2 | System And Communications Protection | Application Partitioning | Shared | n/a | The information system separates user functionality (including user interface services) from information system management functionality. Supplemental Guidance: Information system management functionality includes, for example, functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical. Organizations implement separation of system management-related functionality from user functionality by using different computers, different central processing units, different instances of operating systems, different network addresses, virtualization techniques, or combinations of these or other methods, as appropriate. This type of separation includes, for example, web administrative interfaces that use separate authentication methods for users of any other information system resources. Separation of system and user functionality may include isolating administrative interfaces on different domains and with additional access controls. Related controls: SA-4, SA-8, SC-3. References: None. | link | count: 003 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-20 | FedRAMP_Moderate_R4_SC-20 | FedRAMP Moderate SC-20 | System And Communications Protection | Secure Name / Address Resolution Service (Authoritative Source) | Shared | n/a | The information system: a. Provides additional data origin and integrity artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries; and b. Provides the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace. Supplemental Guidance: This control enables external clients including, for example, remote Internet clients, to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. Information systems that provide name and address resolution services include, for example, domain name system (DNS) servers. Additional artifacts include, for example, DNS Security (DNSSEC) digital signatures and cryptographic keys. DNS resource records are examples of authoritative data. The means to indicate the security status of child zones includes, for example, the use of delegation signer resource records in the DNS. The DNS security controls reflect (and are referenced from) OMB Memorandum 08-23. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to assure the authenticity and integrity of response data. Related controls: AU-10, SC-8, SC-12, SC-13, SC-21, SC-22. References: OMB Memorandum 08-23; NIST Special Publication 800-81. | link | count: 002 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-21 | FedRAMP_Moderate_R4_SC-21 | FedRAMP Moderate SC-21 | System And Communications Protection | Secure Name /Address Resolution Service (Recursive Or Caching Resolver) | Shared | n/a | The information system requests and performs data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources. Supplemental Guidance: Each client of name resolution services either performs this validation on its own, or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching domain name system (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to enable clients to verify the authenticity and integrity of response data. Related controls: SC-20, SC-22. References: NIST Special Publication 800-81. | link | count: 002 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-22 | FedRAMP_Moderate_R4_SC-22 | FedRAMP Moderate SC-22 | System And Communications Protection | Architecture And Provisioning For Name/Address Resolution Service | Shared | n/a | The information systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal/external role separation. Supplemental Guidance: Information systems that provide name and address resolution services include, for example, domain name system (DNS) servers. To eliminate single points of failure and to enhance redundancy, organizations employ at least two authoritative domain name system servers, one configured as the primary server and the other configured as the secondary server. Additionally, organizations typically deploy the servers in two geographically separated network subnetworks (i.e., not located in the same physical facility). For role separation, DNS servers with internal roles only process name and address resolution requests from within organizations (i.e., from internal clients). DNS servers with external roles only process name and address resolution information requests from clients external to organizations (i.e., on external networks including the Internet). Organizations specify clients that can access authoritative DNS servers in particular roles (e.g., by address ranges, explicit lists). Related controls: SC-2, SC-20, SC-21, SC-24. Control Enhancements: None. References: NIST Special Publication 800-81. | link | count: 001 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-23 | FedRAMP_Moderate_R4_SC-23 | FedRAMP Moderate SC-23 | System And Communications Protection | Session Authenticity | Shared | n/a | The information system protects the authenticity of communications sessions. Supplemental Guidance: This control addresses communications protection at the session, versus packet level (e.g., sessions in service-oriented architectures providing web-based services) and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. Authenticity protection includes, for example, protecting against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. Related controls: SC-8, SC-10, SC-11. References: NIST Special Publications 800-52, 800-77, 800-95. | link | count: 002 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce random unique session identifiers (c7d57a6a-7cc2-66c0-299f-83bf90558f5d) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-28 | FedRAMP_Moderate_R4_SC-28 | FedRAMP Moderate SC-28 | System And Communications Protection | Protection Of Information At Rest | Shared | n/a | The information system protects the [Selection (one or more): confidentiality; integrity] of [Assignment: organization-defined information at rest]. Supplemental Guidance: This control addresses the confidentiality and integrity of information at rest and covers user information and system information. Information at rest refers to the state of information when it is located on storage devices as specific components of information systems. System-related information requiring protection includes, for example, configurations or rule sets for firewalls, gateways, intrusion detection/prevention systems, filtering routers, and authenticator content. Organizations may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms and file share scanning. Integrity protection can be achieved, for example, by implementing Write-Once-Read-Many (WORM) technologies. Organizations may also employ other security controls including, for example, secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved and/or continuous monitoring to identify malicious code at rest. Related controls: AC-3, AC-6, CA-7, CM-3, CM-5, CM-6, PE-3, SC-8, SC-13, SI-3, SI-7. References: NIST Special Publications 800-56, 800-57, 800-111. | link | count: 017 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-28(1) | FedRAMP_Moderate_R4_SC-28(1) | FedRAMP Moderate SC-28 (1) | System And Communications Protection | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to prevent unauthorized disclosure and modification of [Assignment: organization-defined information] on [Assignment: organization-defined information system components]. Supplemental Guidance: Selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of organizational information. The strength of mechanism is commensurate with the security category and/or classification of the information. This control enhancement applies to significant concentrations of digital media in organizational areas designated for media storage and also to limited quantities of media generally associated with information system components in operational environments (e.g., portable storage devices, mobile devices). Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). Organizations employing cryptographic mechanisms to protect information at rest also consider cryptographic key management solutions. Related controls: AC-19, SC-12. | link | count: 017 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-39 | FedRAMP_Moderate_R4_SC-39 | FedRAMP Moderate SC-39 | System And Communications Protection | Process Isolation | Shared | n/a | The information system maintains a separate execution domain for each executing process. Supplemental Guidance: Information systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each information system process has a distinct address space so that communication between processes is performed in a manner controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces. This capability is available in most commercial operating systems that employ multi-state processor technologies. Related controls: AC-3, AC-4, AC-6, SA-4, SA-5, SA-8, SC-2, SC-3. References: None. | link | count: 001 Maintain separate execution domains for running processes (bfc540fe-376c-2eef-4355-121312fa4437) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-5 | FedRAMP_Moderate_R4_SC-5 | FedRAMP Moderate SC-5 | System And Communications Protection | Denial Of Service Protection | Shared | n/a | The information system protects against or limits the effects of the following types of denial of service attacks: [Assignment: organization-defined types of denial of service attacks or reference to source for such information] by employing [Assignment: organization-defined security safeguards]. Supplemental Guidance: A variety of technologies exist to limit, or in some cases, eliminate the effects of denial of service attacks. For example, boundary protection devices can filter certain types of packets to protect information system components on internal organizational networks from being directly affected by denial of service attacks. Employing increased capacity and bandwidth combined with service redundancy may also reduce the susceptibility to denial of service attacks. Related controls: SC-6, SC-7. References: None. | link | count: 005 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Develop and document a DDoS response plan (b7306e73-0494-83a2-31f5-280e934a8f70), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Network, Regulatory Compliance, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-6 | FedRAMP_Moderate_R4_SC-6 | FedRAMP Moderate SC-6 | System And Communications Protection | Resource Availability | Shared | n/a | The information system protects the availability of resources by allocating [Assignment: organization-defined resources] by [Selection (one or more); priority; quota; [Assignment: organization-defined security safeguards]]. Supplemental Guidance: Priority protection helps prevent lower-priority processes from delaying or interfering with the information system servicing any higher-priority processes. Quotas prevent users or processes from obtaining more than predetermined amounts of resources. This control does not apply to information system components for which there are only single users/roles. Control Enhancements: None. References: None. | link | count: 003 Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Manage availability and capacity (edcc36f1-511b-81e0-7125-abee29752fe7), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-7 | FedRAMP_Moderate_R4_SC-7 | FedRAMP Moderate SC-7 | System And Communications Protection | Boundary Protection | Shared | n/a | The information system: a. Monitors and controls communications at the external boundary of the system and at key internal boundaries within the system; b. Implements subnetworks for publicly accessible system components that are [Selection: physically; logically] separated from internal organizational networks; and c. Connects to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture. Supplemental Guidance: Managed interfaces include, for example, gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within a security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational information systems includes, for example, restricting external web traffic to designated web servers within managed interfaces and prohibiting external traffic that appears to be spoofing internal addresses. Organizations consider the shared nature of commercial telecommunications services in the implementation of security controls associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers, and may also include third party-provided access lines and other service elements. Such transmission services may represent sources of increased risk despite contract security provisions. Related controls: AC-4, AC-17, CA-3, CM-7, CP-8, IR-4, RA-3, SC-5, SC-13. References: FIPS Publication 199; NIST Special Publications 800-41, 800-77. | link | count: 053 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Regulatory Compliance, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-7(12) | FedRAMP_Moderate_R4_SC-7(12) | FedRAMP Moderate SC-7 (12) | System And Communications Protection | Host-Based Protection | Shared | n/a | The organization implements [Assignment: organization-defined host-based boundary protection mechanisms] at [Assignment: organization-defined information system components]. Supplemental Guidance: Host-based boundary protection mechanisms include, for example, host-based firewalls. Information system components employing host-based boundary protection mechanisms include, for example, servers, workstations, and mobile devices. | link | count: 001 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-7(13) | FedRAMP_Moderate_R4_SC-7(13) | FedRAMP Moderate SC-7 (13) | System And Communications Protection | Isolation Of Security Tools / Mechanisms / Support Components | Shared | n/a | The organization isolates [Assignment: organization-defined information security tools, mechanisms, and support components] from other internal information system components by implementing physically separate subnetworks with managed interfaces to other components of the system. Supplemental Guidance: Physically separate subnetworks with managed interfaces are useful, for example, in isolating computer network defenses from critical operational processing networks to prevent adversaries from discovering the analysis and forensics techniques of organizations. Related controls: SA-8, SC-2, SC-3. | link | count: 001 Isolate SecurID systems, Security Incident Management systems (dd6d00a8-701a-5935-a22b-c7b9c0c698b2) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-7(18) | FedRAMP_Moderate_R4_SC-7(18) | FedRAMP Moderate SC-7 (18) | System And Communications Protection | Fail Secure | Shared | n/a | The information system fails securely in the event of an operational failure of a boundary protection device. Supplemental Guidance: Fail secure is a condition achieved by employing information system mechanisms to ensure that in the event of operational failures of boundary protection devices at managed interfaces (e.g., routers, firewalls, guards, and application gateways residing on protected subnetworks commonly referred to as demilitarized zones), information systems do not enter into unsecure states where intended security properties no longer hold. Failures of boundary protection devices cannot lead to, or cause information external to the devices to enter the devices, nor can failures permit unauthorized information releases. Related controls: CP-2, SC-24. | link | count: 002 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage transfers between standby and active system components (df54d34f-65f3-39f1-103c-a0464b8615df) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-7(3) | FedRAMP_Moderate_R4_SC-7(3) | FedRAMP Moderate SC-7 (3) | System And Communications Protection | Access Points | Shared | n/a | The organization limits the number of external network connections to the information system. Supplemental Guidance: Limiting the number of external network connections facilitates more comprehensive monitoring of inbound and outbound communications traffic. The Trusted Internet Connection (TIC) initiative is an example of limiting the number of external network connections. | link | count: 052 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-7(4) | FedRAMP_Moderate_R4_SC-7(4) | FedRAMP Moderate SC-7 (4) | System And Communications Protection | External Telecommunications Services | Shared | n/a | The organization: (a) Implements a managed interface for each external telecommunication service; (b) Establishes a traffic flow policy for each managed interface; (c) Protects the confidentiality and integrity of the information being transmitted across each interface; (d) Documents each exception to the traffic flow policy with a supporting mission/business need and duration of that need; and (e) Reviews exceptions to the traffic flow policy [Assignment: organization-defined frequency] and removes exceptions that are no longer supported by an explicit mission/business need. Supplemental Guidance: Related control: SC-8. | link | count: 003 Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-7(7) | FedRAMP_Moderate_R4_SC-7(7) | FedRAMP Moderate SC-7 (7) | System And Communications Protection | Prevent Split Tunneling For Remote Devices | Shared | n/a | The information system, in conjunction with a remote device, prevents the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks. Supplemental Guidance: This control enhancement is implemented within remote devices (e.g., notebook computers) through configuration settings to disable split tunneling in those devices, and by preventing those configuration settings from being readily configurable by users. This control enhancement is implemented within the information system by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling. Split tunneling might be desirable by remote users to communicate with local information system resources such as printers/file servers. However, split tunneling would in effect allow unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. The use of VPNs for remote connections, when adequately provisioned with appropriate security controls, may provide the organization with sufficient assurance that it can effectively treat such connections as non-remote connections from the confidentiality and integrity perspective. VPNs thus provide a means for allowing non-remote communications paths from remote devices. The use of an adequately provisioned VPN does not eliminate the need for preventing split tunneling. | link | count: 001 Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-7(8) | FedRAMP_Moderate_R4_SC-7(8) | FedRAMP Moderate SC-7 (8) | System And Communications Protection | Route Traffic To Authenticated Proxy Servers | Shared | n/a | The information system routes [Assignment: organization-defined internal communications traffic] to [Assignment: organization-defined external networks] through authenticated proxy servers at managed interfaces. Supplemental Guidance: External networks are networks outside of organizational control. A proxy server is a server (i.e., information system or application) that acts as an intermediary for clients requesting information system resources (e.g., files, connections, web pages, or services) from other organizational servers. Client requests established through an initial connection to the proxy server are evaluated to manage complexity and to provide additional protection by limiting direct connectivity. Web content filtering devices are one of the most common proxy servers providing access to the Internet. Proxy servers support logging individual Transmission Control Protocol (TCP) sessions and blocking specific Uniform Resource Locators (URLs), domain names, and Internet Protocol (IP) addresses. Web proxies can be configured with organization-defined lists of authorized and unauthorized websites. Related controls: AC-3, AU-2. | link | count: 001 Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-8 | FedRAMP_Moderate_R4_SC-8 | FedRAMP Moderate SC-8 | System And Communications Protection | Transmission Confidentiality And Integrity | Shared | n/a | The information system protects the [Selection (one or more): confidentiality; integrity] of transmitted information. Supplemental Guidance: This control applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and/or integrity of organizational information can be accomplished by physical means (e.g., by employing physical distribution systems) or by logical means (e.g., employing encryption techniques). Organizations relying on commercial providers offering transmission services as commodity services rather than as fully dedicated services (i.e., services which can be highly specialized to individual customer needs), may find it difficult to obtain the necessary assurances regarding the implementation of needed security controls for transmission confidentiality/integrity. In such situations, organizations determine what types of confidentiality/integrity services are available in standard, commercial telecommunication service packages. If it is infeasible or impractical to obtain the necessary security controls and assurances of control effectiveness through appropriate contracting vehicles, organizations implement appropriate compensating security controls or explicitly accept the additional risk. Related controls: AC-17, PE-4. References: FIPS Publications 140-2, 197; NIST Special Publications 800-52, 800-77, 800-81, 800-113; CNSS Policy 15; NSTISSI No. 7003. | link | count: 015 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, Regulatory Compliance, SQL, Storage | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SC-8(1) | FedRAMP_Moderate_R4_SC-8(1) | FedRAMP Moderate SC-8 (1) | System And Communications Protection | Cryptographic Or Alternate Physical Protection | Shared | n/a | The information system implements cryptographic mechanisms to [Selection (one or more): prevent unauthorized disclosure of information; detect changes to information] during transmission unless otherwise protected by [Assignment: organization-defined alternative physical safeguards]. Supplemental Guidance: Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions which have common application in digital signatures, checksums, and message authentication codes. Alternative physical security safeguards include, for example, protected distribution systems. Related control: SC-13. | link | count: 014 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, Regulatory Compliance, SQL, Storage | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-1 | FedRAMP_Moderate_R4_SI-1 | FedRAMP Moderate SI-1 | System And Information Integrity | System And Information Integrity Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system and information integrity policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls; and b. Reviews and updates the current: 1. System and information integrity policy [Assignment: organization-defined frequency]; and 2. System and information integrity procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SI family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-10 | FedRAMP_Moderate_R4_SI-10 | FedRAMP Moderate SI-10 | System And Information Integrity | Information Input Validation | Shared | n/a | The information system checks the validity of [Assignment: organization-defined information inputs]. Supplemental Guidance: Checking the valid syntax and semantics of information system inputs (e.g., character set, length, numerical range, and acceptable values) verifies that inputs match specified definitions for format and content. Software applications typically follow well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If software applications use attacker- supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the tainted output will perform the wrong operations or otherwise interpret the data incorrectly. Prescreening inputs prior to passing to interpreters prevents the content from being unintentionally interpreted as commands. Input validation helps to ensure accurate and correct inputs and prevent attacks such as cross-site scripting and a variety of injection attacks. References: None. | link | count: 001 Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-11 | FedRAMP_Moderate_R4_SI-11 | FedRAMP Moderate SI-11 | System And Information Integrity | Error Handling | Shared | n/a | The information system: a. Generates error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries; and b. Reveals error messages only to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information such as account numbers, social security numbers, and credit card numbers. In addition, error messages may provide a covert channel for transmitting information. Related controls: AU-2, AU-3, SC-31. Control Enhancements: None. References: None. | link | count: 002 Generate error messages (c2cb4658-44dc-9d11-3dad-7c6802dd5ba3), Reveal error messages (20762f1e-85fb-31b0-a600-e833633f10fe) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-12 | FedRAMP_Moderate_R4_SI-12 | FedRAMP Moderate SI-12 | System And Information Integrity | Information Handling And Retention | Shared | n/a | The organization handles and retains information within the information system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements. Supplemental Guidance: Information handling and retention requirements cover the full life cycle of information, in some cases extending beyond the disposal of information systems. The National Archives and Records Administration provides guidance on records retention. Related controls: AC-16, AU-5, AU-11, MP-2, MP-4. Control Enhancements: None. References: None. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-16 | FedRAMP_Moderate_R4_SI-16 | FedRAMP Moderate SI-16 | System And Information Integrity | Memory Protection | Shared | n/a | The information system implements [Assignment: organization-defined security safeguards] to protect its memory from unauthorized code execution. Supplemental Guidance: Some adversaries launch attacks with the intent of executing code in non- executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. Related controls: AC-25, SC-3. Control Enhancements: None. References: None. | link | count: 002 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-2 | FedRAMP_Moderate_R4_SI-2 | FedRAMP Moderate SI-2 | System And Information Integrity | Flaw Remediation | Shared | n/a | The organization: a. Identifies, reports, and corrects information system flaws; b. Tests software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation; c. Installs security-relevant software and firmware updates within [Assignment: organization- defined time period] of the release of the updates; and d. Incorporates flaw remediation into the organizational configuration management process. Supplemental Guidance: Organizations identify information systems affected by announced software flaws including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security responsibilities. Security-relevant software updates include, for example, patches, service packs, hot fixes, and anti-virus signatures. Organizations also address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations take advantage of available resources such as the Common Weakness Enumeration (CWE) or Common Vulnerabilities and Exposures (CVE) databases in remediating flaws discovered in organizational information systems. By incorporating flaw remediation into ongoing configuration management processes, required/anticipated remediation actions can be tracked and verified. Flaw remediation actions that can be tracked and verified include, for example, determining whether organizations follow US-CERT guidance and Information Assurance Vulnerability Alerts. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types. Organizations determine the degree and type of testing needed for the specific type of flaw remediation activity under consideration and also the types of changes that are to be configuration-managed. In some situations, organizations may determine that the testing of software and/or firmware updates is not necessary or practical, for example, when implementing simple anti-virus signature updates. Organizations may also consider in testing decisions, whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures. Related controls: CA-2, CA-7, CM-3, CM-5, CM-8, MA-2, IR-4, RA-5, SA-10, SA-11, SI-11. | link | count: 019 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
App Service, Regulatory Compliance, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-2(2) | FedRAMP_Moderate_R4_SI-2(2) | FedRAMP Moderate SI-2 (2) | System And Information Integrity | Automated Flaw Remediation Status | Shared | n/a | The organization employs automated mechanisms [Assignment: organization-defined frequency] to determine the state of information system components with regard to flaw remediation. Supplemental Guidance: Related controls: CM-6, SI-4. | link | count: 002 Automate flaw remediation (a90c4d44-7fac-8e02-6d5b-0d92046b20e6), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-2(3) | FedRAMP_Moderate_R4_SI-2(3) | FedRAMP Moderate SI-2 (3) | System And Information Integrity | Time To Remediate Flaws / Benchmarks For Corrective Actions | Shared | n/a | The organization: (a) Measures the time between flaw identification and flaw remediation; and (b) Establishes [Assignment: organization-defined benchmarks] for taking corrective actions. Supplemental Guidance: This control enhancement requires organizations to determine the current time it takes on the average to correct information system flaws after such flaws have been identified, and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by type of flaw and/or severity of the potential vulnerability if the flaw can be exploited. | link | count: 002 Establish benchmarks for flaw remediation (dd2523d5-2db3-642b-a1cf-83ac973b32c2), Measure the time between flaw identification and flaw remediation (dad1887d-161b-7b61-2e4d-5124a7b5724e) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-3 | FedRAMP_Moderate_R4_SI-3 | FedRAMP Moderate SI-3 | System And Information Integrity | Malicious Code Protection | Shared | n/a | The organization: a. Employs malicious code protection mechanisms at information system entry and exit points to detect and eradicate malicious code; b. Updates malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures; c. Configures malicious code protection mechanisms to: 1. Perform periodic scans of the information system [Assignment: organization-defined frequency] and real-time scans of files from external sources at [Selection (one or more); endpoint; network entry/exit points] as the files are downloaded, opened, or executed in accordance with organizational security policy; and 2. [Selection (one or more): block malicious code; quarantine malicious code; send alert to administrator; [Assignment: organization-defined action]] in response to malicious code detection; and d. Addresses the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the information system. Supplemental Guidance: Information system entry and exit points include, for example, firewalls, electronic mail servers, web servers, proxy servers, remote-access servers, workstations, notebook computers, and mobile devices. Malicious code includes, for example, viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using steganography. Malicious code can be transported by different means including, for example, web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of information system vulnerabilities. Malicious code protection mechanisms include, for example, anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include, for example, logic bombs, back doors, and other types of cyber attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including, for example, secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. Organizations may determine that in response to the detection of malicious code, different actions may be warranted. For example, organizations can define actions in response to malicious code detection during periodic scans, actions in response to detection of malicious downloads, and/or actions in response to detection of maliciousness when attempting to open or execute files. Related controls: CM-3, MP-2, SA-4, SA-8, SA-12, SA-13, SC-7, SC-26, SC-44, SI-2, SI-4, SI-7. References: NIST Special Publication 800-83. | link | count: 011 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Regulatory Compliance, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-3(1) | FedRAMP_Moderate_R4_SI-3(1) | FedRAMP Moderate SI-3 (1) | System And Information Integrity | Central Management | Shared | n/a | The organization centrally manages malicious code protection mechanisms. Supplemental Guidance: Central management is the organization-wide management and implementation of malicious code protection mechanisms. Central management includes planning, implementing, assessing, authorizing, and monitoring the organization-defined, centrally managed flaw malicious code protection security controls. Related controls: AU-2, SI-8. | link | count: 010 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Regulatory Compliance, Security Center | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-3(2) | FedRAMP_Moderate_R4_SI-3(2) | FedRAMP Moderate SI-3 (2) | System And Information Integrity | Automatic Updates | Shared | n/a | The information system automatically updates malicious code protection mechanisms. Supplemental Guidance: Malicious code protection mechanisms include, for example, signature definitions. Due to information system integrity and availability concerns, organizations give careful consideration to the methodology used to carry out automatic updates. Related control: SI-8. | link | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-3(7) | FedRAMP_Moderate_R4_SI-3(7) | FedRAMP Moderate SI-3 (7) | System And Information Integrity | Nonsignature-Based Detection | Shared | n/a | The information system implements nonsignature-based malicious code detection mechanisms. Supplemental Guidance: Nonsignature-based detection mechanisms include, for example, the use of heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide safeguards against malicious code for which signatures do not yet exist or for which existing signatures may not be effective. This includes polymorphic malicious code (i.e., code that changes signatures when it replicates). This control enhancement does not preclude the use of signature-based detection mechanisms. | link | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-4 | FedRAMP_Moderate_R4_SI-4 | FedRAMP Moderate SI-4 | System And Information Integrity | Information System Monitoring | Shared | n/a | The organization: a. Monitors the information system to detect: 1. Attacks and indicators of potential attacks in accordance with [Assignment: organization- defined monitoring objectives]; and 2. Unauthorized local, network, and remote connections; b. Identifies unauthorized use of the information system through [Assignment: organization- defined techniques and methods]; c. Deploys monitoring devices: (i) strategically within the information system to collect organization-determined essential information; and (ii) at ad hoc locations within the system to track specific types of transactions of interest to the organization; d. Protects information obtained from intrusion-monitoring tools from unauthorized access, modification, and deletion; e. Heightens the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information; f. Obtains legal opinion with regard to information system monitoring activities in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations; and g. Provides [Assignment: or ganization-defined information system monitoring information] to [Assignment: organization-defined personnel or roles] [Selection (one or more): as needed; [Assignment: organization-defined frequency]]. Supplemental Guidance: Information system monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at the information system boundary (i.e., part of perimeter defense and boundary protection). Internal monitoring includes the observation of events occurring within the information system. Organizations can monitor information systems, for example, by observing audit activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives may guide determination of the events. Information system monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Strategic locations for monitoring devices include, for example, selected perimeter locations and near server farms supporting critical applications, with such devices typically being employed at the managed interfaces associated with controls SC-7 and AC-17. Einstein network monitoring devices from the Department of Homeland Security can also be included as monitoring devices. The granularity of monitoring information collected is based on organizational monitoring objectives and the capability of information systems to support such objectives. Specific types of transactions of interest include, for example, Hyper Text Transfer Protocol (HTTP) traffic that bypasses HTTP proxies. Information system monitoring is an integral part of organizational continuous monitoring and incident response programs. Output from system monitoring serves as input to continuous monitoring and incident response programs. A network connection is any connection with a device that communicates through a network (e.g., local area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Local, network, and remote connections can be either wired or wireless. Related controls: AC-3, AC-4, AC-8, AC-17, AU-2, AU-6, AU-7, AU-9, AU-12, CA-7, IR-4, PE-3, RA-5, SC-7, SC-26, SC-35, SI-3, SI-7. References: NIST Special Publications 800-61, 800-83, 800-92, 800-94, 800-137. | link | count: 025 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-4(14) | FedRAMP_Moderate_R4_SI-4(14) | FedRAMP Moderate SI-4 (14) | System And Information Integrity | Wireless Intrusion Detection | Shared | n/a | The organization employs a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises/breaches to the information system. Supplemental Guidance: Wireless signals may radiate beyond the confines of organization- controlled facilities. Organizations proactively search for unauthorized wireless connections including the conduct of thorough scans for unauthorized wireless access points. Scans are not limited to those areas within facilities containing information systems, but also include areas outside of facilities as needed, to verify that unauthorized wireless access points are not connected to the systems. Related controls: AC-18, IA-3. | link | count: 001 Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-4(2) | FedRAMP_Moderate_R4_SI-4(2) | FedRAMP Moderate SI-4 (2) | System And Information Integrity | Automated Tools For Real-Time Analysis | Shared | n/a | The organization employs automated tools to support near real-time analysis of events. Supplemental Guidance: Automated tools include, for example, host-based, network-based, transport-based, or storage-based event monitoring tools or Security Information and Event Management (SIEM) technologies that provide real time analysis of alerts and/or notifications generated by organizational information systems. | link | count: 002 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-4(4) | FedRAMP_Moderate_R4_SI-4(4) | FedRAMP Moderate SI-4 (4) | System And Information Integrity | Inbound And Outbound Communications Traffic | Shared | n/a | The information system monitors inbound and outbound communications traffic [Assignment: organization-defined frequency] for unusual or unauthorized activities or conditions. Supplemental Guidance: Unusual/unauthorized activities or conditions related to information system inbound and outbound communications traffic include, for example, internal traffic that indicates the presence of malicious code within organizational information systems or propagating among system components, the unauthorized exporting of information, or signaling to external information systems. Evidence of malicious code is used to identify potentially compromised information systems or information system components. | link | count: 004 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-4(5) | FedRAMP_Moderate_R4_SI-4(5) | FedRAMP Moderate SI-4 (5) | System And Information Integrity | System-Generated Alerts | Shared | n/a | The information system alerts [Assignment: organization-defined personnel or roles] when the following indications of compromise or potential compromise occur: [Assignment: organization- defined compromise indicators]. Supplemental Guidance: Alerts may be generated from a variety of sources, including, for example, audit records or inputs from malicious code protection mechanisms, intrusion detection or prevention mechanisms, or boundary protection devices such as firewalls, gateways, and routers. Alerts can be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. Organizational personnel on the notification list can include, for example, system administrators, mission/business owners, system owners, or information system security officers. Related controls: AU-5, PE-6. | link | count: 003 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-5 | FedRAMP_Moderate_R4_SI-5 | FedRAMP Moderate SI-5 | System And Information Integrity | Security Alerts, Advisories, And Directives | Shared | n/a | The organization: a. Receives information system security alerts, advisories, and directives from [Assignment: organization-defined external organizations] on an ongoing basis; b. Generates internal security alerts, advisories, and directives as deemed necessary; c. Disseminates security alerts, advisories, and directives to: [Selection (one or more): [Assignment: organization-defined personnel or roles]; [Assignment: organization-defined elements within the organization]; [Assignment: organization-defined external organizations]]; and d. Implements security directives in accordance with established time frames, or notifies the issuing organization of the degree of noncompliance. Supplemental Guidance: The United States Computer Emergency Readiness Team (US-CERT) generates security alerts and advisories to maintain situational awareness across the federal government. Security directives are issued by OMB or other designated organizations with the responsibility and authority to issue such directives. Compliance to security directives is essential due to the critical nature of many of these directives and the potential immediate adverse effects on organizational operations and assets, individuals, other organizations, and the Nation should the directives not be implemented in a timely manner. External organizations include, for example, external mission/business partners, supply chain partners, external service providers, and other peer/supporting organizations. Related control: SI-2. References: NIST Special Publication 800-40. | link | count: 004 Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Generate internal security alerts (171e377b-5224-4a97-1eaa-62a3b5231dac), Implement security directives (26d178a4-9261-6f04-a100-47ed85314c6e) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-6 | FedRAMP_Moderate_R4_SI-6 | FedRAMP Moderate SI-6 | System And Information Integrity | Security Function Verification | Shared | n/a | The information system: a. Verifies the correct operation of [Assignment: organization-defined security functions]; b. Performs this verification [Selection (one or more): [Assignment: organization-defined system transitional states]; upon command by user with appropriate privilege; [Assignment: organization-defined frequency]]; c. Notifies [Assignment: organization-defined personnel or roles] of failed security verification tests; and d. [Selection (one or more): shuts the information system down; restarts the information system; [Assignment: organization-defined alternative action(s)]] when anomalies are discovered. Supplemental Guidance: Transitional states for information systems include, for example, system startup, restart, shutdown, and abort. Notifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications such as lights. Related controls: CA-7, CM-6. References: None. | link | count: 004 Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Notify personnel of any failed security verification tests (18e9d748-73d4-0c96-55ab-b108bfbd5bc3), Perform security function verification at a defined frequency (f30edfad-4e1d-1eef-27ee-9292d6d89842), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-7 | FedRAMP_Moderate_R4_SI-7 | FedRAMP Moderate SI-7 | System And Information Integrity | Software, Firmware, And Information Integrity | Shared | n/a | The organization employs integrity verification tools to detect unauthorized changes to [Assignment: organization-defined software, firmware, and information]. Supplemental Guidance: Unauthorized changes to software, firmware, and information can occur due to errors or malicious activity (e.g., tampering). Software includes, for example, operating systems (with key internal components such as kernels, drivers), middleware, and applications. Firmware includes, for example, the Basic Input Output System (BIOS). Information includes metadata such as security attributes associated with information. State-of-the-practice integrity- checking mechanisms (e.g., parity checks, cyclical redundancy checks, cryptographic hashes) and associated tools can automatically monitor the integrity of information systems and hosted applications. Related controls: SA-12, SC-8, SC-13, SI-3. References: NIST Special Publications 800-147, 800-155. | link | count: 001 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| FedRAMP_Moderate_R4 | SI-7(1) | FedRAMP_Moderate_R4_SI-7(1) | FedRAMP Moderate SI-7 (1) | System And Information Integrity | Integrity Checks | Shared | n/a | The information system performs an integrity check of [Assignment: organization-defined software, firmware, and information] [Selection (one or more): at startup; at [Assignment: organization-defined transitional states or security-relevant events]; [Assignment: organization- defined frequency]]. Supplemental Guidance: Security-relevant events include, for example, the identification of a new threat to which organizational information systems are susceptible, and the installation of new hardware, software, or firmware. Transitional states include, for example, system startup, restart, shutdown, and abort. | link | count: 002 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | FedRAMP Moderate (e95f5a9f-57ad-4d03-bb0b-b1d16db93693) |
| hipaa | 0101.00a1Organizational.123-00.a | hipaa-0101.00a1Organizational.123-00.a | 0101.00a1Organizational.123-00.a | 01 Information Protection Program | 0101.00a1Organizational.123-00.a 0.01 Information Security Management Program | Shared | n/a | The organization has a formal information protection program based on an accepted industry framework that is reviewed and updated as needed. | count: 005 Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Protect the information security program plan (2e7a98c9-219f-0d58-38dc-d69038224442), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0102.00a2Organizational.123-00.a | hipaa-0102.00a2Organizational.123-00.a | 0102.00a2Organizational.123-00.a | 01 Information Protection Program | 0102.00a2Organizational.123-00.a 0.01 Information Security Management Program | Shared | n/a | The information protection program is formally documented and actively monitored, reviewed, and updated to ensure program objectives continue to be met. | count: 003 Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0103.00a3Organizational.1234567-00.a | hipaa-0103.00a3Organizational.1234567-00.a | 0103.00a3Organizational.1234567-00.a | 01 Information Protection Program | 0103.00a3Organizational.1234567-00.a 0.01 Information Security Management Program | Shared | n/a | Independent audits are conducted at least annually to determine whether the information protection program is approved by executive management, communicated to stakeholders, adequately resourced, conforms to relevant legislation or regulations and other business requirements, and adjusted as needed to ensure the program continues to meet defined objectives. | count: 003 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0104.02a1Organizational.12-02.a | hipaa-0104.02a1Organizational.12-02.a | 0104.02a1Organizational.12-02.a | 01 Information Protection Program | 0104.02a1Organizational.12-02.a 02.01 Prior to Employment | Shared | n/a | User security roles and responsibilities are clearly defined and communicated. | count: 014 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0105.02a2Organizational.1-02.a | hipaa-0105.02a2Organizational.1-02.a | 0105.02a2Organizational.1-02.a | 01 Information Protection Program | 0105.02a2Organizational.1-02.a 02.01 Prior to Employment | Shared | n/a | Risk designations are assigned for all positions within the organization as appropriate, with commensurate screening criteria, and reviewed/revised every 365 days. | count: 006 Assign risk designations (b7897ddc-9716-2460-96f7-7757ad038cc4), Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Rescreen individuals at a defined frequency (c6aeb800-0b19-944d-92dc-59b893722329) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0106.02a2Organizational.23-02.a | hipaa-0106.02a2Organizational.23-02.a | 0106.02a2Organizational.23-02.a | 01 Information Protection Program | 0106.02a2Organizational.23-02.a 02.01 Prior to Employment | Shared | n/a | The pre-employment process is reviewed by recruitment to ensure security roles/responsibilities are specifically defined (in writing) and clearly communicated to job candidates. | count: 004 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Rescreen individuals at a defined frequency (c6aeb800-0b19-944d-92dc-59b893722329) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0107.02d1Organizational.1-02.d | hipaa-0107.02d1Organizational.1-02.d | 0107.02d1Organizational.1-02.d | 01 Information Protection Program | 0107.02d1Organizational.1-02.d 02.03 During Employment | Shared | n/a | The organization has an information security workforce improvement program. | count: 001 Establish information security workforce development and improvement program (b544f797-a73b-1be3-6d01-6b1a085376bc) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0108.02d1Organizational.23-02.d | hipaa-0108.02d1Organizational.23-02.d | 0108.02d1Organizational.23-02.d | 01 Information Protection Program | 0108.02d1Organizational.23-02.d 02.03 During Employment | Shared | n/a | The organization ensures plans for security testing, training, and monitoring activities are developed, implemented, maintained, and reviewed for consistency with the risk management strategy and response priorities. | count: 008 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Implement security testing, training, and monitoring plans (21832235-7a07-61f4-530d-d596f76e5b95), Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Require developers to provide training (676c3c35-3c36-612c-9523-36d266a65000), Retain training records (3153d9c0-2584-14d3-362d-578b01358aeb), Review security testing, training, and monitoring plans (c3b3cc61-9c70-5d78-7f12-1aefcc477db7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0109.02d1Organizational.4-02.d | hipaa-0109.02d1Organizational.4-02.d | 0109.02d1Organizational.4-02.d | 01 Information Protection Program | 0109.02d1Organizational.4-02.d 02.03 During Employment | Shared | n/a | Management ensures users are (i) briefed on their security role(s)/responsibilities, conform with the terms and conditions of employment prior to obtaining access to the organization’s information systems; (ii) provided with guidelines regarding the security expectations of their roles; (iii) motivated to comply with security policies; and, (iv) continue to have the appropriate skills and qualifications for their role(s). | count: 020 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide role-based practical exercises (d041726f-00e0-41ca-368c-b1a122066482), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide role-based training on suspicious activities (f6794ab8-9a7d-3b24-76ab-265d3646232b), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0110.02d2Organizational.1-02.d | hipaa-0110.02d2Organizational.1-02.d | 0110.02d2Organizational.1-02.d | 01 Information Protection Program | 0110.02d2Organizational.1-02.d 02.03 During Employment | Shared | n/a | An individual or dedicated team is assigned to manage the information security of the organization's users. | count: 002 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Establish information security workforce development and improvement program (b544f797-a73b-1be3-6d01-6b1a085376bc) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0111.02d2Organizational.2-02.d | hipaa-0111.02d2Organizational.2-02.d | 0111.02d2Organizational.2-02.d | 01 Information Protection Program | 0111.02d2Organizational.2-02.d 02.03 During Employment | Shared | n/a | Non-employees are provided the organization's data privacy and security policy requirements prior to accessing system resources and data. | count: 009 Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 01110.05a1Organizational.5-05.a | hipaa-01110.05a1Organizational.5-05.a | 01110.05a1Organizational.5-05.a | 01 Information Protection Program | 01110.05a1Organizational.5-05.a 05.01 Internal Organization | Shared | n/a | If the senior-level information security official is employed by the organization, one of its affiliates, or a third-party service, the organization retains responsibility for its cybersecurity program, designates a senior member of the organization responsible for direction and oversight, and requires the third-party service to maintain an appropriate cybersecurity program of its own. | count: 004 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 01111.05a2Organizational.5-05.a | hipaa-01111.05a2Organizational.5-05.a | 01111.05a2Organizational.5-05.a | 01 Information Protection Program | 01111.05a2Organizational.5-05.a 05.01 Internal Organization | Shared | n/a | The CISO of the organization reports in writing on the organization's cybersecurity program and material cybersecurity risks, at least annually, to the organization's board of directors, equivalent governing body, or suitable committee. | count: 001 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0112.02d2Organizational.3-02.d | hipaa-0112.02d2Organizational.3-02.d | 0112.02d2Organizational.3-02.d | 01 Information Protection Program | 0112.02d2Organizational.3-02.d 02.03 During Employment | Shared | n/a | Acceptable usage is defined and usage is explicitly authorized. | count: 007 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Enforce appropriate usage of all accounts (fd81a1b3-2d7a-107c-507e-29b87d040c19), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Require compliance with intellectual property rights (725164e5-3b21-1ec2-7e42-14f077862841), Track software license usage (77cc89bb-774f-48d7-8a84-fb8c322c3000) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0113.04a1Organizational.123-04.a | hipaa-0113.04a1Organizational.123-04.a | 0113.04a1Organizational.123-04.a | 01 Information Protection Program | 0113.04a1Organizational.123-04.a 04.01 Information Security Policy | Shared | n/a | Information security objectives, approach, scope, importance, goals, and principles for the organization’s security program are formally identified, communicated throughout the organization to users in a form that is relevant, accessible, and understandable to the intended reader; and supported by a controls framework that considers legislative, regulatory, contractual requirements, and other policy-related requirements. | count: 003 Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Protect the information security program plan (2e7a98c9-219f-0d58-38dc-d69038224442), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0114.04b1Organizational.1-04.b | hipaa-0114.04b1Organizational.1-04.b | 0114.04b1Organizational.1-04.b | 01 Information Protection Program | 0114.04b1Organizational.1-04.b 04.01 Information Security Policy | Shared | n/a | The security policies are regularly reviewed and updated to ensure they reflect leading practices (e.g., for systems and services development and acquisition), and are communicated throughout the organization. | count: 009 Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0115.04b2Organizational.123-04.b | hipaa-0115.04b2Organizational.123-04.b | 0115.04b2Organizational.123-04.b | 01 Information Protection Program | 0115.04b2Organizational.123-04.b 04.01 Information Security Policy | Shared | n/a | The owner of the security policies has management approval and assigned responsibility to develop, review, update (based on specific input), and approve the security policies; and such reviews, updates, and approvals occur no less than annually. | count: 020 Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0116.04b3Organizational.1-04.b | hipaa-0116.04b3Organizational.1-04.b | 0116.04b3Organizational.1-04.b | 01 Information Protection Program | 0116.04b3Organizational.1-04.b 04.01 Information Security Policy | Shared | n/a | The security policy reviews consider all appropriate elements that could impact the organization's risk profile. | count: 004 Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0117.05a1Organizational.1-05.a | hipaa-0117.05a1Organizational.1-05.a | 0117.05a1Organizational.1-05.a | 01 Information Protection Program | 0117.05a1Organizational.1-05.a 05.01 Internal Organization | Shared | n/a | A senior-level information security official is appointed and is responsible for ensuring security processes are in place, communicated to all stakeholders, and consider and address organizational requirements. | count: 001 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0118.05a1Organizational.2-05.a | hipaa-0118.05a1Organizational.2-05.a | 0118.05a1Organizational.2-05.a | 01 Information Protection Program | 0118.05a1Organizational.2-05.a 05.01 Internal Organization | Shared | n/a | Senior management assigns an individual or group to ensure the effectiveness of the information protection program through program oversight; establish and communicate the organization's priorities for organizational mission, objectives, and activities; review and update of the organization's security plan; ensure compliance with the security plan by the workforce; and evaluate and accept security risks on behalf of the organization. | count: 008 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish information security workforce development and improvement program (b544f797-a73b-1be3-6d01-6b1a085376bc), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0119.05a1Organizational.3-05.a | hipaa-0119.05a1Organizational.3-05.a | 0119.05a1Organizational.3-05.a | 01 Information Protection Program | 0119.05a1Organizational.3-05.a 05.01 Internal Organization | Shared | n/a | Security contacts are appointed by name for each major organizational area or business unit. | count: 006 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0120.05a1Organizational.4-05.a | hipaa-0120.05a1Organizational.4-05.a | 0120.05a1Organizational.4-05.a | 01 Information Protection Program | 0120.05a1Organizational.4-05.a 05.01 Internal Organization | Shared | n/a | Capital planning and investment requests include the resources needed to implement the security program, employ a business case (or Exhibit 300 and/or 53 for federal government); and the organization ensures the resources are available for expenditure as planned. | count: 008 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Allocate resources in determining information system requirements (90a156a6-49ed-18d1-1052-69aac27c05cd), Employ business case to record the resources required (2d14ff7e-6ff9-838c-0cde-4962ccdb1689), Ensure capital planning and investment requests include necessary resources (464a7d7a-2358-4869-0b49-6d582ca21292), Establish a discrete line item in budgeting documentation (06af77de-02ca-0f3e-838a-a9420fe466f5), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0121.05a2Organizational.12-05.a | hipaa-0121.05a2Organizational.12-05.a | 0121.05a2Organizational.12-05.a | 01 Information Protection Program | 0121.05a2Organizational.12-05.a 05.01 Internal Organization | Shared | n/a | The organization's information protection and risk management programs, including the risk assessment process, are formally approved, and are reviewed for effectiveness and updated annually. | count: 006 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0122.05a2Organizational.3-05.a | hipaa-0122.05a2Organizational.3-05.a | 0122.05a2Organizational.3-05.a | 01 Information Protection Program | 0122.05a2Organizational.3-05.a 05.01 Internal Organization | Shared | n/a | The individual responsible for information security in the organization is qualified for the role. | count: 006 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0123.05a2Organizational.4-05.a | hipaa-0123.05a2Organizational.4-05.a | 0123.05a2Organizational.4-05.a | 01 Information Protection Program | 0123.05a2Organizational.4-05.a 05.01 Internal Organization | Shared | n/a | Security contacts are formally appointed in writing for each major organizational area or business unit. | count: 002 Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Manage contacts for authorities and special interest groups (5269d7e4-3768-501d-7e46-66c56c15622c) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0124.05a3Organizational.1-05.a | hipaa-0124.05a3Organizational.1-05.a | 0124.05a3Organizational.1-05.a | 01 Information Protection Program | 0124.05a3Organizational.1-05.a 05.01 Internal Organization | Shared | n/a | An information security management committee is chartered and active. | count: 002 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0125.05a3Organizational.2-05.a | hipaa-0125.05a3Organizational.2-05.a | 0125.05a3Organizational.2-05.a | 01 Information Protection Program | 0125.05a3Organizational.2-05.a 05.01 Internal Organization | Shared | n/a | Annual risk assessments are performed by an independent organization. | count: 008 Accept assessment results (3054c74b-9b45-2581-56cf-053a1a716c39), Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0135.02f1Organizational.56-02.f | hipaa-0135.02f1Organizational.56-02.f | 0135.02f1Organizational.56-02.f | 01 Information Protection Program | 0135.02f1Organizational.56-02.f 02.03 During Employment | Shared | n/a | The organization employs a formal sanctions process for personnel failing to comply with established information security policies and procedures, and notifies defined personnel (e.g., supervisors) within a defined time frame (e.g., 24 hours) when a formal sanction process is initiated, identifying the individual sanctioned and the reason for the sanction. Further, the organization includes specific procedures for license, registration, and certification denial or revocation and other disciplinary action. | count: 004 Establish information security workforce development and improvement program (b544f797-a73b-1be3-6d01-6b1a085376bc), Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0137.02a1Organizational.3-02.a | hipaa-0137.02a1Organizational.3-02.a | 0137.02a1Organizational.3-02.a | 01 Information Protection Program | 0137.02a1Organizational.3-02.a 02.01 Prior to Employment | Shared | n/a | The organization formally addresses the purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance requirements for its human resources security protection program (e.g., through policy, standards, guidelines, and procedures). | count: 001 Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0162.04b1Organizational.2-04.b | hipaa-0162.04b1Organizational.2-04.b | 0162.04b1Organizational.2-04.b | 01 Information Protection Program | 0162.04b1Organizational.2-04.b 04.01 Information Security Policy | Shared | n/a | The organization ensures individuals may make complaints concerning the information security policies, procedures, or the organization's compliance with its policies and procedures; documents the complaints and requests for changes; and records their disposition, if applicable. | count: 004 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0165.05a3Organizational.3-05.a | hipaa-0165.05a3Organizational.3-05.a | 0165.05a3Organizational.3-05.a | 01 Information Protection Program | 0165.05a3Organizational.3-05.a 05.01 Internal Organization | Shared | n/a | The organization publishes security guidelines and/or daily operational procedures relating to processes that complement, clarify, and enforce security policies. | count: 001 Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0177.05h1Organizational.12-05.h | hipaa-0177.05h1Organizational.12-05.h | 0177.05h1Organizational.12-05.h | 01 Information Protection Program | 0177.05h1Organizational.12-05.h 05.01 Internal Organization | Shared | n/a | An independent review of the organization's information security management program is initiated by management to ensure the continuing suitability, adequacy, and effectiveness of the organization's approach to managing information security. | count: 005 Accept assessment results (3054c74b-9b45-2581-56cf-053a1a716c39), Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb), Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0178.05h1Organizational.3-05.h | hipaa-0178.05h1Organizational.3-05.h | 0178.05h1Organizational.3-05.h | 01 Information Protection Program | 0178.05h1Organizational.3-05.h 05.01 Internal Organization | Shared | n/a | The results of independent security program reviews are recorded and reported to the management official/office initiating the review; and the results are maintained for a predetermined period of time as determined by the organization, but not less than three years. | count: 003 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0179.05h1Organizational.4-05.h | hipaa-0179.05h1Organizational.4-05.h | 0179.05h1Organizational.4-05.h | 01 Information Protection Program | 0179.05h1Organizational.4-05.h 05.01 Internal Organization | Shared | n/a | If an independent review identifies that the organization's approach and implementation to managing information security is inadequate or not compliant with the direction for information security stated in the information security policy document, management takes corrective actions. | count: 003 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement plans of action and milestones for security program process (d93fe1be-13e4-421d-9c21-3158e2fa2667) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0180.05h2Organizational.1-05.h | hipaa-0180.05h2Organizational.1-05.h | 0180.05h2Organizational.1-05.h | 01 Information Protection Program | 0180.05h2Organizational.1-05.h 05.01 Internal Organization | Shared | n/a | An independent review of the information security management program and information security controls is conducted at least annually or whenever there is a material change to the business practices that may implicate the security or integrity of records containing personal information. | count: 001 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0201.09j1Organizational.124-09.j | hipaa-0201.09j1Organizational.124-09.j | 0201.09j1Organizational.124-09.j | 02 Endpoint Protection | 0201.09j1Organizational.124-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | Anti-virus and anti-spyware are installed, operating and updated on all end-user devices to conduct periodic scans of the systems to identify and remove unauthorized software. Server environments for which the server software developer specifically recommends not installing host-based anti-virus and anti-spyware software are addressed via a network-based malware detection (NBMD) solution. | count: 018 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Deploy default Microsoft IaaSAntimalware extension for Windows Server (2835b622-407b-4114-9198-6f7064cbe0dc), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Compute, Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0202.09j1Organizational.3-09.j | hipaa-0202.09j1Organizational.3-09.j | 0202.09j1Organizational.3-09.j | 02 Endpoint Protection | 0202.09j1Organizational.3-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | Audit logs of the scans are maintained. | count: 015 Adjust level of audit review, analysis, and reporting (de251b09-4a5e-1204-4bef-62ac58d47999), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Integrate Audit record analysis (85335602-93f5-7730-830b-d43426fd51fa), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Specify permitted actions associated with customer audit information (3eecf628-a1c8-1b48-1b5c-7ca781e97970) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0204.09j2Organizational.1-09.j | hipaa-0204.09j2Organizational.1-09.j | 0204.09j2Organizational.1-09.j | 02 Endpoint Protection | 0204.09j2Organizational.1-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | Scans for malicious software are performed on boot and every 12 hours. | count: 011 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Notify personnel of any failed security verification tests (18e9d748-73d4-0c96-55ab-b108bfbd5bc3), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform security function verification at a defined frequency (f30edfad-4e1d-1eef-27ee-9292d6d89842), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0205.09j2Organizational.2-09.j | hipaa-0205.09j2Organizational.2-09.j | 0205.09j2Organizational.2-09.j | 02 Endpoint Protection | 0205.09j2Organizational.2-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | Malicious code that is identified is blocked, quarantined, and an alert is sent to the administrators. | count: 010 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0206.09j2Organizational.34-09.j | hipaa-0206.09j2Organizational.34-09.j | 0206.09j2Organizational.34-09.j | 02 Endpoint Protection | 0206.09j2Organizational.34-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | Anti-malware is centrally managed and cannot be disabled by the users. | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0207.09j2Organizational.56-09.j | hipaa-0207.09j2Organizational.56-09.j | 0207.09j2Organizational.56-09.j | 02 Endpoint Protection | 0207.09j2Organizational.56-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | Centrally-managed, up-to-date anti-spam and anti-malware protection is implemented at information system entry/exit points for the network and on all devices. | count: 007 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0208.09j2Organizational.7-09.j | hipaa-0208.09j2Organizational.7-09.j | 0208.09j2Organizational.7-09.j | 02 Endpoint Protection | 0208.09j2Organizational.7-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | User functionality (including user interface services [e.g., web services]) is separated from information system management (e.g., database management systems) functionality. | count: 004 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0209.09m3Organizational.7-09.m | hipaa-0209.09m3Organizational.7-09.m | 0209.09m3Organizational.7-09.m | 02 Endpoint Protection | 0209.09m3Organizational.7-09.m 09.06 Network Security Management | Shared | n/a | File sharing is disabled on wireless-enabled devices. | count: 006 Automate information sharing decisions (e54901fe-42c2-7f3b-3c5f-327aa5320a69), Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Facilitate information sharing (a44c9fba-43f8-4b7b-7ee6-db52c96b4366), Record disclosures of PII to third parties (8b1da407-5e60-5037-612e-2caa1b590719), Train staff on PII sharing and its consequences (8019d788-713d-90a1-5570-dac5052f517d), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0214.09j1Organizational.6-09.j | hipaa-0214.09j1Organizational.6-09.j | 0214.09j1Organizational.6-09.j | 02 Endpoint Protection | 0214.09j1Organizational.6-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | Protection against malicious code is based on malicious code detection and repair software, security awareness, and appropriate system access and change management controls. | count: 013 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0215.09j2Organizational.8-09.j | hipaa-0215.09j2Organizational.8-09.j | 0215.09j2Organizational.8-09.j | 02 Endpoint Protection | 0215.09j2Organizational.8-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | The organization addresses the receipt of false positives during malicious code detection and eradication, and the resulting potential impact on the availability of the information system. | count: 007 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0216.09j2Organizational.9-09.j | hipaa-0216.09j2Organizational.9-09.j | 0216.09j2Organizational.9-09.j | 02 Endpoint Protection | 0216.09j2Organizational.9-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | For systems considered not commonly affected by malicious software, the organization performs periodic assessments to identify and evaluate evolving malware threats to confirm whether such systems continue to not require anti-virus software. | count: 013 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0217.09j2Organizational.10-09.j | hipaa-0217.09j2Organizational.10-09.j | 0217.09j2Organizational.10-09.j | 02 Endpoint Protection | 0217.09j2Organizational.10-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | The organization configures malicious code and spam protection mechanisms to (i) perform periodic scans of the information system according to organization guidelines; (ii) perform real-time scans of files from external sources at endpoints and network entry/exit points as the files are downloaded, opened, or executed in accordance with organizational security policy; and, (iii) block malicious code, quarantine malicious code, or send an alert to the administrator in response to malicious code detection. | count: 025 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review exploit protection events (a30bd8e9-7064-312a-0e1f-e1b485d59f6e), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0219.09j2Organizational.12-09.j | hipaa-0219.09j2Organizational.12-09.j | 0219.09j2Organizational.12-09.j | 02 Endpoint Protection | 0219.09j2Organizational.12-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | The organization has implemented safeguards to protect its information system's memory from unauthorized code execution. | count: 007 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0225.09k1Organizational.1-09.k | hipaa-0225.09k1Organizational.1-09.k | 0225.09k1Organizational.1-09.k | 02 Endpoint Protection | 0225.09k1Organizational.1-09.k 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | Automated controls (e.g., browser settings) are in place to authorize and restrict the use of mobile code (e.g., Java, JavaScript, ActiveX, PDF, postscript, Shockwave movies, and Flash animations). | count: 010 Authorize, monitor, and control usage of mobile code technologies (291f20d4-8d93-1d73-89f3-6ce28b825563), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Define acceptable and unacceptable mobile code technologies (1afada58-8b34-7ac2-a38a-983218635201), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0226.09k1Organizational.2-09.k | hipaa-0226.09k1Organizational.2-09.k | 0226.09k1Organizational.2-09.k | 02 Endpoint Protection | 0226.09k1Organizational.2-09.k 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | The organization has implemented and regularly updates mobile code protection, including anti-virus and anti-spyware. | count: 009 Authorize, monitor, and control usage of mobile code technologies (291f20d4-8d93-1d73-89f3-6ce28b825563), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Define acceptable and unacceptable mobile code technologies (1afada58-8b34-7ac2-a38a-983218635201), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0227.09k2Organizational.12-09.k | hipaa-0227.09k2Organizational.12-09.k | 0227.09k2Organizational.12-09.k | 02 Endpoint Protection | 0227.09k2Organizational.12-09.k 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | The organization takes specific actions to protect against mobile code performing unauthorized actions. | count: 018 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Authorize, monitor, and control usage of mobile code technologies (291f20d4-8d93-1d73-89f3-6ce28b825563), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Define acceptable and unacceptable mobile code technologies (1afada58-8b34-7ac2-a38a-983218635201), Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0228.09k2Organizational.3-09.k | hipaa-0228.09k2Organizational.3-09.k | 0228.09k2Organizational.3-09.k | 02 Endpoint Protection | 0228.09k2Organizational.3-09.k 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | Rules for the migration of software from development to operational status are defined and documented by the organization hosting the affected application(s), including that development, test, and operational systems are separated (physically or virtually) to reduce the risks of unauthorized access or changes to the operational system. | count: 011 Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0301.09o1Organizational.123-09.o | hipaa-0301.09o1Organizational.123-09.o | 0301.09o1Organizational.123-09.o | 03 Portable Media Security | 0301.09o1Organizational.123-09.o 09.07 Media Handling | Shared | n/a | The organization, based on the data classification level, registers media (including laptops) prior to use, places reasonable restrictions on how such media are used, and provides an appropriate level of physical and logical protection (including encryption) for media containing covered information until properly destroyed or sanitized. | count: 014 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0302.09o2Organizational.1-09.o | hipaa-0302.09o2Organizational.1-09.o | 0302.09o2Organizational.1-09.o | 03 Portable Media Security | 0302.09o2Organizational.1-09.o 09.07 Media Handling | Shared | n/a | The organization protects and controls media containing sensitive information during transport outside of controlled areas. | count: 007 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0303.09o2Organizational.2-09.o | hipaa-0303.09o2Organizational.2-09.o | 0303.09o2Organizational.2-09.o | 03 Portable Media Security | 0303.09o2Organizational.2-09.o 09.07 Media Handling | Shared | n/a | Digital and non-digital media requiring restricted use, and the specific safeguards used to restrict their use are identified. | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0304.09o3Organizational.1-09.o | hipaa-0304.09o3Organizational.1-09.o | 0304.09o3Organizational.1-09.o | 03 Portable Media Security | 0304.09o3Organizational.1-09.o 09.07 Media Handling | Shared | n/a | The organization restricts the use of writable removable media and personally-owned removable media in organizational systems. | count: 008 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Require encryption on Data Lake Store accounts (a7ff3161-0087-490a-9ad9-ad6217f4f43a), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8) |
Data Lake, Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0305.09q1Organizational.12-09.q | hipaa-0305.09q1Organizational.12-09.q | 0305.09q1Organizational.12-09.q | 03 Portable Media Security | 0305.09q1Organizational.12-09.q 09.07 Media Handling | Shared | n/a | Media is labeled, encrypted, and handled according to its classification. | count: 007 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0306.09q1Organizational.3-09.q | hipaa-0306.09q1Organizational.3-09.q | 0306.09q1Organizational.3-09.q | 03 Portable Media Security | 0306.09q1Organizational.3-09.q 09.07 Media Handling | Shared | n/a | The status and location of unencrypted covered information is maintained and monitored. | count: 006 Automate information sharing decisions (e54901fe-42c2-7f3b-3c5f-327aa5320a69), Ensure authorized users protect provided authenticators (37dbe3dc-0e9c-24fa-36f2-11197cbfa207), Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3), Facilitate information sharing (a44c9fba-43f8-4b7b-7ee6-db52c96b4366), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0307.09q2Organizational.12-09.q | hipaa-0307.09q2Organizational.12-09.q | 0307.09q2Organizational.12-09.q | 03 Portable Media Security | 0307.09q2Organizational.12-09.q 09.07 Media Handling | Shared | n/a | Data transfers outside of controlled areas are approved and records of the transfers are maintained. | count: 002 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0308.09q3Organizational.1-09.q | hipaa-0308.09q3Organizational.1-09.q | 0308.09q3Organizational.1-09.q | 03 Portable Media Security | 0308.09q3Organizational.1-09.q 09.07 Media Handling | Shared | n/a | Inventory and disposition records of media are maintained. | count: 003 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0314.09q3Organizational.2-09.q | hipaa-0314.09q3Organizational.2-09.q | 0314.09q3Organizational.2-09.q | 03 Portable Media Security | 0314.09q3Organizational.2-09.q 09.07 Media Handling | Shared | n/a | The organization implements cryptographic mechanisms to protect the confidentiality and integrity of sensitive (non-public) information stored on digital media during transport outside of controlled areas. | count: 009 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0401.01x1System.124579-01.x | hipaa-0401.01x1System.124579-01.x | 0401.01x1System.124579-01.x | 04 Mobile Device Security | 0401.01x1System.124579-01.x 01.07 Mobile Computing and Teleworking | Shared | n/a | Mobile computing devices are protected at all times by access controls, usage restrictions, connection requirements, encryption, virus protections, host-based firewalls, or equivalent functionality, secure configurations, and physical protections. | count: 007 Authorize, monitor, and control usage of mobile code technologies (291f20d4-8d93-1d73-89f3-6ce28b825563), Define acceptable and unacceptable mobile code technologies (1afada58-8b34-7ac2-a38a-983218635201), Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Prohibit remote activation of collaborative computing devices (678ca228-042d-6d8e-a598-c58d5670437d), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0403.01x1System.8-01.x | hipaa-0403.01x1System.8-01.x | 0403.01x1System.8-01.x | 04 Mobile Device Security | 0403.01x1System.8-01.x 01.07 Mobile Computing and Teleworking | Shared | n/a | The organization monitors for unauthorized connections of mobile devices. | count: 007 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0405.01y1Organizational.12345678-01.y | hipaa-0405.01y1Organizational.12345678-01.y | 0405.01y1Organizational.12345678-01.y | 04 Mobile Device Security | 0405.01y1Organizational.12345678-01.y 01.07 Mobile Computing and Teleworking | Shared | n/a | Teleworking activities are only authorized if security arrangements and controls that comply with relevant security policies and organizational requirements are in place. | count: 001 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0407.01y2Organizational.1-01.y | hipaa-0407.01y2Organizational.1-01.y | 0407.01y2Organizational.1-01.y | 04 Mobile Device Security | 0407.01y2Organizational.1-01.y 01.07 Mobile Computing and Teleworking | Shared | n/a | Prior to authorizing teleworking, the physical security of the teleworking site is evaluated and any threats/issues identified are addressed. | count: 002 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0408.01y3Organizational.12-01.y | hipaa-0408.01y3Organizational.12-01.y | 0408.01y3Organizational.12-01.y | 04 Mobile Device Security | 0408.01y3Organizational.12-01.y 01.07 Mobile Computing and Teleworking | Shared | n/a | Prior to authorizing teleworking, (i) the organization provides a definition of the work permitted, standard operating hours, classification of information that may be held/stored, and the internal systems and services that the teleworker is authorized to access; (ii) suitable equipment and storage furniture for the teleworking activities, where the use of privately owned equipment not under the control of the organization is forbidden; (iii) suitable communications equipment, including methods for securing remote access; (iv) rules and guidance on family and visitor access to equipment and information; (v) hardware and software support and maintenance; (vi) procedures for back-up and business continuity; (vii) a means for teleworkers to communicate with information security personnel in case of security incidents or problems; and, (viii) audit and security monitoring. | count: 005 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0409.01y3Organizational.3-01.y | hipaa-0409.01y3Organizational.3-01.y | 0409.01y3Organizational.3-01.y | 04 Mobile Device Security | 0409.01y3Organizational.3-01.y 01.07 Mobile Computing and Teleworking | Shared | n/a | Additional insurance to address the risks of teleworking is provided. | count: 001 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0410.01x1System.12-01.xMobileComputingandCommunications | hipaa-0410.01x1System.12-01.xMobileComputingandCommunications | 0410.01x1System.12-01.xMobileComputingandCommunications | 04 Mobile Device Security | 0410.01x1System.12-01.xMobileComputingandCommunications 01.07 Mobile Computing and Teleworking | Shared | n/a | If it is determined that encryption is not reasonable and appropriate, the organization documents its rationale and acceptance of risk. | count: 002 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0415.01y1Organizational.10-01.y | hipaa-0415.01y1Organizational.10-01.y | 0415.01y1Organizational.10-01.y | 04 Mobile Device Security | 0415.01y1Organizational.10-01.y 01.07 Mobile Computing and Teleworking | Shared | n/a | Suitable protections of the teleworking site are in place to protect against the theft of equipment and information, the unauthorized disclosure of information, and unauthorized remote access to the organization's internal systems or misuse of facilities. | count: 005 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0416.01y3Organizational.4-01.y | hipaa-0416.01y3Organizational.4-01.y | 0416.01y3Organizational.4-01.y | 04 Mobile Device Security | 0416.01y3Organizational.4-01.y 01.07 Mobile Computing and Teleworking | Shared | n/a | The organization instructs all personnel working from home to implement fundamental security controls and practices; including, but not limited to, passwords, virus protection, personal firewalls, laptop cable locks, recording serial numbers and other identification information about laptops, and disconnecting modems at alternate worksites. | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0417.01y3Organizational.5-01.y | hipaa-0417.01y3Organizational.5-01.y | 0417.01y3Organizational.5-01.y | 04 Mobile Device Security | 0417.01y3Organizational.5-01.y 01.07 Mobile Computing and Teleworking | Shared | n/a | Remote access is limited only to information resources required by users to complete job duties. | count: 001 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0425.01x1System.13-01.x | hipaa-0425.01x1System.13-01.x | 0425.01x1System.13-01.x | 04 Mobile Device Security | 0425.01x1System.13-01.x 01.07 Mobile Computing and Teleworking | Shared | n/a | A documented list of approved application stores has been defined as acceptable for mobile devices accessing or storing entity (client) or cloud service provider-managed client data, and the use of unapproved application stores is prohibited for company-owned and BYOD mobile devices. Non-approved applications or approved applications not obtained through approved application stores are prohibited. | count: 001 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0426.01x2System.1-01.x | hipaa-0426.01x2System.1-01.x | 0426.01x2System.1-01.x | 04 Mobile Device Security | 0426.01x2System.1-01.x 01.07 Mobile Computing and Teleworking | Shared | n/a | A centralized, mobile device management solution has been deployed to all mobile devices permitted to store, transmit, or process organizational and/or customer data, enforcing built-in detective and preventative controls. | count: 007 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0427.01x2System.2-01.x | hipaa-0427.01x2System.2-01.x | 0427.01x2System.2-01.x | 04 Mobile Device Security | 0427.01x2System.2-01.x 01.07 Mobile Computing and Teleworking | Shared | n/a | The organization ensures that mobile devices connecting to corporate networks, or storing and accessing company information, allow for remote software version/patch validation. | count: 004 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0428.01x2System.3-01.x | hipaa-0428.01x2System.3-01.x | 0428.01x2System.3-01.x | 04 Mobile Device Security | 0428.01x2System.3-01.x 01.07 Mobile Computing and Teleworking | Shared | n/a | The organization ensures that mobile devices connecting to corporate networks, or storing and accessing company information, allow for remote wipe. | count: 004 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0429.01x1System.14-01.x | hipaa-0429.01x1System.14-01.x | 0429.01x1System.14-01.x | 04 Mobile Device Security | 0429.01x1System.14-01.x 01.07 Mobile Computing and Teleworking | Shared | n/a | The organization prohibits the circumvention of built-in security controls on mobile devices (e.g., jailbreaking or rooting). | count: 007 Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0504.09m2Organizational.5-09.m | hipaa-0504.09m2Organizational.5-09.m | 0504.09m2Organizational.5-09.m | 05 Wireless Security | 0504.09m2Organizational.5-09.m 09.06 Network Security Management | Shared | n/a | Firewalls are configured to deny or control any traffic from a wireless environment into the covered data environment. | count: 004 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0505.09m2Organizational.3-09.m | hipaa-0505.09m2Organizational.3-09.m | 0505.09m2Organizational.3-09.m | 05 Wireless Security | 0505.09m2Organizational.3-09.m 09.06 Network Security Management | Shared | n/a | Quarterly scans are performed to identify unauthorized wireless access points, and appropriate action is taken if any unauthorized access points are discovered. | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Define requirements for managing assets (25a1f840-65d0-900a-43e4-bee253de04de), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0601.06g1Organizational.124-06.g | hipaa-0601.06g1Organizational.124-06.g | 0601.06g1Organizational.124-06.g | 06 Configuration Management | 0601.06g1Organizational.124-06.g 06.02 Compliance with Security Policies and Standards, and Technical Compliance | Shared | n/a | Annual compliance reviews are conducted by security or audit individuals using manual or automated tools; if non-compliance is found, appropriate action is taken. | count: 006 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0602.06g1Organizational.3-06.g | hipaa-0602.06g1Organizational.3-06.g | 0602.06g1Organizational.3-06.g | 06 Configuration Management | 0602.06g1Organizational.3-06.g 06.02 Compliance with Security Policies and Standards, and Technical Compliance | Shared | n/a | The results and recommendations of the reviews are documented and approved by management. | count: 010 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0603.06g2Organizational.1-06.g | hipaa-0603.06g2Organizational.1-06.g | 0603.06g2Organizational.1-06.g | 06 Configuration Management | 0603.06g2Organizational.1-06.g 06.02 Compliance with Security Policies and Standards, and Technical Compliance | Shared | n/a | Automated compliance tools are used when possible. | count: 006 Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0604.06g2Organizational.2-06.g | hipaa-0604.06g2Organizational.2-06.g | 0604.06g2Organizational.2-06.g | 06 Configuration Management | 0604.06g2Organizational.2-06.g 06.02 Compliance with Security Policies and Standards, and Technical Compliance | Shared | n/a | The organization has developed a continuous monitoring strategy and implemented a continuous monitoring program. | count: 007 Analyse data obtained from continuous monitoring (6a379d74-903b-244a-4c44-838728bea6b0), Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Employ independent assessors for continuous monitoring (3baee3fd-30f5-882c-018c-cc78703a0106), Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0605.10h1System.12-10.h | hipaa-0605.10h1System.12-10.h | 0605.10h1System.12-10.h | 06 Configuration Management | 0605.10h1System.12-10.h 10.04 Security of System Files | Shared | n/a | Only authorized administrators are allowed to implement approved upgrades to software, applications, and program libraries, based on business requirements and the security implications of the release. | count: 006 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Windows machines should meet requirements for 'Security Options - Audit' (33936777-f2ac-45aa-82ec-07958ec9ade4), Windows machines should meet requirements for 'System Audit Policies - Account Management' (94d9aca8-3757-46df-aa51-f218c5f11954) |
Guest Configuration, Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0606.10h2System.1-10.h | hipaa-0606.10h2System.1-10.h | 0606.10h2System.1 - 10.h | Control of Operational Software | Applications and operating systems are successfully tested for usability, security and impact prior to production. | Customer | n/a | Sample of SDL change tickets, demonstrating impact analysis, security testing, formal approval, and deployment scheduling of proposed changes. | count: 001 Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0607.10h2System.23-10.h | hipaa-0607.10h2System.23-10.h | 0607.10h2System.23 - 10.h | Control of Operational Software | The organization uses its configuration control program to maintain control of all implemented software and its system documentation and archive prior versions of implemented software and associated system documentation. | Customer | n/a | Evidence that SDL changes can be rolled back (e.g., to resolve post-deployment issues). | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0613.06h1Organizational.12-06.h | hipaa-0613.06h1Organizational.12-06.h | 0613.06h1Organizational.12-06.h | 06 Configuration Management | 0613.06h1Organizational.12-06.h 06.02 Compliance with Security Policies and Standards, and Technical Compliance | Shared | n/a | The organization performs annual checks on the technical security configuration of systems, either manually by an individual with experience with the systems and/or with the assistance of automated software tools, and takes appropriate action if non-compliance is found. | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0614.06h2Organizational.12-06.h | hipaa-0614.06h2Organizational.12-06.h | 0614.06h2Organizational.12-06.h | 06 Configuration Management | 0614.06h2Organizational.12-06.h 06.02 Compliance with Security Policies and Standards, and Technical Compliance | Shared | n/a | Technical compliance checks are performed by an experienced specialist with the assistance of industry standard automated tools, which generate a technical report for subsequent interpretation. These checks are performed annually, but more frequently where needed, based on risk as part of an official risk assessment process. | count: 006 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0615.06h2Organizational.3-06.h | hipaa-0615.06h2Organizational.3-06.h | 0615.06h2Organizational.3-06.h | 06 Configuration Management | 0615.06h2Organizational.3-06.h 06.02 Compliance with Security Policies and Standards, and Technical Compliance | Shared | n/a | Technical compliance checks are used to help support technical interoperability. | count: 001 Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0618.09b1System.1-09.b | hipaa-0618.09b1System.1-09.b | 0618.09b1System.1-09.b | 06 Configuration Management | 0618.09b1System.1-09.b 09.01 Documented Operating Procedures | Shared | n/a | Changes to information assets, including systems, networks, and network services, are controlled and archived. | count: 016 Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147), Retain previous versions of baseline configs (5e4e9685-3818-5934-0071-2620c4fa2ca5), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0626.10h1System.3-10.h | hipaa-0626.10h1System.3-10.h | 0626.10h1System.3-10.h | 06 Configuration Management | 0626.10h1System.3-10.h 10.04 Security of System Files | Shared | n/a | Operational systems only hold approved programs or executable code. | count: 003 Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0627.10h1System.45-10.h | hipaa-0627.10h1System.45-10.h | 0627.10h1System.45-10.h | 06 Configuration Management | 0627.10h1System.45-10.h 10.04 Security of System Files | Shared | n/a | The organization maintains information systems according to a current baseline configuration and configures system security parameters to prevent misuse. Vendor supplied software used in operational systems is maintained at a level supported by the supplier and uses the latest version of web browsers on operational systems to take advantage of the latest security functions in the application. | count: 011 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0), Retain previous versions of baseline configs (5e4e9685-3818-5934-0071-2620c4fa2ca5), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0628.10h1System.6-10.h | hipaa-0628.10h1System.6-10.h | 0628.10h1System.6-10.h | 06 Configuration Management | 0628.10h1System.6-10.h 10.04 Security of System Files | Shared | n/a | If systems or system components in production are no longer supported by the developer, vendor, or manufacturer, the organization is able to provide evidence of a formal migration plan approved by management to replace the system or system components. | count: 004 Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0635.10k1Organizational.12-10.k | hipaa-0635.10k1Organizational.12-10.k | 0635.10k1Organizational.12-10.k | 06 Configuration Management | 0635.10k1Organizational.12-10.k 10.05 Security In Development and Support Processes | Shared | n/a | Managers responsible for application systems are also responsible for the strict control (security) of the project or support environment and ensure that all proposed system changes are reviewed to check that they do not compromise the security of either the system or the operating environment. | count: 009 Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0636.10k2Organizational.1-10.k | hipaa-0636.10k2Organizational.1-10.k | 0636.10k2Organizational.1-10.k | 06 Configuration Management | 0636.10k2Organizational.1-10.k 10.05 Security In Development and Support Processes | Shared | n/a | The organization formally addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance for configuration management (e.g., through policies, standards, processes). | count: 008 Create configuration plan protection (874a6f2e-2098-53bc-3a16-20dcdc425a7e), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0637.10k2Organizational.2-10.k | hipaa-0637.10k2Organizational.2-10.k | 0637.10k2Organizational.2-10.k | 06 Configuration Management | 0637.10k2Organizational.2-10.k 10.05 Security In Development and Support Processes | Shared | n/a | The organization has developed, documented, and implemented a configuration management plan for the information system. | count: 007 Create configuration plan protection (874a6f2e-2098-53bc-3a16-20dcdc425a7e), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0638.10k2Organizational.34569-10.k | hipaa-0638.10k2Organizational.34569-10.k | 0638.10k2Organizational.34569-10.k | 06 Configuration Management | 0638.10k2Organizational.34569-10.k 10.05 Security In Development and Support Processes | Shared | n/a | Changes are formally controlled, documented, and enforced in order to minimize the corruption of information systems. | count: 014 Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0639.10k2Organizational.78-10.k | hipaa-0639.10k2Organizational.78-10.k | 0639.10k2Organizational.78-10.k | 06 Configuration Management | 0639.10k2Organizational.78-10.k 10.05 Security In Development and Support Processes | Shared | n/a | Installation checklists and vulnerability scans are used to validate the configuration of servers, workstations, devices, and appliances, and ensure the configuration meets minimum standards. | count: 008 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0640.10k2Organizational.1012-10.k | hipaa-0640.10k2Organizational.1012-10.k | 0640.10k2Organizational.1012-10.k | 06 Configuration Management | 0640.10k2Organizational.1012-10.k 10.05 Security In Development and Support Processes | Shared | n/a | Where development is outsourced, change control procedures to address security are included in the contract(s) and specifically require the developer to track security flaws and flaw resolution within the system, component, or service and report findings to organization-defined personnel or roles. | count: 022 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0641.10k2Organizational.11-10.k | hipaa-0641.10k2Organizational.11-10.k | 0641.10k2Organizational.11-10.k | 06 Configuration Management | 0641.10k2Organizational.11-10.k 10.05 Security In Development and Support Processes | Shared | n/a | The organization does not use automated updates on critical systems. | count: 013 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0642.10k3Organizational.12-10.k | hipaa-0642.10k3Organizational.12-10.k | 0642.10k3Organizational.12-10.k | 06 Configuration Management | 0642.10k3Organizational.12-10.k 10.05 Security In Development and Support Processes | Shared | n/a | The organization develops, documents, and maintains, under configuration control, a current baseline configuration of the information system, and reviews and updates the baseline as required. | count: 007 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0643.10k3Organizational.3-10.k | hipaa-0643.10k3Organizational.3-10.k | 0643.10k3Organizational.3-10.k | 06 Configuration Management | 0643.10k3Organizational.3-10.k 10.05 Security In Development and Support Processes | Shared | n/a | The organization (i) establishes and documents mandatory configuration settings for information technology products employed within the information system using the latest security configuration baselines; (ii) identifies, documents, and approves exceptions from the mandatory established configuration settings for individual components based on explicit operational requirements; and, (iii) monitors and controls changes to the configuration settings in accordance with organizational policies and procedures. | count: 017 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Retain previous versions of baseline configs (5e4e9685-3818-5934-0071-2620c4fa2ca5), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0644.10k3Organizational.4-10.k | hipaa-0644.10k3Organizational.4-10.k | 0644.10k3Organizational.4-10.k | 06 Configuration Management | 0644.10k3Organizational.4-10.k 10.05 Security In Development and Support Processes | Shared | n/a | The organization employs automated mechanisms to (i) centrally manage, apply, and verify configuration settings; (ii) respond to unauthorized changes to network and system security-related configuration settings; and, (iii) enforce access restrictions and auditing of the enforcement actions. | count: 020 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e), Windows machines should meet requirements for 'System Audit Policies - Detailed Tracking' (58383b73-94a9-4414-b382-4146eb02611b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0662.09sCSPOrganizational.2-09.s | hipaa-0662.09sCSPOrganizational.2-09.s | 0662.09sCSPOrganizational.2-09.s | 06 Configuration Management | 0662.09sCSPOrganizational.2-09.s 09.08 Exchange of Information | Shared | n/a | Cloud service providers use an industry-recognized virtualization platform and standard virtualization formats (e.g., Open Virtualization Format, OVF) to help ensure interoperability, and has documented custom changes made to any hypervisor in use and all solution-specific virtualization hooks available for customer review. | count: 003 App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb), Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0663.10h1System.7-10.h | hipaa-0663.10h1System.7-10.h | 0663.10h1System.7-10.h | 06 Configuration Management | 0663.10h1System.7-10.h 10.04 Security of System Files | Shared | n/a | The operating system has in place supporting technical controls such as antivirus, file integrity monitoring, host-based (personal) firewalls or port filtering tools, and logging as part of its baseline. | count: 016 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0669.10hCSPSystem.1-10.h | hipaa-0669.10hCSPSystem.1-10.h | 0669.10hCSPSystem.1-10.h | 06 Configuration Management | 0669.10hCSPSystem.1-10.h 10.04 Security of System Files | Shared | n/a | Open and published APIs are used by cloud service providers to ensure support for interoperability between components and to facilitate migrating applications. | count: 016 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0670.10hCSPSystem.2-10.h | hipaa-0670.10hCSPSystem.2-10.h | 0670.10hCSPSystem.2-10.h | 06 Configuration Management | 0670.10hCSPSystem.2-10.h 10.04 Security of System Files | Shared | n/a | Structured and unstructured data is available to the organization (customer) and provided to them upon request in an industry-standard format (e.g., .docx, .xlsx, pdf, logs, and flat files). | count: 003 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0671.10k1System.1-10.k | hipaa-0671.10k1System.1-10.k | 0671.10k1System.1-10.k | 06 Configuration Management | 0671.10k1System.1-10.k 10.05 Security In Development and Support Processes | Shared | n/a | The organization manages changes to mobile device operating systems, patch levels, and/or applications through a formal change management process. | count: 016 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0672.10k3System.5-10.k | hipaa-0672.10k3System.5-10.k | 0672.10k3System.5-10.k | 06 Configuration Management | 0672.10k3System.5-10.k 10.05 Security In Development and Support Processes | Shared | n/a | The integrity of all virtual machine images is ensured at all times by (i) logging and raising an alert for any changes made to virtual machine images, and (ii) making available to the business owner(s) and/or customer(s) through electronic methods (e.g., portals or alerts) the results of a change or move and the subsequent validation of the image's integrity. | count: 012 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Prohibit binary/machine-executable code (8e920169-739d-40b5-3f99-c4d855327bb2), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 068.06g2Organizational.34-06.g | hipaa-068.06g2Organizational.34-06.g | 068.06g2Organizational.34-06.g | 06 Configuration Management | 068.06g2Organizational.34-06.g 06.02 Compliance with Security Policies and Standards, and Technical Compliance | Shared | n/a | The organization employs assessors or assessment teams with a level of independence appropriate to its continuous monitoring strategy to monitor the security controls in the information system on an ongoing basis. | count: 006 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Employ independent assessors for continuous monitoring (3baee3fd-30f5-882c-018c-cc78703a0106), Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 069.06g2Organizational.56-06.g | hipaa-069.06g2Organizational.56-06.g | 069.06g2Organizational.56-06.g | 06 Configuration Management | 069.06g2Organizational.56-06.g 06.02 Compliance with Security Policies and Standards, and Technical Compliance | Shared | n/a | The internal security organization reviews and maintains records of compliance results (e.g., organization-defined metrics) in order to better track security trends within the organization, respond to the results of correlation and analysis, and address longer term areas of concern as part of its formal risk assessment process. | count: 007 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0701.07a1Organizational.12-07.a | hipaa-0701.07a1Organizational.12-07.a | 0701.07a1Organizational.12-07.a | 07 Vulnerability Management | 0701.07a1Organizational.12-07.a 07.01 Responsibility for Assets | Shared | n/a | An inventory of assets and services is maintained. | count: 007 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0702.07a1Organizational.3-07.a | hipaa-0702.07a1Organizational.3-07.a | 0702.07a1Organizational.3-07.a | 07 Vulnerability Management | 0702.07a1Organizational.3-07.a 07.01 Responsibility for Assets | Shared | n/a | The information lifecycle manages the secure use, transfer, exchange, and disposal of IT-related assets. | count: 002 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0703.07a2Organizational.1-07.a | hipaa-0703.07a2Organizational.1-07.a | 0703.07a2Organizational.1-07.a | 07 Vulnerability Management | 0703.07a2Organizational.1-07.a 07.01 Responsibility for Assets | Shared | n/a | The inventory of all authorized assets includes the owner of the information asset, custodianship, categorizes the information asset according to criticality and information classification, and identifies protection and sustainment requirements commensurate with the asset's categorization. | count: 003 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0704.07a3Organizational.12-07.a | hipaa-0704.07a3Organizational.12-07.a | 0704.07a3Organizational.12-07.a | 07 Vulnerability Management | 0704.07a3Organizational.12-07.a 07.01 Responsibility for Assets | Shared | n/a | Organizational inventories of IT assets are updated during installations, removals, and system changes, with full physical inventories performed for capital assets (at least annually) and for non-capital assets. | count: 003 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0705.07a3Organizational.3-07.a | hipaa-0705.07a3Organizational.3-07.a | 0705.07a3Organizational.3-07.a | 07 Vulnerability Management | 0705.07a3Organizational.3-07.a 07.01 Responsibility for Assets | Shared | n/a | The IT Asset Lifecycle Program is regularly reviewed and updated. | count: 003 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0706.10b1System.12-10.b | hipaa-0706.10b1System.12-10.b | 0706.10b1System.12-10.b | 07 Vulnerability Management | 0706.10b1System.12-10.b 10.02 Correct Processing in Applications | Shared | n/a | Applications developed by the organization are based on secure coding guidelines to prevent common vulnerabilities or undergo appropriate testing. | count: 004 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0708.10b2System.2-10.b | hipaa-0708.10b2System.2-10.b | 0708.10b2System.2-10.b | 07 Vulnerability Management | 0708.10b2System.2-10.b 10.02 Correct Processing in Applications | Shared | n/a | System and information integrity requirements are developed, documented, disseminated, reviewed, and updated annually. | count: 003 Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0709.10m1Organizational.1-10.m | hipaa-0709.10m1Organizational.1-10.m | 0709.10m1Organizational.1-10.m | 07 Vulnerability Management | 0709.10m1Organizational.1-10.m 10.06 Technical Vulnerability Management | Shared | n/a | Technical vulnerabilities are identified, evaluated for risk, and corrected in a timely manner. | count: 013 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Windows machines should meet requirements for 'Security Options - Microsoft Network Server' (caf2d518-f029-4f6b-833b-d7081702f253) |
Guest Configuration, Regulatory Compliance, Security Center, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0710.10m2Organizational.1-10.m | hipaa-0710.10m2Organizational.1-10.m | 0710.10m2Organizational.1-10.m | 07 Vulnerability Management | 0710.10m2Organizational.1-10.m 10.06 Technical Vulnerability Management | Shared | n/a | A hardened configuration standard exists for all system and network components. | count: 009 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0711.10m2Organizational.23-10.m | hipaa-0711.10m2Organizational.23-10.m | 0711.10m2Organizational.23-10.m | 07 Vulnerability Management | 0711.10m2Organizational.23-10.m 10.06 Technical Vulnerability Management | Shared | n/a | A technical vulnerability management program is in place to monitor, assess, rank, and remediate vulnerabilities identified in systems. | count: 004 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0712.10m2Organizational.4-10.m | hipaa-0712.10m2Organizational.4-10.m | 0712.10m2Organizational.4-10.m | 07 Vulnerability Management | 0712.10m2Organizational.4-10.m 10.06 Technical Vulnerability Management | Shared | n/a | Internal and external vulnerability assessments of covered information systems, virtualized environments, and networked environments, including both network- and application-layer tests, are performed by a qualified individual on a quarterly basis or after significant changes. | count: 002 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132), Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0713.10m2Organizational.5-10.m | hipaa-0713.10m2Organizational.5-10.m | 0713.10m2Organizational.5-10.m | 07 Vulnerability Management | 0713.10m2Organizational.5-10.m 10.06 Technical Vulnerability Management | Shared | n/a | Patches are tested and evaluated before they are installed. | count: 005 Automate flaw remediation (a90c4d44-7fac-8e02-6d5b-0d92046b20e6), Establish benchmarks for flaw remediation (dd2523d5-2db3-642b-a1cf-83ac973b32c2), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Measure the time between flaw identification and flaw remediation (dad1887d-161b-7b61-2e4d-5124a7b5724e), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0714.10m2Organizational.7-10.m | hipaa-0714.10m2Organizational.7-10.m | 0714.10m2Organizational.7-10.m | 07 Vulnerability Management | 0714.10m2Organizational.7-10.m 10.06 Technical Vulnerability Management | Shared | n/a | The technical vulnerability management program is evaluated on a quarterly basis. | count: 020 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Implement privileged access for executing vulnerability scanning activities (5b802722-71dd-a13d-2e7e-231e09589efb), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review exploit protection events (a30bd8e9-7064-312a-0e1f-e1b485d59f6e), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0715.10m2Organizational.8-10.m | hipaa-0715.10m2Organizational.8-10.m | 0715.10m2Organizational.8-10.m | 07 Vulnerability Management | 0715.10m2Organizational.8-10.m 10.06 Technical Vulnerability Management | Shared | n/a | Systems are appropriately hardened (e.g., configured with only necessary and secure services, ports, and protocols enabled). | count: 001 Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0716.10m3Organizational.1-10.m | hipaa-0716.10m3Organizational.1-10.m | 0716.10m3Organizational.1-10.m | 07 Vulnerability Management | 0716.10m3Organizational.1-10.m 10.06 Technical Vulnerability Management | Shared | n/a | The organization conducts an enterprise security posture review as needed but no less than once within every 365 days, in accordance with organizational information security procedures. | count: 005 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0717.10m3Organizational.2-10.m | hipaa-0717.10m3Organizational.2-10.m | 0717.10m3Organizational.2-10.m | 07 Vulnerability Management | 0717.10m3Organizational.2-10.m 10.06 Technical Vulnerability Management | Shared | n/a | Vulnerability scanning tools include the capability to readily update the information system vulnerabilities scanned. | count: 003 Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0718.10m3Organizational.34-10.m | hipaa-0718.10m3Organizational.34-10.m | 0718.10m3Organizational.34-10.m | 07 Vulnerability Management | 0718.10m3Organizational.34-10.m 10.06 Technical Vulnerability Management | Shared | n/a | The organization scans for vulnerabilities in the information system and hosted applications to determine the state of flaw remediation monthly (automatically), and again (manually or automatically) when new vulnerabilities potentially affecting the systems and networked environments are identified and reported. | count: 004 Automate flaw remediation (a90c4d44-7fac-8e02-6d5b-0d92046b20e6), Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0719.10m3Organizational.5-10.m | hipaa-0719.10m3Organizational.5-10.m | 0719.10m3Organizational.5-10.m | 07 Vulnerability Management | 0719.10m3Organizational.5-10.m 10.06 Technical Vulnerability Management | Shared | n/a | The organization updates the list of information system vulnerabilities scanned within every 30 days or when new vulnerabilities are identified and reported. | count: 003 Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0720.07a1Organizational.4-07.a | hipaa-0720.07a1Organizational.4-07.a | 0720.07a1Organizational.4-07.a | 07 Vulnerability Management | 0720.07a1Organizational.4-07.a 07.01 Responsibility for Assets | Shared | n/a | The organization's asset inventory does not duplicate other inventories unnecessarily and ensures their respective content is aligned. | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0722.07a1Organizational.67-07.a | hipaa-0722.07a1Organizational.67-07.a | 0722.07a1Organizational.67-07.a | 07 Vulnerability Management | 0722.07a1Organizational.67-07.a 07.01 Responsibility for Assets | Shared | n/a | If the organization assigns assets to contractors, it ensures that the procedures for assigning and monitoring the use of the property are included in the contract; and, if assigned to volunteer workers, there is a written agreement specifying how and when the property will be inventoried and how it will be returned upon completion of the volunteer assignment. | count: 003 Require compliance with intellectual property rights (725164e5-3b21-1ec2-7e42-14f077862841), Restrict use of open source software (08c11b48-8745-034d-1c1b-a144feec73b9), Track software license usage (77cc89bb-774f-48d7-8a84-fb8c322c3000) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0723.07a1Organizational.8-07.a | hipaa-0723.07a1Organizational.8-07.a | 0723.07a1Organizational.8-07.a | 07 Vulnerability Management | 0723.07a1Organizational.8-07.a 07.01 Responsibility for Assets | Shared | n/a | The organization creates and documents the process/procedure the organization intends to use for deleting data from hard-drives prior to property transfer, exchange, or disposal/surplus. | count: 001 Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0724.07a3Organizational.4-07.a | hipaa-0724.07a3Organizational.4-07.a | 0724.07a3Organizational.4-07.a | 07 Vulnerability Management | 0724.07a3Organizational.4-07.a 07.01 Responsibility for Assets | Shared | n/a | The organization employs automated mechanisms to scan the network, no less than weekly, to detect the presence of unauthorized components/devices (including hardware, firmware and software) in the environment; and disables network access by such components/devices or notify designated organizational officials. | count: 006 Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0725.07a3Organizational.5-07.a | hipaa-0725.07a3Organizational.5-07.a | 0725.07a3Organizational.5-07.a | 07 Vulnerability Management | 0725.07a3Organizational.5-07.a 07.01 Responsibility for Assets | Shared | n/a | The organization provides an updated inventory, identifying assets with covered information (e.g., PII) to the CIO or information security official, and the senior privacy official on an organization-defined basis, but no less than annually. | count: 003 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0733.10b2System.4-10.b | hipaa-0733.10b2System.4-10.b | 0733.10b2System.4-10.b | 07 Vulnerability Management | 0733.10b2System.4-10.b 10.02 Correct Processing in Applications | Shared | n/a | The information system checks the validity of organization-defined information inputs for accuracy, completeness, validity, and authenticity as close to the point of origin as possible. For in-house developed software, the organization ensures that explicit error checking is performed and documented for all input, including for size, data type, and acceptable ranges or formats. | count: 002 Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0786.10m2Organizational.13-10.m | hipaa-0786.10m2Organizational.13-10.m | 0786.10m2Organizational.13-10.m | 07 Vulnerability Management | 0786.10m2Organizational.13-10.m 10.06 Technical Vulnerability Management | Shared | n/a | A prioritization process is implemented to determine which patches are applied across the organization's systems. | count: 001 Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0787.10m2Organizational.14-10.m | hipaa-0787.10m2Organizational.14-10.m | 0787.10m2Organizational.14-10.m | 07 Vulnerability Management | 0787.10m2Organizational.14-10.m 10.06 Technical Vulnerability Management | Shared | n/a | Patches installed in the production environment are also installed in the organization's disaster recovery environment in a timely manner. | count: 004 Automate flaw remediation (a90c4d44-7fac-8e02-6d5b-0d92046b20e6), Establish benchmarks for flaw remediation (dd2523d5-2db3-642b-a1cf-83ac973b32c2), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Measure the time between flaw identification and flaw remediation (dad1887d-161b-7b61-2e4d-5124a7b5724e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0788.10m3Organizational.20-10.m | hipaa-0788.10m3Organizational.20-10.m | 0788.10m3Organizational.20-10.m | 07 Vulnerability Management | 0788.10m3Organizational.20-10.m 10.06 Technical Vulnerability Management | Shared | n/a | The organization undergoes regular penetration testing by an independent agent or team, at least every 365 days, on defined information systems or system components; conducts such testing from outside as well as inside the network perimeter; and such testing includes tests for the protection of unprotected system information that would be useful to attackers. | count: 001 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0790.10m3Organizational.22-10.m | hipaa-0790.10m3Organizational.22-10.m | 0790.10m3Organizational.22-10.m | 07 Vulnerability Management | 0790.10m3Organizational.22-10.m 10.06 Technical Vulnerability Management | Shared | n/a | The organization reviews historic audit logs to determine if high vulnerability scan findings identified in the information system have been previously exploited. | count: 017 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review exploit protection events (a30bd8e9-7064-312a-0e1f-e1b485d59f6e), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0791.10b2Organizational.4-10.b | hipaa-0791.10b2Organizational.4-10.b | 0791.10b2Organizational.4-10.b | 07 Vulnerability Management | 0791.10b2Organizational.4-10.b 10.02 Correct Processing in Applications | Shared | n/a | Procedures, guidelines, and standards for the development of applications are periodically reviewed, assessed, and updated as necessary by the appointed senior-level information security official of the organization. | count: 008 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0805.01m1Organizational.12-01.m | hipaa-0805.01m1Organizational.12-01.m | 0805.01m1Organizational.12-01.m | 08 Network Protection | 0805.01m1Organizational.12-01.m 01.04 Network Access Control | Shared | n/a | The organization's security gateways (e.g., firewalls) (i) enforce security policies; (ii) are configured to filter traffic between domains; (iii) block unauthorized access; (iv) are used to maintain segregation between internal wired, internal wireless, and external network segments (e.g., the Internet), including DMZs; and, (vi) enforce access control policies for each of the domains. | count: 012 [Preview]: Container Registry should use a virtual network service endpoint (c4857be7-912a-4c75-87e6-e30292bcdf78), App Service apps should use a virtual network service endpoint (2d21331d-a4c2-4def-a9ad-ee4e1e023beb), Cosmos DB should use a virtual network service endpoint (e0a2b1a3-f7f9-4569-807f-2a9edebdf4d9), Event Hub should use a virtual network service endpoint (d63edb4a-c612-454d-b47d-191a724fcbf0), Gateway subnets should not be configured with a network security group (35f9c03a-cc27-418e-9c0c-539ff999d010), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Key Vault should use a virtual network service endpoint (ea4d6841-2173-4317-9747-ff522a45120f), SQL Server should use a virtual network service endpoint (ae5d2f14-d830-42b6-9899-df6cfe9c71a3), Storage Accounts should use a virtual network service endpoint (60d21c4f-21a3-4d94-85f4-b924e6aeeda4), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3) |
Network, Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0806.01m2Organizational.12356-01.m | hipaa-0806.01m2Organizational.12356-01.m | 0806.01m2Organizational.12356-01.m | 08 Network Protection | 0806.01m2Organizational.12356-01.m 01.04 Network Access Control | Shared | n/a | The organization’s network is logically and physically segmented with a defined security perimeter and a graduated set of controls, including subnetworks for publicly accessible system components that are logically separated from the internal network, based on organizational requirements; traffic is controlled based on functionality required and classification of the data/systems based on a risk assessment and their respective security requirements. | count: 013 [Preview]: Container Registry should use a virtual network service endpoint (c4857be7-912a-4c75-87e6-e30292bcdf78), App Service apps should use a virtual network service endpoint (2d21331d-a4c2-4def-a9ad-ee4e1e023beb), Cosmos DB should use a virtual network service endpoint (e0a2b1a3-f7f9-4569-807f-2a9edebdf4d9), Event Hub should use a virtual network service endpoint (d63edb4a-c612-454d-b47d-191a724fcbf0), Gateway subnets should not be configured with a network security group (35f9c03a-cc27-418e-9c0c-539ff999d010), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Isolate SecurID systems, Security Incident Management systems (dd6d00a8-701a-5935-a22b-c7b9c0c698b2), Key Vault should use a virtual network service endpoint (ea4d6841-2173-4317-9747-ff522a45120f), SQL Server should use a virtual network service endpoint (ae5d2f14-d830-42b6-9899-df6cfe9c71a3), Storage Accounts should use a virtual network service endpoint (60d21c4f-21a3-4d94-85f4-b924e6aeeda4), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3) |
Network, Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0808.10b2System.3-10.b | hipaa-0808.10b2System.3-10.b | 0808.10b2System.3-10.b | 08 Network Protection | 0808.10b2System.3-10.b 10.02 Correct Processing in Applications | Shared | n/a | For any public-facing web applications, application-level firewalls have been implemented to control traffic. For any public-facing applications that are not web-based, the organization has implemented a network-based firewall specific to the application type. If the traffic to the public-facing application is encrypted, the device either sits behind the encryption or is capable of decrypting the traffic prior to analysis. | count: 002 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0809.01n2Organizational.1234-01.n | hipaa-0809.01n2Organizational.1234-01.n | 0809.01n2Organizational.1234-01.n | 08 Network Protection | 0809.01n2Organizational.1234-01.n 01.04 Network Access Control | Shared | n/a | Network traffic is controlled in accordance with the organization’s access control policy through firewall and other network-related restrictions for each network access point or external telecommunication service's managed interface. | count: 018 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3) |
App Service, Cache, Network, Regulatory Compliance, Security Center, SQL, Storage | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0810.01n2Organizational.5-01.n | hipaa-0810.01n2Organizational.5-01.n | 0810.01n2Organizational.5-01.n | 08 Network Protection | 0810.01n2Organizational.5-01.n 01.04 Network Access Control | Shared | n/a | Transmitted information is secured and, at a minimum, encrypted over open, public networks. | count: 017 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3) |
App Service, Cache, Network, Regulatory Compliance, Security Center, SQL, Storage | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 08101.09m2Organizational.14-09.m | hipaa-08101.09m2Organizational.14-09.m | 08101.09m2Organizational.14-09.m | 08 Network Protection | 08101.09m2Organizational.14-09.m 09.06 Network Security Management | Shared | n/a | The organization uses secured and encrypted communication channels when migrating physical servers, applications, or data to virtualized servers. | count: 008 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 08102.09nCSPOrganizational.1-09.n | hipaa-08102.09nCSPOrganizational.1-09.n | 08102.09nCSPOrganizational.1-09.n | 08 Network Protection | 08102.09nCSPOrganizational.1-09.n 09.06 Network Security Management | Shared | n/a | Business-critical or customer (tenant) impacting (physical and virtual) application and interface designs (API), configurations, network infrastructure, and systems components, are designed, developed, and deployed in accordance with mutually agreed-upon service and capacity-level expectations, as well as IT governance and service management policies and procedures. | count: 002 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0811.01n2Organizational.6-01.n | hipaa-0811.01n2Organizational.6-01.n | 0811.01n2Organizational.6-01.n | 08 Network Protection | 0811.01n2Organizational.6-01.n 01.04 Network Access Control | Shared | n/a | Exceptions to the traffic flow policy are documented with a supporting mission/business need, duration of the exception, and reviewed at least annually; traffic flow policy exceptions are removed when no longer supported by an explicit mission/business need. | count: 024 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Determine information protection needs (dbcef108-7a04-38f5-8609-99da110a2a57), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3) |
App Service, Cache, Network, Regulatory Compliance, Security Center, SQL, Storage | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0812.01n2Organizational.8-01.n | hipaa-0812.01n2Organizational.8-01.n | 0812.01n2Organizational.8-01.n | 08 Network Protection | 0812.01n2Organizational.8-01.n 01.04 Network Access Control | Shared | n/a | Remote devices establishing a non-remote connection are not allowed to communicate with external (remote) resources. | count: 013 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3) |
App Service, Cache, Network, Regulatory Compliance, Security Center, SQL, Storage | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0814.01n1Organizational.12-01.n | hipaa-0814.01n1Organizational.12-01.n | 0814.01n1Organizational.12-01.n | 08 Network Protection | 0814.01n1Organizational.12-01.n 01.04 Network Access Control | Shared | n/a | The ability of users to connect to the internal network is restricted using a deny-by-default and allow-by-exception policy at managed interfaces according to the access control policy and the requirements of its business applications. | count: 012 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3) |
App Service, Cache, Network, Security Center, SQL, Storage | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0815.01o2Organizational.123-01.o | hipaa-0815.01o2Organizational.123-01.o | 0815.01o2Organizational.123-01.o | 08 Network Protection | 0815.01o2Organizational.123-01.o 01.04 Network Access Control | Shared | n/a | Requirements for network routing control are based on the access control policy, including positive source and destination checking mechanisms, such as firewall validation of source/destination addresses, and the hiding of internal directory services and IP addresses. The organization designed and implemented network perimeters so that all outgoing network traffic to the Internet passes through at least one application layer filtering proxy server. The proxy supports decrypting network traffic, logging individual TCP sessions, blocking specific URLs, domain names, and IP addresses to implement a blacklist, and applying whitelists of allowed sites that can be accessed through the proxy while blocking all other sites. The organization forces outbound traffic to the Internet through an authenticated proxy server on the enterprise perimeter. | count: 004 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0816.01w1System.1-01.w | hipaa-0816.01w1System.1-01.w | 0816.01w1System.1-01.w | 08 Network Protection | 0816.01w1System.1-01.w 01.06 Application and Information Access Control | Shared | n/a | The sensitivity of applications/systems is explicitly identified and documented by the application/system owner. | count: 006 Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Distribute information system documentation (84a01872-5318-049e-061e-d56734183e84), Document customer-defined actions (8c44a0ea-9b09-4d9c-0e91-f9bee3d05bfb), Obtain Admin documentation (3f1216b0-30ee-1ac9-3899-63eb744e85f5), Obtain user security function documentation (be1c34ab-295a-07a6-785c-36f63c1d223e), Protect administrator and user documentation (09960521-759e-5d12-086f-4192a72a5e92) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0817.01w2System.123-01.w | hipaa-0817.01w2System.123-01.w | 0817.01w2System.123-01.w | 08 Network Protection | 0817.01w2System.123-01.w 01.06 Application and Information Access Control | Shared | n/a | Unless the risk is identified and accepted by the data owner, sensitive systems are isolated (physically or logically) from non-sensitive applications/systems. | count: 013 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182), Ensure system capable of dynamic isolation of resources (83eea3d3-0d2c-9ccd-1021-2111b29b2a62), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Isolate SecurID systems, Security Incident Management systems (dd6d00a8-701a-5935-a22b-c7b9c0c698b2), Maintain separate execution domains for running processes (bfc540fe-376c-2eef-4355-121312fa4437), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0818.01w3System.12-01.w | hipaa-0818.01w3System.12-01.w | 0818.01w3System.12-01.w | 08 Network Protection | 0818.01w3System.12-01.w 01.06 Application and Information Access Control | Shared | n/a | Shared system resources (e.g., registers, main memory, secondary storage) are released back to the system, protected from disclosure to other systems/applications/users, and users cannot intentionally or unintentionally access information remnants. | count: 004 Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Maintain separate execution domains for running processes (bfc540fe-376c-2eef-4355-121312fa4437), Manage availability and capacity (edcc36f1-511b-81e0-7125-abee29752fe7), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0819.09m1Organizational.23-09.m | hipaa-0819.09m1Organizational.23-09.m | 0819.09m1Organizational.23-09.m | 08 Network Protection | 0819.09m1Organizational.23-09.m 09.06 Network Security Management | Shared | n/a | A current network diagram (including wireless networks) exists, and is updated whenever there are network changes and no less than every six months. | count: 002 Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0821.09m2Organizational.2-09.m | hipaa-0821.09m2Organizational.2-09.m | 0821.09m2Organizational.2-09.m | 08 Network Protection | 0821.09m2Organizational.2-09.m 09.06 Network Security Management | Shared | n/a | The organization tests and approves all network connections and firewall, router, and switch configuration changes prior to implementation. Any deviations from the standard configuration or updates to the standard configuration are documented and approved in a change control system. All new configuration rules beyond a baseline-hardened configuration that allow traffic to flow through network security devices, such as firewalls and network-based IPS, are also documented and recorded, with a specific business reason for each change, a specific individual’s name responsible for that business need, and an expected duration of the need. | count: 018 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Create configuration plan protection (874a6f2e-2098-53bc-3a16-20dcdc425a7e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Review changes for any unauthorized changes (c246d146-82b0-301f-32e7-1065dcd248b7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0822.09m2Organizational.4-09.m | hipaa-0822.09m2Organizational.4-09.m | 0822.09m2Organizational.4-09.m | 08 Network Protection | 0822.09m2Organizational.4-09.m 09.06 Network Security Management | Shared | n/a | Firewalls restrict inbound and outbound traffic to the minimum necessary. | count: 007 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0824.09m3Organizational.1-09.m | hipaa-0824.09m3Organizational.1-09.m | 0824.09m3Organizational.1-09.m | 08 Network Protection | 0824.09m3Organizational.1-09.m 09.06 Network Security Management | Shared | n/a | The impact of the loss of network service to the business is defined. | count: 010 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0825.09m3Organizational.23-09.m | hipaa-0825.09m3Organizational.23-09.m | 0825.09m3Organizational.23-09.m | 08 Network Protection | 0825.09m3Organizational.23-09.m 09.06 Network Security Management | Shared | n/a | Technical tools such as an IDS/IPS are implemented and operating on the network perimeter and other key points to identify vulnerabilities, monitor traffic, detect attack attempts and successful compromises, and mitigate threats; and these tools are updated on a regular basis. | count: 007 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0826.09m3Organizational.45-09.m | hipaa-0826.09m3Organizational.45-09.m | 0826.09m3Organizational.45-09.m | 08 Network Protection | 0826.09m3Organizational.45-09.m 09.06 Network Security Management | Shared | n/a | Firewall and router configuration standards are defined and implemented, and are reviewed every six months. | count: 003 Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0828.09m3Organizational.8-09.m | hipaa-0828.09m3Organizational.8-09.m | 0828.09m3Organizational.8-09.m | 08 Network Protection | 0828.09m3Organizational.8-09.m 09.06 Network Security Management | Shared | n/a | Quarterly network scans are performed to identify unauthorized components/devices. | count: 001 Review changes for any unauthorized changes (c246d146-82b0-301f-32e7-1065dcd248b7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0829.09m3Organizational.911-09.m | hipaa-0829.09m3Organizational.911-09.m | 0829.09m3Organizational.911-09.m | 08 Network Protection | 0829.09m3Organizational.911-09.m 09.06 Network Security Management | Shared | n/a | The organization utilizes firewalls from at least two different vendors that employ stateful packet inspection (also known as dynamic packet filtering). | count: 002 Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0830.09m3Organizational.1012-09.m | hipaa-0830.09m3Organizational.1012-09.m | 0830.09m3Organizational.1012-09.m | 08 Network Protection | 0830.09m3Organizational.1012-09.m 09.06 Network Security Management | Shared | n/a | A DMZ is established with all database(s), servers, and other system components storing or processing covered information placed behind it to limit external network traffic to the internal network. | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0832.09m3Organizational.14-09.m | hipaa-0832.09m3Organizational.14-09.m | 0832.09m3Organizational.14-09.m | 08 Network Protection | 0832.09m3Organizational.14-09.m 09.06 Network Security Management | Shared | n/a | The organization uses at least two DNS servers located on different subnets, which are geographically separated and perform different roles (internal and external) to eliminate single points of failure and enhance redundancy. | count: 003 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0835.09n1Organizational.1-09.n | hipaa-0835.09n1Organizational.1-09.n | 0835.09n1Organizational.1-09.n | 08 Network Protection | 0835.09n1Organizational.1-09.n 09.06 Network Security Management | Shared | n/a | Agreed services provided by a network service provider/manager are formally managed and monitored to ensure they are provided securely. | count: 007 [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0836.09.n2Organizational.1-09.n | hipaa-0836.09.n2Organizational.1-09.n | 0836.09.n2Organizational.1-09.n | 08 Network Protection | 0836.09.n2Organizational.1-09.n 09.06 Network Security Management | Shared | n/a | The organization formally authorizes and documents the characteristics of each connection from an information system to other information systems outside the organization. | count: 004 [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0837.09.n2Organizational.2-09.n | hipaa-0837.09.n2Organizational.2-09.n | 0837.09.n2Organizational.2-09.n | 08 Network Protection | 0837.09.n2Organizational.2-09.n 09.06 Network Security Management | Shared | n/a | Formal agreements with external information system providers include specific obligations for security and privacy. | count: 020 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0850.01o1Organizational.12-01.o | hipaa-0850.01o1Organizational.12-01.o | 0850.01o1Organizational.12-01.o | 08 Network Protection | 0850.01o1Organizational.12-01.o 01.04 Network Access Control | Shared | n/a | Routing controls are implemented through security gateways (e.g., firewalls) used between internal and external networks (e.g., the Internet and third-party networks). | count: 001 Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0858.09m1Organizational.4-09.m | hipaa-0858.09m1Organizational.4-09.m | 0858.09m1Organizational.4-09.m | 08 Network Protection | 0858.09m1Organizational.4-09.m 09.06 Network Security Management | Shared | n/a | The organization monitors for all authorized and unauthorized wireless access to the information system and prohibits installation of wireless access points (WAPs) unless explicitly authorized in writing by the CIO or his/her designated representative. | count: 007 All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1), Windows machines should meet requirements for 'Windows Firewall Properties' (35d9882c-993d-44e6-87d2-db66ce21b636) |
Guest Configuration, Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0859.09m1Organizational.78-09.m | hipaa-0859.09m1Organizational.78-09.m | 0859.09m1Organizational.78-09.m | 08 Network Protection | 0859.09m1Organizational.78-09.m 09.06 Network Security Management | Shared | n/a | The organization ensures the security of information in networks, availability of network services and information services using the network, and the protection of connected services from unauthorized access. | count: 014 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0860.09m1Organizational.9-09.m | hipaa-0860.09m1Organizational.9-09.m | 0860.09m1Organizational.9-09.m | 08 Network Protection | 0860.09m1Organizational.9-09.m 09.06 Network Security Management | Shared | n/a | The organization formally manages equipment on the network, including equipment in user areas. | count: 005 Deploy Diagnostic Settings for Network Security Groups (c9c29499-c1d1-4195-99bd-2ec9e3a9dc89), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0861.09m2Organizational.67-09.m | hipaa-0861.09m2Organizational.67-09.m | 0861.09m2Organizational.67-09.m | 08 Network Protection | 0861.09m2Organizational.67-09.m 09.06 Network Security Management | Shared | n/a | To identify and authenticate devices on local and/or wide area networks, including wireless networks, the information system uses either a (i) shared known information solution, or (ii) an organizational authentication solution, the exact selection and strength of which is dependent on the security categorization of the information system. | count: 007 App Service apps should use a virtual network service endpoint (2d21331d-a4c2-4def-a9ad-ee4e1e023beb), Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1), Windows machines should meet requirements for 'Security Options - Network Access' (3ff60f98-7fa4-410a-9f7f-0b00f5afdbdd) |
Guest Configuration, Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0862.09m2Organizational.8-09.m | hipaa-0862.09m2Organizational.8-09.m | 0862.09m2Organizational.8-09.m | 08 Network Protection | 0862.09m2Organizational.8-09.m 09.06 Network Security Management | Shared | n/a | The organization ensures information systems protect the confidentiality and integrity of transmitted information, including during preparation for transmission and during reception. | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), SQL Server should use a virtual network service endpoint (ae5d2f14-d830-42b6-9899-df6cfe9c71a3) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0863.09m2Organizational.910-09.m | hipaa-0863.09m2Organizational.910-09.m | 0863.09m2Organizational.910-09.m | 08 Network Protection | 0863.09m2Organizational.910-09.m 09.06 Network Security Management | Shared | n/a | The organization builds a firewall configuration that restricts connections between untrusted networks and any system components in the covered information environment; and any changes to the firewall configuration are updated in the network diagram. | count: 025 Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Event Hub should use a virtual network service endpoint (d63edb4a-c612-454d-b47d-191a724fcbf0), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0864.09m2Organizational.12-09.m | hipaa-0864.09m2Organizational.12-09.m | 0864.09m2Organizational.12-09.m | 08 Network Protection | 0864.09m2Organizational.12-09.m 09.06 Network Security Management | Shared | n/a | Usage restrictions and implementation guidance are formally defined for VoIP, including the authorization and monitoring of the service. | count: 004 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Cosmos DB should use a virtual network service endpoint (e0a2b1a3-f7f9-4569-807f-2a9edebdf4d9), Establish voip usage restrictions (68a39c2b-0f17-69ee-37a3-aa10f9853a08), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0865.09m2Organizational.13-09.m | hipaa-0865.09m2Organizational.13-09.m | 0865.09m2Organizational.13-09.m | 08 Network Protection | 0865.09m2Organizational.13-09.m 09.06 Network Security Management | Shared | n/a | The organization (i) authorizes connections from the information system to other information systems outside of the organization through the use of interconnection security agreements or other formal agreement; (ii) documents each connection, the interface characteristics, security requirements, and the nature of the information communicated; (iii) employs a deny-all, permit-by-exception policy for allowing connections from the information system to other information systems outside of the organization; and, (iv) applies a default-deny rule that drops all traffic via host-based firewalls or port filtering tools on its endpoints (workstations, servers, etc.), except those services and ports that are explicitly allowed. | count: 005 Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Employ restrictions on external system interconnections (80029bc5-834f-3a9c-a2d8-acbc1aab4e9f), Key Vault should use a virtual network service endpoint (ea4d6841-2173-4317-9747-ff522a45120f), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0866.09m3Organizational.1516-09.m | hipaa-0866.09m3Organizational.1516-09.m | 0866.09m3Organizational.1516-09.m | 08 Network Protection | 0866.09m3Organizational.1516-09.m 09.06 Network Security Management | Shared | n/a | The organization describes the groups, roles, and responsibilities for the logical management of network components, and ensures coordination of and consistency in the elements of the network infrastructure. | count: 011 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Regulatory Compliance, Storage | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0867.09m3Organizational.17-09.m | hipaa-0867.09m3Organizational.17-09.m | 0867.09m3Organizational.17 - 09.m | Network Controls | Wireless access points are placed in secure areas and shut down when not in use (e.g. nights, weekends). | Customer | n/a | Wireless access is not implemented for Azure datacenter or service provision environments. Therefore, this requirement is not applicable. | count: 001 Storage Accounts should use a virtual network service endpoint (60d21c4f-21a3-4d94-85f4-b924e6aeeda4) |
Network | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0868.09m3Organizational.18-09.m | hipaa-0868.09m3Organizational.18-09.m | 0868.09m3Organizational.18-09.m | 08 Network Protection | 0868.09m3Organizational.18-09.m 09.06 Network Security Management | Shared | n/a | The organization builds a firewall configuration to restrict inbound and outbound traffic to that which is necessary for the covered data environment. | count: 005 [Preview]: Container Registry should use a virtual network service endpoint (c4857be7-912a-4c75-87e6-e30292bcdf78), Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0869.09m3Organizational.19-09.m | hipaa-0869.09m3Organizational.19-09.m | 0869.09m3Organizational.19-09.m | 08 Network Protection | 0869.09m3Organizational.19-09.m 09.06 Network Security Management | Shared | n/a | The router configuration files are secured and synchronized. | count: 011 [Preview]: Container Registry should use a virtual network service endpoint (c4857be7-912a-4c75-87e6-e30292bcdf78), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Create configuration plan protection (874a6f2e-2098-53bc-3a16-20dcdc425a7e), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0870.09m3Organizational.20-09.m | hipaa-0870.09m3Organizational.20-09.m | 0870.09m3Organizational.20-09.m | 08 Network Protection | 0870.09m3Organizational.20-09.m 09.06 Network Security Management | Shared | n/a | Access to all proxies is denied, except for those hosts, ports, and services that are explicitly required. | count: 008 [Preview]: Container Registry should use a virtual network service endpoint (c4857be7-912a-4c75-87e6-e30292bcdf78), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0871.09m3Organizational.22-09.m | hipaa-0871.09m3Organizational.22-09.m | 0871.09m3Organizational.22-09.m | 08 Network Protection | 0871.09m3Organizational.22-09.m 09.06 Network Security Management | Shared | n/a | Authoritative DNS servers are segregated into internal and external roles. | count: 004 [Preview]: Container Registry should use a virtual network service endpoint (c4857be7-912a-4c75-87e6-e30292bcdf78), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0885.09n2Organizational.3-09.n | hipaa-0885.09n2Organizational.3-09.n | 0885.09n2Organizational.3-09.n | 08 Network Protection | 0885.09n2Organizational.3-09.n 09.06 Network Security Management | Shared | n/a | The organization reviews and updates the interconnection security agreements on an ongoing basis, verifying enforcement of security requirements. | count: 003 [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0886.09n2Organizational.4-09.n | hipaa-0886.09n2Organizational.4-09.n | 0886.09n2Organizational.4-09.n | 08 Network Protection | 0886.09n2Organizational.4-09.n 09.06 Network Security Management | Shared | n/a | The organization employs and documents in a formal agreement or other document—either i) allow-all, deny-by-exception, or ii) deny-all, permit-by-exception (preferred)—policy for allowing specific information systems to connect to external information systems. | count: 002 Employ restrictions on external system interconnections (80029bc5-834f-3a9c-a2d8-acbc1aab4e9f), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0887.09n2Organizational.5-09.n | hipaa-0887.09n2Organizational.5-09.n | 0887.09n2Organizational.5-09.n | 08 Network Protection | 0887.09n2Organizational.5-09.n 09.06 Network Security Management | Shared | n/a | The organization requires external/outsourced service providers to identify the specific functions, ports, and protocols used in the provision of the external/outsourced services. | count: 003 [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Require developer to identify SDLC ports, protocols, and services (f6da5cca-5795-60ff-49e1-4972567815fe), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0888.09n2Organizational.6-09.n | hipaa-0888.09n2Organizational.6-09.n | 0888.09n2Organizational.6-09.n | 08 Network Protection | 0888.09n2Organizational.6-09.n 09.06 Network Security Management | Shared | n/a | The contract with the external/outsourced service provider includes the specification that the service provider is responsible for the protection of covered information shared. | count: 017 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Network, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0894.01m2Organizational.7-01.m | hipaa-0894.01m2Organizational.7-01.m | 0894.01m2Organizational.7-01.m | 08 Network Protection | 0894.01m2Organizational.7-01.m 01.04 Network Access Control | Shared | n/a | Networks are segregated from production-level networks when migrating physical servers, applications, or data to virtualized servers. | count: 019 [Preview]: Container Registry should use a virtual network service endpoint (c4857be7-912a-4c75-87e6-e30292bcdf78), App Service apps should use a virtual network service endpoint (2d21331d-a4c2-4def-a9ad-ee4e1e023beb), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Cosmos DB should use a virtual network service endpoint (e0a2b1a3-f7f9-4569-807f-2a9edebdf4d9), Deploy network watcher when virtual networks are created (a9b99dd8-06c5-4317-8629-9d86a3c6e7d9), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Event Hub should use a virtual network service endpoint (d63edb4a-c612-454d-b47d-191a724fcbf0), Gateway subnets should not be configured with a network security group (35f9c03a-cc27-418e-9c0c-539ff999d010), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Key Vault should use a virtual network service endpoint (ea4d6841-2173-4317-9747-ff522a45120f), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09), SQL Server should use a virtual network service endpoint (ae5d2f14-d830-42b6-9899-df6cfe9c71a3), Storage Accounts should use a virtual network service endpoint (60d21c4f-21a3-4d94-85f4-b924e6aeeda4), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3) |
Network, Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0901.09s1Organizational.1-09.s | hipaa-0901.09s1Organizational.1-09.s | 0901.09s1Organizational.1-09.s | 09 Transmission Protection | 0901.09s1Organizational.1-09.s 09.08 Exchange of Information | Shared | n/a | The organization formally addresses multiple safeguards before allowing the use of information systems for information exchange. | count: 031 App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Categorize information (93fa357f-2e38-22a9-5138-8cc5124e1923), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop business classification schemes (11ba0508-58a8-44de-5f3a-9e05d80571da), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Ensure security categorization is approved (6c79c3e5-5f7b-a48a-5c7b-8c158bc01115), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0902.09s2Organizational.13-09.s | hipaa-0902.09s2Organizational.13-09.s | 0902.09s2Organizational.13-09.s | 09 Transmission Protection | 0902.09s2Organizational.13-09.s 09.08 Exchange of Information | Shared | n/a | Remote (external) access to the organization's information assets and access to external information assets (for which the organization has no control) is based on clearly defined terms and conditions. | count: 014 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Authorize remote access to privileged commands (01c387ea-383d-4ca9-295a-977fab516b03), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Provide capability to disconnect or disable remote access (4edaca8c-0912-1ac5-9eaa-6a1057740fae), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0903.10f1Organizational.1-10.f | hipaa-0903.10f1Organizational.1-10.f | 0903.10f1Organizational.1-10.f | 09 Transmission Protection | 0903.10f1Organizational.1-10.f 10.03 Cryptographic Controls | Shared | n/a | Encryption is used to protect covered information on mobile/removable media and across communication lines based on pre-determined criteria. | count: 003 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0904.10f2Organizational.1-10.f | hipaa-0904.10f2Organizational.1-10.f | 0904.10f2Organizational.1-10.f | 09 Transmission Protection | 0904.10f2Organizational.1-10.f 10.03 Cryptographic Controls | Shared | n/a | Key management is implemented based on specific roles and responsibilities, and in consideration of national and international regulations, restrictions, and issues. | count: 010 Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0912.09s1Organizational.4-09.s | hipaa-0912.09s1Organizational.4-09.s | 0912.09s1Organizational.4-09.s | 09 Transmission Protection | 0912.09s1Organizational.4-09.s 09.08 Exchange of Information | Shared | n/a | Cryptography is used to protect the confidentiality and integrity of remote access sessions to the internal network and to external systems. | count: 009 App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0913.09s1Organizational.5-09.s | hipaa-0913.09s1Organizational.5-09.s | 0913.09s1Organizational.5-09.s | 09 Transmission Protection | 0913.09s1Organizational.5-09.s 09.08 Exchange of Information | Shared | n/a | Strong cryptography protocols are used to safeguard covered information during transmission over less trusted/open public networks. | count: 005 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0914.09s1Organizational.6-09.s | hipaa-0914.09s1Organizational.6-09.s | 0914.09s1Organizational.6-09.s | 09 Transmission Protection | 0914.09s1Organizational.6-09.s 09.08 Exchange of Information | Shared | n/a | The organization ensures that communication protection requirements, including the security of exchanges of information, are the subject of policy development and compliance audits. | count: 006 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0915.09s2Organizational.2-09.s | hipaa-0915.09s2Organizational.2-09.s | 0915.09s2Organizational.2-09.s | 09 Transmission Protection | 0915.09s2Organizational.2-09.s 09.08 Exchange of Information | Shared | n/a | The organization limits the use of organization-controlled portable storage media by authorized individuals on external information systems. | count: 004 App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0916.09s2Organizational.4-09.s | hipaa-0916.09s2Organizational.4-09.s | 0916.09s2Organizational.4-09.s | 09 Transmission Protection | 0916.09s2Organizational.4-09.s 09.08 Exchange of Information | Shared | n/a | The information system prohibits remote activation of collaborative computing devices and provides an explicit indication of use to users physically present at the devices. | count: 007 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Explicitly notify use of collaborative computing devices (62fa14f0-4cbe-762d-5469-0899a99b98aa), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Prohibit remote activation of collaborative computing devices (678ca228-042d-6d8e-a598-c58d5670437d), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0926.09v1Organizational.2-09.v | hipaa-0926.09v1Organizational.2-09.v | 0926.09v1Organizational.2-09.v | 09 Transmission Protection | 0926.09v1Organizational.2-09.v 09.08 Exchange of Information | Shared | n/a | Approvals are obtained prior to using external public services, including instant messaging or file sharing. | count: 005 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0927.09v1Organizational.3-09.v | hipaa-0927.09v1Organizational.3-09.v | 0927.09v1Organizational.3-09.v | 09 Transmission Protection | 0927.09v1Organizational.3-09.v 09.08 Exchange of Information | Shared | n/a | Stronger levels of authentication are implemented to control access from publicly accessible networks. | count: 004 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0928.09v1Organizational.45-09.v | hipaa-0928.09v1Organizational.45-09.v | 0928.09v1Organizational.45-09.v | 09 Transmission Protection | 0928.09v1Organizational.45-09.v 09.08 Exchange of Information | Shared | n/a | Stronger controls are implemented to protect certain electronic messages, and electronic messages are protected throughout the duration of its end-to-end transport path, using cryptographic mechanisms unless protected by alternative measures. | count: 009 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0929.09v1Organizational.6-09.v | hipaa-0929.09v1Organizational.6-09.v | 0929.09v1Organizational.6-09.v | 09 Transmission Protection | 0929.09v1Organizational.6-09.v 09.08 Exchange of Information | Shared | n/a | The organization never sends unencrypted sensitive information by end-user messaging technologies (e.g., email, instant messaging, and chat). | count: 009 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0943.09y1Organizational.1-09.y | hipaa-0943.09y1Organizational.1-09.y | 0943.09y1Organizational.1-09.y | 09 Transmission Protection | 0943.09y1Organizational.1-09.y 09.09 Electronic Commerce Services | Shared | n/a | Data involved in electronic commerce and online transactions is checked to determine if it contains covered information. | count: 004 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Document process to ensure integrity of PII (18e7906d-4197-20fa-2f14-aaac21864e71), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
Regulatory Compliance, Storage | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0944.09y1Organizational.2-09.y | hipaa-0944.09y1Organizational.2-09.y | 0944.09y1Organizational.2-09.y | 09 Transmission Protection | 0944.09y1Organizational.2-09.y 09.09 Electronic Commerce Services | Shared | n/a | Security is maintained through all aspects of the transaction. | count: 008 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0945.09y1Organizational.3-09.y | hipaa-0945.09y1Organizational.3-09.y | 0945.09y1Organizational.3-09.y | 09 Transmission Protection | 0945.09y1Organizational.3-09.y 09.09 Electronic Commerce Services | Shared | n/a | Protocols used to communicate between all involved parties are secured using cryptographic techniques (e.g., SSL). | count: 006 Audit Windows machines that do not contain the specified certificates in Trusted Root (934345e1-4dfb-4c70-90d7-41990dc9608b), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0946.09y2Organizational.14-09.y | hipaa-0946.09y2Organizational.14-09.y | 0946.09y2Organizational.14 - 09.y | On-line Transactions | The organization requires the use of encryption between, and the use of electronic signatures by, each of the parties involved in the transaction. | Customer | n/a | Azure does not implement electronic messaging and electronic signatures, per FDA CFR 21 Part 11; therefore, the requirement is not applicable. | count: 001 Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb) |
Cache | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0947.09y2Organizational.2-09.y | hipaa-0947.09y2Organizational.2-09.y | 0947.09y2Organizational.2-09.y | 09 Transmission Protection | 0947.09y2Organizational.2-09.y 09.09 Electronic Commerce Services | Shared | n/a | The organization ensures the storage of the transaction details are located outside of any publicly accessible environments (e.g., on a storage platform existing on the organization's intranet) and not retained and exposed on a storage medium directly accessible from the Internet. | count: 011 Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Restrict location of information processing, storage and services (0040d2e5-2779-170d-6a2c-1f5fca353335), Transfer backup information to an alternate storage site (7bdb79ea-16b8-453e-4ca4-ad5b16012414) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0948.09y2Organizational.3-09.y | hipaa-0948.09y2Organizational.3-09.y | 0948.09y2Organizational.3-09.y | 09 Transmission Protection | 0948.09y2Organizational.3-09.y 09.09 Electronic Commerce Services | Shared | n/a | Where a trusted authority is used (e.g., for the purposes of issuing and maintaining digital signatures and/or digital certificates), security is integrated and embedded throughout the entire end-to-end certificate/signature management process. | count: 006 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Distribute authenticators (098dcde7-016a-06c3-0985-0daaf3301d3a), Enforce random unique session identifiers (c7d57a6a-7cc2-66c0-299f-83bf90558f5d), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0949.09y2Organizational.5-09.y | hipaa-0949.09y2Organizational.5-09.y | 0949.09y2Organizational.5-09.y | 09 Transmission Protection | 0949.09y2Organizational.5-09.y 09.09 Electronic Commerce Services | Shared | n/a | The protocols used for communications are enhanced to address any new vulnerability, and the updated versions of the protocols are adopted as soon as possible. | count: 006 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Require developer to identify SDLC ports, protocols, and services (f6da5cca-5795-60ff-49e1-4972567815fe) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 0960.09sCSPOrganizational.1-09.s | hipaa-0960.09sCSPOrganizational.1-09.s | 0960.09sCSPOrganizational.1-09.s | 09 Transmission Protection | 0960.09sCSPOrganizational.1-09.s 09.08 Exchange of Information | Shared | n/a | Cloud service providers use secure (e.g., non-clear text and authenticated) standardized network protocols for the import and export of data and to manage the service, and make available a document to consumers (tenants) detailing the relevant interoperability and portability standards that are involved. | count: 002 Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 099.09m2Organizational.11-09.m | hipaa-099.09m2Organizational.11-09.m | 099.09m2Organizational.11-09.m | 09 Transmission Protection | 099.09m2Organizational.11-09.m 09.06 Network Security Management | Shared | n/a | The organization uses FIPS-validated cryptographic mechanisms during transmission to prevent unauthorized disclosure of information and detect changes to information unless otherwise protected by organization-defined alternative physical measures. | count: 003 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1002.01d1System.1-01.d | hipaa-1002.01d1System.1-01.d | 1002.01d1System.1-01.d | 10 Password Management | 1002.01d1System.1-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | Passwords are not displayed when entered. | count: 002 Obscure feedback information during authentication process (1ff03f2a-974b-3272-34f2-f6cd51420b30), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1003.01d1System.3-01.d | hipaa-1003.01d1System.3-01.d | 1003.01d1System.3-01.d | 10 Password Management | 1003.01d1System.3-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | User identities are verified prior to performing password resets. | count: 003 Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1004.01d1System.8913-01.d | hipaa-1004.01d1System.8913-01.d | 1004.01d1System.8913-01.d | 10 Password Management | 1004.01d1System.8913-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | The organization maintains a list of commonly-used, expected, or compromised passwords, and updates the list (i) at least every 180 days and (ii) when organizational passwords are suspected to have been compromised (either directly or indirectly); allows users to select long passwords and passphrases, including spaces and all printable characters; employs automated tools to assist the user in selecting strong passwords and authenticators; and verifies, when users create or update passwords, that the passwords are not found on the organization-defined list of commonly-used, expected, or compromised passwords. | count: 008 Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1005.01d1System.1011-01.d | hipaa-1005.01d1System.1011-01.d | 1005.01d1System.1011-01.d | 10 Password Management | 1005.01d1System.1011-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | The organization transmits passwords only when cryptographically-protected and stores passwords using an approved hash algorithm. | count: 006 Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1006.01d2System.1-01.d | hipaa-1006.01d2System.1-01.d | 1006.01d2System.1-01.d | 10 Password Management | 1006.01d2System.1-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | Passwords are not included in automated log-on processes. | count: 005 Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3), Generate error messages (c2cb4658-44dc-9d11-3dad-7c6802dd5ba3), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Obscure feedback information during authentication process (1ff03f2a-974b-3272-34f2-f6cd51420b30) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1007.01d2System.2-01.d | hipaa-1007.01d2System.2-01.d | 1007.01d2System.2-01.d | 10 Password Management | 1007.01d2System.2-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | Passwords are encrypted during transmission and storage on all system components. | count: 001 Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1008.01d2System.3-01.d | hipaa-1008.01d2System.3-01.d | 1008.01d2System.3-01.d | 10 Password Management | 1008.01d2System.3-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | Users sign a statement acknowledging their responsibility to keep passwords confidential. | count: 015 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document organizational access agreements (c981fa70-2e58-8141-1457-e7f62ebc2ade), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Require users to sign access agreement (3af53f59-979f-24a8-540f-d7cdbc366607), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update organizational access agreements (e21f91d1-2803-0282-5f2d-26ebc4b170ef), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1009.01d2System.4-01.d | hipaa-1009.01d2System.4-01.d | 1009.01d2System.4-01.d | 10 Password Management | 1009.01d2System.4-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | Temporary passwords are unique and not guessable. | count: 004 Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1014.01d1System.12-01.d | hipaa-1014.01d1System.12-01.d | 1014.01d1System.12-01.d | 10 Password Management | 1014.01d1System.12-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | The organization avoids the use of third-parties or unprotected (clear text) electronic mail messages for the dissemination of passwords. | count: 011 Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1015.01d1System.14-01.d | hipaa-1015.01d1System.14-01.d | 1015.01d1System.14-01.d | 10 Password Management | 1015.01d1System.14-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | Users acknowledge receipt of passwords. | count: 004 Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1022.01d1System.15-01.d | hipaa-1022.01d1System.15-01.d | 1022.01d1System.15-01.d | 10 Password Management | 1022.01d1System.15-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | Password policies, applicable to mobile devices, are documented and enforced through technical controls on all company devices or devices approved for BYOD usage, and prohibit the changing of password/PIN lengths and authentication requirements. | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1031.01d1System.34510-01.d | hipaa-1031.01d1System.34510-01.d | 1031.01d1System.34510-01.d | 10 Password Management | 1031.01d1System.34510-01.d 01.02 Authorized Access to Information Systems | Shared | n/a | The organization changes passwords for default system accounts, whenever there is any indication of password compromise, at first logon following the issuance of a temporary password, and requires immediate selection of a new password upon account recovery. | count: 006 Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1106.01b1System.1-01.b | hipaa-1106.01b1System.1-01.b | 1106.01b1System.1-01.b | 11 Access Control | 1106.01b1System.1-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | User identities are verified prior to establishing accounts. | count: 010 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1107.01b1System.2-01.b | hipaa-1107.01b1System.2-01.b | 1107.01b1System.2-01.b | 11 Access Control | 1107.01b1System.2-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | Default and unnecessary system accounts are removed, disabled, or otherwise secured (e.g., the passwords are changed and privileges are reduced to the lowest levels of access). | count: 004 Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1108.01b1System.3-01.b | hipaa-1108.01b1System.3-01.b | 1108.01b1System.3-01.b | 11 Access Control | 1108.01b1System.3-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | Account managers are notified when users' access rights change (e.g., termination, change in position) and modify the user's account accordingly. | count: 004 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1109.01b1System.479-01.b | hipaa-1109.01b1System.479-01.b | 1109.01b1System.479-01.b | 11 Access Control | 1109.01b1System.479-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | User registration and deregistration, at a minimum: (i) communicates relevant policies to users and require acknowledgement (e.g., signed or captured electronically); (ii) checks authorization and minimum level of access necessary prior to granting access; (iii) ensures access is appropriate to the business needs (consistent with sensitivity/risk and does not violate segregation of duties requirements); (iv) addresses termination and transfer; (v) ensures default accounts are removed and/or renamed; (vi) removes or blocks critical access rights of users who have changed roles or jobs; and, (vii) automatically removes or disables inactive accounts. | count: 024 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1110.01b1System.5-01.b | hipaa-1110.01b1System.5-01.b | 1110.01b1System.5-01.b | 11 Access Control | 1110.01b1System.5-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | Users are given a written statement of their access rights, which they are required to sign stating they understand the conditions of access. Guest/anonymous, shared/group, emergency and temporary accounts are specifically authorized and use monitored. | count: 011 Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11109.01q1Organizational.57-01.q | hipaa-11109.01q1Organizational.57-01.q | 11109.01q1Organizational.57-01.q | 11 Access Control | 11109.01q1Organizational.57-01.q 01.05 Operating System Access Control | Shared | n/a | The organization ensures that redundant user IDs are not issued to other users and that all users are uniquely identified and authenticated for both local and remote access to information systems. | count: 007 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Identify status of individual users (ca748dfe-3e28-1d18-4221-89aea30aa0a5), Prevent identifier reuse for the defined time period (4781e5fd-76b8-7d34-6df3-a0a7fca47665), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1111.01b2System.1-01.b | hipaa-1111.01b2System.1-01.b | 1111.01b2System.1-01.b | 11 Access Control | 1111.01b2System.1-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | Group, shared or generic accounts and passwords (e.g., for first-time log-on) are not used. | count: 002 Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11110.01q1Organizational.6-01.q | hipaa-11110.01q1Organizational.6-01.q | 11110.01q1Organizational.6 - 01.q | User Identification and Authentication | Non-organizational users (all information system users other than organizational users, such as patients, customers, contractors, or foreign nationals), or processes acting on behalf of non-organizational users, determined to need access to information residing on the organization's information systems, are uniquely identified and authenticated. | Customer | n/a | Azure personnel have not access or visibility into hosted customer environments, and therefore do not dictate or manage the account provisioning of a customer's users. Therefore, this requirement is not applicable. | count: 001 Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11111.01q2System.4-01.q | hipaa-11111.01q2System.4-01.q | 11111.01q2System.4-01.q | 11 Access Control | 11111.01q2System.4-01.q 01.05 Operating System Access Control | Shared | n/a | When PKI-based authentication is used, the information system validates certificates by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information; enforces access to the corresponding private key; maps the identity to the corresponding account of the individual or group; and implements a local cache of revocation data to support path discovery and validation in case of an inability to access revocation information via the network. | count: 004 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11112.01q2Organizational.67-01.q | hipaa-11112.01q2Organizational.67-01.q | 11112.01q2Organizational.67-01.q | 11 Access Control | 11112.01q2Organizational.67-01.q 01.05 Operating System Access Control | Shared | n/a | The information system employs replay-resistant authentication mechanisms such as nonce, one-time passwords, or time stamps to secure network access for privileged accounts. | count: 003 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1112.01b2System.2-01.b | hipaa-1112.01b2System.2-01.b | 1112.01b2System.2-01.b | 11 Access Control | 1112.01b2System.2-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | User identities are verified in person before a designated registration authority with authorization by a designated organizational official (e.g., a supervisor or other individual defined in an applicable security plan) prior to receiving a hardware token. | count: 007 Assign an authorizing official (AO) (e29a8f1b-149b-2fa3-969d-ebee1baa9472), Distribute authenticators (098dcde7-016a-06c3-0985-0daaf3301d3a), Ensure resources are authorized (0716f0f5-4955-2ccb-8d5e-c6be14d57c0f), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1), Update the security authorization (449ebb52-945b-36e5-3446-af6f33770f8f), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11126.01t1Organizational.12-01.t | hipaa-11126.01t1Organizational.12-01.t | 11126.01t1Organizational.12-01.t | 11 Access Control | 11126.01t1Organizational.12-01.t 01.05 Operating System Access Control | Shared | n/a | A time-out mechanism (e.g., a screen saver) pauses the session screen after 15 minutes of inactivity, closes network sessions after 30 minutes of inactivity, and requires the user to reestablish authenticated access once the session has been paused or closed; or, if the system cannot be modified, a limited form of time-out that clears the screen but does not close down the application or network sessions is used. | count: 001 Reauthenticate or terminate a user session (d6653f89-7cb5-24a4-9d71-51581038231b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1114.01h1Organizational.123-01.h | hipaa-1114.01h1Organizational.123-01.h | 1114.01h1Organizational.123-01.h | 11 Access Control | 1114.01h1Organizational.123-01.h 01.03 User Responsibilities | Shared | n/a | Covered or critical business information is not left unattended or available for unauthorized individuals to access, including on desks, printers, copiers, fax machines, and computer monitors. | count: 002 Define and enforce the limit of concurrent sessions (d8350d4c-9314-400b-288f-20ddfce04fbd), Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11154.02i1Organizational.5-02.i | hipaa-11154.02i1Organizational.5-02.i | 11154.02i1Organizational.5-02.i | 11 Access Control | 11154.02i1Organizational.5-02.i 02.04 Termination or Change of Employment | Shared | n/a | Access rights to information assets and facilities is reduced or removed before the employment or other workforce arrangement terminates or changes, depending on the evaluation of risk factors. | count: 008 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11155.02i2Organizational.2-02.i | hipaa-11155.02i2Organizational.2-02.i | 11155.02i2Organizational.2-02.i | 11 Access Control | 11155.02i2Organizational.2-02.i 02.04 Termination or Change of Employment | Shared | n/a | The organization employs automated mechanisms to notify specific personnel or roles (formally defined by the organization) upon termination of an individual. | count: 010 Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1116.01j1Organizational.145-01.j | hipaa-1116.01j1Organizational.145-01.j | 1116.01j1Organizational.145-01.j | 11 Access Control | 1116.01j1Organizational.145-01.j 01.04 Network Access Control | Shared | n/a | Strong authentication methods are implemented for all external connections to the organization’s network. | count: 006 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1117.01j1Organizational.23-01.j | hipaa-1117.01j1Organizational.23-01.j | 1117.01j1Organizational.23 - 01.j | User Authentication for External Connections | Remote access by vendors and business partners (e.g., for remote maintenance) is disabled/deactivated when not in use. | Customer | n/a | Sample of disabled accounts for third-party service providers. | count: 001 Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1118.01j2Organizational.124-01.j | hipaa-1118.01j2Organizational.124-01.j | 1118.01j2Organizational.124-01.j | 11 Access Control | 1118.01j2Organizational.124-01.j 01.04 Network Access Control | Shared | n/a | The organization has implemented encryption (e.g., VPN solutions or private lines) and logs remote access to the organization's network by employees, contractors, or third-party. | count: 009 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11180.01c3System.6-01.c | hipaa-11180.01c3System.6-01.c | 11180.01c3System.6-01.c | 11 Access Control | 11180.01c3System.6-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | Access to management functions or administrative consoles for systems hosting virtualized systems are restricted to personnel based upon the principle of least privilege and supported through technical controls. | count: 007 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1119.01j2Organizational.3-01.j | hipaa-1119.01j2Organizational.3-01.j | 1119.01j2Organizational.3-01.j | 11 Access Control | 1119.01j2Organizational.3-01.j 01.04 Network Access Control | Shared | n/a | Network equipment is checked for unanticipated dial-up capabilities. | count: 005 Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11190.01t1Organizational.3-01.t | hipaa-11190.01t1Organizational.3-01.t | 11190.01t1Organizational.3-01.t | 11 Access Control | 11190.01t1Organizational.3-01.t 01.05 Operating System Access Control | Shared | n/a | Bring your own device (BYOD) and/or company-owned devices are configured to require an automatic lockout screen, and the requirement is enforced through technical controls. | count: 005 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1120.09ab3System.9-09.ab | hipaa-1120.09ab3System.9-09.ab | 1120.09ab3System.9-09.ab | 11 Access Control | 1120.09ab3System.9-09.ab 09.10 Monitoring | Shared | n/a | Unauthorized remote connections to the information systems are monitored and reviewed at least quarterly, and appropriate action is taken if an unauthorized connection is discovered. | count: 001 Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9) |
Monitoring | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11208.01q1Organizational.8-01.q | hipaa-11208.01q1Organizational.8-01.q | 11208.01q1Organizational.8 - 01.q | User Identification and Authentication | The organization requires that electronic signatures, unique to one individual, cannot be reused by, or reassigned to, anyone else. | Customer | n/a | Azure does not implement identification codes and electronic signatures, per FDA CFR 21 Part 11. | count: 001 There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1121.01j3Organizational.2-01.j | hipaa-1121.01j3Organizational.2-01.j | 1121.01j3Organizational.2-01.j | 11 Access Control | 1121.01j3Organizational.2-01.j 01.04 Network Access Control | Shared | n/a | Remote administration sessions are authorized, encrypted, and employ increased security measures. | count: 011 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11210.01q2Organizational.10-01.q | hipaa-11210.01q2Organizational.10-01.q | 11210.01q2Organizational.10 - 01.q | User Identification and Authentication | Electronic signatures and handwritten signatures executed to electronic records shall be linked to their respective electronic records. | Customer | n/a | Azure does not implement identification codes and electronic signatures, per FDA CFR 21 Part 11. | count: 001 Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f) |
Guest Configuration | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11211.01q2Organizational.11-01.q | hipaa-11211.01q2Organizational.11-01.q | 11211.01q2Organizational.11 - 01.q | User Identification and Authentication | Signed electronic records shall contain information associated with the signing in human-readable format. | Customer | n/a | Azure does not implement identification codes and electronic signatures, per FDA CFR 21 Part 11. | count: 001 Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7) |
Guest Configuration | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11219.01b1Organizational.10-01.b | hipaa-11219.01b1Organizational.10-01.b | 11219.01b1Organizational.10-01.b | 11 Access Control | 11219.01b1Organizational.10-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | The organization maintains a current listing of all workforce members (individuals, contractors, vendors, business partners, etc.) with access to sensitive information (e.g., PII). | count: 005 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1122.01q1System.1-01.q | hipaa-1122.01q1System.1-01.q | 1122.01q1System.1-01.q | 11 Access Control | 1122.01q1System.1-01.q 01.05 Operating System Access Control | Shared | n/a | Unique IDs that can be used to trace activities to the responsible individual are required for all types of organizational and non-organizational users. | count: 007 Accept only FICAM-approved third-party credentials (2d2ca910-7957-23ee-2945-33f401606efc), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Conform to FICAM-issued profiles (a8df9c78-4044-98be-2c05-31a315ac8957), Employ FICAM-approved resources to accept third-party credentials (db8b35d6-8adb-3f51-44ff-c648ab5b1530), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 11220.01b1System.10-01.b | hipaa-11220.01b1System.10-01.b | 11220.01b1System.10-01.b | 11 Access Control | 11220.01b1System.10-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | User registration and de-registration formally address establishing, activating, modifying, reviewing, disabling and removing accounts. | count: 026 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1123.01q1System.2-01.q | hipaa-1123.01q1System.2-01.q | 1123.01q1System.2-01.q | 11 Access Control | 1123.01q1System.2-01.q 01.05 Operating System Access Control | Shared | n/a | Users who perform privileged functions (e.g., system administration) use separate accounts when performing those privileged functions. | count: 006 Audit Windows machines that have extra accounts in the Administrators group (3d2a3320-2a72-4c67-ac5f-caa40fbee2b2), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1124.01q1System.34-01.q | hipaa-1124.01q1System.34-01.q | 1124.01q1System.34-01.q | 11 Access Control | 1124.01q1System.34-01.q 01.05 Operating System Access Control | Shared | n/a | Shared/group and generic user IDs are only used in exceptional circumstances where there is a clear business benefit, when user functions do not need to be traced, additional accountability controls are implemented, and after approval by management. | count: 002 Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1125.01q2System.1-01.q | hipaa-1125.01q2System.1-01.q | 1125.01q2System.1-01.q | 11 Access Control | 1125.01q2System.1-01.q 01.05 Operating System Access Control | Shared | n/a | Multi-factor authentication methods are used in accordance with organizational policy (e.g., for remote network access). | count: 004 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1127.01q2System.3-01.q | hipaa-1127.01q2System.3-01.q | 1127.01q2System.3-01.q | 11 Access Control | 1127.01q2System.3-01.q 01.05 Operating System Access Control | Shared | n/a | Where tokens are provided for multi-factor authentication, in-person verification is required prior to granting access. | count: 002 Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7), Distribute authenticators (098dcde7-016a-06c3-0985-0daaf3301d3a) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1128.01q2System.5-01.q | hipaa-1128.01q2System.5-01.q | 1128.01q2System.5-01.q | 11 Access Control | 1128.01q2System.5-01.q 01.05 Operating System Access Control | Shared | n/a | Help desk support requires user identification for any transaction that has information security implications. | count: 003 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1129.01v1System.12-01.v | hipaa-1129.01v1System.12-01.v | 1129.01v1System.12-01.v | 11 Access Control | 1129.01v1System.12-01.v 01.06 Application and Information Access Control | Shared | n/a | Access rights to applications and application functions should be restricted in accordance with the access control policy. | count: 012 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1130.01v2System.1-01.v | hipaa-1130.01v2System.1-01.v | 1130.01v2System.1-01.v | 11 Access Control | 1130.01v2System.1-01.v 01.06 Application and Information Access Control | Shared | n/a | Access rights from an application to other applications are controlled. | count: 005 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1131.01v2System.2-01.v | hipaa-1131.01v2System.2-01.v | 1131.01v2System.2-01.v | 11 Access Control | 1131.01v2System.2-01.v 01.06 Application and Information Access Control | Shared | n/a | Outputs from application systems handling covered information are limited to the minimum necessary and sent only to authorized terminals/locations. | count: 006 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1132.01v2System.3-01.v | hipaa-1132.01v2System.3-01.v | 1132.01v2System.3-01.v | 11 Access Control | 1132.01v2System.3-01.v 01.06 Application and Information Access Control | Shared | n/a | Covered information is encrypted when stored in non-secure areas and, if not encrypted at rest, the organization documents its rationale. | count: 002 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1133.01v2System.4-01.v | hipaa-1133.01v2System.4-01.v | 1133.01v2System.4-01.v | 11 Access Control | 1133.01v2System.4-01.v 01.06 Application and Information Access Control | Shared | n/a | Actions that can be performed without identification and authentication are permitted by exception. | count: 001 Identify actions allowed without authentication (92a7591f-73b3-1173-a09c-a08882d84c70) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1134.01v3System.1-01.v | hipaa-1134.01v3System.1-01.v | 1134.01v3System.1-01.v | 11 Access Control | 1134.01v3System.1-01.v 01.06 Application and Information Access Control | Shared | n/a | Copy, move, print, and storage of sensitive data are prohibited when accessed remotely without a defined business need. | count: 003 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1135.02i1Organizational.1234-02.i | hipaa-1135.02i1Organizational.1234-02.i | 1135.02i1Organizational.1234-02.i | 11 Access Control | 1135.02i1Organizational.1234-02.i 02.04 Termination or Change of Employment | Shared | n/a | Upon termination or changes in employment for employees, contractors, third-party users, or other workforce arrangement, physical and logical access rights and associated materials (e.g., passwords, keycards, keys, documentation that identify them as current members of the organization) are removed or modified to restrict access within 24 hours and old accounts are closed after 90 days of opening new accounts. | count: 009 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1136.02i2Organizational.1-02.i | hipaa-1136.02i2Organizational.1-02.i | 1136.02i2Organizational.1-02.i | 11 Access Control | 1136.02i2Organizational.1-02.i 02.04 Termination or Change of Employment | Shared | n/a | For instances of increased risk, physical, and logical access rights are immediately removed or modified following employee, contractor or third-party user termination, and allow for immediate escorting from the site, if necessary. | count: 006 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Disable user accounts posing a significant risk (22c16ae4-19d0-29cb-422f-cb44061180ee), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1137.06e1Organizational.1-06.e | hipaa-1137.06e1Organizational.1-06.e | 1137.06e1Organizational.1-06.e | 11 Access Control | 1137.06e1Organizational.1-06.e 06.01 Compliance with Legal Requirements | Shared | n/a | Acceptable use agreements are signed by all employees before being allowed access to information assets. | count: 008 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1139.01b1System.68-01.b | hipaa-1139.01b1System.68-01.b | 1139.01b1System.68-01.b | 11 Access Control | 1139.01b1System.68-01.b 01.02 Authorized Access to Information Systems | Shared | n/a | Account types are identified (individual, shared/group, system, application, guest/anonymous, emergency and temporary), conditions for group and role membership are established, and, if used, shared/group account credentials are modified when users are removed from the group. | count: 006 Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1143.01c1System.123-01.c | hipaa-1143.01c1System.123-01.c | 1143.01c1System.123-01.c | 11 Access Control | 1143.01c1System.123-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | Privileges are formally authorized and controlled, allocated to users on a need-to-use and event-by-event basis for their functional role (e.g., user or administrator), and documented for each system product/element. | count: 010 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1144.01c1System.4-01.c | hipaa-1144.01c1System.4-01.c | 1144.01c1System.4-01.c | 11 Access Control | 1144.01c1System.4-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | The organization explicitly authorizes access to specific security relevant functions (deployed in hardware, software, and firmware) and security-relevant information. | count: 006 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1145.01c2System.1-01.c | hipaa-1145.01c2System.1-01.c | 1145.01c2System.1-01.c | 11 Access Control | 1145.01c2System.1-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | Role-based access control is implemented and capable of mapping each user to one or more roles, and each role to one or more system functions. | count: 008 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1146.01c2System.23-01.c | hipaa-1146.01c2System.23-01.c | 1146.01c2System.23-01.c | 11 Access Control | 1146.01c2System.23-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | The organization promotes the development and use of programs that avoid the need to run with elevated privileges and system routines to avoid the need to grant privileges to users. | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Enforce software execution privileges (68d2e478-3b19-23eb-1357-31b296547457), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1147.01c2System.456-01.c | hipaa-1147.01c2System.456-01.c | 1147.01c2System.456-01.c | 11 Access Control | 1147.01c2System.456-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | Elevated privileges are assigned to a different user ID from those used for normal business use, all users access privileged services in a single role, and such privileged access is minimized. | count: 006 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1148.01c2System.78-01.c | hipaa-1148.01c2System.78-01.c | 1148.01c2System.78-01.c | 11 Access Control | 1148.01c2System.78-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | The organization restricts access to privileged functions and all security-relevant information. | count: 008 Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Windows machines should meet requirements for 'Security Options - Accounts' (ee984370-154a-4ee8-9726-19d900e56fc0) |
General, Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1149.01c2System.9-01.c | hipaa-1149.01c2System.9-01.c | 1149.01c2System.9 - 01.c | Privilege Management | The organization facilitates information sharing by enabling authorized users to determine a business partner's access when discretion is allowed as defined by the organization and by employing manual processes or automated mechanisms to assist users in making information sharing/collaboration decisions. | Customer | n/a | Sample of signed information sharing agreements (e.g., disclosure agreements) with business partners, depicting sharing terms and conditions. Third-party security policy and procedures (e.g., Azure Third Party Management SOP). |
count: 001 Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1150.01c2System.10-01.c | hipaa-1150.01c2System.10-01.c | 1150.01c2System.10-01.c | 11 Access Control | 1150.01c2System.10-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | The access control system for the system components storing, processing or transmitting covered information is set with a default "deny-all" setting. | count: 007 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1151.01c3System.1-01.c | hipaa-1151.01c3System.1-01.c | 1151.01c3System.1-01.c | 11 Access Control | 1151.01c3System.1-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | The organization limits authorization to privileged accounts on information systems to a pre-defined subset of users. | count: 007 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1152.01c3System.2-01.c | hipaa-1152.01c3System.2-01.c | 1152.01c3System.2-01.c | 11 Access Control | 1152.01c3System.2-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | The organization audits the execution of privileged functions on information systems and ensures information systems prevent non-privileged users from executing privileged functions. | count: 009 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1153.01c3System.35-01.c | hipaa-1153.01c3System.35-01.c | 1153.01c3System.35-01.c | 11 Access Control | 1153.01c3System.35-01.c 01.02 Authorized Access to Information Systems | Shared | n/a | All file system access not explicitly required is disabled, and only authorized users are permitted access to only that which is expressly required for the performance of the users' job duties. | count: 002 Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1154.01c3System.4-01.c | hipaa-1154.01c3System.4-01.c | 1154.01c3System.4 - 01.c | Privilege Management | Contractors are provided with minimal system and physical access only after the organization assesses the contractor's ability to comply with its security requirements and the contractor agrees to comply. | Customer | n/a | Master Supplier Service Agreement (MSSA) Supplier Data Protection Requirements (DPR) Sample of TVRA reports |
count: 001 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1166.01e1System.12-01.e | hipaa-1166.01e1System.12-01.e | 1166.01e1System.12-01.e | 11 Access Control | 1166.01e1System.12-01.e 01.02 Authorized Access to Information Systems | Shared | n/a | User access rights are reviewed after any changes and reallocated as necessary. | count: 008 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1167.01e2System.1-01.e | hipaa-1167.01e2System.1-01.e | 1167.01e2System.1-01.e | 11 Access Control | 1167.01e2System.1-01.e 01.02 Authorized Access to Information Systems | Shared | n/a | The organization maintains a documented list of authorized users of information assets. | count: 002 Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Identify status of individual users (ca748dfe-3e28-1d18-4221-89aea30aa0a5) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1168.01e2System.2-01.e | hipaa-1168.01e2System.2-01.e | 1168.01e2System.2-01.e | 11 Access Control | 1168.01e2System.2-01.e 01.02 Authorized Access to Information Systems | Shared | n/a | The organization reviews critical system accounts and privileged access rights every 60 days; all other accounts, including user access and changes to access authorizations, are reviewed every 90 days. | count: 004 Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1173.01j1Organizational.6-01.j | hipaa-1173.01j1Organizational.6-01.j | 1173.01j1Organizational.6 - 01.j | User Authentication for External Connections | If encryption is not used for dial-up connections, the CIO or his/her designated representative provides specific written authorization. | Customer | n/a | Dialup modems and connectivity is not permitted within production data and datacenter hosting environments; thus, the control is not applicable. | count: 001 Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1174.01j1Organizational.7-01.j | hipaa-1174.01j1Organizational.7-01.j | 1174.01j1Organizational.7 - 01.j | User Authentication for External Connections | The organization protects wireless access to systems containing sensitive information by authenticating both users and devices. | Customer | n/a | Wireless access is not permitted for production data and datacenter hosting environments; thus, the control is not applicable. | count: 001 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1175.01j1Organizational.8-01.j | hipaa-1175.01j1Organizational.8-01.j | 1175.01j1Organizational.8-01.j | 11 Access Control | 1175.01j1Organizational.8-01.j 01.04 Network Access Control | Shared | n/a | Remote access to business information across public networks only takes place after successful identification and authentication. | count: 005 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1176.01j2Organizational.5-01.j | hipaa-1176.01j2Organizational.5-01.j | 1176.01j2Organizational.5 - 01.j | User Authentication for External Connections | The organization requires a callback capability with re-authentication to verify dial-up connections from authorized locations. | Customer | n/a | Dialup modems and connectivity is not permitted within production data and datacenter hosting environments; thus, the control is not applicable. | count: 001 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1177.01j2Organizational.6-01.j | hipaa-1177.01j2Organizational.6-01.j | 1177.01j2Organizational.6 - 01.j | User Authentication for External Connections | User IDs assigned to vendors are reviewed in accordance with the organization's access review policy, at a minimum annually. | Customer | n/a | Evidence of annual review of vendor accounts (e.g., a sample of User Access Rights (UAR) reviews of vendor accounts). | count: 001 Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1178.01j2Organizational.7-01.j | hipaa-1178.01j2Organizational.7-01.j | 1178.01j2Organizational.7-01.j | 11 Access Control | 1178.01j2Organizational.7-01.j 01.04 Network Access Control | Shared | n/a | Node authentication, including cryptographic techniques (e.g., machine certificates), can serve as an alternative means of authenticating groups of remote users where they are connected to a secure, shared computer facility. | count: 004 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Require use of individual authenticators (08ad71d0-52be-6503-4908-e015460a16ae), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1179.01j3Organizational.1-01.j | hipaa-1179.01j3Organizational.1-01.j | 1179.01j3Organizational.1-01.j | 11 Access Control | 1179.01j3Organizational.1-01.j 01.04 Network Access Control | Shared | n/a | The information system monitors and controls remote access methods. | count: 007 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1192.01l1Organizational.1-01.l | hipaa-1192.01l1Organizational.1-01.l | 1192.01l1Organizational.1-01.l | 11 Access Control | 1192.01l1Organizational.1-01.l 01.04 Network Access Control | Shared | n/a | Access to network equipment is physically protected. | count: 005 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1193.01l2Organizational.13-01.l | hipaa-1193.01l2Organizational.13-01.l | 1193.01l2Organizational.13-01.l | 11 Access Control | 1193.01l2Organizational.13-01.l 01.04 Network Access Control | Shared | n/a | Controls for the access to diagnostic and configuration ports include the use of a key lock and the implementation of supporting procedures to control physical access to the port. | count: 005 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1194.01l2Organizational.2-01.l | hipaa-1194.01l2Organizational.2-01.l | 1194.01l2Organizational.2-01.l | 11 Access Control | 1194.01l2Organizational.2-01.l 01.04 Network Access Control | Shared | n/a | Ports, services, and similar applications installed on a computer or network systems, which are not specifically required for business functionality, are disabled or removed. | count: 001 App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71) |
App Service | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1195.01l3Organizational.1-01.l | hipaa-1195.01l3Organizational.1-01.l | 1195.01l3Organizational.1-01.l | 11 Access Control | 1195.01l3Organizational.1-01.l 01.04 Network Access Control | Shared | n/a | The organization reviews the information system within 365 days to identify and disable unnecessary and non-secure functions, ports, protocols, and/or services. | count: 001 Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9) |
App Service | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1197.01l3Organizational.3-01.l | hipaa-1197.01l3Organizational.3-01.l | 1197.01l3Organizational.3-01.l | 11 Access Control | 1197.01l3Organizational.3-01.l 01.04 Network Access Control | Shared | n/a | The organization disables Bluetooth and peer-to-peer networking protocols within the information system determined to be unnecessary or non-secure. | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1201.06e1Organizational.2-06.e | hipaa-1201.06e1Organizational.2-06.e | 1201.06e1Organizational.2-06.e | 12 Audit Logging & Monitoring | 1201.06e1Organizational.2-06.e 06.01 Compliance with Legal Requirements | Shared | n/a | The organization provides notice that the employee's actions may be monitored, and that the employee consents to such monitoring. | count: 012 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1202.09aa1System.1-09.aa | hipaa-1202.09aa1System.1-09.aa | 1202.09aa1System.1-09.aa | 12 Audit Logging & Monitoring | 1202.09aa1System.1-09.aa 09.10 Monitoring | Shared | n/a | A secure audit record is created for all activities on the system (create, read, update, delete) involving covered information. | count: 005 Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Review and update the events defined in AU-02 (a930f477-9dcb-2113-8aa7-45bb6fc90861), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe) |
Data Lake, Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1203.09aa1System.2-09.aa | hipaa-1203.09aa1System.2-09.aa | 1203.09aa1System.2-09.aa | 12 Audit Logging & Monitoring | 1203.09aa1System.2-09.aa 09.10 Monitoring | Shared | n/a | Audit records include the unique user ID, unique data subject ID, function performed, and date/time the event was performed. | count: 003 Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d) |
Logic Apps, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1204.09aa1System.3-09.aa | hipaa-1204.09aa1System.3-09.aa | 1204.09aa1System.3-09.aa | 12 Audit Logging & Monitoring | 1204.09aa1System.3-09.aa 09.10 Monitoring | Shared | n/a | The activities of privileged users (administrators, operators, etc.) include the success/failure of the event, time the event occurred, the account involved, the processes involved, and additional information about the event. | count: 004 Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4) |
Internet of Things, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1205.09aa2System.1-09.aa | hipaa-1205.09aa2System.1-09.aa | 1205.09aa2System.1-09.aa | 12 Audit Logging & Monitoring | 1205.09aa2System.1-09.aa 09.10 Monitoring | Shared | n/a | Logs of messages sent and received are maintained including the date, time, origin and destination of the message, but not its contents. | count: 006 Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Ensure audit records are not altered (27ce30dd-3d56-8b54-6144-e26d9a37a541), Provide audit review, analysis, and reporting capability (44f8a42d-739f-8030-89a8-4c2d5b3f6af3), Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d) |
Batch, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1206.09aa2System.23-09.aa | hipaa-1206.09aa2System.23-09.aa | 1206.09aa2System.23-09.aa | 12 Audit Logging & Monitoring | 1206.09aa2System.23-09.aa 09.10 Monitoring | Shared | n/a | Auditing is always available while the system is active and tracks key events, success/failed data access, system security configuration changes, privileged or utility use, any alarms raised, activation and de-activation of protection systems (e.g., A/V and IDS), activation and deactivation of identification and authentication mechanisms, and creation and deletion of system-level objects. | count: 006 Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Prohibit binary/machine-executable code (8e920169-739d-40b5-3f99-c4d855327bb2), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1207.09aa2System.4-09.aa | hipaa-1207.09aa2System.4-09.aa | 1207.09aa2System.4-09.aa | 12 Audit Logging & Monitoring | 1207.09aa2System.4-09.aa 09.10 Monitoring | Shared | n/a | Audit records are retained for 90 days and older audit records are archived for one year. | count: 013 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Event Hub, Regulatory Compliance, Stream Analytics | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1208.09aa3System.1-09.aa | hipaa-1208.09aa3System.1-09.aa | 1208.09aa3System.1-09.aa | 12 Audit Logging & Monitoring | 1208.09aa3System.1-09.aa 09.10 Monitoring | Shared | n/a | Audit logs are maintained for management activities, system and application startup/shutdown/errors, file changes, and security policy changes. | count: 018 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance, Search, Service Bus | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1209.09aa3System.2-09.aa | hipaa-1209.09aa3System.2-09.aa | 1209.09aa3System.2-09.aa | 12 Audit Logging & Monitoring | 1209.09aa3System.2-09.aa 09.10 Monitoring | Shared | n/a | The information system generates audit records containing the following detailed information: (i) filename accessed; (ii) program or command used to initiate the event; and, (iii) source and destination addresses. | count: 003 App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1210.09aa3System.3-09.aa | hipaa-1210.09aa3System.3-09.aa | 1210.09aa3System.3-09.aa | 12 Audit Logging & Monitoring | 1210.09aa3System.3-09.aa 09.10 Monitoring | Shared | n/a | All disclosures of covered information within or outside of the organization are logged including type of disclosure, date/time of the event, recipient, and sender. | count: 011 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review and update the events defined in AU-02 (a930f477-9dcb-2113-8aa7-45bb6fc90861), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Data Lake, Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 12100.09ab2System.15-09.ab | hipaa-12100.09ab2System.15-09.ab | 12100.09ab2System.15-09.ab | 12 Audit Logging & Monitoring | 12100.09ab2System.15-09.ab 09.10 Monitoring | Shared | n/a | The organization monitors the information system to identify irregularities or anomalies that are indicators of a system malfunction or compromise and help confirm the system is functioning in an optimal, resilient and secure state. | count: 003 Discover any indicators of compromise (07b42fb5-027e-5a3c-4915-9d9ef3020ec7), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 12101.09ab1Organizational.3-09.ab | hipaa-12101.09ab1Organizational.3-09.ab | 12101.09ab1Organizational.3-09.ab | 12 Audit Logging & Monitoring | 12101.09ab1Organizational.3-09.ab 09.10 Monitoring | Shared | n/a | The organization specifies how often audit logs are reviewed, how the reviews are documented, and the specific roles and responsibilities of the personnel conducting the reviews, including the professional certifications or other qualifications required. | count: 018 Adjust level of audit review, analysis, and reporting (de251b09-4a5e-1204-4bef-62ac58d47999), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Specify permitted actions associated with customer audit information (3eecf628-a1c8-1b48-1b5c-7ca781e97970), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 12102.09ab1Organizational.4-09.ab | hipaa-12102.09ab1Organizational.4-09.ab | 12102.09ab1Organizational.4-09.ab | 12 Audit Logging & Monitoring | 12102.09ab1Organizational.4-09.ab 09.10 Monitoring | Shared | n/a | The organization periodically tests its monitoring and detection processes, remediates deficiencies, and improves its processes. | count: 007 Audit Windows machines on which the Log Analytics agent is not connected as expected (6265018c-d7e2-432f-a75d-094d5f6f4465), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884), Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 12103.09ab1Organizational.5-09.ab | hipaa-12103.09ab1Organizational.5-09.ab | 12103.09ab1Organizational.5-09.ab | 12 Audit Logging & Monitoring | 12103.09ab1Organizational.5-09.ab 09.10 Monitoring | Shared | n/a | Information collected from multiple sources is aggregated for review. | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1211.09aa3System.4-09.aa | hipaa-1211.09aa3System.4-09.aa | 1211.09aa3System.4-09.aa | 12 Audit Logging & Monitoring | 1211.09aa3System.4-09.aa 09.10 Monitoring | Shared | n/a | The organization verifies every 90 days for each extract of covered information recorded that the data is erased or its use is still required. | count: 009 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Resource logs in Azure Key Vault Managed HSM should be enabled (a2a5b911-5617-447e-a49e-59dbe0e0434b), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Key Vault, Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1212.09ab1System.1-09.ab | hipaa-1212.09ab1System.1-09.ab | 1212.09ab1System.1-09.ab | 12 Audit Logging & Monitoring | 1212.09ab1System.1-09.ab 09.10 Monitoring | Shared | n/a | All applicable legal requirements related to monitoring authorized access and unauthorized access attempts are met. | count: 003 Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1213.09ab2System.128-09.ab | hipaa-1213.09ab2System.128-09.ab | 1213.09ab2System.128-09.ab | 12 Audit Logging & Monitoring | 1213.09ab2System.128-09.ab 09.10 Monitoring | Shared | n/a | Automated systems deployed throughout the organization's environment are used to monitor key events and anomalous activity, and analyze system logs, the results of which are reviewed regularly. | count: 003 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1214.09ab2System.3456-09.ab | hipaa-1214.09ab2System.3456-09.ab | 1214.09ab2System.3456-09.ab | 12 Audit Logging & Monitoring | 1214.09ab2System.3456-09.ab 09.10 Monitoring | Shared | n/a | Monitoring includes privileged operations, authorized access or unauthorized access attempts, including attempts to access deactivated accounts, and system alerts or failures. | count: 009 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1215.09ab2System.7-09.ab | hipaa-1215.09ab2System.7-09.ab | 1215.09ab2System.7-09.ab | 12 Audit Logging & Monitoring | 1215.09ab2System.7-09.ab 09.10 Monitoring | Shared | n/a | Auditing and monitoring systems employed by the organization support audit reduction and report generation. | count: 004 Ensure audit records are not altered (27ce30dd-3d56-8b54-6144-e26d9a37a541), Provide audit review, analysis, and reporting capability (44f8a42d-739f-8030-89a8-4c2d5b3f6af3), Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1216.09ab3System.12-09.ab | hipaa-1216.09ab3System.12-09.ab | 1216.09ab3System.12-09.ab | 12 Audit Logging & Monitoring | 1216.09ab3System.12-09.ab 09.10 Monitoring | Shared | n/a | Automated systems are used to review monitoring activities of security systems (e.g., IPS/IDS) and system records on a daily basis, and identify and document anomalies. | count: 020 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review and update the events defined in AU-02 (a930f477-9dcb-2113-8aa7-45bb6fc90861), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1217.09ab3System.3-09.ab | hipaa-1217.09ab3System.3-09.ab | 1217.09ab3System.3-09.ab | 12 Audit Logging & Monitoring | 1217.09ab3System.3-09.ab 09.10 Monitoring | Shared | n/a | Alerts are generated for technical personnel to analyze and investigate suspicious activity or suspected violations. | count: 005 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Audit Windows machines on which the Log Analytics agent is not connected as expected (6265018c-d7e2-432f-a75d-094d5f6f4465), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1218.09ab3System.47-09.ab | hipaa-1218.09ab3System.47-09.ab | 1218.09ab3System.47-09.ab | 12 Audit Logging & Monitoring | 1218.09ab3System.47-09.ab 09.10 Monitoring | Shared | n/a | Automated systems support near real-time analysis and alerting of events (e.g., malicious code, potential intrusions) and integrate intrusion detection into access and flow control mechanisms. | count: 007 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1219.09ab3System.10-09.ab | hipaa-1219.09ab3System.10-09.ab | 1219.09ab3System.10-09.ab | 12 Audit Logging & Monitoring | 1219.09ab3System.10-09.ab 09.10 Monitoring | Shared | n/a | The information system is able to automatically process audit records for events of interest based on selectable criteria. | count: 004 Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Ensure audit records are not altered (27ce30dd-3d56-8b54-6144-e26d9a37a541), Provide audit review, analysis, and reporting capability (44f8a42d-739f-8030-89a8-4c2d5b3f6af3), Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1220.09ab3System.56-09.ab | hipaa-1220.09ab3System.56-09.ab | 1220.09ab3System.56-09.ab | 12 Audit Logging & Monitoring | 1220.09ab3System.56-09.ab 09.10 Monitoring | Shared | n/a | Monitoring includes inbound and outbound communications and file integrity monitoring. | count: 005 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1222.09ab3System.8-09.ab | hipaa-1222.09ab3System.8-09.ab | 1222.09ab3System.8-09.ab | 12 Audit Logging & Monitoring | 1222.09ab3System.8-09.ab 09.10 Monitoring | Shared | n/a | The organization analyzes and correlates audit records across different repositories using a security information and event management (SIEM) tool or log analytics tools for log aggregation and consolidation from multiple systems/machines/devices, and correlates this information with input from non-technical sources to gain and enhance organization-wide situational awareness. Using the SIEM tool, the organization devise profiles of common events from given systems/machines/devices so that it can tune detection to focus on unusual activity, avoid false positives, more rapidly identify anomalies, and prevent overwhelming analysts with insignificant alerts. | count: 010 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Generate internal security alerts (171e377b-5224-4a97-1eaa-62a3b5231dac), Implement security directives (26d178a4-9261-6f04-a100-47ed85314c6e), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1229.09c1Organizational.1-09.c | hipaa-1229.09c1Organizational.1-09.c | 1229.09c1Organizational.1-09.c | 12 Audit Logging & Monitoring | 1229.09c1Organizational.1-09.c 09.01 Documented Operating Procedures | Shared | n/a | Separation of duties is used to limit the risk of unauthorized or unintentional modification of information and systems. | count: 004 Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance, Security Center | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1230.09c2Organizational.1-09.c | hipaa-1230.09c2Organizational.1-09.c | 1230.09c2Organizational.1-09.c | 12 Audit Logging & Monitoring | 1230.09c2Organizational.1-09.c 09.01 Documented Operating Procedures | Shared | n/a | No single person is able to access, modify, or use information systems without authorization or detection. | count: 013 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
General, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1231.09c2Organizational.23-09.c | hipaa-1231.09c2Organizational.23-09.c | 1231.09c2Organizational.23-09.c | 12 Audit Logging & Monitoring | 1231.09c2Organizational.23-09.c 09.01 Documented Operating Procedures | Shared | n/a | Job descriptions define duties and responsibilities that support the separation of duties across multiple users. | count: 003 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1232.09c3Organizational.12-09.c | hipaa-1232.09c3Organizational.12-09.c | 1232.09c3Organizational.12-09.c | 12 Audit Logging & Monitoring | 1232.09c3Organizational.12-09.c 09.01 Documented Operating Procedures | Shared | n/a | Access for individuals responsible for administering access controls is limited to the minimum necessary based upon each user's role and responsibilities and these individuals cannot access audit functions related to these controls. | count: 021 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Enforce software execution privileges (68d2e478-3b19-23eb-1357-31b296547457), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4), Windows machines should meet requirements for 'User Rights Assignment' (e068b215-0026-4354-b347-8fb2766f73a2) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1233.09c3Organizational.3-09.c | hipaa-1233.09c3Organizational.3-09.c | 1233.09c3Organizational.3-09.c | 12 Audit Logging & Monitoring | 1233.09c3Organizational.3-09.c 09.01 Documented Operating Procedures | Shared | n/a | Development, testing, quality assurance and production functions are separated among multiple individuals/groups. | count: 003 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1270.09ad1System.12-09.ad | hipaa-1270.09ad1System.12-09.ad | 1270.09ad1System.12-09.ad | 12 Audit Logging & Monitoring | 1270.09ad1System.12-09.ad 09.10 Monitoring | Shared | n/a | The organization ensures proper logging is enabled in order to audit administrator activities; and reviews system administrator and operator logs on a regular basis. | count: 018 An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1271.09ad1System.1-09.ad | hipaa-1271.09ad1System.1-09.ad | 1271.09ad1System.1-09.ad | 12 Audit Logging & Monitoring | 1271.09ad1System.1-09.ad 09.10 Monitoring | Shared | n/a | An intrusion detection system managed outside of the control of system and network administrators is used to monitor system and network administration activities for compliance. | count: 008 An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Monitoring, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1271.09ad2System.1 | hipaa-1271.09ad2System.1 | 1271.09ad2System.1 | 12 Audit Logging & Monitoring | 1271.09ad2System.1 09.10 Monitoring | Shared | n/a | An intrusion detection system managed outside of the control of system and network administrators is used to monitor system and network administration activities for compliance. | count: 007 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1276.09c2Organizational.2-09.c | hipaa-1276.09c2Organizational.2-09.c | 1276.09c2Organizational.2-09.c | 12 Audit Logging & Monitoring | 1276.09c2Organizational.2-09.c 09.01 Documented Operating Procedures | Shared | n/a | Security audit activities are independent. | count: 018 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Enforce software execution privileges (68d2e478-3b19-23eb-1357-31b296547457), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1277.09c2Organizational.4-09.c | hipaa-1277.09c2Organizational.4-09.c | 1277.09c2Organizational.4-09.c | 12 Audit Logging & Monitoring | 1277.09c2Organizational.4-09.c 09.01 Documented Operating Procedures | Shared | n/a | The initiation of an event is separated from its authorization to reduce the possibility of collusion. | count: 004 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), Windows machines should meet requirements for 'Security Options - User Account Control' (492a29ed-d143-4f03-b6a4-705ce081b463) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1278.09c2Organizational.56-09.c | hipaa-1278.09c2Organizational.56-09.c | 1278.09c2Organizational.56-09.c | 12 Audit Logging & Monitoring | 1278.09c2Organizational.56-09.c 09.01 Documented Operating Procedures | Shared | n/a | The organization identifies duties that require separation and defines information system access authorizations to support separation of duties; and incompatible duties are segregated across multiple users to minimize the opportunity for misuse or fraud. | count: 003 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1279.09c3Organizational.4-09.c | hipaa-1279.09c3Organizational.4-09.c | 1279.09c3Organizational.4-09.c | 12 Audit Logging & Monitoring | 1279.09c3Organizational.4-09.c 09.01 Documented Operating Procedures | Shared | n/a | The organization ensures that mission critical functions and information system support functions are divided among separate individuals. | count: 003 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1301.02e1Organizational.12-02.e | hipaa-1301.02e1Organizational.12-02.e | 1301.02e1Organizational.12-02.e | 13 Education, Training and Awareness | 1301.02e1Organizational.12-02.e 02.03 During Employment | Shared | n/a | Employees and contractors receive documented initial (as part of their onboarding within 60 days of hire), annual, and ongoing training on their roles related to security and privacy. | count: 017 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide role-based practical exercises (d041726f-00e0-41ca-368c-b1a122066482), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide role-based training on suspicious activities (f6794ab8-9a7d-3b24-76ab-265d3646232b), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1302.02e2Organizational.134-02.e | hipaa-1302.02e2Organizational.134-02.e | 1302.02e2Organizational.134-02.e | 13 Education, Training and Awareness | 1302.02e2Organizational.134-02.e 02.03 During Employment | Shared | n/a | Dedicated security and privacy awareness training is developed as part of the organization's onboarding program, is documented and tracked, and includes the recognition and reporting of potential indicators of an insider threat. | count: 019 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Implement a threat awareness program (015b4935-448a-8684-27c0-d13086356c33), Implement an insider threat program (35de8462-03ff-45b3-5746-9d4603c74c56), Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Retain training records (3153d9c0-2584-14d3-362d-578b01358aeb), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1303.02e2Organizational.2-02.e | hipaa-1303.02e2Organizational.2-02.e | 1303.02e2Organizational.2-02.e | 13 Education, Training and Awareness | 1303.02e2Organizational.2-02.e 02.03 During Employment | Shared | n/a | Employees sign acceptance/acknowledgement of their security and privacy responsibilities. | count: 008 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1304.02e3Organizational.1-02.e | hipaa-1304.02e3Organizational.1-02.e | 1304.02e3Organizational.1-02.e | 13 Education, Training and Awareness | 1304.02e3Organizational.1-02.e 02.03 During Employment | Shared | n/a | Personnel with significant security responsibilities receive specialized education and training on their roles and responsibilities: (i) prior to being granted access to the organization’s systems and resources; (ii) when required by system changes; (iii) when entering into a new position that requires additional training; and, (iv) no less than annually thereafter. | count: 009 Provide contingency training (de936662-13dc-204c-75ec-1af80f994088), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Require developers to provide training (676c3c35-3c36-612c-9523-36d266a65000), Train personnel on disclosure of nonpublic information (97f0d974-1486-01e2-2088-b888f46c0589) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1305.02e3Organizational.23-02.e | hipaa-1305.02e3Organizational.23-02.e | 1305.02e3Organizational.23-02.e | 13 Education, Training and Awareness | 1305.02e3Organizational.23-02.e 02.03 During Employment | Shared | n/a | The organization maintains a documented list of each individual who completes the on-boarding process and maintains all training records for at least five years. | count: 003 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a), Retain training records (3153d9c0-2584-14d3-362d-578b01358aeb) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1306.06e1Organizational.5-06.e | hipaa-1306.06e1Organizational.5-06.e | 1306.06e1Organizational.5-06.e | 13 Education, Training and Awareness | 1306.06e1Organizational.5-06.e 06.01 Compliance with Legal Requirements | Shared | n/a | Employees and contractors are informed in writing that violations of the security policies will result in sanctions or disciplinary action. | count: 011 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1307.07c1Organizational.124-07.c | hipaa-1307.07c1Organizational.124-07.c | 1307.07c1Organizational.124-07.c | 13 Education, Training and Awareness | 1307.07c1Organizational.124-07.c 07.01 Responsibility for Assets | Shared | n/a | The organization defines rules to describe user responsibilities and acceptable behavior for information system usage, including at a minimum, rules for email, Internet, mobile devices, social media and facility usage. | count: 009 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1308.09j1Organizational.5-09.j | hipaa-1308.09j1Organizational.5-09.j | 1308.09j1Organizational.5-09.j | 13 Education, Training and Awareness | 1308.09j1Organizational.5-09.j 09.04 Protection Against Malicious and Mobile Code | Shared | n/a | The organization prohibits users from installing unauthorized software, including data and software from external networks, and ensures users are made aware and trained on these requirements. | count: 012 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1309.01x1System.36-01.x | hipaa-1309.01x1System.36-01.x | 1309.01x1System.36-01.x | 13 Education, Training and Awareness | 1309.01x1System.36-01.x 01.07 Mobile Computing and Teleworking | Shared | n/a | Personnel using mobile computing devices are trained on the risks, the controls implemented, and their responsibilities (e.g., shoulder surfing, physical protections). | count: 006 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1310.01y1Organizational.9-01.y | hipaa-1310.01y1Organizational.9-01.y | 1310.01y1Organizational.9-01.y | 13 Education, Training and Awareness | 1310.01y1Organizational.9-01.y 01.07 Mobile Computing and Teleworking | Shared | n/a | Personnel who telework are trained on the risks, the controls implemented, and their responsibilities. | count: 010 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide role-based practical exercises (d041726f-00e0-41ca-368c-b1a122066482), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide role-based training on suspicious activities (f6794ab8-9a7d-3b24-76ab-265d3646232b), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1311.12c2Organizational.3-12.c | hipaa-1311.12c2Organizational.3-12.c | 1311.12c2Organizational.3-12.c | 13 Education, Training and Awareness | 1311.12c2Organizational.3-12.c 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | The organization’s employees are provided with crisis management awareness and training. | count: 003 Incorporate simulated contingency training (9c954fcf-6dd8-81f1-41b5-832ae5c62caf), Provide contingency training (de936662-13dc-204c-75ec-1af80f994088), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1313.02e1Organizational.3-02.e | hipaa-1313.02e1Organizational.3-02.e | 1313.02e1Organizational.3-02.e | 13 Education, Training and Awareness | 1313.02e1Organizational.3-02.e 02.03 During Employment | Shared | n/a | The organization provides incident response and contingency training to information system users consistent with assigned roles and responsibilities within 90 days of assuming an incident response role or responsibility; when required by information system changes; and within every 365 days thereafter. | count: 003 Provide contingency training (de936662-13dc-204c-75ec-1af80f994088), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1314.02e2Organizational.5-02.e | hipaa-1314.02e2Organizational.5-02.e | 1314.02e2Organizational.5-02.e | 13 Education, Training and Awareness | 1314.02e2Organizational.5-02.e 02.03 During Employment | Shared | n/a | The organization conducts an internal annual review of the effectiveness of its security and privacy education and training program, and updates the program to reflect risks identified in the organization's risk assessment. | count: 004 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1315.02e2Organizational.67-02.e | hipaa-1315.02e2Organizational.67-02.e | 1315.02e2Organizational.67-02.e | 13 Education, Training and Awareness | 1315.02e2Organizational.67-02.e 02.03 During Employment | Shared | n/a | The organization provides specialized security and privacy education and training appropriate to the employee's roles/responsibilities, including organizational business unit security POCs and system/software developers. | count: 006 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1324.07c1Organizational.3-07.c | hipaa-1324.07c1Organizational.3-07.c | 1324.07c1Organizational.3-07.c | 13 Education, Training and Awareness | 1324.07c1Organizational.3-07.c 07.01 Responsibility for Assets | Shared | n/a | Employees, contractors and third-party system users are aware of the limits existing for their use of the organization's information and assets associated with information processing facilities and resources; and they are responsible for their use of any information resource and of any use carried out under their responsibility. | count: 008 Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1325.09s1Organizational.3-09.s | hipaa-1325.09s1Organizational.3-09.s | 1325.09s1Organizational.3-09.s | 13 Education, Training and Awareness | 1325.09s1Organizational.3-09.s 09.08 Exchange of Information | Shared | n/a | Personnel are appropriately trained on leading principles and practices for all types of information exchange (oral, paper and electronic). | count: 011 Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
App Service, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1327.02e2Organizational.8-02.e | hipaa-1327.02e2Organizational.8-02.e | 1327.02e2Organizational.8-02.e | 13 Education, Training and Awareness | 1327.02e2Organizational.8-02.e 02.03 During Employment | Shared | n/a | The organization trains its workforce to ensure covered information is stored in organization-specified locations. | count: 005 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1331.02e3Organizational.4-02.e | hipaa-1331.02e3Organizational.4-02.e | 1331.02e3Organizational.4-02.e | 13 Education, Training and Awareness | 1331.02e3Organizational.4-02.e 02.03 During Employment | Shared | n/a | The organization trains workforce members on how to properly respond to perimeter security alarms. | count: 006 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Incorporate simulated events into incident response training (1fdeb7c4-4c93-8271-a135-17ebe85f1cc7), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1334.02e2Organizational.12-02.e | hipaa-1334.02e2Organizational.12-02.e | 1334.02e2Organizational.12-02.e | 13 Education, Training and Awareness | 1334.02e2Organizational.12-02.e 02.03 During Employment | Shared | n/a | The organization ensures that the senior executives have been trained in their specific roles and responsibilities. | count: 004 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1336.02e1Organizational.5-02.e | hipaa-1336.02e1Organizational.5-02.e | 1336.02e1Organizational.5-02.e | 13 Education, Training and Awareness | 1336.02e1Organizational.5-02.e 02.03 During Employment | Shared | n/a | The organization’s security awareness and training program (i) identifies how workforce members are provided security awareness and training, and the workforce members who will receive security awareness and training; (ii) describes the types of security awareness and training that is reasonable and appropriate for its workforce members; (iii) how workforce members are provided security and awareness training when there is a change in the organization’s information systems; and, (iv) how frequently security awareness and training is provided to all workforce members. | count: 007 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide role-based practical exercises (d041726f-00e0-41ca-368c-b1a122066482), Provide role-based training on suspicious activities (f6794ab8-9a7d-3b24-76ab-265d3646232b), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1401.05i1Organizational.1239-05.i | hipaa-1401.05i1Organizational.1239-05.i | 1401.05i1Organizational.1239 - 05.i | Identification of Risks Related to External Parties | Access to the organizations information and systems by external parties is not permitted until due diligence has been conducted, the appropriate controls have been implemented, and a contract/agreement reflecting the security requirements is signed acknowledging they understand and accept their obligations. | Customer | n/a | Master Supplier Service Agreement (MSSA)) Supplier Data Protection Requirements (DPR) Supplier Code of Conduct (SCoC) Sample of Datacenter TVRAs |
count: 001 Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
Storage | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1402.05i1Organizational.45-05.i | hipaa-1402.05i1Organizational.45-05.i | 1402.05i1Organizational.45 - 05.i | Identification of Risks Related to External Parties | Remote access connections between the organization and external parties are encrypted. | Customer | n/a | Transmission encryption configuration settings. | count: 001 Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab) |
App Service | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1403.05i1Organizational.67-05.i | hipaa-1403.05i1Organizational.67-05.i | 1403.05i1Organizational.67 - 05.i | Identification of Risks Related to External Parties | Access granted to external parties is limited to the minimum necessary and granted only for the duration required. | Customer | n/a | Master Supplier Service Agreement (MSSA)) Supplier Data Protection Requirements (DPR) Supplier Code of Conduct (SCoC) |
count: 001 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d) |
App Service | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1404.05i2Organizational.1-05.i | hipaa-1404.05i2Organizational.1-05.i | 1404.05i2Organizational.1-05.i | 14 Third Party Assurance | 1404.05i2Organizational.1-05.i 05.02 External Parties | Shared | n/a | Due diligence of the external party includes interviews, document review, checklists, certification reviews (e.g., HITRUST) or other remote means. | count: 001 Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1406.05k1Organizational.110-05.k | hipaa-1406.05k1Organizational.110-05.k | 1406.05k1Organizational.110-05.k | 14 Third Party Assurance | 1406.05k1Organizational.110-05.k 05.02 External Parties | Shared | n/a | A standard agreement with third-parties is defined and includes the required security controls in accordance with the organization's security policies. | count: 011 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1407.05k2Organizational.1-05.k | hipaa-1407.05k2Organizational.1-05.k | 1407.05k2Organizational.1-05.k | 14 Third Party Assurance | 1407.05k2Organizational.1-05.k 05.02 External Parties | Shared | n/a | The specific limitations of access, arrangements for compliance auditing, penalties, and the requirement for notification of third-party personnel transfers and terminations are identified in the agreement with the third-party. | count: 005 Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1408.09e1System.1-09.e | hipaa-1408.09e1System.1-09.e | 1408.09e1System.1-09.e | 14 Third Party Assurance | 1408.09e1System.1-09.e 09.02 Control Third Party Service Delivery | Shared | n/a | Service Level Agreements (SLAs) or contracts with an agreed service arrangement address liability, service definitions, security controls, and other aspects of services management. | count: 006 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1409.09e2System.1-09.e | hipaa-1409.09e2System.1-09.e | 1409.09e2System.1-09.e | 14 Third Party Assurance | 1409.09e2System.1-09.e 09.02 Control Third Party Service Delivery | Shared | n/a | The organization develops, disseminates and annually reviews/updates a list of current service providers, which includes a description of services provided. | count: 015 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1410.09e2System.23-09.e | hipaa-1410.09e2System.23-09.e | 1410.09e2System.23-09.e | 14 Third Party Assurance | 1410.09e2System.23-09.e 09.02 Control Third Party Service Delivery | Shared | n/a | The organization addresses information security and other business considerations when acquiring systems or services; including maintaining security during transitions and continuity following a failure or disaster. | count: 011 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1411.09f1System.1-09.f | hipaa-1411.09f1System.1-09.f | 1411.09f1System.1-09.f | 14 Third Party Assurance | 1411.09f1System.1-09.f 09.02 Control Third Party Service Delivery | Shared | n/a | The results of monitoring activities of third-party services are compared against the Service Level Agreements or contracts at least annually. | count: 009 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1416.10l1Organizational.1-10.l | hipaa-1416.10l1Organizational.1-10.l | 1416.10l1Organizational.1-10.l | 14 Third Party Assurance | 1416.10l1Organizational.1-10.l 10.05 Security In Development and Support Processes | Shared | n/a | Where software development is outsourced, formal contracts are in place to address the ownership and security of the code and application. | count: 011 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1417.10l2Organizational.1-10.l | hipaa-1417.10l2Organizational.1-10.l | 1417.10l2Organizational.1-10.l | 14 Third Party Assurance | 1417.10l2Organizational.1-10.l 10.05 Security In Development and Support Processes | Shared | n/a | Where software development is outsourced, the development process is monitored by the organization and includes independent security and code reviews. | count: 012 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1418.05i1Organizational.8-05.i | hipaa-1418.05i1Organizational.8-05.i | 1418.05i1Organizational.8 - 05.i | Identification of Risks Related to External Parties | The identification of risks related to external party access takes into account a minimal set of specifically defined issues. | Customer | n/a | Master Supplier Service Agreement (MSSA)) Supplier Data Protection Requirements (DPR) Supplier Code of Conduct (SCoC) Sample of Datacenter TVRAs |
count: 001 Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d) |
SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1419.05j1Organizational.12-05.j | hipaa-1419.05j1Organizational.12-05.j | 1419.05j1Organizational.12-05.j | 14 Third Party Assurance | 1419.05j1Organizational.12-05.j 05.02 External Parties | Shared | n/a | The organization ensures that customers are aware of their obligations and rights, and accept the responsibilities and liabilities prior to accessing, processing, communicating, or managing the organization's information and information assets. | count: 011 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1421.05j2Organizational.12-05.j | hipaa-1421.05j2Organizational.12-05.j | 1421.05j2Organizational.12-05.j | 14 Third Party Assurance | 1421.05j2Organizational.12-05.j 05.02 External Parties | Shared | n/a | Access by customers to the organization's information is not provided until the appropriate controls have been implemented and, where feasible, a contract has been signed defining the terms and conditions for the connection or access and the working arrangement, including specific terms around asset protection, access control policy, arrangements for the resolution of inaccuracies, a description of each service provided, service levels, benefits to the customer, legal responsibilities of the organization and the customer, and any intellectual property rights. | count: 010 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1422.05j2Organizational.3-05.j | hipaa-1422.05j2Organizational.3-05.j | 1422.05j2Organizational.3-05.j | 14 Third Party Assurance | 1422.05j2Organizational.3-05.j 05.02 External Parties | Shared | n/a | All security requirements resulting from work with external parties or internal controls are reflected by the agreement with the external party. | count: 006 Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Obtain approvals for acquisitions and outsourcing (92b94485-1c49-3350-9ada-dffe94f08e87), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1423.05j2Organizational.4-05.j | hipaa-1423.05j2Organizational.4-05.j | 1423.05j2Organizational.4-05.j | 14 Third Party Assurance | 1423.05j2Organizational.4-05.j 05.02 External Parties | Shared | n/a | For all system connections that allow customers to access the organization's computing assets such as websites, kiosks, and public access terminals, the organization provides appropriate text or a link to the organization's privacy policy for data use and protection as well as the customer's responsibilities when accessing the data. | count: 009 Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182), Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412), Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Verify security controls for external information systems (dc7ec756-221c-33c8-0afe-c48e10e42321) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1424.05j2Organizational.5-05.j | hipaa-1424.05j2Organizational.5-05.j | 1424.05j2Organizational.5-05.j | 14 Third Party Assurance | 1424.05j2Organizational.5-05.j 05.02 External Parties | Shared | n/a | The organization has a formal mechanism to authenticate the customer's identity prior to granting access to covered information. | count: 008 Accept only FICAM-approved third-party credentials (2d2ca910-7957-23ee-2945-33f401606efc), Accept PIV credentials (55be3260-a7a2-3c06-7fe6-072d07525ab7), Conform to FICAM-issued profiles (a8df9c78-4044-98be-2c05-31a315ac8957), Employ FICAM-approved resources to accept third-party credentials (db8b35d6-8adb-3f51-44ff-c648ab5b1530), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1429.05k1Organizational.34-05.k | hipaa-1429.05k1Organizational.34-05.k | 1429.05k1Organizational.34-05.k | 14 Third Party Assurance | 1429.05k1Organizational.34-05.k 05.02 External Parties | Shared | n/a | The organization maintains written agreements (contracts) that include: (i) an acknowledgement that the third-party (e.g., a service provider) is responsible for the security of the data and requirements to address the associated information security risks; and, (ii) requirements to address the information security risks associated with information and communications technology services (e.g., cloud computing services) and product supply chain. | count: 014 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1430.05k1Organizational.56-05.k | hipaa-1430.05k1Organizational.56-05.k | 1430.05k1Organizational.56-05.k | 14 Third Party Assurance | 1430.05k1Organizational.56-05.k 05.02 External Parties | Shared | n/a | The agreement ensures that there is no misunderstanding between the organization and the third-party and satisfies the organization as to the indemnity of the third-party. | count: 013 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1431.05k1Organizational.7-05.k | hipaa-1431.05k1Organizational.7-05.k | 1431.05k1Organizational.7-05.k | 14 Third Party Assurance | 1431.05k1Organizational.7-05.k 05.02 External Parties | Shared | n/a | The organization establishes personnel security requirements, including security roles and responsibilities, for third-party providers that are coordinated and aligned with internal security roles and responsibilities. | count: 005 Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1432.05k1Organizational.89-05.k | hipaa-1432.05k1Organizational.89-05.k | 1432.05k1Organizational.89-05.k | 14 Third Party Assurance | 1432.05k1Organizational.89-05.k 05.02 External Parties | Shared | n/a | The organization ensures a screening process is carried out for contractors and third-party users, and, where contractors are provided through an organization, the contract with the organization clearly specifies (i) the organization's responsibilities for screening and the notification procedures they need to follow if screening has not been completed, or if the results give cause for doubt or concern; and, (ii) all responsibilities and notification procedures for screening. | count: 007 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish privacy requirements for contractors and service providers (f8d141b7-4e21-62a6-6608-c79336e36bc9), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1438.09e2System.4-09.e | hipaa-1438.09e2System.4-09.e | 1438.09e2System.4-09.e | 14 Third Party Assurance | 1438.09e2System.4-09.e 09.02 Control Third Party Service Delivery | Shared | n/a | The service provider protects the company's data with reasonable controls (e.g., policies and procedures) designed to detect, prevent, and mitigate risk. | count: 014 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1450.05i2Organizational.2-05.i | hipaa-1450.05i2Organizational.2-05.i | 1450.05i2Organizational.2-05.i | 14 Third Party Assurance | 1450.05i2Organizational.2-05.i 05.02 External Parties | Shared | n/a | The organization obtains satisfactory assurances that reasonable information security exists across its information supply chain by performing an annual review, which includes all partners/third-party providers upon which their information supply chain depends. | count: 010 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1451.05iCSPOrganizational.2-05.i | hipaa-1451.05iCSPOrganizational.2-05.i | 1451.05iCSPOrganizational.2-05.i | 14 Third Party Assurance | 1451.05iCSPOrganizational.2-05.i 05.02 External Parties | Shared | n/a | Cloud service providers design and implement controls to mitigate and contain data security risks through proper separation of duties, role-based access, and least-privilege access for all personnel within their supply chain. | count: 021 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Enforce software execution privileges (68d2e478-3b19-23eb-1357-31b296547457), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Cache, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1452.05kCSPOrganizational.1-05.k | hipaa-1452.05kCSPOrganizational.1-05.k | 1452.05kCSPOrganizational.1-05.k | 14 Third Party Assurance | 1452.05kCSPOrganizational.1-05.k 05.02 External Parties | Shared | n/a | The organization ensures that mutually-agreed upon provisions and/or terms are established to satisfy customer (tenant) requirements for service-to-service application (API) and information processing interoperability, and portability for application development and information exchange, usage, and integrity persistence. | count: 003 Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1453.05kCSPOrganizational.2-05.k | hipaa-1453.05kCSPOrganizational.2-05.k | 1453.05kCSPOrganizational.2-05.k | 14 Third Party Assurance | 1453.05kCSPOrganizational.2-05.k 05.02 External Parties | Shared | n/a | Supply chain agreements (e.g., SLAs) between cloud service providers and customers (tenants) incorporate at least the following mutually-agreed upon provisions and/or terms: (i) scope of business relationship and services offered, data acquisition, exchange and usage, feature sets and functionality, personnel and infrastructure network and systems components for service delivery and support, roles and responsibilities of provider and customer (tenant) and any subcontracted or outsourced business relationships, physical geographical location of hosted services, and any known regulatory compliance considerations; (ii) information security requirements, points of contact, and references to detailed supporting and relevant business processes and technical measures implemented; (iii) notification and/or pre-authorization of any changes controlled by the provider with customer (tenant) impacts; (iv) timely notification of a security incident to all customers (tenants) and other business relationships impacted; (v) assessment and independent verification of compliance with agreement provisions and/or terms (e.g., industry-acceptable certification, attestation audit report, or equivalent forms of assurance) without posing an unacceptable business risk of exposure to the organization being assessed; (vi) expiration of the business relationship and treatment of customer (tenant) data impacted; and, (vii) customer (tenant) service-to-service application (API) and data interoperability and portability requirements for application development and information exchange, usage, and integrity persistence. | count: 010 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1454.05kCSPOrganizational.3-05.k | hipaa-1454.05kCSPOrganizational.3-05.k | 1454.05kCSPOrganizational.3-05.k | 14 Third Party Assurance | 1454.05kCSPOrganizational.3-05.k 05.02 External Parties | Shared | n/a | Service agreements (e.g., SLAs) between providers and customers (tenants) across the relevant supply chain (upstream/downstream) are reviewed consistently and no less than annually to identify any non-conformance to established agreements. The reviews result in actions to address service-level conflicts or inconsistencies resulting from disparate supplier relationships. | count: 008 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1455.05kCSPOrganizational.4-05.k | hipaa-1455.05kCSPOrganizational.4-05.k | 1455.05kCSPOrganizational.4-05.k | 14 Third Party Assurance | 1455.05kCSPOrganizational.4-05.k 05.02 External Parties | Shared | n/a | Third-party service providers demonstrate compliance with information security and confidentiality, access control, service definitions, and service-level agreements included in third-party contracts. Third-party reports, records, and services undergo audit and review at least annually to govern and maintain compliance with the service delivery agreements. | count: 009 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1464.09e2Organizational.5-09.e | hipaa-1464.09e2Organizational.5-09.e | 1464.09e2Organizational.5-09.e | 14 Third Party Assurance | 1464.09e2Organizational.5-09.e 09.02 Control Third Party Service Delivery | Shared | n/a | The organization restricts the location of facilities that process, transmit or store covered information (e.g., to those located in the United States), as needed, based on its legal, regulatory, contractual and other security and privacy-related obligations. | count: 005 Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722), Recover and reconstitute resources after any disruption (f33c3238-11d2-508c-877c-4262ec1132e1) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1501.02f1Organizational.123-02.f | hipaa-1501.02f1Organizational.123-02.f | 1501.02f1Organizational.123-02.f | 15 Incident Management | 1501.02f1Organizational.123-02.f 02.03 During Employment | Shared | n/a | Sanctions are fairly applied to employees following violations of the information security policies once a breach is verified and includes consideration of multiple factors. The organization documents personnel involved in incidents, steps taken, and the timeline associated with those steps, steps taken for notification, the rationale for discipline, and the final outcome for each incident. | count: 011 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1503.02f2Organizational.12-02.f | hipaa-1503.02f2Organizational.12-02.f | 1503.02f2Organizational.12-02.f | 15 Incident Management | 1503.02f2Organizational.12-02.f 02.03 During Employment | Shared | n/a | A contact in HR is appointed to handle employee security incidents and notify the CISO or a designated representative of the application of a formal employee sanctions process, identifying the individual and the reason for the sanction. | count: 011 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Implement Incident handling capability (98e33927-8d7f-6d5f-44f5-2469b40b7215), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1504.06e1Organizational.34-06.e | hipaa-1504.06e1Organizational.34-06.e | 1504.06e1Organizational.34-06.e | 15 Incident Management | 1504.06e1Organizational.34-06.e 06.01 Compliance with Legal Requirements | Shared | n/a | Management approves the use of information assets and takes appropriate action when unauthorized activity occurs. | count: 016 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Establish relationship between incident response capability and external providers (b470a37a-7a47-3792-34dd-7a793140702e), Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1505.11a1Organizational.13-11.a | hipaa-1505.11a1Organizational.13-11.a | 1505.11a1Organizational.13-11.a | 15 Incident Management | 1505.11a1Organizational.13-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | A formal security incident response program has been established to respond, report (without fear of repercussion), escalate and treat breaches and reported security events or incidents. Organization-wide standards are specified for the time required for system administrators and other personnel to report anomalous events to the incident handling team, the mechanisms for such reporting, and the kind of information that should be included in the incident notification. This reporting includes notifying internal and external stakeholders, the appropriate community Computer Emergency Response Team, and law enforcement agencies in accordance with all legal or regulatory requirements for involving such organizations in computer incidents. | count: 019 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish relationship between incident response capability and external providers (b470a37a-7a47-3792-34dd-7a793140702e), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5), Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1506.11a1Organizational.2-11.a | hipaa-1506.11a1Organizational.2-11.a | 1506.11a1Organizational.2-11.a | 15 Incident Management | 1506.11a1Organizational.2-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | There is a point of contact for reporting information security events who is made known throughout the organization, always available, and able to provide adequate and timely response. The organization also maintains a list of third-party contact information (e.g., the email addresses of their information security officers), which can be used to report a security incident. | count: 010 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Manage contacts for authorities and special interest groups (5269d7e4-3768-501d-7e46-66c56c15622c), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1507.11a1Organizational.4-11.a | hipaa-1507.11a1Organizational.4-11.a | 1507.11a1Organizational.4-11.a | 15 Incident Management | 1507.11a1Organizational.4-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | The organization has implemented an insider threat program that includes a cross-discipline insider threat incident handling team. | count: 003 Implement an insider threat program (35de8462-03ff-45b3-5746-9d4603c74c56), Implement Incident handling capability (98e33927-8d7f-6d5f-44f5-2469b40b7215), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1508.11a2Organizational.1-11.a | hipaa-1508.11a2Organizational.1-11.a | 1508.11a2Organizational.1-11.a | 15 Incident Management | 1508.11a2Organizational.1-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | The organization provides a process/mechanism to anonymously report security issues. | count: 008 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1509.11a2Organizational.236-11.a | hipaa-1509.11a2Organizational.236-11.a | 1509.11a2Organizational.236-11.a | 15 Incident Management | 1509.11a2Organizational.236-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | The incident management program formally defines information security incidents and the phases of incident response; roles and responsibilities; incident handling, reporting and communication processes; third-party relationships and the handling of third-party breaches; and the supporting forensics program. The organization formally assigns job titles and duties for handling computer and network security incidents to specific individuals and identifies management personnel who will support the incident handling process by acting in key decision-making roles. | count: 017 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1510.11a2Organizational.47-11.a | hipaa-1510.11a2Organizational.47-11.a | 1510.11a2Organizational.47-11.a | 15 Incident Management | 1510.11a2Organizational.47-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | Reports and communications are made without unreasonable delay and no later than 60 days after the discovery of an incident, unless otherwise stated by law enforcement orally or in writing, and include the necessary elements. | count: 011 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1511.11a2Organizational.5-11.a | hipaa-1511.11a2Organizational.5-11.a | 1511.11a2Organizational.5-11.a | 15 Incident Management | 1511.11a2Organizational.5-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | All employees, contractors and third-party users receive mandatory incident response training to ensure they are aware of their responsibilities to report information security events as quickly as possible, the procedure for reporting information security events, and the point(s) of contact, including the incident response team, and the contact information is published and made readily available. | count: 013 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Incorporate simulated events into incident response training (1fdeb7c4-4c93-8271-a135-17ebe85f1cc7), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1512.11a2Organizational.8-11.a | hipaa-1512.11a2Organizational.8-11.a | 1512.11a2Organizational.8-11.a | 15 Incident Management | 1512.11a2Organizational.8-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | Intrusion detection/information protection system (IDS/IPS) alerts are utilized for reporting information security events. | count: 017 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1515.11a3Organizational.3-11.a | hipaa-1515.11a3Organizational.3-11.a | 1515.11a3Organizational.3-11.a | 15 Incident Management | 1515.11a3Organizational.3-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | Incidents (or a sample of incidents) are reviewed to identify necessary improvement to the security controls. | count: 011 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1516.11c1Organizational.12-11.c | hipaa-1516.11c1Organizational.12-11.c | 1516.11c1Organizational.12-11.c | 15 Incident Management | 1516.11c1Organizational.12-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | The security incident response program accounts for and prepares the organization for a variety of incidents. | count: 010 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1517.11c1Organizational.3-11.c | hipaa-1517.11c1Organizational.3-11.c | 1517.11c1Organizational.3-11.c | 15 Incident Management | 1517.11c1Organizational.3-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | There is a point of contact who is responsible for coordinating incident responses and has the authority to direct actions required in all phases of the incident response process. | count: 006 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1518.11c2Organizational.13-11.c | hipaa-1518.11c2Organizational.13-11.c | 1518.11c2Organizational.13-11.c | 15 Incident Management | 1518.11c2Organizational.13-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | The organization formally addresses the purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities and compliance requirements for its incident management program. | count: 001 Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1519.11c2Organizational.2-11.c | hipaa-1519.11c2Organizational.2-11.c | 1519.11c2Organizational.2-11.c | 15 Incident Management | 1519.11c2Organizational.2-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | For unauthorized disclosures of covered information, a log is maintained and annually submitted to the appropriate parties (e.g., a state, regional or national regulatory agency). | count: 014 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate Audit record analysis (85335602-93f5-7730-830b-d43426fd51fa), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1520.11c2Organizational.4-11.c | hipaa-1520.11c2Organizational.4-11.c | 1520.11c2Organizational.4-11.c | 15 Incident Management | 1520.11c2Organizational.4-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | The incident response plan is communicated to the appropriate individuals throughout the organization. | count: 008 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1521.11c2Organizational.56-11.c | hipaa-1521.11c2Organizational.56-11.c | 1521.11c2Organizational.56-11.c | 15 Incident Management | 1521.11c2Organizational.56-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | Testing exercises are planned, coordinated, executed, and documented periodically, at least annually, using reviews, analyses, and simulations to determine incident response effectiveness. Testing includes personnel associated with the incident handling team to ensure that they understand current threats and risks, as well as their responsibilities in supporting the incident handling team. | count: 016 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Implement Incident handling capability (98e33927-8d7f-6d5f-44f5-2469b40b7215), Incorporate simulated events into incident response training (1fdeb7c4-4c93-8271-a135-17ebe85f1cc7), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1522.11c3Organizational.13-11.c | hipaa-1522.11c3Organizational.13-11.c | 1522.11c3Organizational.13-11.c | 15 Incident Management | 1522.11c3Organizational.13-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | An incident response support resource, who is an integral part of the organization's incident response capability, is available to offer advice and assistance to users of information systems for the handling and reporting of security incidents in a timely manner. | count: 006 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1523.11c3Organizational.24-11.c | hipaa-1523.11c3Organizational.24-11.c | 1523.11c3Organizational.24-11.c | 15 Incident Management | 1523.11c3Organizational.24-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | Incidents are promptly reported to the appropriate authorities and outside parties (e.g., FedCIRC, CERT/CC). | count: 004 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Establish relationship between incident response capability and external providers (b470a37a-7a47-3792-34dd-7a793140702e), Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f), Use automated mechanisms for security alerts (b8689b2e-4308-a58b-a0b4-6f3343a000df) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1524.11a1Organizational.5-11.a | hipaa-1524.11a1Organizational.5-11.a | 1524.11a1Organizational.5-11.a | 15 Incident Management | 1524.11a1Organizational.5-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | Workforce members cooperate with federal or state investigations or disciplinary proceedings. | count: 003 Coordinate with external organizations to achieve cross org perspective (d4e6a629-28eb-79a9-000b-88030e4823ca), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1525.11a1Organizational.6-11.a | hipaa-1525.11a1Organizational.6-11.a | 1525.11a1Organizational.6-11.a | 15 Incident Management | 1525.11a1Organizational.6-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | The organization takes disciplinary action against workforce members that fail to cooperate with federal and state investigations. | count: 006 Establish information security workforce development and improvement program (b544f797-a73b-1be3-6d01-6b1a085376bc), Implement an insider threat program (35de8462-03ff-45b3-5746-9d4603c74c56), Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Implement Incident handling capability (98e33927-8d7f-6d5f-44f5-2469b40b7215), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1560.11d1Organizational.1-11.d | hipaa-1560.11d1Organizational.1-11.d | 1560.11d1Organizational.1-11.d | 15 Incident Management | 1560.11d1Organizational.1-11.d 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | The information gained from the evaluation of information security incidents is used to identify recurring or high-impact incidents, and update the incident response and recovery strategy. | count: 008 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1561.11d2Organizational.14-11.d | hipaa-1561.11d2Organizational.14-11.d | 1561.11d2Organizational.14-11.d | 15 Incident Management | 1561.11d2Organizational.14-11.d 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | The organization has implemented an incident handling capability for security incidents that addresses: (i) policy (setting corporate direction) and procedures defining roles and responsibilities; (ii) incident handling procedures (business and technical); (iii) communication; (iv) reporting and retention; and, (v) references to a vulnerability management program. | count: 006 Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1562.11d2Organizational.2-11.d | hipaa-1562.11d2Organizational.2-11.d | 1562.11d2Organizational.2-11.d | 15 Incident Management | 1562.11d2Organizational.2-11.d 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | The organization coordinates incident handling activities with contingency planning activities. | count: 012 Address information security issues (56fb5173-3865-5a5d-5fad-ae33e53e1577), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1563.11d2Organizational.3-11.d | hipaa-1563.11d2Organizational.3-11.d | 1563.11d2Organizational.3-11.d | 15 Incident Management | 1563.11d2Organizational.3-11.d 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | The organization incorporates lessons learned from ongoing incident handling activities and industry developments into incident response procedures, training and testing exercises, and implements the resulting changes accordingly. | count: 004 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1577.11aCSPOrganizational.1-11.a | hipaa-1577.11aCSPOrganizational.1-11.a | 1577.11aCSPOrganizational.1-11.a | 15 Incident Management | 1577.11aCSPOrganizational.1-11.a 11.01 Reporting Information Security Incidents and Weaknesses | Shared | n/a | Cloud service providers make security incident information available to all affected customers and providers periodically through electronic methods (e.g., portals). | count: 002 Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412), Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1587.11c2Organizational.10-11.c | hipaa-1587.11c2Organizational.10-11.c | 1587.11c2Organizational.10-11.c | 15 Incident Management | 1587.11c2Organizational.10-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | The incident management plan is reviewed and updated annually. | count: 009 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1589.11c1Organizational.5-11.c | hipaa-1589.11c1Organizational.5-11.c | 1589.11c1Organizational.5-11.c | 15 Incident Management | 1589.11c1Organizational.5-11.c 11.02 Management of Information Security Incidents and Improvements | Shared | n/a | The organization tests and/or exercises its incident response capability regularly. | count: 004 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Incorporate simulated events into incident response training (1fdeb7c4-4c93-8271-a135-17ebe85f1cc7), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1601.12c1Organizational.1238-12.c | hipaa-1601.12c1Organizational.1238-12.c | 1601.12c1Organizational.1238-12.c | 16 Business Continuity & Disaster Recovery | 1601.12c1Organizational.1238-12.c 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | The organization can recover and restore business operations and establish an availability of information in the time frame required by the business objectives and without a deterioration of the security measures. | count: 003 Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Test the business continuity and disaster recovery plan (58a51cde-008b-1a5d-61b5-d95849770677), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1602.12c1Organizational.4567-12.c | hipaa-1602.12c1Organizational.4567-12.c | 1602.12c1Organizational.4567-12.c | 16 Business Continuity & Disaster Recovery | 1602.12c1Organizational.4567-12.c 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | The contingency program addresses required capacity, identifies critical missions and business functions, defines recovery objectives and priorities, and identifies roles and responsibilities. | count: 003 Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4), Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1603.12c1Organizational.9-12.c | hipaa-1603.12c1Organizational.9-12.c | 1603.12c1Organizational.9-12.c | 16 Business Continuity & Disaster Recovery | 1603.12c1Organizational.9-12.c 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Copies of the business continuity plans are distributed to key contingency personnel. | count: 005 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1604.12c2Organizational.16789-12.c | hipaa-1604.12c2Organizational.16789-12.c | 1604.12c2Organizational.16789-12.c | 16 Business Continuity & Disaster Recovery | 1604.12c2Organizational.16789-12.c 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Alternative storage and processing sites are identified (permanent and/or temporary) at a sufficient distance from the primary facility and configured with security measures equivalent to the primary site, and the necessary third-party service agreements have been established to allow for the resumption of information systems operations of critical business functions within the time period defined (e.g., priority of service provisions) based on a risk assessment, including Recovery Time Objectives (RTO), in accordance with the organization's availability requirements. | count: 006 Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Establish alternate storage site that facilitates recovery operations (245fe58b-96f8-9f1e-48c5-7f49903f66fd), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1607.12c2Organizational.4-12.c | hipaa-1607.12c2Organizational.4-12.c | 1607.12c2Organizational.4-12.c | 16 Business Continuity & Disaster Recovery | 1607.12c2Organizational.4-12.c 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Business continuity planning includes identification and agreement on all responsibilities, business continuity processes, and the acceptable loss of information and services. | count: 002 Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1608.12c2Organizational.5-12.c | hipaa-1608.12c2Organizational.5-12.c | 1608.12c2Organizational.5-12.c | 16 Business Continuity & Disaster Recovery | 1608.12c2Organizational.5-12.c 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Business continuity plans are stored in a remote location. | count: 003 Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7), Transfer backup information to an alternate storage site (7bdb79ea-16b8-453e-4ca4-ad5b16012414) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1609.12c3Organizational.12-12.c | hipaa-1609.12c3Organizational.12-12.c | 1609.12c3Organizational.12-12.c | 16 Business Continuity & Disaster Recovery | 1609.12c3Organizational.12-12.c 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Alternate telecommunications services that are sufficiently separated from the primary service provider are established with priority-of-service provisions. | count: 001 Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1616.09l1Organizational.16-09.l | hipaa-1616.09l1Organizational.16-09.l | 1616.09l1Organizational.16-09.l | 16 Business Continuity & Disaster Recovery | 1616.09l1Organizational.16-09.l 09.05 Information Back-Up | Shared | n/a | Backup copies of information and software are made, and tests of the media and restoration procedures are regularly performed at appropriate intervals. | count: 002 Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1617.09l1Organizational.23-09.l | hipaa-1617.09l1Organizational.23-09.l | 1617.09l1Organizational.23-09.l | 16 Business Continuity & Disaster Recovery | 1617.09l1Organizational.23-09.l 09.05 Information Back-Up | Shared | n/a | A formal definition of the level of backup required for each system is defined and documented including how each system will be restored, the scope of data to be imaged, frequency of imaging, and duration of retention based on relevant contractual, legal, regulatory and business requirements. | count: 003 Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1618.09l1Organizational.45-09.l | hipaa-1618.09l1Organizational.45-09.l | 1618.09l1Organizational.45-09.l | 16 Business Continuity & Disaster Recovery | 1618.09l1Organizational.45-09.l 09.05 Information Back-Up | Shared | n/a | The backups are stored in a physically secure remote location, at a sufficient distance to make them reasonably immune from damage to data at the primary site, and reasonable physical and environmental controls are in place to ensure their protection at the remote location. | count: 007 Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Establish alternate storage site that facilitates recovery operations (245fe58b-96f8-9f1e-48c5-7f49903f66fd), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1619.09l1Organizational.7-09.l | hipaa-1619.09l1Organizational.7-09.l | 1619.09l1Organizational.7-09.l | 16 Business Continuity & Disaster Recovery | 1619.09l1Organizational.7-09.l 09.05 Information Back-Up | Shared | n/a | Inventory records for the backup copies, including content and current location, are maintained. | count: 002 Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1620.09l1Organizational.8-09.l | hipaa-1620.09l1Organizational.8-09.l | 1620.09l1Organizational.8-09.l | 16 Business Continuity & Disaster Recovery | 1620.09l1Organizational.8-09.l 09.05 Information Back-Up | Shared | n/a | When the backup service is delivered by the third-party, the service level agreement includes the detailed protections to control confidentiality, integrity and availability of the backup information. | count: 005 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7), Transfer backup information to an alternate storage site (7bdb79ea-16b8-453e-4ca4-ad5b16012414) |
Backup, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1621.09l2Organizational.1-09.l | hipaa-1621.09l2Organizational.1-09.l | 1621.09l2Organizational.1-09.l | 16 Business Continuity & Disaster Recovery | 1621.09l2Organizational.1-09.l 09.05 Information Back-Up | Shared | n/a | Automated tools are used to track all backups. | count: 003 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1622.09l2Organizational.23-09.l | hipaa-1622.09l2Organizational.23-09.l | 1622.09l2Organizational.23-09.l | 16 Business Continuity & Disaster Recovery | 1622.09l2Organizational.23-09.l 09.05 Information Back-Up | Shared | n/a | The integrity and security of the backup copies are maintained to ensure future availability, and any potential accessibility problems with the backup copies are identified and mitigated in the event of an area-wide disaster. | count: 004 Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1623.09l2Organizational.4-09.l | hipaa-1623.09l2Organizational.4-09.l | 1623.09l2Organizational.4-09.l | 16 Business Continuity & Disaster Recovery | 1623.09l2Organizational.4-09.l 09.05 Information Back-Up | Shared | n/a | Covered information is backed-up in an encrypted format to ensure confidentiality. | count: 003 Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1624.09l3Organizational.12-09.l | hipaa-1624.09l3Organizational.12-09.l | 1624.09l3Organizational.12-09.l | 16 Business Continuity & Disaster Recovery | 1624.09l3Organizational.12-09.l 09.05 Information Back-Up | Shared | n/a | The organization performs incremental or differential backups daily and full backups weekly to separate media. | count: 003 Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1625.09l3Organizational.34-09.l | hipaa-1625.09l3Organizational.34-09.l | 1625.09l3Organizational.34-09.l | 16 Business Continuity & Disaster Recovery | 1625.09l3Organizational.34-09.l 09.05 Information Back-Up | Shared | n/a | Three generations of backups (full plus all related incremental or differential backups) are stored off-site, and both on-site and off-site backups are logged with name, date, time and action. | count: 002 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf) |
Backup, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1626.09l3Organizational.5-09.l | hipaa-1626.09l3Organizational.5-09.l | 1626.09l3Organizational.5-09.l | 16 Business Continuity & Disaster Recovery | 1626.09l3Organizational.5-09.l 09.05 Information Back-Up | Shared | n/a | The organization ensures a current, retrievable copy of covered information is available before movement of servers. | count: 002 Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1627.09l3Organizational.6-09.l | hipaa-1627.09l3Organizational.6-09.l | 1627.09l3Organizational.6-09.l | 16 Business Continuity & Disaster Recovery | 1627.09l3Organizational.6-09.l 09.05 Information Back-Up | Shared | n/a | The organization tests backup information following each backup to verify media reliability and information integrity, and at least annually thereafter. | count: 002 Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7) |
Regulatory Compliance, SQL | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1634.12b1Organizational.1-12.b | hipaa-1634.12b1Organizational.1-12.b | 1634.12b1Organizational.1-12.b | 16 Business Continuity & Disaster Recovery | 1634.12b1Organizational.1-12.b 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | The organization identifies the critical business processes requiring business continuity. | count: 005 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82) |
Compute, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1635.12b1Organizational.2-12.b | hipaa-1635.12b1Organizational.2-12.b | 1635.12b1Organizational.2-12.b | 16 Business Continuity & Disaster Recovery | 1635.12b1Organizational.2-12.b 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Information security aspects of business continuity are: (i) based on identifying events (or sequence of events) that can cause interruptions to the organization's critical business processes (e.g., equipment failure, human errors, theft, fire, natural disasters acts of terrorism); (ii) followed by a risk assessment to determine the probability and impact of such interruptions, in terms of time, damage scale and recovery period; (iii) based on the results of the risk assessment, a business continuity strategy is developed to identify the overall approach to business continuity; and, (iv) once this strategy has been created, endorsement is provided by management, and a plan created and endorsed to implement this strategy. | count: 006 Azure Key Vault Managed HSM should have purge protection enabled (c39ba22d-4428-4149-b981-70acb31fc383), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Perform a business impact assessment and application criticality assessment (cb8841d4-9d13-7292-1d06-ba4d68384681), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928) |
Key Vault, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1636.12b2Organizational.1-12.b | hipaa-1636.12b2Organizational.1-12.b | 1636.12b2Organizational.1-12.b | 16 Business Continuity & Disaster Recovery | 1636.12b2Organizational.1-12.b 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | The organization identifies its critical business processes and integrates the information security management requirements of business continuity with other continuity requirements relating to such aspects as operations, staffing, materials, transport and facilities. | count: 003 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Perform a business impact assessment and application criticality assessment (cb8841d4-9d13-7292-1d06-ba4d68384681) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1637.12b2Organizational.2-12.b | hipaa-1637.12b2Organizational.2-12.b | 1637.12b2Organizational.2-12.b | 16 Business Continuity & Disaster Recovery | 1637.12b2Organizational.2-12.b 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Business impact analyses are used to evaluate the consequences of disasters, security failures, loss of service, and service availability. | count: 008 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155), Windows machines should meet requirements for 'Security Options - Recovery console' (f71be03e-e25b-4d0f-b8bc-9b3e309b66c0) |
Guest Configuration, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1638.12b2Organizational.345-12.b | hipaa-1638.12b2Organizational.345-12.b | 1638.12b2Organizational.345-12.b | 16 Business Continuity & Disaster Recovery | 1638.12b2Organizational.345-12.b 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Business continuity risk assessments: (i) are carried out annually with full involvement from owners of business resources and processes; (ii) consider all business processes and is not limited to the information assets, but includes the results specific to information security; and, (iii) identifies, quantifies, and prioritizes risks against key business objectives and criteria relevant to the organization, including critical resources, impacts of disruptions, allowable outage times, and recovery priorities. | count: 005 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928) |
Compute, Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1666.12d1Organizational.1235-12.d | hipaa-1666.12d1Organizational.1235-12.d | 1666.12d1Organizational.1235-12.d | 16 Business Continuity & Disaster Recovery | 1666.12d1Organizational.1235-12.d 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | The organization creates, at a minimum, one business continuity plan and ensures each plan: (i) has an owner; (ii) describes the approach for continuity, ensuring at a minimum the approach to maintain information or information asset availability and security; and, (iii) specifies the escalation plan and the conditions for its activation, as well as the individuals responsible for executing each component of the plan. | count: 004 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1667.12d1Organizational.4-12.d | hipaa-1667.12d1Organizational.4-12.d | 1667.12d1Organizational.4-12.d | 16 Business Continuity & Disaster Recovery | 1667.12d1Organizational.4-12.d 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | When new requirements are identified, any existing emergency procedures (e.g., evacuation plans or fallback arrangements) are amended as appropriate. | count: 004 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1668.12d1Organizational.67-12.d | hipaa-1668.12d1Organizational.67-12.d | 1668.12d1Organizational.67-12.d | 16 Business Continuity & Disaster Recovery | 1668.12d1Organizational.67-12.d 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Emergency procedures, manual "fallback" procedures, and resumption plans are the responsibility of the owner of the business resources or processes involved; and fallback arrangements for alternative technical services, such as information processing and communications facilities, are the responsibility of the service providers. | count: 004 Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1669.12d1Organizational.8-12.d | hipaa-1669.12d1Organizational.8-12.d | 1669.12d1Organizational.8-12.d | 16 Business Continuity & Disaster Recovery | 1669.12d1Organizational.8-12.d 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | The business continuity planning framework addresses a specific, minimal set of information security requirements. | count: 006 Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Perform a business impact assessment and application criticality assessment (cb8841d4-9d13-7292-1d06-ba4d68384681), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928), Provide contingency training (de936662-13dc-204c-75ec-1af80f994088), Test the business continuity and disaster recovery plan (58a51cde-008b-1a5d-61b5-d95849770677), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1670.12d2Organizational.1-12.d | hipaa-1670.12d2Organizational.1-12.d | 1670.12d2Organizational.1-12.d | 16 Business Continuity & Disaster Recovery | 1670.12d2Organizational.1-12.d 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | Each business unit creates at a minimum one business continuity plan. | count: 001 Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1671.12d2Organizational.2-12.d | hipaa-1671.12d2Organizational.2-12.d | 1671.12d2Organizational.2-12.d | 16 Business Continuity & Disaster Recovery | 1671.12d2Organizational.2-12.d 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | The organization ensures business continuity matters are always timely addressed in its management of system changes. | count: 003 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Review contingency plan (53fc1282-0ee3-2764-1319-e20143bb0ea5), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1672.12d2Organizational.3-12.d | hipaa-1672.12d2Organizational.3-12.d | 1672.12d2Organizational.3-12.d | 16 Business Continuity & Disaster Recovery | 1672.12d2Organizational.3-12.d 12.01 Information Security Aspects of Business Continuity Management | Shared | n/a | The business continuity planning framework addresses the specific, minimal set of information security requirements as well as (i) temporary operational procedures to follow pending completion of recovery and restoration, and (ii) the responsibilities of the individuals, describing who is responsible for executing which component of the plan (alternatives are nominated as required). | count: 005 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1699.09l1Organizational.10-09.l | hipaa-1699.09l1Organizational.10-09.l | 1699.09l1Organizational.10 - 09.l | Back-up | Workforce members roles and responsibilities in the data backup process are identified and communicated to the workforce; in particular, Bring Your Own Device (BYOD) users are required to perform backups of organizational and/or client data on their devices. | Customer | n/a | Portable/mobile device usage is not permitted within production data and datacenter hosting environments; thus, the control is not applicable. | count: 001 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d) |
Backup | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1704.03b1Organizational.12-03.b | hipaa-1704.03b1Organizational.12-03.b | 1704.03b1Organizational.12-03.b | 17 Risk Management | 1704.03b1Organizational.12-03.b 03.01 Risk Management Program | Shared | n/a | The organization performs risk assessments in a consistent way and at planned intervals, or when there are major changes to the organization's environment, and reviews the risk assessment results annually. | count: 002 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1705.03b2Organizational.12-03.b | hipaa-1705.03b2Organizational.12-03.b | 1705.03b2Organizational.12-03.b | 17 Risk Management | 1705.03b2Organizational.12-03.b 03.01 Risk Management Program | Shared | n/a | The organization updates the results of a formal, comprehensive risk assessment every two (2) years, or whenever there is a significant change to the information system or operational environment, assesses a subset of the security controls within every three hundred sixty-five (365) days during continuous monitoring, and reviews the risk assessment results annually. | count: 002 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1707.03c1Organizational.12-03.c | hipaa-1707.03c1Organizational.12-03.c | 1707.03c1Organizational.12-03.c | 17 Risk Management | 1707.03c1Organizational.12-03.c 03.01 Risk Management Program | Shared | n/a | The organization uses a formal methodology with defined criteria for determining risk treatments and ensuring that corrective action plans for the security program and the associated organizational information systems are prioritized and maintained; and the remedial information security actions necessary to mitigate risk to organizational operations and assets, individuals, and other organizations are documented. | count: 001 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1708.03c2Organizational.12-03.c | hipaa-1708.03c2Organizational.12-03.c | 1708.03c2Organizational.12-03.c | 17 Risk Management | 1708.03c2Organizational.12-03.c 03.01 Risk Management Program | Shared | n/a | A risk treatment plan that identifies risks and nonconformities, corrective actions, resources, responsibilities and priorities for managing information security risks is regularly reviewed and updated. | count: 002 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 17100.10a3Organizational.5 | hipaa-17100.10a3Organizational.5 | 17100.10a3Organizational.5 | 17 Risk Management | 17100.10a3Organizational.5 10.01 Security Requirements of Information Systems | Shared | n/a | The organization includes specific security-related requirements in information system acquisition contracts based on applicable laws, policies, standards, guidelines and business needs. | count: 008 Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 17101.10a3Organizational.6-10.a | hipaa-17101.10a3Organizational.6-10.a | 17101.10a3Organizational.6-10.a | 17 Risk Management | 17101.10a3Organizational.6-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to provide specific control design and implementation information. | count: 007 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Obtain design and implementation information for the security controls (22a02c9a-49e4-5dc9-0d14-eb35ad717154), Obtain functional properties of security controls (44b71aa8-099d-8b97-1557-0e853ec38e0d), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 17120.10a3Organizational.5-10.a | hipaa-17120.10a3Organizational.5-10.a | 17120.10a3Organizational.5-10.a | 17 Risk Management | 17120.10a3Organizational.5-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization documents all existing outsourced information services and conducts an organizational assessment of risk prior to the acquisition or outsourcing of information services. | count: 010 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Obtain approvals for acquisitions and outsourcing (92b94485-1c49-3350-9ada-dffe94f08e87) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 17126.03c1System.6-03.c | hipaa-17126.03c1System.6-03.c | 17126.03c1System.6-03.c | 17 Risk Management | 17126.03c1System.6-03.c 03.01 Risk Management Program | Shared | n/a | The organization has implemented an integrated control system characterized using different control types (e.g., layered, preventative, detective, corrective, and compensating) that mitigates identified risks. | count: 003 Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1713.03c1Organizational.3-03.c | hipaa-1713.03c1Organizational.3-03.c | 1713.03c1Organizational.3-03.c | 17 Risk Management | 1713.03c1Organizational.3-03.c 03.01 Risk Management Program | Shared | n/a | The organization mitigates any harmful effect that is known to the organization of a use or disclosure of sensitive information (e.g., PII) by the organization or its business partners, vendors, contractors, or similar third-parties in violation of its policies and procedures. | count: 009 Define the duties of processors (52375c01-4d4c-7acc-3aa4-5b3d53a047ec), Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Evaluate and review PII holdings regularly (b6b32f80-a133-7600-301e-398d688e7e0c), Issue guidelines for ensuring data quality and integrity (0a24f5dc-8c40-94a7-7aee-bb7cd4781d37), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Record disclosures of PII to third parties (8b1da407-5e60-5037-612e-2caa1b590719), Train staff on PII sharing and its consequences (8019d788-713d-90a1-5570-dac5052f517d), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1733.03d1Organizational.1-03.d | hipaa-1733.03d1Organizational.1-03.d | 1733.03d1Organizational.1-03.d | 17 Risk Management | 1733.03d1Organizational.1-03.d 03.01 Risk Management Program | Shared | n/a | The risk management program includes the requirement that risk assessments be re-evaluated at least annually, or when there are significant changes in the environment. | count: 003 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1734.03d2Organizational.1-03.d | hipaa-1734.03d2Organizational.1-03.d | 1734.03d2Organizational.1-03.d | 17 Risk Management | 1734.03d2Organizational.1-03.d 03.01 Risk Management Program | Shared | n/a | The risk management process is integrated with the change management process within the organization. | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1735.03d2Organizational.23-03.d | hipaa-1735.03d2Organizational.23-03.d | 1735.03d2Organizational.23-03.d | 17 Risk Management | 1735.03d2Organizational.23-03.d 03.01 Risk Management Program | Shared | n/a | Risk assessments are conducted whenever there is a significant change in the environment, or a change that could have a significant impact, and the results of the assessments are included in the change management process, so they may guide the decisions within the change management process (e.g., approvals for changes). | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1736.03d2Organizational.4-03.d | hipaa-1736.03d2Organizational.4-03.d | 1736.03d2Organizational.4-03.d | 17 Risk Management | 1736.03d2Organizational.4-03.d 03.01 Risk Management Program | Shared | n/a | The organization updates the risk assessment before issuing a new formal authorization to operate or within every three years, whichever comes first, or when conditions occur that may impact the security or authorization state of the system. | count: 001 Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1737.03d2Organizational.5-03.d | hipaa-1737.03d2Organizational.5-03.d | 1737.03d2Organizational.5-03.d | 17 Risk Management | 1737.03d2Organizational.5-03.d 03.01 Risk Management Program | Shared | n/a | The privacy, security and risk management program(s) is/are updated to reflect changes in risks. | count: 004 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1780.10a1Organizational.1-10.a | hipaa-1780.10a1Organizational.1-10.a | 1780.10a1Organizational.1-10.a | 17 Risk Management | 1780.10a1Organizational.1-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization formally addresses the purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance with system and information integrity requirements and facilitates the implementation of system and information integrity requirements/controls. | count: 003 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1781.10a1Organizational.23-10.a | hipaa-1781.10a1Organizational.23-10.a | 1781.10a1Organizational.23-10.a | 17 Risk Management | 1781.10a1Organizational.23-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | Information system specifications for security control requirements state that security controls are to be incorporated in the information system, supplemented by manual controls as needed, and these considerations are also applied when evaluating software packages, developed or purchased. | count: 004 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1782.10a1Organizational.4-10.a | hipaa-1782.10a1Organizational.4-10.a | 1782.10a1Organizational.4-10.a | 17 Risk Management | 1782.10a1Organizational.4-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | Security requirements and controls reflect the business value of the information assets involved, and the potential business damage that might result from a failure or absence of security. | count: 006 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1783.10a1Organizational.56-10.a | hipaa-1783.10a1Organizational.56-10.a | 1783.10a1Organizational.56-10.a | 17 Risk Management | 1783.10a1Organizational.56-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | A formal acquisition process is followed for purchased commercial products, and supplier contracts include the identified security requirements. | count: 008 Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1784.10a1Organizational.7-10.a | hipaa-1784.10a1Organizational.7-10.a | 1784.10a1Organizational.7-10.a | 17 Risk Management | 1784.10a1Organizational.7-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | Where the security functionality in a proposed product does not satisfy the specified requirement, the risk introduced and associated controls are reconsidered prior to purchasing the product. | count: 001 Employ FIPS 201-approved technology for PIV (8b333332-6efd-7c0d-5a9f-d1eb95105214) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1785.10a1Organizational.8-10.a | hipaa-1785.10a1Organizational.8-10.a | 1785.10a1Organizational.8-10.a | 17 Risk Management | 1785.10a1Organizational.8-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | Where additional functionality is supplied and causes a security risk, the functionality is disabled or mitigated through application of additional controls. | count: 005 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Require developers to describe accurate security functionality (3e37c891-840c-3eb4-78d2-e2e0bb5063e0), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1786.10a1Organizational.9-10.a | hipaa-1786.10a1Organizational.9-10.a | 1786.10a1Organizational.9-10.a | 17 Risk Management | 1786.10a1Organizational.9-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization requires developers of information systems, components, and developers or providers of services to identify (document) early in the system development life cycle, the functions, ports, protocols, and services intended for organizational use. | count: 004 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Require developer to identify SDLC ports, protocols, and services (f6da5cca-5795-60ff-49e1-4972567815fe) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1787.10a2Organizational.1-10.a | hipaa-1787.10a2Organizational.1-10.a | 1787.10a2Organizational.1-10.a | 17 Risk Management | 1787.10a2Organizational.1-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | Information security and privacy are addressed in all phases of the project management methodology. | count: 005 Automate privacy controls (b9d45adb-471b-56a5-64d2-5b241f126174), Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Information security and personal data protection (34738025-5925-51f9-1081-f2d0060133ed), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1788.10a2Organizational.2-10.a | hipaa-1788.10a2Organizational.2-10.a | 1788.10a2Organizational.2-10.a | 17 Risk Management | 1788.10a2Organizational.2-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization has established and appropriately protected secure development environments for system development and integration efforts that cover the entire system development life cycle. | count: 009 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1789.10a2Organizational.3-10.a | hipaa-1789.10a2Organizational.3-10.a | 1789.10a2Organizational.3-10.a | 17 Risk Management | 1789.10a2Organizational.3-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization applies information system security engineering principles in the specification, design, development, implementation, and modification of security requirements and controls in developed and acquired information systems. | count: 004 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1790.10a2Organizational.45-10.a | hipaa-1790.10a2Organizational.45-10.a | 1790.10a2Organizational.45-10.a | 17 Risk Management | 1790.10a2Organizational.45-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization includes business requirements for the availability of information systems when specifying the security requirements; and, where availability cannot be guaranteed using existing architectures, redundant components or architectures are considered along with the risks associated with implementing such redundancies. | count: 006 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8), Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1791.10a2Organizational.6-10.a | hipaa-1791.10a2Organizational.6-10.a | 1791.10a2Organizational.6-10.a | 17 Risk Management | 1791.10a2Organizational.6-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | Specifications for the security control requirements state automated controls will be incorporated in the information system, supplemented by manual controls as needed, as evidenced throughout the SDLC. | count: 005 Automate flaw remediation (a90c4d44-7fac-8e02-6d5b-0d92046b20e6), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1792.10a2Organizational.7814-10.a | hipaa-1792.10a2Organizational.7814-10.a | 1792.10a2Organizational.7814-10.a | 17 Risk Management | 1792.10a2Organizational.7814-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | Information security risk management is integrated into the SDLC, and information security roles and responsibilities are defined for all SDLC phases. | count: 004 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1793.10a2Organizational.91011-10.a | hipaa-1793.10a2Organizational.91011-10.a | 1793.10a2Organizational.91011-10.a | 17 Risk Management | 1793.10a2Organizational.91011-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The requirement definition phase includes (i) consideration of system requirements for information security and the processes for implementing security, and (ii) data classification and risk to information assets are assigned and approved (signed-off) by management to ensure appropriate controls are considered and the correct project team members are involved. | count: 006 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1794.10a2Organizational.12-10.a | hipaa-1794.10a2Organizational.12-10.a | 1794.10a2Organizational.12-10.a | 17 Risk Management | 1794.10a2Organizational.12-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | When developing software or systems the organization performs thorough testing and verification during the development process. | count: 001 Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1795.10a2Organizational.13-10.a | hipaa-1795.10a2Organizational.13-10.a | 1795.10a2Organizational.13-10.a | 17 Risk Management | 1795.10a2Organizational.13-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | Independent acceptance testing proportional to the importance and nature of the system is performed both for in-house and for outsourced development to ensure the system works as expected and only as expected. | count: 005 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1796.10a2Organizational.15-10.a | hipaa-1796.10a2Organizational.15-10.a | 1796.10a2Organizational.15-10.a | 17 Risk Management | 1796.10a2Organizational.15-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | Commercial products other than operating system software used to store and/or process covered information undergo a security assessment and/or security certification by a qualified assessor prior to implementation. | count: 006 Accept assessment results (3054c74b-9b45-2581-56cf-053a1a716c39), Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1797.10a3Organizational.1-10.a | hipaa-1797.10a3Organizational.1-10.a | 1797.10a3Organizational.1-10.a | 17 Risk Management | 1797.10a3Organizational.1-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization develops enterprise architecture with consideration for information security and the resulting risk to the organization's operations, assets, and individuals, as well as other organizations. | count: 005 Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Develop an enterprise architecture (57adc919-9dca-817c-8197-64d812070316), Require developers to build security architecture (f131c8c5-a54a-4888-1efc-158928924bc1), Require developers to describe accurate security functionality (3e37c891-840c-3eb4-78d2-e2e0bb5063e0), Require developers to provide unified security protection approach (7a114735-a420-057d-a651-9a73cd0416ef) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1798.10a3Organizational.2-10.a | hipaa-1798.10a3Organizational.2-10.a | 1798.10a3Organizational.2-10.a | 17 Risk Management | 1798.10a3Organizational.2-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization has developed an information security architecture for the information system. | count: 004 Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Develop an enterprise architecture (57adc919-9dca-817c-8197-64d812070316), Require developers to build security architecture (f131c8c5-a54a-4888-1efc-158928924bc1), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1799.10a3Organizational.34-10.a | hipaa-1799.10a3Organizational.34-10.a | 1799.10a3Organizational.34-10.a | 17 Risk Management | 1799.10a3Organizational.34-10.a 10.01 Security Requirements of Information Systems | Shared | n/a | The organization reviews and updates (as necessary) the information security architecture whenever changes are made to the enterprise architecture, and ensures that planned information security architecture changes are reflected in the security plan and organizational procurements and acquisitions. | count: 006 Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Develop an enterprise architecture (57adc919-9dca-817c-8197-64d812070316), Require developers to build security architecture (f131c8c5-a54a-4888-1efc-158928924bc1), Require developers to describe accurate security functionality (3e37c891-840c-3eb4-78d2-e2e0bb5063e0), Require developers to provide unified security protection approach (7a114735-a420-057d-a651-9a73cd0416ef), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1801.08b1Organizational.124-08.b | hipaa-1801.08b1Organizational.124-08.b | 1801.08b1Organizational.124-08.b | 18 Physical & Environmental Security | 1801.08b1Organizational.124-08.b 08.01 Secure Areas | Shared | n/a | Visitor and third-party support access is recorded and supervised unless previously approved. | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1802.08b1Organizational.3-08.b | hipaa-1802.08b1Organizational.3-08.b | 1802.08b1Organizational.3-08.b | 18 Physical & Environmental Security | 1802.08b1Organizational.3-08.b 08.01 Secure Areas | Shared | n/a | Areas where sensitive information (e.g., covered information, payment card data) is stored or processed are controlled and restricted to authorized individuals only. | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1803.08b1Organizational.5-08.b | hipaa-1803.08b1Organizational.5-08.b | 1803.08b1Organizational.5-08.b | 18 Physical & Environmental Security | 1803.08b1Organizational.5-08.b 08.01 Secure Areas | Shared | n/a | Repairs or modifications to the physical components of a facility which are related to security (e.g., hardware, walls, doors and locks) are documented and retained in accordance with the organization's retention policy. | count: 003 Automate remote maintenance activities (b8587fce-138f-86e8-33a3-c60768bf1da6), Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Produce complete records of remote maintenance activities (74041cfe-3f87-1d17-79ec-34ca5f895542) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1804.08b2Organizational.12-08.b | hipaa-1804.08b2Organizational.12-08.b | 1804.08b2Organizational.12-08.b | 18 Physical & Environmental Security | 1804.08b2Organizational.12-08.b 08.01 Secure Areas | Shared | n/a | A visitor log containing appropriate information is reviewed monthly and maintained for at least two years. | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1805.08b2Organizational.3-08.b | hipaa-1805.08b2Organizational.3-08.b | 1805.08b2Organizational.3-08.b | 18 Physical & Environmental Security | 1805.08b2Organizational.3-08.b 08.01 Secure Areas | Shared | n/a | Physical authentication controls are used to authorize and validate access. | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1806.08b2Organizational.4-08.b | hipaa-1806.08b2Organizational.4-08.b | 1806.08b2Organizational.4-08.b | 18 Physical & Environmental Security | 1806.08b2Organizational.4-08.b 08.01 Secure Areas | Shared | n/a | An audit trail of all physical access is maintained. | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1807.08b2Organizational.56-08.b | hipaa-1807.08b2Organizational.56-08.b | 1807.08b2Organizational.56-08.b | 18 Physical & Environmental Security | 1807.08b2Organizational.56-08.b 08.01 Secure Areas | Shared | n/a | Visible identification that clearly identifies the individual is required to be worn by employees, visitors, contractors and third-parties. | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1808.08b2Organizational.7-08.b | hipaa-1808.08b2Organizational.7-08.b | 1808.08b2Organizational.7-08.b | 18 Physical & Environmental Security | 1808.08b2Organizational.7-08.b 08.01 Secure Areas | Shared | n/a | Physical access rights are reviewed every 90 days and updated accordingly. | count: 007 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1810.08b3Organizational.2-08.b | hipaa-1810.08b3Organizational.2-08.b | 1810.08b3Organizational.2-08.b | 18 Physical & Environmental Security | 1810.08b3Organizational.2-08.b 08.01 Secure Areas | Shared | n/a | Inventories of physical access devices are performed every 90 days. | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 18108.08j1Organizational.1-08.j | hipaa-18108.08j1Organizational.1-08.j | 18108.08j1Organizational.1-08.j | 18 Physical & Environmental Security | 18108.08j1Organizational.1-08.j 08.02 Equipment Security | Shared | n/a | The organization formally addresses the purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities and compliance requirements for its equipment maintenance program (e.g., through policy, standards, guidelines, and procedures). | count: 002 Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 18109.08j1Organizational.4-08.j | hipaa-18109.08j1Organizational.4-08.j | 18109.08j1Organizational.4-08.j | 18 Physical & Environmental Security | 18109.08j1Organizational.4-08.j 08.02 Equipment Security | Shared | n/a | The organization maintains a list of authorized maintenance organizations or personnel, ensures that non-escorted personnel performing maintenance on the information system have required access authorizations, and designates organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations. | count: 004 Designate personnel to supervise unauthorized maintenance activities (7a489c62-242c-5db9-74df-c073056d6fa3), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Maintain list of authorized remote maintenance personnel (4ce91e4e-6dab-3c46-011a-aa14ae1561bf), Manage maintenance personnel (b273f1e3-79e7-13ee-5b5d-dca6c66c3d5d) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1811.08b3Organizational.3-08.b | hipaa-1811.08b3Organizational.3-08.b | 1811.08b3Organizational.3-08.b | 18 Physical & Environmental Security | 1811.08b3Organizational.3-08.b 08.01 Secure Areas | Shared | n/a | Combinations and keys for organization-defined high-risk entry/exit points are changed when lost or stolen or combinations are compromised. | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 18110.08j1Organizational.5-08.j | hipaa-18110.08j1Organizational.5-08.j | 18110.08j1Organizational.5-08.j | 18 Physical & Environmental Security | 18110.08j1Organizational.5-08.j 08.02 Equipment Security | Shared | n/a | The organization monitors and controls non-local maintenance and diagnostic activities; and prohibits non-local system maintenance unless explicitly authorized, in writing, by the CIO or his/her designated representative. | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Implement cryptographic mechanisms (10c3a1b1-29b0-a2d5-8f4c-a284b0f07830), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Perform all non-local maintenance (5bac5fb7-7735-357b-767d-02264bfe5c3b) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 18111.08j1Organizational.6-08.j | hipaa-18111.08j1Organizational.6-08.j | 18111.08j1Organizational.6-08.j | 18 Physical & Environmental Security | 18111.08j1Organizational.6-08.j 08.02 Equipment Security | Shared | n/a | The organization obtains maintenance support and/or spare parts for defined key information system components (defined in the applicable security plan) within the applicable Recovery Time Objective (RTO) specified in the contingency plan. | count: 001 Provide timely maintenance support (eb598832-4bcc-658d-4381-3ecbe17b9866) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 18112.08j3Organizational.4-08.j | hipaa-18112.08j3Organizational.4-08.j | 18112.08j3Organizational.4-08.j | 18 Physical & Environmental Security | 18112.08j3Organizational.4-08.j 08.02 Equipment Security | Shared | n/a | The organization documents the requirements (e.g., policies and procedures) for the establishment and use of non-local maintenance and diagnostic connections in the security plan for the information system. | count: 003 Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1812.08b3Organizational.46-08.b | hipaa-1812.08b3Organizational.46-08.b | 1812.08b3Organizational.46-08.b | 18 Physical & Environmental Security | 1812.08b3Organizational.46-08.b 08.01 Secure Areas | Shared | n/a | Intrusion detection systems (e.g., alarms and surveillance equipment) are installed on all external doors and accessible windows, the systems are monitored, and incidents/alarms are investigated. | count: 003 Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 18127.08l1Organizational.3-08.l | hipaa-18127.08l1Organizational.3-08.l | 18127.08l1Organizational.3-08.l | 18 Physical & Environmental Security | 18127.08l1Organizational.3-08.l 08.02 Equipment Security | Shared | n/a | Surplus equipment is stored securely while not in use, and disposed of or sanitized when no longer required. | count: 001 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1813.08b3Organizational.56-08.b | hipaa-1813.08b3Organizational.56-08.b | 1813.08b3Organizational.56-08.b | 18 Physical & Environmental Security | 1813.08b3Organizational.56-08.b 08.01 Secure Areas | Shared | n/a | The organization actively monitors unoccupied areas at all times and sensitive and/or restricted areas in real time as appropriate for the area. | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 18130.09p1Organizational.24-09.p | hipaa-18130.09p1Organizational.24-09.p | 18130.09p1Organizational.24-09.p | 18 Physical & Environmental Security | 18130.09p1Organizational.24-09.p 09.07 Media Handling | Shared | n/a | The organization ensures the risk of information leakage to unauthorized persons during secure media disposal is minimized. If collection and disposal services offered by other organizations are used, care is taken in selecting a suitable contractor with adequate controls and experience. | count: 001 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1814.08d1Organizational.12-08.d | hipaa-1814.08d1Organizational.12-08.d | 1814.08d1Organizational.12-08.d | 18 Physical & Environmental Security | 1814.08d1Organizational.12-08.d 08.01 Secure Areas | Shared | n/a | Fire extinguishers and detectors are installed according to applicable laws and regulations. | count: 003 Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 18145.08b3Organizational.7-08.b | hipaa-18145.08b3Organizational.7-08.b | 18145.08b3Organizational.7-08.b | 18 Physical & Environmental Security | 18145.08b3Organizational.7-08.b 08.01 Secure Areas | Shared | n/a | The organization regularly tests alarms to ensure proper operation. | count: 002 Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 18146.08b3Organizational.8-08.b | hipaa-18146.08b3Organizational.8-08.b | 18146.08b3Organizational.8-08.b | 18 Physical & Environmental Security | 18146.08b3Organizational.8-08.b 08.01 Secure Areas | Shared | n/a | The organization maintains an electronic log of alarm system events and regularly reviews the logs, no less than monthly. | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1815.08d2Organizational.123-08.d | hipaa-1815.08d2Organizational.123-08.d | 1815.08d2Organizational.123-08.d | 18 Physical & Environmental Security | 1815.08d2Organizational.123-08.d 08.01 Secure Areas | Shared | n/a | Fire prevention and suppression mechanisms, including workforce training, are provided. | count: 003 Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1816.08d2Organizational.4-08.d | hipaa-1816.08d2Organizational.4-08.d | 1816.08d2Organizational.4-08.d | 18 Physical & Environmental Security | 1816.08d2Organizational.4-08.d 08.01 Secure Areas | Shared | n/a | Any security threats presented by neighboring premises are identified. | count: 004 Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1817.08d3Organizational.12-08.d | hipaa-1817.08d3Organizational.12-08.d | 1817.08d3Organizational.12-08.d | 18 Physical & Environmental Security | 1817.08d3Organizational.12-08.d 08.01 Secure Areas | Shared | n/a | Water detection mechanisms are in place with master shutoff or isolation valves accessible, working and known. | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1818.08d3Organizational.3-08.d | hipaa-1818.08d3Organizational.3-08.d | 1818.08d3Organizational.3-08.d | 18 Physical & Environmental Security | 1818.08d3Organizational.3-08.d 08.01 Secure Areas | Shared | n/a | Fire suppression and detection systems are supported by an independent energy source. | count: 003 Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1819.08j1Organizational.23-08.j | hipaa-1819.08j1Organizational.23-08.j | 1819.08j1Organizational.23-08.j | 18 Physical & Environmental Security | 1819.08j1Organizational.23-08.j 08.02 Equipment Security | Shared | n/a | Maintenance and service are controlled and conducted by authorized personnel in accordance with supplier-recommended intervals, insurance policies and the organization’s maintenance program, taking into account whether this maintenance is performed by personnel on site or external to the organization. | count: 007 Automate remote maintenance activities (b8587fce-138f-86e8-33a3-c60768bf1da6), Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Designate personnel to supervise unauthorized maintenance activities (7a489c62-242c-5db9-74df-c073056d6fa3), Maintain list of authorized remote maintenance personnel (4ce91e4e-6dab-3c46-011a-aa14ae1561bf), Manage maintenance personnel (b273f1e3-79e7-13ee-5b5d-dca6c66c3d5d), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Produce complete records of remote maintenance activities (74041cfe-3f87-1d17-79ec-34ca5f895542) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1820.08j2Organizational.1-08.j | hipaa-1820.08j2Organizational.1-08.j | 1820.08j2Organizational.1-08.j | 18 Physical & Environmental Security | 1820.08j2Organizational.1-08.j 08.02 Equipment Security | Shared | n/a | Covered information is cleared from equipment prior to maintenance unless explicitly authorized. | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1821.08j2Organizational.3-08.j | hipaa-1821.08j2Organizational.3-08.j | 1821.08j2Organizational.3-08.j | 18 Physical & Environmental Security | 1821.08j2Organizational.3-08.j 08.02 Equipment Security | Shared | n/a | Following maintenance, security controls are checked and verified. | count: 004 Automate remote maintenance activities (b8587fce-138f-86e8-33a3-c60768bf1da6), Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Produce complete records of remote maintenance activities (74041cfe-3f87-1d17-79ec-34ca5f895542) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1822.08j2Organizational.2-08.j | hipaa-1822.08j2Organizational.2-08.j | 1822.08j2Organizational.2-08.j | 18 Physical & Environmental Security | 1822.08j2Organizational.2-08.j 08.02 Equipment Security | Shared | n/a | Records of maintenance are maintained. | count: 004 Automate remote maintenance activities (b8587fce-138f-86e8-33a3-c60768bf1da6), Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Produce complete records of remote maintenance activities (74041cfe-3f87-1d17-79ec-34ca5f895542) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1823.08j3Organizational.12-08.j | hipaa-1823.08j3Organizational.12-08.j | 1823.08j3Organizational.12-08.j | 18 Physical & Environmental Security | 1823.08j3Organizational.12-08.j 08.02 Equipment Security | Shared | n/a | Tools for maintenance are approved, controlled, monitored and periodically checked. | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1824.08j3Organizational.3-08.j | hipaa-1824.08j3Organizational.3-08.j | 1824.08j3Organizational.3-08.j | 18 Physical & Environmental Security | 1824.08j3Organizational.3-08.j 08.02 Equipment Security | Shared | n/a | Media containing diagnostic and test programs are checked for malicious code prior to use. | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1826.09p1Organizational.1-09.p | hipaa-1826.09p1Organizational.1-09.p | 1826.09p1Organizational.1-09.p | 18 Physical & Environmental Security | 1826.09p1Organizational.1-09.p 09.07 Media Handling | Shared | n/a | The organization securely disposes of media containing sensitive information. | count: 003 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1844.08b1Organizational.6-08.b | hipaa-1844.08b1Organizational.6-08.b | 1844.08b1Organizational.6-08.b | 18 Physical & Environmental Security | 1844.08b1Organizational.6-08.b 08.01 Secure Areas | Shared | n/a | The organization develops, approves and maintains a list of individuals with authorized access to the facility where the information system resides; issues authorization credentials for facility access; reviews the access list and authorization credentials periodically but no less than quarterly; and removes individuals from the facility access list when access is no longer required. | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1845.08b1Organizational.7-08.b | hipaa-1845.08b1Organizational.7-08.b | 1845.08b1Organizational.7-08.b | 18 Physical & Environmental Security | 1845.08b1Organizational.7-08.b 08.01 Secure Areas | Shared | n/a | For facilities where the information system resides, the organization enforces physical access authorizations at defined entry/exit points to the facility where the information system resides, maintains physical access audit logs, and provides security safeguards that the organization determines necessary for areas officially designated as publicly accessible. | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1846.08b2Organizational.8-08.b | hipaa-1846.08b2Organizational.8-08.b | 1846.08b2Organizational.8-08.b | 18 Physical & Environmental Security | 1846.08b2Organizational.8-08.b 08.01 Secure Areas | Shared | n/a | Visitors are only granted access for specific and authorized purposes and issued with instructions on the security requirements of the area and on emergency procedures. | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1847.08b2Organizational.910-08.b | hipaa-1847.08b2Organizational.910-08.b | 1847.08b2Organizational.910-08.b | 18 Physical & Environmental Security | 1847.08b2Organizational.910-08.b 08.01 Secure Areas | Shared | n/a | The organization ensures onsite personnel and visitor identification (e.g., badges) are revoked, updated when access requirements change, or terminated when expired or when access is no longer authorized, and all physical access mechanisms, such as keys, access cards and combinations, are returned, disabled or changed. | count: 002 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1848.08b2Organizational.11-08.b | hipaa-1848.08b2Organizational.11-08.b | 1848.08b2Organizational.11-08.b | 18 Physical & Environmental Security | 1848.08b2Organizational.11-08.b 08.01 Secure Areas | Shared | n/a | A restricted area, security room, or locked room is used to control access to areas containing covered information, and is controlled accordingly. | count: 001 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1862.08d1Organizational.3-08.d | hipaa-1862.08d1Organizational.3-08.d | 1862.08d1Organizational.3-08.d | 18 Physical & Environmental Security | 1862.08d1Organizational.3-08.d 08.01 Secure Areas | Shared | n/a | Fire authorities are automatically notified when a fire alarm is activated. | count: 002 Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1862.08d3Organizational.3 | hipaa-1862.08d3Organizational.3 | 1862.08d3Organizational.3 | 18 Physical & Environmental Security | 1862.08d3Organizational.3 08.01 Secure Areas | Shared | n/a | Fire authorities are automatically notified when a fire alarm is activated. | count: 002 Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1892.01l1Organizational.1 | hipaa-1892.01l1Organizational.1 | 1892.01l1Organizational.1 | 18 Physical & Environmental Security | 1892.01l1Organizational.1 01.04 Network Access Control | Shared | n/a | Access to network equipment is physically protected. | count: 002 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1901.06d1Organizational.1-06.d | hipaa-1901.06d1Organizational.1-06.d | 1901.06d1Organizational.1-06.d | 19 Data Protection & Privacy | 1901.06d1Organizational.1-06.d 06.01 Compliance with Legal Requirements | Shared | n/a | The organization has formally appointed a qualified data protection officer, reporting to senior management, and who is directly and fully responsible for the privacy of covered information. | count: 003 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Manage compliance activities (4e400494-53a5-5147-6f4d-718b539c7394) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1902.06d1Organizational.2-06.d | hipaa-1902.06d1Organizational.2-06.d | 1902.06d1Organizational.2-06.d | 19 Data Protection & Privacy | 1902.06d1Organizational.2-06.d 06.01 Compliance with Legal Requirements | Shared | n/a | When required, consent is obtained before any PII (e.g., about a client/customer) is emailed, faxed, or communicated by telephone conversation, or otherwise disclosed to parties external to the organization. | count: 011 Define the duties of processors (52375c01-4d4c-7acc-3aa4-5b3d53a047ec), Document and distribute a privacy policy (ee67c031-57fc-53d0-0cca-96c4c04345e8), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Keep accurate accounting of disclosures of information (0bbfd658-93ab-6f5e-1e19-3c1c1da62d01), Make accounting of disclosures available upon request (d4f70530-19a2-2a85-6e0c-0c3c465e3325), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Record disclosures of PII to third parties (8b1da407-5e60-5037-612e-2caa1b590719), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9), Retain accounting of disclosures of information (75b9db50-7906-2351-98ae-0458218609e5), Train staff on PII sharing and its consequences (8019d788-713d-90a1-5570-dac5052f517d) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1903.06d1Organizational.3456711-06.d | hipaa-1903.06d1Organizational.3456711-06.d | 1903.06d1Organizational.3456711-06.d | 19 Data Protection & Privacy | 1903.06d1Organizational.3456711-06.d 06.01 Compliance with Legal Requirements | Shared | n/a | The confidentiality and integrity of covered information at rest is protected using an encryption method appropriate to the medium where it is stored; where the organization chooses not to encrypt covered information, a documented rationale for not doing so is maintained or alternative compensating controls are used if the method is approved and reviewed annually by the CISO. | count: 005 Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1904.06.d2Organizational.1-06.d | hipaa-1904.06.d2Organizational.1-06.d | 1904.06.d2Organizational.1-06.d | 19 Data Protection & Privacy | 1904.06.d2Organizational.1-06.d 06.01 Compliance with Legal Requirements | Shared | n/a | Covered information is retained only for as long as required. | count: 003 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1906.06.c1Organizational.2-06.c | hipaa-1906.06.c1Organizational.2-06.c | 1906.06.c1Organizational.2-06.c | 19 Data Protection & Privacy | 1906.06.c1Organizational.2-06.c 06.01 Compliance with Legal Requirements | Shared | n/a | The organization documents compliance with the notice requirements by retaining copies of the notices issued by the organization for a period of six years and, if applicable, any written acknowledgements of receipt of the notice or documentation of good faith efforts to obtain such written acknowledgement. | count: 004 Make SORNs available publicly (f3c17714-8ce7-357f-4af2-a0baa63a063f), Provide formal notice to individuals (95eb7d09-9937-5df9-11d9-20317e3f60df), Provide privacy notice to the public and to individuals (5023a9e7-8e64-2db6-31dc-7bce27f796af), Publish SORNs for systems containing PII (898a5781-2254-5a37-34c7-d78ea7c20d55) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1907.06.c1Organizational.3-06.c | hipaa-1907.06.c1Organizational.3-06.c | 1907.06.c1Organizational.3-06.c | 19 Data Protection & Privacy | 1907.06.c1Organizational.3-06.c 06.01 Compliance with Legal Requirements | Shared | n/a | The organization documents restrictions in writing and formally maintains such writing, or an electronic copy of such writing, as an organizational record for a period of six years. | count: 004 Keep SORNs updated (3bd4e0af-7cbb-a3ec-4918-056a3c017ae2), Make SORNs available publicly (f3c17714-8ce7-357f-4af2-a0baa63a063f), Provide formal notice to individuals (95eb7d09-9937-5df9-11d9-20317e3f60df), Publish SORNs for systems containing PII (898a5781-2254-5a37-34c7-d78ea7c20d55) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1908.06.c1Organizational.4-06.c | hipaa-1908.06.c1Organizational.4-06.c | 1908.06.c1Organizational.4-06.c | 19 Data Protection & Privacy | 1908.06.c1Organizational.4-06.c 06.01 Compliance with Legal Requirements | Shared | n/a | The organization documents and maintains (i) designated record sets that are subject to access by individuals, and (ii) titles of the persons or office responsible for receiving and processing requests for access by individuals as organizational records for a period of six years. | count: 011 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Keep SORNs updated (3bd4e0af-7cbb-a3ec-4918-056a3c017ae2), Make SORNs available publicly (f3c17714-8ce7-357f-4af2-a0baa63a063f), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Provide formal notice to individuals (95eb7d09-9937-5df9-11d9-20317e3f60df), Publish SORNs for systems containing PII (898a5781-2254-5a37-34c7-d78ea7c20d55), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 1911.06d1Organizational.13-06.d | hipaa-1911.06d1Organizational.13-06.d | 1911.06d1Organizational.13-06.d | 19 Data Protection & Privacy | 1911.06d1Organizational.13-06.d 06.01 Compliance with Legal Requirements | Shared | n/a | Records with sensitive personal information are protected during transfer to organizations lawfully collecting such information. | count: 005 Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35), Evaluate and review PII holdings regularly (b6b32f80-a133-7600-301e-398d688e7e0c), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Remove or redact any PII (94c842e3-8098-38f9-6d3f-8872b790527d) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 19134.05j1Organizational.5-05.j | hipaa-19134.05j1Organizational.5-05.j | 19134.05j1Organizational.5-05.j | 19 Data Protection & Privacy | 19134.05j1Organizational.5-05.j 05.02 External Parties | Shared | n/a | The public has access to information about the organization's security and privacy activities and is able to communicate with its senior security official and senior privacy official. | count: 012 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Information security and personal data protection (34738025-5925-51f9-1081-f2d0060133ed), Manage compliance activities (4e400494-53a5-5147-6f4d-718b539c7394), Review content prior to posting publicly accessible information (9e3c505e-7aeb-2096-3417-b132242731fc), Review publicly accessible content for nonpublic information (b5244f81-6cab-3188-2412-179162294996), Train personnel on disclosure of nonpublic information (97f0d974-1486-01e2-2088-b888f46c0589), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 19141.06c1Organizational.7-06.c | hipaa-19141.06c1Organizational.7-06.c | 19141.06c1Organizational.7-06.c | 19 Data Protection & Privacy | 19141.06c1Organizational.7-06.c 06.01 Compliance with Legal Requirements | Shared | n/a | Important records, such as contracts, personnel records, financial information, client/customer information, etc., of the organization are protected from loss, destruction and falsification through the implementation of security controls such as access controls, encryption, backups, electronic signatures, locked facilities or containers, etc. | count: 010 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Implement transaction based recovery (ba02d0a0-566a-25dc-73f1-101c726a19c5), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 19142.06c1Organizational.8-06.c | hipaa-19142.06c1Organizational.8-06.c | 19142.06c1Organizational.8-06.c | 19 Data Protection & Privacy | 19142.06c1Organizational.8-06.c 06.01 Compliance with Legal Requirements | Shared | n/a | Guidelines are issued by the organization on the ownership, classification, retention, storage, handling and disposal of all records and information. | count: 009 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 19143.06c1Organizational.9-06.c | hipaa-19143.06c1Organizational.9-06.c | 19143.06c1Organizational.9-06.c | 19 Data Protection & Privacy | 19143.06c1Organizational.9-06.c 06.01 Compliance with Legal Requirements | Shared | n/a | Designated senior management within the organization reviews and approves the security categorizations and associated guidelines. | count: 006 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Categorize information (93fa357f-2e38-22a9-5138-8cc5124e1923), Develop business classification schemes (11ba0508-58a8-44de-5f3a-9e05d80571da), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Ensure security categorization is approved (6c79c3e5-5f7b-a48a-5c7b-8c158bc01115), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 19144.06c2Organizational.1-06.c | hipaa-19144.06c2Organizational.1-06.c | 19144.06c2Organizational.1-06.c | 19 Data Protection & Privacy | 19144.06c2Organizational.1-06.c 06.01 Compliance with Legal Requirements | Shared | n/a | The organization has established a formal records document retention program. | count: 007 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 19145.06c2Organizational.2-06.c | hipaa-19145.06c2Organizational.2-06.c | 19145.06c2Organizational.2-06.c | 19 Data Protection & Privacy | 19145.06c2Organizational.2-06.c 06.01 Compliance with Legal Requirements | Shared | n/a | Specific controls for record storage, access, retention, and destruction have been implemented. | count: 008 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 19242.06d1Organizational.14-06.d | hipaa-19242.06d1Organizational.14-06.d | 19242.06d1Organizational.14-06.d | 19 Data Protection & Privacy | 19242.06d1Organizational.14-06.d 06.01 Compliance with Legal Requirements | Shared | n/a | Covered information storage is kept to a minimum. | count: 004 Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Evaluate and review PII holdings regularly (b6b32f80-a133-7600-301e-398d688e7e0c), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Remove or redact any PII (94c842e3-8098-38f9-6d3f-8872b790527d) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 19243.06d1Organizational.15-06.d | hipaa-19243.06d1Organizational.15-06.d | 19243.06d1Organizational.15-06.d | 19 Data Protection & Privacy | 19243.06d1Organizational.15-06.d 06.01 Compliance with Legal Requirements | Shared | n/a | The organization specifies where covered information can be stored. | count: 009 Automate privacy controls (b9d45adb-471b-56a5-64d2-5b241f126174), Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Evaluate and review PII holdings regularly (b6b32f80-a133-7600-301e-398d688e7e0c), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Information security and personal data protection (34738025-5925-51f9-1081-f2d0060133ed), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Remove or redact any PII (94c842e3-8098-38f9-6d3f-8872b790527d), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| hipaa | 19245.06d2Organizational.2-06.d | hipaa-19245.06d2Organizational.2-06.d | 19245.06d2Organizational.2-06.d | 19 Data Protection & Privacy | 19245.06d2Organizational.2-06.d 06.01 Compliance with Legal Requirements | Shared | n/a | The organization has implemented technical means to ensure covered information is stored in organization-specified locations. | count: 007 Confirm quality and integrity of PII (8bb40df9-23e4-4175-5db3-8dba86349b73), Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Evaluate and review PII holdings regularly (b6b32f80-a133-7600-301e-398d688e7e0c), Issue guidelines for ensuring data quality and integrity (0a24f5dc-8c40-94a7-7aee-bb7cd4781d37), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Publish Computer Matching Agreements on public website (cdcb825f-a0fb-31f9-29c1-ab566718499a) |
Regulatory Compliance | HITRUST/HIPAA (a169a624-5599-4385-a696-c8d643089fab) | |
| IRS_1075_9.3 | .1.12 | IRS_1075_9.3.1.12 | IRS 1075 9.3.1.12 | Access Control | Remote Access (AC-17) | n/a | The agency must: a. Establish and document usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed b. Authorize remote access to the information system prior to allowing such connections c. Authorize and document the execution of privileged commands and access to security-relevant information via remote access for compelling operational needs only (CE4) The information system must: a. Monitor and control remote access methods (CE1) b. Implement cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions where FTI is transmitted over the remote connection and (CE2) c. Route all remote accesses through a limited number of managed network access control points (CE3) Remote access is defined as any access to an agency information system by a user communicating through an external network, for example, the Internet. Any remote access where FTI is accessed over the remote connection must be performed using multi-factor authentication. FTI cannot be accessed remotely by agency employees, agents, representatives, or contractors located offshore--outside of the United States territories, embassies, or military installations. Further, FTI may not be received, processed, stored, transmitted, or disposed of by IT systems located offshore. | link | count: 007 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
App Service, Guest Configuration, Storage | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .1.2 | IRS_1075_9.3.1.2 | IRS 1075 9.3.1.2 | Access Control | Account Management (AC-2) | n/a | The agency must: a. Identify and select the accounts with access to FTI to support agency missions/business functions b. Assign account managers for information system accounts; c. Establish conditions for group and role membership d. Specify authorized users of the information system, group and role membership, and access authorizations (i.e., privileges) and other attributes (as required) for each account e. Require approval for requests to create information system accounts f. Create, enable, modify, disable, and remove information system accounts in accordance with documented agency account management procedures g. Monitor the use of information system accounts h. Notify account managers when accounts are no longer required, when users are terminated or transferred, or when individual information system usage or need- to-know permission changes i. Authorize access to information systems that receive, process, store, or transmit FTI based on a valid access authorization, need-to-know permission, and under the authority to re-disclosed FTI under the provisions of IRC 6103 j. Review accounts for compliance with account management requirements at a k. minimum of annually for user accounts and semi-annually for privileged accounts l. Establish a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group. The information system must automatically disable inactive accounts after 120 days of inactivity. (CE3) | link | count: 009 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
General, Security Center, Service Fabric, SQL | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .1.4 | IRS_1075_9.3.1.4 | IRS 1075 9.3.1.4 | Access Control | Information Flow Enforcement (AC-4) | n/a | The information system must enforce approved authorizations for controlling the flow of FTI within the system and between interconnected systems based on the technical safeguards in place to protect the FTI. Additional requirements for protecting the flow of FTI can be found in: - Section 9.4.3, Email Communications - Section 9.4.4, Fax Equipment - Section 9.4.9, Multi-Functional Devices | link | count: 001 App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9) |
App Service | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .1.5 | IRS_1075_9.3.1.5 | IRS 1075 9.3.1.5 | Access Control | Separation of Duties (AC-5) | n/a | The agency must: a. Separate duties of individuals to prevent harmful activity without collusion b. Document separation of duties of individuals c. Define information system access authorizations to support separation of duties | link | count: 007 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .1.6 | IRS_1075_9.3.1.6 | IRS 1075 9.3.1.6 | Access Control | Least Privilege (AC-6) | n/a | The agency must: a. Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned tasks in accordance with agency missions and business functions b. Explicitly authorize access to FTI (CE1) c. Require that users of information system accounts, or roles, with access to FTI, use non-privileged accounts or roles when accessing non-security functions (CE2) d. Restrict privileged accounts on the information system to a limited number of individuals with a need to perform administrative duties (CE5) The information system must: a. Audit the execution of privileged functions (CE9) b. Prevent non-privileged users from executing privileged functions; including disabling, circumventing, or altering implemented security safeguards/countermeasures (CE10) | link | count: 007 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .14.3 | IRS_1075_9.3.14.3 | IRS 1075 9.3.14.3 | Risk Assessment | Vulnerability Scanning (RA-5) | n/a | The agency must: a. Scan for vulnerabilities in the information system and hosted applications at a minimum of monthly for all systems and when new vulnerabilities potentially affecting the system/applications are identified and reported b. Employ vulnerability scanning tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: 1. Enumerating platforms, software flaws, and improper configurations 2. Formatting checklists and test procedures 3. Measuring vulnerability impact c. Analyze vulnerability scan reports and results from security control assessments d. Remediate legitimate vulnerabilities in accordance with an assessment of risk e. Share information obtained from the vulnerability scanning process and security control assessments with designated agency officials to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies) f. Employ vulnerability scanning tools that include the capability to readily update the information system vulnerabilities to be scanned (CE1) | link | count: 006 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center, SQL | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .16.15 | IRS_1075_9.3.16.15 | IRS 1075 9.3.16.15 | System and Communications Protection | Protection of Information at Rest (SC-28) | n/a | The information system must protect the confidentiality and integrity of FTI at rest. Information at rest refers to the state of information when it is located on storage devices as specific components of information systems. Agencies may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms, file share scanning, and integrity protection. Agencies may also employ other security controls, including, for example, secure offline storage in lieu of online storage, when adequate protection of information at rest cannot otherwise be achieved or when continuously monitoring to identify malicious code at rest. The confidentiality and integrity of information at rest shall be protected when located on a secondary (non-mobile) storage device (e.g., disk drive, tape drive) with cryptography mechanisms FTI stored on deployed user workstations, in non-volatile storage, shall be encrypted with FIPS-validated or National Security Agency (NSA)-approved encryption during storage (regardless of location) except when no approved encryption technology solution is available that addresses the specific technology. Mobile devices do require encryption at rest (see Section 9.3.1.14, Access Control for Mobile Devices (AC-19), and Section 9.4.8, Mobile Devices). | link | count: 004 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Security Center, SQL | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .16.4 | IRS_1075_9.3.16.4 | IRS 1075 9.3.16.4 | System and Communications Protection | Denial of Service Protection (SC-5) | n/a | The information system must protect against or limit the effects of denial of service attacks. Refer to NIST SP 800-61 R2, Computer Security Incident Handling Guide, for additional information on denial of service. | link | count: 001 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd) |
Security Center | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .16.5 | IRS_1075_9.3.16.5 | IRS 1075 9.3.16.5 | System and Communications Protection | Boundary Protection (SC-7) | n/a | The information system must: a. Monitor and control communications at the external boundary of the system and at key internal boundaries within the system b. Implement subnetworks for publicly accessible system components that are physically and logically separated from internal agency networks c. Connect to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with agency security architecture requirements Managed interfaces include, for example, gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within the security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). The agency must limit the number of external network connections to the information system. (CE3) The agency must: (CE4) a. Implement a secure managed interface for each external telecommunication service b. Establish a traffic flow policy for each managed interface d. Protect the confidentiality and integrity of the information being transmitted across each interface e. Document each exception to the traffic flow policy with a supporting mission/business need and duration of that need, and accept the associated risk f. Review exceptions to the traffic flow policy at a minimum annually, and remove exceptions that are no longer supported by an explicit mission/business need The information system at managed interfaces must deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). (CE5) The information system must, in conjunction with a remote device, prevent the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks. (CE7) Additional requirements for protecting FTI on networks are provided in Section 9.4.10, Network Protections. | link | count: 004 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Security Center, Storage | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .16.6 | IRS_1075_9.3.16.6 | IRS 1075 9.3.16.6 | System and Communications Protection | Transmission Confidentiality and Integrity (SC-8) | n/a | Information systems that receive, process, store, or transmit FTI, must: a. Protect the confidentiality and integrity of transmitted information b. Implement FIPS 140-2 cryptographic mechanisms to prevent unauthorized disclosure of FTI and detect changes to information during transmission across the wide area network (WAN) and within the local area network (LAN) (CE1) The agency must ensure that all network infrastructure, access points, wiring, conduits, and cabling are within the control of authorized agency personnel. Network monitoring capabilities must be implemented to detect and monitor for suspicious network traffic. For physical security protections of transmission medium, see Section 9.3.11.4, Access Control for Transmission Medium (PE-4). This control applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, fax machines). | link | count: 008 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, Storage | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .17.2 | IRS_1075_9.3.17.2 | IRS 1075 9.3.17.2 | System and Information Integrity | Flaw Remediation (SI-2) | n/a | The agency must: a. Identify, report, and correct information system flaws b. Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation c. Install security-relevant software and firmware updates based on severity and associated risk to the confidentiality of FTI d. Incorporate flaw remediation into the agency configuration management process e. Centrally manage the flaw remediation process (CE1) Security-relevant software updates include, for example, patches, service packs, hot fixes, and antivirus signatures. | link | count: 006 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .17.3 | IRS_1075_9.3.17.3 | IRS 1075 9.3.17.3 | System and Information Integrity | Malicious Code Protection (SI-3) | n/a | Malicious code protection includes antivirus software and antimalware and intrusion detection systems. The agency must: a. Employ malicious code protection mechanisms at information system entry and exit points to detect and eradicate malicious code b. Update malicious code protection mechanisms whenever new releases are available in accordance with agency configuration management policy and procedures c. Configure malicious code protection mechanisms to: 1. Perform periodic scans of the information system weekly and real-time scans of files from external sources at endpoint and network entry/exit points as the files are downloaded, opened, or executed in accordance with agency security policy 2. Either block or quarantine malicious code and send an alert to the administrator in response to malicious code detection d. Address the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the information system e. Centrally manage malicious code protection mechanisms (CE1) The information system must automatically update malicious code protection mechanisms. (CE2) Information system entry and exit points include, for example, firewalls, electronic mail servers, Web servers, proxy servers, remote access servers, workstations, notebook computers, and mobile devices. Malicious code includes, for example, viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files or hidden in files using steganography. Malicious code can be transported by different means, including, for example, Web accesses, electronic mail, electronic mail attachments, and portable storage devices. | link | count: 002 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Security Center | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .17.4 | IRS_1075_9.3.17.4 | IRS 1075 9.3.17.4 | System and Information Integrity | Information System Monitoring (SI-4) | n/a | The agency must: a. Monitor the information system to detect: 1. Attacks and indicators of potential attacks 2. Unauthorized local, network, and remote connections b. Identify unauthorized use of the information system c. Deploy monitoring devices: (i) strategically within the information system to collect agency-determined essential information; and (ii) at ad hoc locations within the system to track specific types of transactions of interest to the agency d. Protect information obtained from intrusion-monitoring tools from unauthorized access, modification, and deletion e. Heighten the level of information system monitoring activity whenever there is an indication of increased risk to agency operations and assets, individuals, other organizations, or the nation, based on law enforcement information, intelligence information, or other credible sources of information f. Provide information system monitoring information to designated agency officials as needed g. Analyze outbound communications traffic at the external boundary of the information system and selected interior points within the network (e.g., subnetworks, subsystems) to discover anomalies--anomalies within agency information systems include, for example, large file transfers, long-time persistent connections, unusual protocols and ports in use, and attempted communications with suspected malicious external addresses h. Employ automated mechanisms to alert security personnel of inappropriate or unusual activities with security implications (CE11) i. Implement host-based monitoring mechanisms (e.g., Host intrusion prevention system (HIPS)) on information systems that receive, process, store, or transmit FTI (CE23) The information system must: a. Monitor inbound and outbound communications traffic continuously for unusual or unauthorized activities or conditions (CE4) b. Alert designated agency officials when indications of compromise or potential compromise occur--alerts may be generated from a variety of sources, including, for example, audit records or inputs from malicious code protection mechanisms; intrusion detection or prevention mechanisms; or boundary protection devices, such as firewalls, gateways, and routers and alerts can be transmitted, for example, telephonically, by electronic mail messages, or by text messaging; agency personnel on the notification list can include, for example, system administrators, mission/business owners, system owners, or information system security officers (CE5) c. Notify designated agency officials of detected suspicious events and take necessary actions to address suspicious events (CE7) Information system monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at the information system boundary (i.e., part of perimeter defense and boundary protection). Internal monitoring includes the observation of events occurring within the information system. Information system monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Strategic locations for monitoring devices include, for example, selected perimeter locations and nearby server farms supporting critical applications, with such devices typically being employed at the managed interfaces. | link | count: 005 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917) |
Monitoring, SQL | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .3.11 | IRS_1075_9.3.3.11 | IRS 1075 9.3.3.11 | Awareness and Training | Audit Generation (AU-12) | n/a | The information system must: a. Provide audit record generation capability for the auditable events defined in Section 9.3.3.2, Audit Events (AU-2) b. Allow designated agency officials to select which auditable events are to be audited by specific components of the information system c. Generate audit records for the events with the content defined in Section 9.3.3.4, Content of Audit Records (AU-3). | link | count: 007 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917) |
Monitoring, SQL | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .3.3 | IRS_1075_9.3.3.3 | IRS 1075 9.3.3.3 | Awareness and Training | Content of Audit Records (AU-3) | n/a | The information system must: a. Generate audit records containing information that establishes what type of event occurred, when the event occurred, where the event occurred, the source of the event, the outcome of the event, and the identity of any individuals or subjects associated with the event b. Generate audit records containing details to facilitate the reconstruction of events if unauthorized activity or a malfunction occurs or is suspected in the audit records for audit events identified by type, location, or subject (CE1) | link | count: 003 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917) |
Monitoring | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .3.5 | IRS_1075_9.3.3.5 | IRS 1075 9.3.3.5 | Awareness and Training | Response to Audit Processing Failures (AU-5) | n/a | The information system must: a. Alert designated agency officials in the event of an audit processing failure b. Monitor system operational status using operating system or system audit logs and verify functions and performance of the system. Logs shall be able to identify where system process failures have taken place and provide information relative to corrective actions to be taken by the system administrator c. Provide a warning when allocated audit record storage volume reaches a maximum audit record storage capacity (CE1) | link | count: 004 Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
Monitoring, SQL | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .3.6 | IRS_1075_9.3.3.6 | IRS 1075 9.3.3.6 | Awareness and Training | Audit Review, Analysis, and Reporting (AU-6) | n/a | The agency must: a. Review and analyze information system audit records at least weekly or more frequently at the discretion of the information system owner for indications of unusual activity related to potential unauthorized FTI access b. Report findings according to the agency incident response policy. If the finding involves a potential unauthorized disclosure of FTI, the appropriate special agent-in-charge, Treasury Inspector General for Tax Administration (TIGTA), and the IRS Office of Safeguards must be contacted, as described in Section 10.0, Reporting Improper Inspections or Disclosures. The Office of Safeguards recommends agencies identify events that may indicate a potential unauthorized access to FTI. This recommendation is not a requirement at this time, but agencies are encouraged to contact the Office of Safeguards with any questions regarding implementation strategies. Methods of detecting unauthorized access to FTI include matching audit trails to access attempts (successful or unsuccessful) across the following categories: Do Not Access List, Time of Day Access, Name Searches, Previous Accesses, Volume, Zip Code, Restricted TIN It is recommended the agency define a frequency in which the preceding categories are updated for an individual to ensure the information is kept current. | link | count: 003 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917) |
Monitoring | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .5.11 | IRS_1075_9.3.5.11 | IRS 1075 9.3.5.11 | Configuration Management | User-Installed Software (CM-11) | n/a | The agency must: a. Establish policies governing the installation of software by users b. Enforce software installation policies through automated methods c. Monitor policy compliance on a continual basis All FTI that is transmitted to agencies is backed up and protected within IRS facilities. As such, the focus of contingency planning controls is on the protection of FTI stored in backup media or used at alternative facilities and not focused on the availability of data. Agencies must develop applicable contingencies for ensuring that FTI is available, based upon their individual risk-based approaches. | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .5.7 | IRS_1075_9.3.5.7 | IRS 1075 9.3.5.7 | Configuration Management | Least Functionality (CM-7) | n/a | The agency must: a. Configure the information system to provide only essential capabilities b. Prohibit or restrict the use of the functions, ports, protocols, or services as defined in Office of Safeguards-approved compliance requirements (e.g., SCSEMs, assessment tools) c. Review the information system as part of vulnerability assessments to identify unnecessary or non-secure functions, ports, protocols, and services (see Section 9.3.14.3, Vulnerability Scanning (RA-5)) d. Disable defined functions, ports, protocols, and services within the information system deemed to be unnecessary or non-secure | link | count: 001 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc) |
Security Center | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .6.6 | IRS_1075_9.3.6.6 | IRS 1075 9.3.6.6 | Contingency Planning | Alternate Processing Site (CP-7) | n/a | The agency must: a. Establish an alternate processing site, including necessary agreements to permit the transfer and resumption of information system operations, in accordance with the agency's contingency plan when the primary processing capabilities are unavailable b. Ensure that equipment and supplies required to transfer and resume operations are available at the alternate processing site or contracts are in place to support delivery to the site within the agency-defined time period for transfer/resumption c. Ensure that the alternate storage site provides information security safeguards that meet the minimum protection standards and the disclosure provisions of IRC 6103 | link | count: 001 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56) |
Compute | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .7.2 | IRS_1075_9.3.7.2 | IRS 1075 9.3.7.2 | Identification and Authentication | Identification and Authentication (Organizational Users) (IA-2) | n/a | The information system must: a. Uniquely identify and authenticate agency users (or processes acting on behalf of agency users) b. Implement multi-factor authentication for all remote network access to privileged and non-privileged accounts for information systems that receive, process, store, or transmit FTI. (CE1, CE2) c. Implement multi-factor authentication for remote access to privileged and non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access. NIST SP 800-63 allows the use of software tokens. (CE11) | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| IRS_1075_9.3 | .7.5 | IRS_1075_9.3.7.5 | IRS 1075 9.3.7.5 | Identification and Authentication | Authenticator Management (IA-5) | n/a | The agency must manage information system authenticators by: a. Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, or device receiving the authenticator b. Establishing initial authenticator content for authenticators defined by the agency c. Ensuring that authenticators have sufficient strength of mechanism for their intended use d. Establishing and implementing administrative procedures for initial authenticator distribution, for lost/compromised or damaged authenticators, and for revoking authenticators e. Changing default content of authenticators prior to information system installation f. Establishing minimum and maximum lifetime restrictions and reuse conditions for authenticators g. Changing/refreshing authenticators h. Protecting authenticator content from unauthorized disclosure and modification i. Requiring individuals to take, and having devices implement, specific security safeguards to protect authenticators j. Changing authenticators for group/role accounts when membership to those accounts changes The information system must, for password-based authentication: a. Enforce minimum password complexity of: 1. Eight characters 2. At least one numeric and at least one special character 3. A mixture of at least one uppercase and at least one lowercase letter 4. Storing and transmitting only encrypted representations of passwords b. Enforce password minimum lifetime restriction of one day c. Enforce non-privileged account passwords to be changed at least every 90 days d. Enforce privileged account passwords to be changed at least every 60 days e. Prohibit password reuse for 24 generations f. Allow the use of a temporary password for system logon requiring an immediate change to a permanent password g. Password-protect system initialization (boot) settings | link | count: 012 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | IRS1075 September 2016 (105e0327-6175-4eb2-9af4-1fba43bdb39d) | |
| ISO27001-2013 | A.10.1.1 | ISO27001-2013_A.10.1.1 | ISO 27001:2013 A.10.1.1 | Cryptography | Policy on the use of cryptographic controls | Shared | n/a | A policy on the use of cryptographic controls for protection of information shall be developed and implemented. | link | count: 018 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Document and distribute a privacy policy (ee67c031-57fc-53d0-0cca-96c4c04345e8), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Cache, Guest Configuration, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.10.1.2 | ISO27001-2013_A.10.1.2 | ISO 27001:2013 A.10.1.2 | Cryptography | Key Management | Shared | n/a | A policy on the use, protection and lifetime of cryptographic keys shall be developed and implemented through their whole lifecycle. | link | count: 015 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Identify actions allowed without authentication (92a7591f-73b3-1173-a09c-a08882d84c70), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Terminate customer controlled account credentials (76d66b5c-85e4-93f5-96a5-ebb2fad61dc6) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.1.1 | ISO27001-2013_A.11.1.1 | ISO 27001:2013 A.11.1.1 | Physical And Environmental Security | Physical security perimeter | Shared | n/a | Security perimeters shall be defined and used to protect areas that contain either sensitive or critical information and information processing facilities. | link | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.1.2 | ISO27001-2013_A.11.1.2 | ISO 27001:2013 A.11.1.2 | Physical And Environmental Security | Physical entry controls | Shared | n/a | Secure areas shall be protected by appropriate entry controls to ensure that only authorized personnel are allowed access. | link | count: 009 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Designate personnel to supervise unauthorized maintenance activities (7a489c62-242c-5db9-74df-c073056d6fa3), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Maintain list of authorized remote maintenance personnel (4ce91e4e-6dab-3c46-011a-aa14ae1561bf), Manage maintenance personnel (b273f1e3-79e7-13ee-5b5d-dca6c66c3d5d), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.1.3 | ISO27001-2013_A.11.1.3 | ISO 27001:2013 A.11.1.3 | Physical And Environmental Security | Securing offices, rooms and facilities | Shared | n/a | Physical security for offices, rooms and facilities shall be designed and applied. | link | count: 005 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.1.4 | ISO27001-2013_A.11.1.4 | ISO 27001:2013 A.11.1.4 | Physical And Environmental Security | Protecting against external and environmental threats | Shared | n/a | Physical protection against natural disasters, malicious attack or accidents shall be designed and applied. | link | count: 009 Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Ensure information system fails in known state (12af7c7a-92af-9e96-0d0c-5e732d1a3751), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.1.5 | ISO27001-2013_A.11.1.5 | ISO 27001:2013 A.11.1.5 | Physical And Environmental Security | Working in secure areas | Shared | n/a | Procedures for working in secure areas shall be designed and applied. | link | count: 003 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.1.6 | ISO27001-2013_A.11.1.6 | ISO 27001:2013 A.11.1.6 | Physical And Environmental Security | Delivering and loading areas | Shared | n/a | Access points such as delivery and loading areas and other points where unauthorized persons could enter the premises shall be controlled and, if possible, isolated from information processing facilities to avoid unauthorized access. | link | count: 005 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Define requirements for managing assets (25a1f840-65d0-900a-43e4-bee253de04de), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.2.1 | ISO27001-2013_A.11.2.1 | ISO 27001:2013 A.11.2.1 | Physical And Environmental Security | Equipment sitting and protection | Shared | n/a | Equipment shall be sited and protected to reduce the risks from environmental threats and hazards, and opportunities for unauthorized access. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.2.2 | ISO27001-2013_A.11.2.2 | ISO 27001:2013 A.11.2.2 | Physical And Environmental Security | Supporting utilities | Shared | n/a | Equipment shall be protected from power failures and other disruptions caused by failures in supporting utilities. | link | count: 003 Employ automatic emergency lighting (aa892c0d-2c40-200c-0dd8-eac8c4748ede), Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.2.3 | ISO27001-2013_A.11.2.3 | ISO 27001:2013 A.11.2.3 | Physical And Environmental Security | Cabling security | Shared | n/a | Power and telecommunications cabling carrying data or supporting information services shall be protected from interception, interference or damage. | link | count: 004 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.2.4 | ISO27001-2013_A.11.2.4 | ISO 27001:2013 A.11.2.4 | Physical And Environmental Security | Equipment maintenance | Shared | n/a | Equipment shall be correctly maintained to ensure its continued availability and integrity. | link | count: 009 Automate remote maintenance activities (b8587fce-138f-86e8-33a3-c60768bf1da6), Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Produce complete records of remote maintenance activities (74041cfe-3f87-1d17-79ec-34ca5f895542), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide timely maintenance support (eb598832-4bcc-658d-4381-3ecbe17b9866) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.2.5 | ISO27001-2013_A.11.2.5 | ISO 27001:2013 A.11.2.5 | Physical And Environmental Security | Removal of assets | Shared | n/a | Equipment, information or software shall not be taken off-site without prior authorization. | link | count: 006 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Define requirements for managing assets (25a1f840-65d0-900a-43e4-bee253de04de), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.2.6 | ISO27001-2013_A.11.2.6 | ISO 27001:2013 A.11.2.6 | Physical And Environmental Security | Security of equipment and assets off-premises | Shared | n/a | Security shall be applied to off-site assets taking into account the different risks of working outside the organization's premises. | link | count: 010 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Verify security controls for external information systems (dc7ec756-221c-33c8-0afe-c48e10e42321) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.2.7 | ISO27001-2013_A.11.2.7 | ISO 27001:2013 A.11.2.7 | Physical And Environmental Security | Secure disposal or re-use of equipment | Shared | n/a | All items of equipment containing storage media shall be verified to ensure that any sensitive data and licensed software has been removed or securely overwritten prior to disposal or re-use. | link | count: 005 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.2.8 | ISO27001-2013_A.11.2.8 | ISO 27001:2013 A.11.2.8 | Physical And Environmental Security | Unattended user equipment | Shared | n/a | Users shall ensure that unattended equipment has appropriate protection. | link | count: 002 Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.11.2.9 | ISO27001-2013_A.11.2.9 | ISO 27001:2013 A.11.2.9 | Physical And Environmental Security | Clear desk and clear screen policy | Shared | n/a | A clear desk policy for papers and removable storage media and a clear screen policy for information processing facilities shall be adopted. | link | count: 003 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.1.1 | ISO27001-2013_A.12.1.1 | ISO 27001:2013 A.12.1.1 | Operations Security | Documented operating procedures | Shared | n/a | Operating procedures shall be documented and made available to all users who need them. | link | count: 031 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Distribute information system documentation (84a01872-5318-049e-061e-d56734183e84), Document customer-defined actions (8c44a0ea-9b09-4d9c-0e91-f9bee3d05bfb), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Obtain Admin documentation (3f1216b0-30ee-1ac9-3899-63eb744e85f5), Obtain user security function documentation (be1c34ab-295a-07a6-785c-36f63c1d223e), Protect administrator and user documentation (09960521-759e-5d12-086f-4192a72a5e92), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.1.2 | ISO27001-2013_A.12.1.2 | ISO 27001:2013 A.12.1.2 | Operations Security | Change management | Shared | n/a | Changes to organization, business processes, information processing facilities and systems that affect information security shall be controlled. | link | count: 027 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.1.3 | ISO27001-2013_A.12.1.3 | ISO 27001:2013 A.12.1.3 | Operations Security | Capacity management | Shared | n/a | The use of resources shall be monitored, tuned, and projections made of future capacity requirements to ensure the required system performance. | link | count: 002 Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.1.4 | ISO27001-2013_A.12.1.4 | ISO 27001:2013 A.12.1.4 | Operations Security | Separation of development, testing and operational environments | Shared | n/a | Development, testing, and operational environments shall be separated to reduce the risks of unauthorized access or changes to the operational environment. | link | count: 010 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Implement controls to protect PII (cf79f602-1e60-5423-6c0c-e632c2ea1fc0), Incorporate security and data privacy practices in research processing (834b7a4a-83ab-2188-1a26-9c5033d8173b), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.2.1 | ISO27001-2013_A.12.2.1 | ISO 27001:2013 A.12.2.1 | Operations Security | Controls against malware | Shared | n/a | Detection, prevention, and recovery controls to protect against malware shall be implemented, combined with appropriate user awareness. | link | count: 012 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.3.1 | ISO27001-2013_A.12.3.1 | ISO 27001:2013 A.12.3.1 | Operations Security | Information backup | Shared | n/a | Backup copies of information, software and system images shall be taken and tested regularly in accordance with an agreed backup policy. | link | count: 013 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Ensure information system fails in known state (12af7c7a-92af-9e96-0d0c-5e732d1a3751), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement transaction based recovery (ba02d0a0-566a-25dc-73f1-101c726a19c5), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7), Transfer backup information to an alternate storage site (7bdb79ea-16b8-453e-4ca4-ad5b16012414), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.4.1 | ISO27001-2013_A.12.4.1 | ISO 27001:2013 A.12.4.1 | Operations Security | Event Logging | Shared | n/a | Event logs recording user activities, exceptions, faults and information security events shall be produced, kept and regularly reviewed. | link | count: 053 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Dependency agent should be enabled for listed virtual machine images (11ac78e3-31bc-4f0c-8434-37ab963cea07), Dependency agent should be enabled in virtual machine scale sets for listed virtual machine images (e2dd799a-a932-4e9d-ac17-d473bc3c6c10), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Discover any indicators of compromise (07b42fb5-027e-5a3c-4915-9d9ef3020ec7), Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Enforce and audit access restrictions (8cd815bf-97e1-5144-0735-11f6ddb50a59), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Implement methods for consumer requests (b8ec9ebb-5b7f-8426-17c1-2bc3fcd54c6e), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6), Publish access procedures in SORNs (b2c723e8-a1a0-8e38-5cf1-f5a20ffe4f51), Publish rules and regulations accessing Privacy Act records (ad1d562b-a04b-15d3-6770-ed310b601cb5), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review and update the events defined in AU-02 (a930f477-9dcb-2113-8aa7-45bb6fc90861), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review changes for any unauthorized changes (c246d146-82b0-301f-32e7-1065dcd248b7), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Monitoring, Regulatory Compliance, SQL | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.4.2 | ISO27001-2013_A.12.4.2 | ISO 27001:2013 A.12.4.2 | Operations Security | Protection of log information | Shared | n/a | Logging facilities and log information shall be protected against tampering and unauthorized access. | link | count: 008 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Define the duties of processors (52375c01-4d4c-7acc-3aa4-5b3d53a047ec), Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Record disclosures of PII to third parties (8b1da407-5e60-5037-612e-2caa1b590719), Train staff on PII sharing and its consequences (8019d788-713d-90a1-5570-dac5052f517d), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.4.3 | ISO27001-2013_A.12.4.3 | ISO 27001:2013 A.12.4.3 | Operations Security | Administrator and operator logs | Shared | n/a | System administrator and system operator activities shall be logged and the logs protected and regularly reviewed. | link | count: 029 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Dependency agent should be enabled for listed virtual machine images (11ac78e3-31bc-4f0c-8434-37ab963cea07), Dependency agent should be enabled in virtual machine scale sets for listed virtual machine images (e2dd799a-a932-4e9d-ac17-d473bc3c6c10), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Monitoring, Regulatory Compliance, SQL | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.4.4 | ISO27001-2013_A.12.4.4 | ISO 27001:2013 A.12.4.4 | Operations Security | Clock Synchronization | Shared | n/a | The clocks of all relevant information processing systems within an organization or security domain shall be synchronized to a single reference time source. | link | count: 008 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Compile Audit records into system wide audit (214ea241-010d-8926-44cc-b90a96d52adc), Dependency agent should be enabled for listed virtual machine images (11ac78e3-31bc-4f0c-8434-37ab963cea07), Dependency agent should be enabled in virtual machine scale sets for listed virtual machine images (e2dd799a-a932-4e9d-ac17-d473bc3c6c10), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Monitoring, Regulatory Compliance, SQL | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.5.1 | ISO27001-2013_A.12.5.1 | ISO 27001:2013 A.12.5.1 | Operations Security | Installation of software on operational systems | Shared | n/a | Procedures shall be implemented to control the installation of software on operational systems. | link | count: 019 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance, Security Center | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.6.1 | ISO27001-2013_A.12.6.1 | ISO 27001:2013 A.12.6.1 | Operations Security | Management of technical vulnerabilities | Shared | n/a | Information about technical vulnerabilities of information systems being used shall be obtained in a timely fashion, the organization's exposure to such vulnerabilities evaluated and appropriate measures taken to address the associated risk. | link | count: 013 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Regulatory Compliance, Security Center | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.6.2 | ISO27001-2013_A.12.6.2 | ISO 27001:2013 A.12.6.2 | Operations Security | Restrictions on software installation | Shared | n/a | Rules governing the installation of software by users shall be established and implemented. | link | count: 019 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance, Security Center | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.12.7.1 | ISO27001-2013_A.12.7.1 | ISO 27001:2013 A.12.7.1 | Operations Security | Information systems audit controls | Shared | n/a | Audit requirements and activities involving verification of operational systems shall be carefully planned and agreed to minimize disruptions to business processes. | link | count: 001 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.13.1.1 | ISO27001-2013_A.13.1.1 | ISO 27001:2013 A.13.1.1 | Communications Security | Network controls | Shared | n/a | Networks shall be managed and controlled to protect information in systems and applications. | link | count: 040 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933), Reauthenticate or terminate a user session (d6653f89-7cb5-24a4-9d71-51581038231b), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59), Verify security controls for external information systems (dc7ec756-221c-33c8-0afe-c48e10e42321) |
Regulatory Compliance, Security Center, Storage | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.13.1.2 | ISO27001-2013_A.13.1.2 | ISO 27001:2013 A.13.1.2 | Communications Security | Security of network services | Shared | n/a | Security mechanisms, service levels and management requirements of all network services shall be identified and included in network services agreements, whether these services are provided in-house or outsourced. | link | count: 016 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Establish electronic signature and certificate requirements (6f3866e8-6e12-69cf-788c-809d426094a1), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.13.1.3 | ISO27001-2013_A.13.1.3 | ISO 27001:2013 A.13.1.3 | Communications Security | Segregation of networks | Shared | n/a | Groups of information services, users, and information systems shall be segregated on networks. | link | count: 017 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd), Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.13.2.1 | ISO27001-2013_A.13.2.1 | ISO 27001:2013 A.13.2.1 | Communications Security | Information transfer policies and procedures | Shared | n/a | Formal transfer policies, procedures and controls shall be in place to protect the transfer of information through the use of all types of communication facilities. | link | count: 032 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35), Explicitly notify use of collaborative computing devices (62fa14f0-4cbe-762d-5469-0899a99b98aa), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Prohibit remote activation of collaborative computing devices (678ca228-042d-6d8e-a598-c58d5670437d), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50), Verify security controls for external information systems (dc7ec756-221c-33c8-0afe-c48e10e42321) |
Cache, Regulatory Compliance, Storage | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.13.2.2 | ISO27001-2013_A.13.2.2 | ISO 27001:2013 A.13.2.2 | Communications Security | Agreements on information transfer | Shared | n/a | Agreements shall address the secure transfer of business information between the organization and external parties. | link | count: 011 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.13.2.3 | ISO27001-2013_A.13.2.3 | ISO 27001:2013 A.13.2.3 | Communications Security | Electronic messaging | Shared | n/a | Information involved in electronic messaging shall be appropriately protected. | link | count: 010 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.13.2.4 | ISO27001-2013_A.13.2.4 | ISO 27001:2013 A.13.2.4 | Communications Security | Confidentiality or non-disclosure agreements | Shared | n/a | Requirements for confidentiality or non-disclosure agreements reflecting the organization's needs for the protection of information shall be identified, regularly reviewed and documented. | link | count: 014 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Document organizational access agreements (c981fa70-2e58-8141-1457-e7f62ebc2ade), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Ensure access agreements are signed or resigned timely (e7589f4e-1e8b-72c2-3692-1e14d7f3699f), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Require users to sign access agreement (3af53f59-979f-24a8-540f-d7cdbc366607), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update organizational access agreements (e21f91d1-2803-0282-5f2d-26ebc4b170ef), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.1.1 | ISO27001-2013_A.14.1.1 | ISO 27001:2013 A.14.1.1 | System Acquisition, Development And Maintenance | Information security requirements analysis and specification | Shared | n/a | The information security related requirements shall be included in the requirements for new information systems or enhancements to existing information systems. | link | count: 024 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8), Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.1.2 | ISO27001-2013_A.14.1.2 | ISO 27001:2013 A.14.1.2 | System Acquisition, Development And Maintenance | Securing application services on public networks | Shared | n/a | Information involved in application services passing over public networks shall be protected from fraudulent activity, contract dispute and unauthorized disclosure and modification. | link | count: 032 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.1.3 | ISO27001-2013_A.14.1.3 | ISO 27001:2013 A.14.1.3 | System Acquisition, Development And Maintenance | Protecting application services transactions | Shared | n/a | Information involved in application service transactions shall be protected to prevent incomplete transmission, mis-routing, unauthorized message alteration, unauthorized disclosure, unauthorized message duplication or replay. | link | count: 029 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd), Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.2.1 | ISO27001-2013_A.14.2.1 | ISO 27001:2013 A.14.2.1 | System Acquisition, Development And Maintenance | Secure development policy | Shared | n/a | Rules for the development of software and systems shall be established and applied to developments within the organization. | link | count: 007 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), Require developers to build security architecture (f131c8c5-a54a-4888-1efc-158928924bc1), Require developers to describe accurate security functionality (3e37c891-840c-3eb4-78d2-e2e0bb5063e0), Require developers to provide unified security protection approach (7a114735-a420-057d-a651-9a73cd0416ef), Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.2.2 | ISO27001-2013_A.14.2.2 | ISO 27001:2013 A.14.2.2 | System Acquisition, Development And Maintenance | System change control procedures | Shared | n/a | Changes to systems within the development lifecycle shall be controlled by the use of formal change control procedures. | link | count: 025 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.2.3 | ISO27001-2013_A.14.2.3 | ISO 27001:2013 A.14.2.3 | System Acquisition, Development And Maintenance | Technical review of applications after operating platform changes | Shared | n/a | When operating platforms are changed, business critical applications shall be reviewed and tested to ensure there is no adverse impact on organizational operations or security. | link | count: 018 Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.2.4 | ISO27001-2013_A.14.2.4 | ISO 27001:2013 A.14.2.4 | System Acquisition, Development And Maintenance | Restrictions on changes to software packages | Shared | n/a | Modifications to software packages shall be discouraged, limited to necessary changes and all changes shall be strictly controlled. | link | count: 024 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.2.5 | ISO27001-2013_A.14.2.5 | ISO 27001:2013 A.14.2.5 | System Acquisition, Development And Maintenance | Secure system engineering principles | Shared | n/a | Principles for engineering secure systems shall be established, documented, maintained and applied to any information system implementation efforts. | link | count: 005 Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e), Require developers to build security architecture (f131c8c5-a54a-4888-1efc-158928924bc1), Require developers to describe accurate security functionality (3e37c891-840c-3eb4-78d2-e2e0bb5063e0), Require developers to provide unified security protection approach (7a114735-a420-057d-a651-9a73cd0416ef), Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.2.6 | ISO27001-2013_A.14.2.6 | ISO 27001:2013 A.14.2.6 | System Acquisition, Development And Maintenance | Secure development environment | Shared | n/a | Organizations shall establish and appropriately protect secure development environments for system development and integration efforts that cover the entire system development lifecycle. | link | count: 010 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.2.7 | ISO27001-2013_A.14.2.7 | ISO 27001:2013 A.14.2.7 | System Acquisition, Development And Maintenance | Outsourced development | Shared | n/a | The organization shall supervise and monitor the activity of outsourced system development. | link | count: 028 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.2.8 | ISO27001-2013_A.14.2.8 | ISO 27001:2013 A.14.2.8 | System Acquisition, Development And Maintenance | System security testing | Shared | n/a | Testing of security functionality shall be carried out during development. | link | count: 008 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.2.9 | ISO27001-2013_A.14.2.9 | ISO 27001:2013 A.14.2.9 | System Acquisition, Development And Maintenance | System acceptance testing | Shared | n/a | Acceptance testing programs and related criteria shall be established for new information systems, upgrades and new versions. | link | count: 014 Assign an authorizing official (AO) (e29a8f1b-149b-2fa3-969d-ebee1baa9472), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Ensure resources are authorized (0716f0f5-4955-2ccb-8d5e-c6be14d57c0f), Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.14.3.1 | ISO27001-2013_A.14.3.1 | ISO 27001:2013 A.14.3.1 | System Acquisition, Development And Maintenance | Protection of test data | Shared | n/a | Test data shall be selected carefully, protected and controlled. | link | count: 011 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.15.1.1 | ISO27001-2013_A.15.1.1 | ISO 27001:2013 A.15.1.1 | Supplier Relationships | Information security policy for supplier relationships | Shared | n/a | Information security requirements for mitigating the risks associated with supplier's access to the organization's assets shall be agreed with the supplier and documented. | link | count: 006 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.15.1.2 | ISO27001-2013_A.15.1.2 | ISO 27001:2013 A.15.1.2 | Supplier Relationships | Addressing security within supplier agreement | Shared | n/a | All relevant information security requirements shall be established and agreed with each supplier that may access, process, store, communicate, or provide IT infrastructure components for, the organization's information. | link | count: 024 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.15.1.3 | ISO27001-2013_A.15.1.3 | ISO 27001:2013 A.15.1.3 | Supplier Relationships | Information and communication technology supply chain | Shared | n/a | Agreements with suppliers shall include requirements to address the information security risks associated with information and communications technology services and product supply chain. | link | count: 004 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.15.2.1 | ISO27001-2013_A.15.2.1 | ISO 27001:2013 A.15.2.1 | Supplier Relationships | Monitoring and review of supplier services | Shared | n/a | Organizations shall be regularly monitor, review and audit supplier service delivery. | link | count: 004 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.15.2.2 | ISO27001-2013_A.15.2.2 | ISO 27001:2013 A.15.2.2 | Supplier Relationships | Managing changes to supplier services | Shared | n/a | Changes to the provision of services by suppliers, including maintaining and improving existing information security policies, procedures and controls, shall be managed, taking account of the criticality of business information, systems and processes involved and re-assessment of risks. | link | count: 015 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.16.1.1 | ISO27001-2013_A.16.1.1 | ISO 27001:2013 A.16.1.1 | Information Security Incident Management | Responsibilities and procedures | Shared | n/a | Management responsibilities and procedures shall be established to ensure a quick, effective and orderly response to information security incidents. | link | count: 007 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.16.1.2 | ISO27001-2013_A.16.1.2 | ISO 27001:2013 A.16.1.2 | Information Security Incident Management | Reporting information security events | Shared | n/a | Information security events shall be reported through appropriate management channels as quickly as possible. | link | count: 014 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.16.1.3 | ISO27001-2013_A.16.1.3 | ISO 27001:2013 A.16.1.3 | Information Security Incident Management | Reporting information security weaknesses | Shared | n/a | Employees and contractors using the organization's information systems and services shall be required to note and report any observed or suspected information security weaknesses in systems or services. | link | count: 004 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.16.1.4 | ISO27001-2013_A.16.1.4 | ISO 27001:2013 A.16.1.4 | Information Security Incident Management | Assessment of and decision on information security events | Shared | n/a | Information security events shall be assessed and it shall be decided if they are to be classified as information security incidents. | link | count: 023 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.16.1.5 | ISO27001-2013_A.16.1.5 | ISO 27001:2013 A.16.1.5 | Information Security Incident Management | Response to information security incidents | Shared | n/a | Information security incidents shall be responded to in accordance with the documented procedures. | link | count: 012 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.16.1.6 | ISO27001-2013_A.16.1.6 | ISO 27001:2013 A.16.1.6 | Information Security Incident Management | Learning from information security incidents | Shared | n/a | Knowledge gained from analyzing and resolving information security incidents shall be used to reduce the likelihood or impact of future incidents. | link | count: 013 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Discover any indicators of compromise (07b42fb5-027e-5a3c-4915-9d9ef3020ec7), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.16.1.7 | ISO27001-2013_A.16.1.7 | ISO 27001:2013 A.16.1.7 | Information Security Incident Management | Collection of evidence | Shared | n/a | The organization shall define and apply procedures for the identification, collection, acquisition and preservation of information which can serve as evidence. | link | count: 007 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.17.1.1 | ISO27001-2013_A.17.1.1 | ISO 27001:2013 A.17.1.1 | Information Security Aspects Of Business Continuity Management | Planning information security continuity | Shared | n/a | The organization shall determine its requirements for information security and the continuity of information security management in adverse situations, e.g. during a crisis or disaster. | link | count: 011 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928), Resume all mission and business functions (91a54089-2d69-0f56-62dc-b6371a1671c0), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review contingency plan (53fc1282-0ee3-2764-1319-e20143bb0ea5), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.17.1.2 | ISO27001-2013_A.17.1.2 | ISO 27001:2013 A.17.1.2 | Information Security Aspects Of Business Continuity Management | Implementing information security continuity | Shared | n/a | The organization shall establish, document, implement and maintain processes, procedures and controls to ensure the required level of continuity for information security during an adverse situation. | link | count: 018 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Ensure information system fails in known state (12af7c7a-92af-9e96-0d0c-5e732d1a3751), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf), Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement transaction based recovery (ba02d0a0-566a-25dc-73f1-101c726a19c5), Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928), Recover and reconstitute resources after any disruption (f33c3238-11d2-508c-877c-4262ec1132e1), Resume all mission and business functions (91a54089-2d69-0f56-62dc-b6371a1671c0) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.17.1.3 | ISO27001-2013_A.17.1.3 | ISO 27001:2013 A.17.1.3 | Information Security Aspects Of Business Continuity Management | Verify, review and evaluate information security continuity | Shared | n/a | The organization shall verify the established and implemented information security continuity controls at regular intervals in order to ensure that they are valid and effective during adverse situations. | link | count: 003 Initiate contingency plan testing corrective actions (8bfdbaa6-6824-3fec-9b06-7961bf7389a6), Review the results of contingency plan testing (5d3abfea-a130-1208-29c0-e57de80aa6b0), Test the business continuity and disaster recovery plan (58a51cde-008b-1a5d-61b5-d95849770677) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.17.2.1 | ISO27001-2013_A.17.2.1 | ISO 27001:2013 A.17.2.1 | Information Security Aspects Of Business Continuity Management | Availability of information processing facilities | Shared | n/a | Information processing facilities shall be implemented with redundancy sufficient to meet availability requirements. | link | count: 017 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82), Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Ensure information system fails in known state (12af7c7a-92af-9e96-0d0c-5e732d1a3751), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722), Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928), Resume all mission and business functions (91a54089-2d69-0f56-62dc-b6371a1671c0), Review contingency plan (53fc1282-0ee3-2764-1319-e20143bb0ea5), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.18.1.1 | ISO27001-2013_A.18.1.1 | ISO 27001:2013 A.18.1.1 | Compliance | Identification applicable legislation and contractual requirements | Shared | n/a | All relevant legislative statutory, regulatory, contractual requirements and the organization's approach to meet these requirements shall be explicitly identified, documented and kept up to date for each information system and the organization. | link | count: 030 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Protect the information security program plan (2e7a98c9-219f-0d58-38dc-d69038224442), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.18.1.2 | ISO27001-2013_A.18.1.2 | ISO 27001:2013 A.18.1.2 | Compliance | Intellectual property rights | Shared | n/a | Appropriate procedures shall be implemented to ensure compliance with legislative, regulatory, and contractual requirements related to intellectual property rights and use of proprietary software products. | link | count: 002 Require compliance with intellectual property rights (725164e5-3b21-1ec2-7e42-14f077862841), Track software license usage (77cc89bb-774f-48d7-8a84-fb8c322c3000) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.18.1.3 | ISO27001-2013_A.18.1.3 | ISO 27001:2013 A.18.1.3 | Compliance | Protection of records | Shared | n/a | Records shall be protected from loss, destruction, falsification, unauthorized access and unauthorized release, in accordance with legislative, regulatory, contractual and business requirements. | link | count: 015 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Ensure information system fails in known state (12af7c7a-92af-9e96-0d0c-5e732d1a3751), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement transaction based recovery (ba02d0a0-566a-25dc-73f1-101c726a19c5), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.18.1.4 | ISO27001-2013_A.18.1.4 | ISO 27001:2013 A.18.1.4 | Compliance | Privacy and protection of personally identifiable information | Shared | n/a | Privacy and protection of personally identifiable information shall be ensured as required in relevant legislation and regulation where applicable. | link | count: 006 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Manage compliance activities (4e400494-53a5-5147-6f4d-718b539c7394), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.18.1.5 | ISO27001-2013_A.18.1.5 | ISO 27001:2013 A.18.1.5 | Compliance | Regulation of cryptographic controls | Shared | n/a | Cryptographic controls shall be used in compliance with all relevant agreements, legislation and regulations. | link | count: 002 Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.18.2.1 | ISO27001-2013_A.18.2.1 | ISO 27001:2013 A.18.2.1 | Compliance | Independent review of information security | Shared | n/a | The organization's approach to managing information security and its implementation (i.e. control objectives, controls, policies, processes, and procedures for information security) shall be reviewed independently at planned intervals, or when significant changes occur. | link | count: 002 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.18.2.2 | ISO27001-2013_A.18.2.2 | ISO 27001:2013 A.18.2.2 | Compliance | Compliance with security policies and standards | Shared | n/a | Managers shall regularly review the compliance of information processing and procedures within their area of responsibility with the appropriate security policies, standards and any other security requirements. | link | count: 036 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), Protect the information security program plan (2e7a98c9-219f-0d58-38dc-d69038224442), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.18.2.3 | ISO27001-2013_A.18.2.3 | ISO 27001:2013 A.18.2.3 | Compliance | Technical compliance review | Shared | n/a | Information systems shall be regularly reviewed for compliance with the organization's information security policies and standards. | link | count: 005 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.5.1.1 | ISO27001-2013_A.5.1.1 | ISO 27001:2013 A.5.1.1 | Information Security Policies | Policies for information security | Shared | n/a | A set of policies for information security shall be defined, approved by management, published and communicated to employees and relevant external parties. | link | count: 042 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish privacy requirements for contractors and service providers (f8d141b7-4e21-62a6-6608-c79336e36bc9), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Manage compliance activities (4e400494-53a5-5147-6f4d-718b539c7394), Protect the information security program plan (2e7a98c9-219f-0d58-38dc-d69038224442), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.5.1.2 | ISO27001-2013_A.5.1.2 | ISO 27001:2013 A.5.1.2 | Information Security Policies | Review of the policies for information security | Shared | n/a | The policies for information security shall be reviewed at planned intervals or if significant changes occur to ensure their continuing suitability, adequacy, and effectiveness. | link | count: 029 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Protect the information security program plan (2e7a98c9-219f-0d58-38dc-d69038224442), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.6.1.1 | ISO27001-2013_A.6.1.1 | ISO 27001:2013 A.6.1.1 | Organization of Information Security | Information security roles and responsibilities | Shared | n/a | All information security responsibilities shall be clearly defined and allocated. | link | count: 073 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Create configuration plan protection (874a6f2e-2098-53bc-3a16-20dcdc425a7e), Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Designate individuals to fulfill specific roles and responsibilities (8b077bff-516f-3983-6c42-c86e9a11868b), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document and implement privacy complaint procedures (eab4450d-9e5c-4f38-0656-2ff8c78c83f3), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Ensure privacy program information is publicly available (1beb1269-62ee-32cd-21ad-43d6c9750eb6), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), Manage security state of information systems (6baae474-434f-2e91-7163-a72df30c4847), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928), Protect the information security program plan (2e7a98c9-219f-0d58-38dc-d69038224442), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6), Resume all mission and business functions (91a54089-2d69-0f56-62dc-b6371a1671c0), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Review contingency plan (53fc1282-0ee3-2764-1319-e20143bb0ea5), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.6.1.2 | ISO27001-2013_A.6.1.2 | ISO 27001:2013 A.6.1.2 | Organization of Information Security | Segregation of Duties | Shared | n/a | Conflicting duties and areas of responsibility shall be segregated to reduce opportunities for unauthorized or unintentional modification or misuse of the organization's assets. | link | count: 005 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Regulatory Compliance, Security Center | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.6.1.3 | ISO27001-2013_A.6.1.3 | ISO 27001:2013 A.6.1.3 | Organization of Information Security | Contact with authorities | Shared | n/a | Appropriate contacts with relevant authorities shall be maintained. | link | count: 002 Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Manage contacts for authorities and special interest groups (5269d7e4-3768-501d-7e46-66c56c15622c) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.6.1.4 | ISO27001-2013_A.6.1.4 | ISO 27001:2013 A.6.1.4 | Organization of Information Security | Contact with special interest groups | Shared | n/a | Appropriate contacts with special interest groups or other specialist security forums and professional associations shall be maintained. | link | count: 006 Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Generate internal security alerts (171e377b-5224-4a97-1eaa-62a3b5231dac), Implement security directives (26d178a4-9261-6f04-a100-47ed85314c6e), Manage contacts for authorities and special interest groups (5269d7e4-3768-501d-7e46-66c56c15622c) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.6.1.5 | ISO27001-2013_A.6.1.5 | ISO 27001:2013 A.6.1.5 | Organization of Information Security | Information security in project management | Shared | n/a | Information security shall be addressed in project management, regardless of the type of the project. | link | count: 025 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Allocate resources in determining information system requirements (90a156a6-49ed-18d1-1052-69aac27c05cd), Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Establish a discrete line item in budgeting documentation (06af77de-02ca-0f3e-838a-a9420fe466f5), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.6.2.1 | ISO27001-2013_A.6.2.1 | ISO 27001:2013 A.6.2.1 | Organization of Information Security | Mobile device policy | Shared | n/a | A policy and supporting security measures shall be adopted to manage the risks introduced by using mobile devices. | link | count: 013 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.6.2.2 | ISO27001-2013_A.6.2.2 | ISO 27001:2013 A.6.2.2 | Organization of Information Security | Teleworking | Shared | n/a | A policy and supporting security measures shall be implemented to protect information accessed, processed or stored at teleworking sites. | link | count: 016 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.7.1.1 | ISO27001-2013_A.7.1.1 | ISO 27001:2013 A.7.1.1 | Human Resources Security | Screening | Shared | n/a | Background verification checks for all candidates for employment shall be carried out in accordance with relevant laws, regulations and ethics and shall be proportional to the business requirements, the classification of the information to be accessed and the perceived risks. | link | count: 003 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Rescreen individuals at a defined frequency (c6aeb800-0b19-944d-92dc-59b893722329) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.7.1.2 | ISO27001-2013_A.7.1.2 | ISO 27001:2013 A.7.1.2 | Human Resources Security | Terms and conditions of employment | Shared | n/a | The contractual agreements with employees and contractors shall state their and the organization's responsibilities for information security. | link | count: 024 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document organizational access agreements (c981fa70-2e58-8141-1457-e7f62ebc2ade), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Ensure access agreements are signed or resigned timely (e7589f4e-1e8b-72c2-3692-1e14d7f3699f), Ensure privacy program information is publicly available (1beb1269-62ee-32cd-21ad-43d6c9750eb6), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Require users to sign access agreement (3af53f59-979f-24a8-540f-d7cdbc366607), Update organizational access agreements (e21f91d1-2803-0282-5f2d-26ebc4b170ef) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.7.2.1 | ISO27001-2013_A.7.2.1 | ISO 27001:2013 A.7.2.1 | Human Resources Security | Management responsibilities | Shared | n/a | Management shall require all employees and contractors to apply information security in accordance with the established policies and procedures of the organization. | link | count: 026 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document organizational access agreements (c981fa70-2e58-8141-1457-e7f62ebc2ade), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Ensure access agreements are signed or resigned timely (e7589f4e-1e8b-72c2-3692-1e14d7f3699f), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6), Require users to sign access agreement (3af53f59-979f-24a8-540f-d7cdbc366607), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Update organizational access agreements (e21f91d1-2803-0282-5f2d-26ebc4b170ef) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.7.2.2 | ISO27001-2013_A.7.2.2 | ISO 27001:2013 A.7.2.2 | Human Resources Security | Information security awareness, education and training | Shared | n/a | All employees of the organization and, where relevant, contractors shall receive appropriate awareness training and regular updates in organizational policies and procedures, as relevant for their job function. | link | count: 015 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Employ automated training environment (c8aa992d-76b7-7ca0-07b3-31a58d773fa9), Establish information security workforce development and improvement program (b544f797-a73b-1be3-6d01-6b1a085376bc), Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a), Provide contingency training (de936662-13dc-204c-75ec-1af80f994088), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169), Retain training records (3153d9c0-2584-14d3-362d-578b01358aeb), Train personnel on disclosure of nonpublic information (97f0d974-1486-01e2-2088-b888f46c0589) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.7.2.3 | ISO27001-2013_A.7.2.3 | ISO 27001:2013 A.7.2.3 | Human Resources Security | Disciplinary process | Shared | n/a | There shall be a formal and communicated disciplinary process in place to take action against employees who have committed an information security breach. | link | count: 002 Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.7.3.1 | ISO27001-2013_A.7.3.1 | ISO 27001:2013 A.7.3.1 | Human Resources Security | Termination or change of employment responsibilities | Shared | n/a | Information security responsibilities and duties that remain valid after termination or change of employment shall be defined, communicated to the employee or contractor and enforced. | link | count: 008 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.1.1 | ISO27001-2013_A.8.1.1 | ISO 27001:2013 A.8.1.1 | Asset Management | Inventory of assets | Shared | n/a | Assets associated with information and information processing facilities shall be identified and an inventory of these assets shall be drawn up and maintained. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.1.2 | ISO27001-2013_A.8.1.2 | ISO 27001:2013 A.8.1.2 | Asset Management | Ownership of assets | Shared | n/a | Assets maintained in the inventory shall be owned. | link | count: 007 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.1.3 | ISO27001-2013_A.8.1.3 | ISO 27001:2013 A.8.1.3 | Asset Management | Acceptable use of assets | Shared | n/a | Rules for the acceptable use of information and of assets associated with information processing facilities shall be identified, documented and implemented | link | count: 002 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.1.4 | ISO27001-2013_A.8.1.4 | ISO 27001:2013 A.8.1.4 | Asset Management | Return of assets | Shared | n/a | All employees and external party users shall return all of the organizational assets in their possession upon termination of their employment, contract or agreement. | link | count: 008 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.2.1 | ISO27001-2013_A.8.2.1 | ISO 27001:2013 A.8.2.1 | Asset Management | Classification of information | Shared | n/a | Information shall be classified in terms of legal requirements, value, criticality and sensitivity to unauthorized disclosure or modification. | link | count: 005 Categorize information (93fa357f-2e38-22a9-5138-8cc5124e1923), Develop business classification schemes (11ba0508-58a8-44de-5f3a-9e05d80571da), Ensure security categorization is approved (6c79c3e5-5f7b-a48a-5c7b-8c158bc01115), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc) |
Regulatory Compliance, Security Center | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.2.2 | ISO27001-2013_A.8.2.2 | ISO 27001:2013 A.8.2.2 | Asset Management | Labelling of information | Shared | n/a | An appropriate set of procedures for information labeling shall be developed and implemented in accordance with the information classification scheme adopted by the organization. | link | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.2.3 | ISO27001-2013_A.8.2.3 | ISO 27001:2013 A.8.2.3 | Asset Management | Handling of assets | Shared | n/a | Procedures for handling assets shall be developed and implemented in accordance with the information classification scheme adopted by the organization. | link | count: 026 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Define requirements for managing assets (25a1f840-65d0-900a-43e4-bee253de04de), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.3.1 | ISO27001-2013_A.8.3.1 | ISO 27001:2013 A.8.3.1 | Asset Management | Management of removable media | Shared | n/a | Procedures shall be implemented for the management of removable media in accordance with the classification scheme adopted by the organization. | link | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.3.2 | ISO27001-2013_A.8.3.2 | ISO 27001:2013 A.8.3.2 | Asset Management | Disposal of media | Shared | n/a | Media shall be disposed of securely and safely when no longer required, using formal procedures. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.8.3.3 | ISO27001-2013_A.8.3.3 | ISO 27001:2013 A.8.3.3 | Asset Management | Physical media transfer | Shared | n/a | Media containing information shall be protected against unauthorized access, misuse or corruption during transportation. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.1.1 | ISO27001-2013_A.9.1.1 | ISO 27001:2013 A.9.1.1 | Access Control | Access control policy | Shared | n/a | An access control policy shall be established, documented, and reviewed based on business and information security requirements. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.1.2 | ISO27001-2013_A.9.1.2 | ISO 27001:2013 A.9.1.2 | Access Control | Access to networks and network services | Shared | n/a | Users shall only be provided with access to the network and network services that they have been specifically authorized to use. | link | count: 029 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Establish electronic signature and certificate requirements (6f3866e8-6e12-69cf-788c-809d426094a1), Identify actions allowed without authentication (92a7591f-73b3-1173-a09c-a08882d84c70), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Guest Configuration, Regulatory Compliance, Storage | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.2.1 | ISO27001-2013_A.9.2.1 | ISO 27001:2013 A.9.2.1 | Access Control | User registration and de-registration | Shared | n/a | A formal user registration and de-registration process shall be implemented to enable assignment of access rights. | link | count: 027 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Identify actions allowed without authentication (92a7591f-73b3-1173-a09c-a08882d84c70), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Prevent identifier reuse for the defined time period (4781e5fd-76b8-7d34-6df3-a0a7fca47665), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.2.2 | ISO27001-2013_A.9.2.2 | ISO 27001:2013 A.9.2.2 | Access Control | User access provisioning | Shared | n/a | A formal user access provisioning process shall be implemented to assign or revoke access rights for all user types to all systems and services. | link | count: 019 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32), Review user accounts (79f081c7-1634-01a1-708e-376197999289) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.2.3 | ISO27001-2013_A.9.2.3 | ISO 27001:2013 A.9.2.3 | Access Control | Management of privileged access rights | Shared | n/a | The allocation and use of privileged access rights shall be restricted and controlled. | link | count: 033 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
General, Regulatory Compliance, Security Center, Service Fabric, SQL | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.2.4 | ISO27001-2013_A.9.2.4 | ISO 27001:2013 A.9.2.4 | Access Control | Management of secret authentication information of users | Shared | n/a | The allocation of secret authentication information shall be controlled through a formal management process. | link | count: 021 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Guest Configuration, Regulatory Compliance, Security Center | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.2.5 | ISO27001-2013_A.9.2.5 | ISO 27001:2013 A.9.2.5 | Access Control | Review of user access rights | Shared | n/a | Asset owners shall review users' access rights at regular intervals. | link | count: 017 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
Regulatory Compliance, Security Center | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.2.6 | ISO27001-2013_A.9.2.6 | ISO 27001:2013 A.9.2.6 | Access Control | Removal or adjustment of access rights | Shared | n/a | The access rights of all employees and external party users to information and information processing facilities shall be removed upon termination of their employment, contract or agreement, or adjusted upon change. | link | count: 017 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32), Review user accounts (79f081c7-1634-01a1-708e-376197999289) |
Regulatory Compliance, Security Center | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.3.1 | ISO27001-2013_A.9.3.1 | ISO 27001:2013 A.9.3.1 | Access Control | Use of secret authentication information | Shared | n/a | Users shall be required to follow the organization's practices in the use of secret authentication information. | link | count: 015 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Terminate customer controlled account credentials (76d66b5c-85e4-93f5-96a5-ebb2fad61dc6), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.4.1 | ISO27001-2013_A.9.4.1 | ISO 27001:2013 A.9.4.1 | Access Control | Information access restriction | Shared | n/a | Access to information and application system functions shall be restricted in accordance with the access control policy. | link | count: 011 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.4.2 | ISO27001-2013_A.9.4.2 | ISO 27001:2013 A.9.4.2 | Access Control | Secure log-on procedures | Shared | n/a | Where required by the access control policy, access to systems and applications shall be controlled by a secure log-on procedure. | link | count: 017 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Enforce a limit of consecutive failed login attempts (b4409bff-2287-8407-05fd-c73175a68302), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Establish electronic signature and certificate requirements (6f3866e8-6e12-69cf-788c-809d426094a1), Generate error messages (c2cb4658-44dc-9d11-3dad-7c6802dd5ba3), Identify actions allowed without authentication (92a7591f-73b3-1173-a09c-a08882d84c70), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136), Obscure feedback information during authentication process (1ff03f2a-974b-3272-34f2-f6cd51420b30), Reveal error messages (20762f1e-85fb-31b0-a600-e833633f10fe), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a), Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance, Security Center | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.4.3 | ISO27001-2013_A.9.4.3 | ISO 27001:2013 A.9.4.3 | Access Control | Password management system | Shared | n/a | Password management systems shall be interactive and shall ensure quality password. | link | count: 022 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Guest Configuration, Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.4.4 | ISO27001-2013_A.9.4.4 | ISO 27001:2013 A.9.4.4 | Access Control | Use of privileged utility programs | Shared | n/a | The use of utility programs that might be capable of overriding system and application controls shall be restricted and tightly controlled. | link | count: 009 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | A.9.4.5 | ISO27001-2013_A.9.4.5 | ISO 27001:2013 A.9.4.5 | Access Control | Access control to program source code | Shared | n/a | Access to program source code shall be restricted. | link | count: 010 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.10.1.d | ISO27001-2013_C.10.1.d | ISO 27001:2013 C.10.1.d | Improvement | Nonconformity and corrective action | Shared | n/a | When a nonconformity occurs, the organization shall: d) review the effectiveness of any corrective action taken. | link | count: 001 Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.10.1.e | ISO27001-2013_C.10.1.e | ISO 27001:2013 C.10.1.e | Improvement | Nonconformity and corrective action | Shared | n/a | When a nonconformity occurs, the organization shall: e) make changes to the information security management system, if necessary. | link | count: 001 Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.10.1.f | ISO27001-2013_C.10.1.f | ISO 27001:2013 C.10.1.f | Improvement | Nonconformity and corrective action | Shared | n/a | Corrective actions shall be appropriate to the effects of the nonconformities encountered. The organization shall retain documented information as evidence of: f) the nature of the nonconformities and any subsequent actions taken. | link | count: 003 Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.10.1.g | ISO27001-2013_C.10.1.g | ISO 27001:2013 C.10.1.g | Improvement | Nonconformity and corrective action | Shared | n/a | Corrective actions shall be appropriate to the effects of the nonconformities encountered. The organization shall retain documented information as evidence of: g) the results of any corrective action. | link | count: 003 Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.4.3.a | ISO27001-2013_C.4.3.a | ISO 27001:2013 C.4.3.a | Context of the organization | Determining the scope of the information security management system | Shared | n/a | The organization shall determine the boundaries and applicability of the information security management system to establish its scope. When determining this scope, the organization shall consider: a) the external and internal issues referred to in 4.1; The scope shall be available as documented information. | link | count: 003 Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.4.3.b | ISO27001-2013_C.4.3.b | ISO 27001:2013 C.4.3.b | Context of the organization | Determining the scope of the information security management system | Shared | n/a | The organization shall determine the boundaries and applicability of the information security management system to establish its scope. When determining this scope, the organization shall consider: b) the requirements referred to in 4.2. The scope shall be available as documented information. | link | count: 003 Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.4.3.c | ISO27001-2013_C.4.3.c | ISO 27001:2013 C.4.3.c | Context of the organization | Determining the scope of the information security management system | Shared | n/a | The organization shall determine the boundaries and applicability of the information security management system to establish its scope. When determining this scope, the organization shall consider: c) interfaces and dependencies between activities performed by the organization, and those that are performed by other organizations. The scope shall be available as documented information. | link | count: 018 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Employ business case to record the resources required (2d14ff7e-6ff9-838c-0cde-4962ccdb1689), Ensure capital planning and investment requests include necessary resources (464a7d7a-2358-4869-0b49-6d582ca21292), Establish privacy requirements for contractors and service providers (f8d141b7-4e21-62a6-6608-c79336e36bc9), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.4.4 | ISO27001-2013_C.4.4 | ISO 27001:2013 C.4.4 | Context of the organization | Information security management system | Shared | n/a | The organization shall establish, implement, maintain and continually improve an information security management system, in accordance with the requirements of this International Standard. | link | count: 005 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.1.a | ISO27001-2013_C.5.1.a | ISO 27001:2013 C.5.1.a | Leadership | Leadership and commitment | Shared | n/a | Top management shall demonstrate leadership and commitment with respect to the information security management system by: a) ensuring the information security policy and the information security objectives are established and are compatible with the strategic direction of the organization; | link | count: 006 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.1.b | ISO27001-2013_C.5.1.b | ISO 27001:2013 C.5.1.b | Leadership | Leadership and commitment | Shared | n/a | Top management shall demonstrate leadership and commitment with respect to the information security management system by: b) ensuring the integration of the information security management system requirements into the organization’s processes. | link | count: 028 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.1.c | ISO27001-2013_C.5.1.c | ISO 27001:2013 C.5.1.c | Leadership | Leadership and commitment | Shared | n/a | Top management shall demonstrate leadership and commitment with respect to the information security management system by: c) ensuring that the resources needed for the information security management system are available. | link | count: 010 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Allocate resources in determining information system requirements (90a156a6-49ed-18d1-1052-69aac27c05cd), Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Employ business case to record the resources required (2d14ff7e-6ff9-838c-0cde-4962ccdb1689), Ensure capital planning and investment requests include necessary resources (464a7d7a-2358-4869-0b49-6d582ca21292), Ensure privacy program information is publicly available (1beb1269-62ee-32cd-21ad-43d6c9750eb6), Establish a discrete line item in budgeting documentation (06af77de-02ca-0f3e-838a-a9420fe466f5), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.1.d | ISO27001-2013_C.5.1.d | ISO 27001:2013 C.5.1.d | Leadership | Leadership and commitment | Shared | n/a | Top management shall demonstrate leadership and commitment with respect to the information security management system by: d) communicating the importance of effective information security management and of conforming to the information security management system requirements. | link | count: 001 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.1.e | ISO27001-2013_C.5.1.e | ISO 27001:2013 C.5.1.e | Leadership | Leadership and commitment | Shared | n/a | Top management shall demonstrate leadership and commitment with respect to the information security management system by: e) ensuring that the information security management system achieves its intended outcome(s). | link | count: 003 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Define performance metrics (39999038-9ef1-602a-158c-ce2367185230), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.1.f | ISO27001-2013_C.5.1.f | ISO 27001:2013 C.5.1.f | Leadership | Leadership and commitment | Shared | n/a | Top management shall demonstrate leadership and commitment with respect to the information security management system by: f) directing and supporting persons to contribute to the effectiveness of the information security management system. | link | count: 009 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Allocate resources in determining information system requirements (90a156a6-49ed-18d1-1052-69aac27c05cd), Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Employ business case to record the resources required (2d14ff7e-6ff9-838c-0cde-4962ccdb1689), Ensure capital planning and investment requests include necessary resources (464a7d7a-2358-4869-0b49-6d582ca21292), Establish a discrete line item in budgeting documentation (06af77de-02ca-0f3e-838a-a9420fe466f5), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.1.g | ISO27001-2013_C.5.1.g | ISO 27001:2013 C.5.1.g | Leadership | Leadership and commitment | Shared | n/a | Top management shall demonstrate leadership and commitment with respect to the information security management system by: g) promoting continual improvement. | link | count: 003 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Define performance metrics (39999038-9ef1-602a-158c-ce2367185230), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.1.h | ISO27001-2013_C.5.1.h | ISO 27001:2013 C.5.1.h | Leadership | Leadership and commitment | Shared | n/a | Top management shall demonstrate leadership and commitment with respect to the information security management system by: h) supporting other relevant management roles to demonstrate their leadership as it applies to their areas of responsibility. | link | count: 001 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.2.a | ISO27001-2013_C.5.2.a | ISO 27001:2013 C.5.2.a | Leadership | Policy | Shared | n/a | Top management shall establish an information security policy that: a) is appropriate to the purpose of the organization. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.2.b | ISO27001-2013_C.5.2.b | ISO 27001:2013 C.5.2.b | Leadership | Policy | Shared | n/a | Top management shall establish an information security policy that: b) includes information security objectives (see 6.2) or provides the framework for setting information security objectives. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.2.c | ISO27001-2013_C.5.2.c | ISO 27001:2013 C.5.2.c | Leadership | Policy | Shared | n/a | Top management shall establish an information security policy that: c) includes a commitment to satisfy applicable requirements related to information security. | link | count: 023 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.2.d | ISO27001-2013_C.5.2.d | ISO 27001:2013 C.5.2.d | Leadership | Policy | Shared | n/a | Top management shall establish an information security policy that: d) includes a commitment to continual improvement of the information security management system. | link | count: 023 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413), Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae), Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37), Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.2.e | ISO27001-2013_C.5.2.e | ISO 27001:2013 C.5.2.e | Leadership | Policy | Shared | n/a | Top management shall establish an information security policy. The information security policy shall: e) be available as documented information. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.2.f | ISO27001-2013_C.5.2.f | ISO 27001:2013 C.5.2.f | Leadership | Policy | Shared | n/a | Top management shall establish an information security policy. The information security policy shall: f) be communicated within the organization. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.2.g | ISO27001-2013_C.5.2.g | ISO 27001:2013 C.5.2.g | Leadership | Policy | Shared | n/a | Top management shall establish an information security policy. The information security policy shall: g) be available to interested parties, as appropriate. | link | count: 001 Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.5.3.b | ISO27001-2013_C.5.3.b | ISO 27001:2013 C.5.3.b | Leadership | Organizational roles, responsibilities and authorities | Shared | n/a | Top management shall ensure that the responsibilities and authorities for roles relevant to information security are assigned and communicated. Top management shall assign the responsibility and authority for: b) reporting on the performance of the information security management system to top management. NOTE Top management may also assign responsibilities and authorities for reporting performance of the information security management system within the organization. | link | count: 002 Define performance metrics (39999038-9ef1-602a-158c-ce2367185230), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.1.a | ISO27001-2013_C.6.1.1.a | ISO 27001:2013 C.6.1.1.a | Planning | General | Shared | n/a | When planning for the information security management system, the organization shall consider the issues referred to in 4.1 and the requirements referred to in 4.2 and determine the risks and opportunities that need to be addressed to: a) ensure the information security management system can achieve its intended outcome(s). | link | count: 003 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.1.b | ISO27001-2013_C.6.1.1.b | ISO 27001:2013 C.6.1.1.b | Planning | General | Shared | n/a | When planning for the information security management system, the organization shall consider the issues referred to in 4.1 and the requirements referred to in 4.2 and determine the risks and opportunities that need to be addressed to: b) prevent, or reduce, undesired effects. | link | count: 003 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.1.c | ISO27001-2013_C.6.1.1.c | ISO 27001:2013 C.6.1.1.c | Planning | General | Shared | n/a | When planning for the information security management system, the organization shall consider the issues referred to in 4.1 and the requirements referred to in 4.2 and determine the risks and opportunities that need to be addressed to: c) achieve continual improvement. | link | count: 003 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.1.d | ISO27001-2013_C.6.1.1.d | ISO 27001:2013 C.6.1.1.d | Planning | General | Shared | n/a | When planning for the information security management system, the organization shall consider the issues referred to in 4.1 and the requirements referred to in 4.2 and determine the risks and opportunities that need to be addressed. The organization shall plan: d) actions to address these risks and opportunities. | link | count: 003 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.1.e.1 | ISO27001-2013_C.6.1.1.e.1 | ISO 27001:2013 C.6.1.1.e.1 | Planning | General | Shared | n/a | When planning for the information security management system, the organization shall consider the issues referred to in 4.1 and the requirements referred to in 4.2 and determine the risks and opportunities that need to be addressed. The organization shall plan: e) how to - 1) integrate and implement the actions into its information security management system processes. | link | count: 003 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.1.e.2 | ISO27001-2013_C.6.1.1.e.2 | ISO 27001:2013 C.6.1.1.e.2 | Planning | General | Shared | n/a | When planning for the information security management system, the organization shall consider the issues referred to in 4.1 and the requirements referred to in 4.2 and determine the risks and opportunities that need to be addressed. The organization shall plan: e) how to - 2) evaluate the effectiveness of these actions. | link | count: 003 Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.a.1 | ISO27001-2013_C.6.1.2.a.1 | ISO 27001:2013 C.6.1.2.a.1 | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: a) establishes and maintains information security risk criteria that include: - 1) the risk acceptance criteria. The organization shall retain documented information about the information security risk assessment process. | link | count: 002 Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.a.2 | ISO27001-2013_C.6.1.2.a.2 | ISO 27001:2013 C.6.1.2.a.2 | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: a) establishes and maintains information security risk criteria that include: - 2) criteria for performing information security risk assessments. The organization shall retain documented information about the information security risk assessment process. | link | count: 002 Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.b | ISO27001-2013_C.6.1.2.b | ISO 27001:2013 C.6.1.2.b | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: b) ensures that repeated information security risk assessments produce consistent, valid and comparable results. The organization shall retain documented information about the information security risk assessment process. | link | count: 001 Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.c.1 | ISO27001-2013_C.6.1.2.c.1 | ISO 27001:2013 C.6.1.2.c.1 | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: c) identifies the information security risks: - 1) apply the information security risk assessment process to identify risks associated with the loss of confidentiality, integrity and availability for information within the scope of the information security management system. The organization shall retain documented information about the information security risk assessment process. | link | count: 002 Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.c.2 | ISO27001-2013_C.6.1.2.c.2 | ISO 27001:2013 C.6.1.2.c.2 | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: c) identifies the information security risks: - 2) identify the risk owners. The organization shall retain documented information about the information security risk assessment process. | link | count: 002 Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.d.1 | ISO27001-2013_C.6.1.2.d.1 | ISO 27001:2013 C.6.1.2.d.1 | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: d) analyses the information security risks: - 1) assess the potential consequences that would result if the risks identified in 6.1.2 c) 1) were to materialize. The organization shall retain documented information about the information security risk assessment process. | link | count: 002 Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.d.2 | ISO27001-2013_C.6.1.2.d.2 | ISO 27001:2013 C.6.1.2.d.2 | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: d) analyses the information security risks: - 2) assess the realistic likelihood of the occurrence of the risks identified in 6.1.2 c) 1). The organization shall retain documented information about the information security risk assessment process. | link | count: 002 Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.d.3 | ISO27001-2013_C.6.1.2.d.3 | ISO 27001:2013 C.6.1.2.d.3 | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: d) analyses the information security risks: - 3) determine the levels of risk. The organization shall retain documented information about the information security risk assessment process. | link | count: 002 Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.e.1 | ISO27001-2013_C.6.1.2.e.1 | ISO 27001:2013 C.6.1.2.e.1 | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: e) evaluates the information security risks: - 1) compare the results of risk analysis with the risk criteria established in 6.1.2 a). The organization shall retain documented information about the information security risk assessment process. | link | count: 002 Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.2.e.2 | ISO27001-2013_C.6.1.2.e.2 | ISO 27001:2013 C.6.1.2.e.2 | Planning | Information security risk assessment | Shared | n/a | The organization shall define and apply an information security risk assessment process that: e) evaluates the information security risks: - 2) prioritize the analysed risks for risk treatment. The organization shall retain documented information about the information security risk assessment process. | link | count: 002 Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.3.a | ISO27001-2013_C.6.1.3.a | ISO 27001:2013 C.6.1.3.a | Planning | Information security risk treatment | Shared | n/a | The organization shall define and apply an information security risk treatment process to: a) select appropriate information security risk treatment options, taking account of the risk assessment results; NOTE Organizations can design controls as required, or identify them from any source. NOTE 1 AnnexA contains a comprehensive list of control objectives and controls. Users of this International Standard are directed to Annex A to ensure that no necessary controls are overlooked. NOTE 2 Control objectives are implicitly included in the controls chosen. The control objectives and controls listed in Annex A are not exhaustive and additional control objectives and controls may be needed. The organization shall retain documented information about the information security risk treatment process. | link | count: 001 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.3.b | ISO27001-2013_C.6.1.3.b | ISO 27001:2013 C.6.1.3.b | Planning | Information security risk treatment | Shared | n/a | The organization shall define and apply an information security risk treatment process to: b) determine all controls that are necessary to implement the information security risk treatment option(s) chosen; NOTE Organizations can design controls as required, or identify them from any source. NOTE 1 AnnexA contains a comprehensive list of control objectives and controls. Users of this International Standard are directed to Annex A to ensure that no necessary controls are overlooked. NOTE 2 Control objectives are implicitly included in the controls chosen. The control objectives and controls listed in Annex A are not exhaustive and additional control objectives and controls may be needed. The organization shall retain documented information about the information security risk treatment process. | link | count: 001 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.3.c | ISO27001-2013_C.6.1.3.c | ISO 27001:2013 C.6.1.3.c | Planning | Information security risk treatment | Shared | n/a | The organization shall define and apply an information security risk treatment process to: c) compare the controls determined in 6.1.3 b) above with those in AnnexA and verify that no necessary controls have been omitted; NOTE Organizations can design controls as required, or identify them from any source. NOTE 1 AnnexA contains a comprehensive list of control objectives and controls. Users of this International Standard are directed to Annex A to ensure that no necessary controls are overlooked. NOTE 2 Control objectives are implicitly included in the controls chosen. The control objectives and controls listed in Annex A are not exhaustive and additional control objectives and controls may be needed. The organization shall retain documented information about the information security risk treatment process. | link | count: 001 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.3.d | ISO27001-2013_C.6.1.3.d | ISO 27001:2013 C.6.1.3.d | Planning | Information security risk treatment | Shared | n/a | The organization shall define and apply an information security risk treatment process to: d) produce a Statement of Applicability that contains the necessary controls (see 6.1.3 b) and c)) and justification for inclusions, whether they are implemented or not, and the justification for exclusions of controls from Annex A; NOTE Organizations can design controls as required, or identify them from any source. NOTE 1 AnnexA contains a comprehensive list of control objectives and controls. Users of this International Standard are directed to Annex A to ensure that no necessary controls are overlooked. NOTE 2 Control objectives are implicitly included in the controls chosen. The control objectives and controls listed in Annex A are not exhaustive and additional control objectives and controls may be needed. The organization shall retain documented information about the information security risk treatment process. | link | count: 001 Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.3.e | ISO27001-2013_C.6.1.3.e | ISO 27001:2013 C.6.1.3.e | Planning | Information security risk treatment | Shared | n/a | The organization shall define and apply an information security risk treatment process to: e) formulate an information security risk treatment plan; and NOTE Organizations can design controls as required, or identify them from any source. NOTE 1 AnnexA contains a comprehensive list of control objectives and controls. Users of this International Standard are directed to Annex A to ensure that no necessary controls are overlooked. NOTE 2 Control objectives are implicitly included in the controls chosen. The control objectives and controls listed in Annex A are not exhaustive and additional control objectives and controls may be needed. The organization shall retain documented information about the information security risk treatment process. | link | count: 001 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.1.3.f | ISO27001-2013_C.6.1.3.f | ISO 27001:2013 C.6.1.3.f | Planning | Information security risk treatment | Shared | n/a | The organization shall define and apply an information security risk treatment process to: f) obtain risk owners’ approval of the information security risk treatment plan and acceptance of the residual information security risks. NOTE Organizations can design controls as required, or identify them from any source. NOTE 1 AnnexA contains a comprehensive list of control objectives and controls. Users of this International Standard are directed to Annex A to ensure that no necessary controls are overlooked. NOTE 2 Control objectives are implicitly included in the controls chosen. The control objectives and controls listed in Annex A are not exhaustive and additional control objectives and controls may be needed. The organization shall retain documented information about the information security risk treatment process. | link | count: 001 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.6.2.e | ISO27001-2013_C.6.2.e | ISO 27001:2013 C.6.2.e | Planning | Information security objectives and planning to achieve them | Shared | n/a | The organization shall establish information security objectives at relevant functions and levels. The information security objectives shall: e) be updated as appropriate. The organization shall retain documented information on the information security objectives. | link | count: 002 Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.1 | ISO27001-2013_C.7.1 | ISO 27001:2013 C.7.1 | Support | Resources | Shared | n/a | The organization shall determine and provide the resources needed for the establishment, implementation, maintenance and continual improvement of the information security management system. | link | count: 007 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Allocate resources in determining information system requirements (90a156a6-49ed-18d1-1052-69aac27c05cd), Employ business case to record the resources required (2d14ff7e-6ff9-838c-0cde-4962ccdb1689), Ensure capital planning and investment requests include necessary resources (464a7d7a-2358-4869-0b49-6d582ca21292), Establish a discrete line item in budgeting documentation (06af77de-02ca-0f3e-838a-a9420fe466f5), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.2.a | ISO27001-2013_C.7.2.a | ISO 27001:2013 C.7.2.a | Support | Competence | Shared | n/a | The organization shall: a) determine the necessary competence of person(s) doing work under its control that affects its information security performance; NOTE Applicable actions may include, for example: the provision of training to, the mentoring of, or the reassignment of current employees; or the hiring or contracting of competent persons. | link | count: 003 Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.2.b | ISO27001-2013_C.7.2.b | ISO 27001:2013 C.7.2.b | Support | Competence | Shared | n/a | The organization shall: b) ensure that these persons are competent on the basis of appropriate education, training, or experience; NOTE Applicable actions may include, for example: the provision of training to, the mentoring of, or the reassignment of current employees; or the hiring or contracting of competent persons. | link | count: 001 Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.2.c | ISO27001-2013_C.7.2.c | ISO 27001:2013 C.7.2.c | Support | Competence | Shared | n/a | The organization shall: c) where applicable, take actions to acquire the necessary competence, and evaluate the effectiveness of the actions taken; NOTE Applicable actions may include, for example: the provision of training to, the mentoring of, or the reassignment of current employees; or the hiring or contracting of competent persons. | link | count: 001 Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.2.d | ISO27001-2013_C.7.2.d | ISO 27001:2013 C.7.2.d | Support | Competence | Shared | n/a | The organization shall: d) retain appropriate documented information as evidence of competence. NOTE Applicable actions may include, for example: the provision of training to, the mentoring of, or the reassignment of current employees; or the hiring or contracting of competent persons. | link | count: 001 Retain training records (3153d9c0-2584-14d3-362d-578b01358aeb) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.3.a | ISO27001-2013_C.7.3.a | ISO 27001:2013 C.7.3.a | Support | Awareness | Shared | n/a | Persons doing work under the organization’s control shall be aware of: a) the information security policy. | link | count: 003 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.3.b | ISO27001-2013_C.7.3.b | ISO 27001:2013 C.7.3.b | Support | Awareness | Shared | n/a | Persons doing work under the organization’s control shall be aware of: b) their contribution to the effectiveness of the information security management system, including the benefits of improved information security performance. | link | count: 003 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.3.c | ISO27001-2013_C.7.3.c | ISO 27001:2013 C.7.3.c | Support | Awareness | Shared | n/a | Persons doing work under the organization’s control shall be aware of: c) the implications of not conforming with the information security management system requirements. | link | count: 003 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.4.a | ISO27001-2013_C.7.4.a | ISO 27001:2013 C.7.4.a | Support | Communication | Shared | n/a | The organization shall determine the need for internal and external communications relevant to the information security management system including: a) on what to communicate. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.4.b | ISO27001-2013_C.7.4.b | ISO 27001:2013 C.7.4.b | Support | Communication | Shared | n/a | The organization shall determine the need for internal and external communications relevant to the information security management system including: b) when to communicate. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.4.c | ISO27001-2013_C.7.4.c | ISO 27001:2013 C.7.4.c | Support | Communication | Shared | n/a | The organization shall determine the need for internal and external communications relevant to the information security management system including: c) with whom to communicate. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.4.d | ISO27001-2013_C.7.4.d | ISO 27001:2013 C.7.4.d | Support | Communication | Shared | n/a | The organization shall determine the need for internal and external communications relevant to the information security management system including: d) who shall communicate. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.4.e | ISO27001-2013_C.7.4.e | ISO 27001:2013 C.7.4.e | Support | Communication | Shared | n/a | The organization shall determine the need for internal and external communications relevant to the information security management system including: e) the processes by which communication shall be effected. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.5.2.c | ISO27001-2013_C.7.5.2.c | ISO 27001:2013 C.7.5.2.c | Support | Creating and updating | Shared | n/a | When creating and updating documented information the organization shall ensure appropriate: c) review and approval for suitability and adequacy. | link | count: 001 Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.5.3.a | ISO27001-2013_C.7.5.3.a | ISO 27001:2013 C.7.5.3.a | Support | Control of documented information | Shared | n/a | Documented information required by the information security management system and by this International Standard shall be controlled to ensure: a) it is available and suitable for use, where and when it is needed. | link | count: 001 Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.5.3.b | ISO27001-2013_C.7.5.3.b | ISO 27001:2013 C.7.5.3.b | Support | Control of documented information | Shared | n/a | Documented information required by the information security management system and by this International Standard shall be controlled to ensure: b) it is adequately protected (e.g. from loss of confidentiality, improper use, or loss of integrity). | link | count: 003 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.5.3.c | ISO27001-2013_C.7.5.3.c | ISO 27001:2013 C.7.5.3.c | Support | Control of documented information | Shared | n/a | For the control of documented information, the organization shall address the following activities, as applicable: c) distribution, access, retrieval and use; Documented information of external origin, determined by the organization to be necessary for the planning and operation of the information security management system, shall be identified as appropriate, and controlled. NOTE Access implies a decision regarding the permission to view the documented information only, or the permission and authority to view and change the documented information, etc. | link | count: 001 Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.5.3.d | ISO27001-2013_C.7.5.3.d | ISO 27001:2013 C.7.5.3.d | Support | Control of documented information | Shared | n/a | For the control of documented information, the organization shall address the following activities, as applicable: d) storage and preservation, including the preservation of legibility. Documented information of external origin, determined by the organization to be necessary for the planning and operation of the information security management system, shall be identified as appropriate, and controlled. NOTE Access implies a decision regarding the permission to view the documented information only, or the permission and authority to view and change the documented information, etc. | link | count: 003 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.5.3.e | ISO27001-2013_C.7.5.3.e | ISO 27001:2013 C.7.5.3.e | Support | Control of documented information | Shared | n/a | For the control of documented information, the organization shall address the following activities, as applicable: e) control of changes (e.g. version control); and Documented information of external origin, determined by the organization to be necessary for the planning and operation of the information security management system, shall be identified as appropriate, and controlled. NOTE Access implies a decision regarding the permission to view the documented information only, or the permission and authority to view and change the documented information, etc. | link | count: 003 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.7.5.3.f | ISO27001-2013_C.7.5.3.f | ISO 27001:2013 C.7.5.3.f | Support | Control of documented information | Shared | n/a | For the control of documented information, the organization shall address the following activities, as applicable: f) retention and disposition. Documented information of external origin, determined by the organization to be necessary for the planning and operation of the information security management system, shall be identified as appropriate, and controlled. NOTE Access implies a decision regarding the permission to view the documented information only, or the permission and authority to view and change the documented information, etc. | link | count: 007 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.8.1 | ISO27001-2013_C.8.1 | ISO 27001:2013 C.8.1 | Operation | Operational planning and control | Shared | n/a | The organization shall plan, implement and control the processes needed to meet information security requirements, and to implement the actions determined in 6.1. The organization shall also implement plans to achieve information security objectives determined in 6.2. The organization shall keep documented information to the extent necessary to have confidence that the processes have been carried out as planned. The organization shall control planned changes and review the consequences of unintended changes, taking action to mitigate any adverse effects, as necessary. The organization shall ensure that outsourced processes are determined and controlled. | link | count: 021 Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.8.2 | ISO27001-2013_C.8.2 | ISO 27001:2013 C.8.2 | Operation | Information security risk assessment | Shared | n/a | The organization shall perform information security risk assessments at planned intervals or when significant changes are proposed or occur, taking account of the criteria established in 6.1.2 a). The organization shall retain documented information of the results of the information security risk assessments. | link | count: 003 Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.8.3 | ISO27001-2013_C.8.3 | ISO 27001:2013 C.8.3 | Operation | Information security risk treatment | Shared | n/a | The organization shall implement the information security risk treatment plan. The organization shall retain documented information of the results of the information security risk treatment. | link | count: 004 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.1.a | ISO27001-2013_C.9.1.a | ISO 27001:2013 C.9.1.a | Performance Evaluation | Monitoring, measurement, analysis and evaluation | Shared | n/a | The organization shall evaluate the information security performance and the effectiveness of the information security management system. The organization shall determine: a) what needs to be monitored and measured, including information security processes and controls. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.1.b | ISO27001-2013_C.9.1.b | ISO 27001:2013 C.9.1.b | Performance Evaluation | Monitoring, measurement, analysis and evaluation | Shared | n/a | The organization shall evaluate the information security performance and the effectiveness of the information security management system. The organization shall determine: b) the methods for monitoring, measurement, analysis and evaluation, as applicable, to ensure valid results. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.1.c | ISO27001-2013_C.9.1.c | ISO 27001:2013 C.9.1.c | Performance Evaluation | Monitoring, measurement, analysis and evaluation | Shared | n/a | The organization shall evaluate the information security performance and the effectiveness of the information security management system. NOTE The methods selected should produce comparable and reproducible results to be considered valid. c) when the monitoring and measuring shall be performed. The organization shall retain appropriate documented information as evidence of the monitoring and measurement results. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.1.d | ISO27001-2013_C.9.1.d | ISO 27001:2013 C.9.1.d | Performance Evaluation | Monitoring, measurement, analysis and evaluation | Shared | n/a | The organization shall evaluate the information security performance and the effectiveness of the information security management system. NOTE The methods selected should produce comparable and reproducible results to be considered valid. d) who shall monitor and measure; The organization shall retain appropriate documented information as evidence of the monitoring and measurement results. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.1.e | ISO27001-2013_C.9.1.e | ISO 27001:2013 C.9.1.e | Performance Evaluation | Monitoring, measurement, analysis and evaluation | Shared | n/a | The organization shall evaluate the information security performance and the effectiveness of the information security management system. NOTE The methods selected should produce comparable and reproducible results to be considered valid. e) when the results from monitoring and measurement shall be analysed and evaluated. The organization shall retain appropriate documented information as evidence of the monitoring and measurement results. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.1.f | ISO27001-2013_C.9.1.f | ISO 27001:2013 C.9.1.f | Performance Evaluation | Monitoring, measurement, analysis and evaluation | Shared | n/a | The organization shall evaluate the information security performance and the effectiveness of the information security management system. NOTE The methods selected should produce comparable and reproducible results to be considered valid. f) who shall analyse and evaluate these results. The organization shall retain appropriate documented information as evidence of the monitoring and measurement results. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.2.a.1 | ISO27001-2013_C.9.2.a.1 | ISO 27001:2013 C.9.2.a.1 | Performance Evaluation | Internal audit | Shared | n/a | The organization shall conduct internal audits at planned intervals to provide information on whether the information security management system: a) conforms to - 1) the organization’s own requirements for its information security management system; and | link | count: 001 Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.2.a.2 | ISO27001-2013_C.9.2.a.2 | ISO 27001:2013 C.9.2.a.2 | Performance Evaluation | Internal audit | Shared | n/a | The organization shall conduct internal audits at planned intervals to provide information on whether the information security management system: a) conforms to - 2) the requirements of this International Standard; | link | count: 001 Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.2.b | ISO27001-2013_C.9.2.b | ISO 27001:2013 C.9.2.b | Performance Evaluation | Internal audit | Shared | n/a | The organization shall conduct internal audits at planned intervals to provide information on whether the information security management system: b) is effectively implemented and maintained. | link | count: 001 Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.2.c | ISO27001-2013_C.9.2.c | ISO 27001:2013 C.9.2.c | Performance Evaluation | Internal audit | Shared | n/a | The organization shall conduct internal audits at planned intervals to provide information on whether the information security management system: The organization shall: c) plan, establish, implement and maintain an audit programme(s), including the frequency, methods, responsibilities, planning requirements and reporting. The audit programme(s) shall take into consideration the importance of the processes concerned and the results of previous audits. | link | count: 002 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.2.d | ISO27001-2013_C.9.2.d | ISO 27001:2013 C.9.2.d | Performance Evaluation | Internal audit | Shared | n/a | The organization shall conduct internal audits at planned intervals to provide information on whether the information security management system: The organization shall: d) define the audit criteria and scope for each audit. | link | count: 001 Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.2.e | ISO27001-2013_C.9.2.e | ISO 27001:2013 C.9.2.e | Performance Evaluation | Internal audit | Shared | n/a | The organization shall conduct internal audits at planned intervals to provide information on whether the information security management system: e) select auditors and conduct audits that ensure objectivity and the impartiality of the audit process. | link | count: 005 Adjust level of audit review, analysis, and reporting (de251b09-4a5e-1204-4bef-62ac58d47999), Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.2.f | ISO27001-2013_C.9.2.f | ISO 27001:2013 C.9.2.f | Performance Evaluation | Internal audit | Shared | n/a | The organization shall conduct internal audits at planned intervals to provide information on whether the information security management system: f) ensure that the results of the audits are reported to relevant management. | link | count: 001 Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.2.g | ISO27001-2013_C.9.2.g | ISO 27001:2013 C.9.2.g | Performance Evaluation | Internal audit | Shared | n/a | The organization shall conduct internal audits at planned intervals to provide information on whether the information security management system: g) retain documented information as evidence of the audit programme(s) and the audit results. | link | count: 003 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.3.a | ISO27001-2013_C.9.3.a | ISO 27001:2013 C.9.3.a | Performance Evaluation | Management review | Shared | n/a | Top management shall review the organization’s information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness. The management review shall include consideration of: a) the status of actions from previous management reviews; The outputs of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system. The organization shall retain documented information as evidence of the results of management reviews. | link | count: 005 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Implement plans of action and milestones for security program process (d93fe1be-13e4-421d-9c21-3158e2fa2667), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.3.b | ISO27001-2013_C.9.3.b | ISO 27001:2013 C.9.3.b | Performance Evaluation | Management review | Shared | n/a | Top management shall review the organization’s information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness. The management review shall include consideration of: b) changes in external and internal issues that are relevant to the information security management system. The outputs of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system. The organization shall retain documented information as evidence of the results of management reviews. | link | count: 004 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.3.c.1 | ISO27001-2013_C.9.3.c.1 | ISO 27001:2013 C.9.3.c.1 | Performance Evaluation | Management review | Shared | n/a | Top management shall review the organization’s information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness. The management review shall include consideration of: c) feedback on the information security performance, including trends in: - 1) nonconformities and corrective actions. The outputs of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system. The organization shall retain documented information as evidence of the results of management reviews. | link | count: 006 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Define performance metrics (39999038-9ef1-602a-158c-ce2367185230), Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.3.c.2 | ISO27001-2013_C.9.3.c.2 | ISO 27001:2013 C.9.3.c.2 | Performance Evaluation | Management review | Shared | n/a | Top management shall review the organization’s information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness. The management review shall include consideration of: c) feedback on the information security performance, including trends in: - 2) monitoring and measurement results. The outputs of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system. The organization shall retain documented information as evidence of the results of management reviews. | link | count: 004 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.3.c.3 | ISO27001-2013_C.9.3.c.3 | ISO 27001:2013 C.9.3.c.3 | Performance Evaluation | Management review | Shared | n/a | Top management shall review the organization’s information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness. The management review shall include consideration of: c) feedback on the information security performance, including trends in: - 3) audit results. The outputs of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system. The organization shall retain documented information as evidence of the results of management reviews. | link | count: 004 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Define performance metrics (39999038-9ef1-602a-158c-ce2367185230), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.3.c.4 | ISO27001-2013_C.9.3.c.4 | ISO 27001:2013 C.9.3.c.4 | Performance Evaluation | Management review | Shared | n/a | Top management shall review the organization’s information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness. The management review shall include consideration of: c) feedback on the information security performance, including trends in: - 4) fulfilment of information security objectives; The outputs of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system. The organization shall retain documented information as evidence of the results of management reviews. | link | count: 004 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Define performance metrics (39999038-9ef1-602a-158c-ce2367185230), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.3.d | ISO27001-2013_C.9.3.d | ISO 27001:2013 C.9.3.d | Performance Evaluation | Management review | Shared | n/a | Top management shall review the organization’s information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness. The management review shall include consideration of: d) feedback from interested parties; The outputs of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system. The organization shall retain documented information as evidence of the results of management reviews. | link | count: 003 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.3.e | ISO27001-2013_C.9.3.e | ISO 27001:2013 C.9.3.e | Performance Evaluation | Management review | Shared | n/a | Top management shall review the organization’s information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness. The management review shall include consideration of: e) results of risk assessment and status of risk treatment plan; and The outputs of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system. The organization shall retain documented information as evidence of the results of management reviews. | link | count: 003 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| ISO27001-2013 | C.9.3.f | ISO27001-2013_C.9.3.f | ISO 27001:2013 C.9.3.f | Performance Evaluation | Management review | Shared | n/a | Top management shall review the organization’s information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness. The management review shall include consideration of: f) opportunities for continual improvement. The outputs of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system. The organization shall retain documented information as evidence of the results of management reviews. | link | count: 003 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | ISO 27001:2013 (89c6cddc-1c73-4ac1-b19c-54d1a15a42f2) |
| NIST_SP_800-171_R2_3 | .1.1 | NIST_SP_800-171_R2_3.1.1 | NIST SP 800-171 R2 3.1.1 | Access Control | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Access control policies (e.g., identity- or role-based policies, control matrices, and cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, and domains) in systems. Access enforcement mechanisms can be employed at the application and service level to provide increased information security. Other systems include systems internal and external to the organization. This requirement focuses on account management for systems and applications. The definition of and enforcement of access authorizations, other than those determined by account type (e.g., privileged verses non-privileged) are addressed in requirement 3.1.2. | link | count: 055 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, General, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Security Center, Service Bus, Service Fabric, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.11 | NIST_SP_800-171_R2_3.1.11 | NIST SP 800-171 R2 3.1.11 | Access Control | Terminate (automatically) a user session after a defined condition. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., disconnecting from the network). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user’s logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on system use. | link | count: 001 Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.12 | NIST_SP_800-171_R2_3.1.12 | NIST SP 800-171 R2 3.1.12 | Access Control | Monitor and control remote access sessions. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Remote access is access to organizational systems by users (or processes acting on behalf of users) communicating through external networks (e.g., the Internet). Remote access methods include dial-up, broadband, and wireless. Organizations often employ encrypted virtual private networks (VPNs) to enhance confidentiality over remote connections. The use of encrypted VPNs does not make the access non-remote; however, the use of VPNs, when adequately provisioned with appropriate control (e.g., employing encryption techniques for confidentiality protection), may provide sufficient assurance to the organization that it can effectively treat such connections as internal networks. VPNs with encrypted tunnels can affect the capability to adequately monitor network communications traffic for malicious code. Automated monitoring and control of remote access sessions allows organizations to detect cyber-attacks and help to ensure ongoing compliance with remote access policies by auditing connection activities of remote users on a variety of system components (e.g., servers, workstations, notebook computers, smart phones, and tablets). [SP 800-46], [SP 800-77], and [SP 800-113] provide guidance on secure remote access and virtual private networks. | link | count: 036 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.13 | NIST_SP_800-171_R2_3.1.13 | NIST SP 800-171 R2 3.1.13 | Access Control | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. See [NIST CRYPTO]; [NIST CAVP]; [NIST CMVP]; National Security Agency Cryptographic Standards. | link | count: 031 App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.14 | NIST_SP_800-171_R2_3.1.14 | NIST SP 800-171 R2 3.1.14 | Access Control | Route remote access via managed access control points. | Shared | The customer is responsible for implementing this requirement. | Routing remote access through managed access control points enhances explicit, organizational control over such connections, reducing the susceptibility to unauthorized access to organizational systems resulting in the unauthorized disclosure of CUI. | link | count: 030 App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.15 | NIST_SP_800-171_R2_3.1.15 | NIST SP 800-171 R2 3.1.15 | Access Control | Authorize remote execution of privileged commands and remote access to security-relevant information. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | A privileged command is a human-initiated (interactively or via a process operating on behalf of the human) command executed on a system involving the control, monitoring, or administration of the system including security functions and associated security-relevant information. Security-relevant information is any information within the system that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Privileged commands give individuals the ability to execute sensitive, security-critical, or security-relevant system functions. Controlling such access from remote locations helps to ensure that unauthorized individuals are not able to execute such commands freely with the potential to do serious or catastrophic damage to organizational systems. Note that the ability to affect the integrity of the system is considered security-relevant as that could enable the means to by-pass security functions although not directly impacting the function itself. | link | count: 005 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Authorize remote access to privileged commands (01c387ea-383d-4ca9-295a-977fab516b03), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.16 | NIST_SP_800-171_R2_3.1.16 | NIST SP 800-171 R2 3.1.16 | Access Control | Authorize wireless access prior to allowing such connections | Shared | Microsoft is responsible for implementing this requirement. | Establishing usage restrictions and configuration/connection requirements for wireless access to the system provides criteria for organizations to support wireless access authorization decisions. Such restrictions and requirements reduce the susceptibility to unauthorized access to the system through wireless technologies. Wireless networks use authentication protocols which provide credential protection and mutual authentication. [SP 800-97] provides guidance on secure wireless networks. | link | count: 002 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.17 | NIST_SP_800-171_R2_3.1.17 | NIST SP 800-171 R2 3.1.17 | Access Control | Protect wireless access using authentication and encryption | Shared | Microsoft is responsible for implementing this requirement. | Organizations authenticate individuals and devices to help protect wireless access to the system. Special attention is given to the wide variety of devices that are part of the Internet of Things with potential wireless access to organizational systems. See [NIST CRYPTO]. | link | count: 003 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.18 | NIST_SP_800-171_R2_3.1.18 | NIST SP 800-171 R2 3.1.18 | Access Control | Control connection of mobile devices. | Shared | Microsoft is responsible for implementing this requirement. | A mobile device is a computing device that has a small form factor such that it can easily be carried by a single individual; is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); possesses local, non-removable or removable data storage; and includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, or built-in features for synchronizing local data with remote locations. Examples of mobile devices include smart phones, e-readers, and tablets. Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different types of devices. Usage restrictions and implementation guidance for mobile devices include: device identification and authentication; configuration management; implementation of mandatory protective software (e.g., malicious code detection, firewall); scanning devices for malicious code; updating virus protection software; scanning for critical software updates and patches; conducting primary operating system (and possibly other resident software) integrity checks; and disabling unnecessary hardware (e.g., wireless, infrared). The need to provide adequate security for mobile devices goes beyond this requirement. Many controls for mobile devices are reflected in other CUI security requirements. [SP 800-124] provides guidance on mobile device security. | link | count: 001 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.19 | NIST_SP_800-171_R2_3.1.19 | NIST SP 800-171 R2 3.1.19 | Access Control | Encrypt CUI on mobile devices and mobile computing platforms | Shared | Microsoft is responsible for implementing this requirement. | Organizations can employ full-device encryption or container-based encryption to protect the confidentiality of CUI on mobile devices and computing platforms. Container-based encryption provides a more fine-grained approach to the encryption of data and information including encrypting selected data structures such as files, records, or fields. See [NIST CRYPTO]. Mobile devices and computing platforms include, for example, smartphones and tablets. | link | count: 002 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.2 | NIST_SP_800-171_R2_3.1.2 | NIST SP 800-171 R2 3.1.2 | Access Control | Limit system access to the types of transactions and functions that authorized users are permitted to execute. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. System account types include individual, shared, group, system, anonymous, guest, emergency, developer, manufacturer, vendor, and temporary. Other attributes required for authorizing access include restrictions on time-of-day, day-of-week, and point-of-origin. In defining other account attributes, organizations consider system-related requirements (e.g., system upgrades scheduled maintenance,) and mission or business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements). | link | count: 031 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Enforce appropriate usage of all accounts (fd81a1b3-2d7a-107c-507e-29b87d040c19), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
App Service, Azure Ai Services, Compute, General, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.20 | NIST_SP_800-171_R2_3.1.20 | NIST SP 800-171 R2 3.1.20 | Access Control | Verify and control/limit connections to and use of external systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | External systems are systems or components of systems for which organizations typically have no direct supervision and authority over the application of security requirements and controls or the determination of the effectiveness of implemented controls on those systems. External systems include personally owned systems, components, or devices and privately-owned computing and communications devices resident in commercial or public facilities. This requirement also addresses the use of external systems for the processing, storage, or transmission of CUI, including accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational systems. Organizations establish terms and conditions for the use of external systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum, the types of applications that can be accessed on organizational systems from external systems. If terms and conditions with the owners of external systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems. This requirement recognizes that there are circumstances where individuals using external systems (e.g., contractors, coalition partners) need to access organizational systems. In those situations, organizations need confidence that the external systems contain the necessary controls so as not to compromise, damage, or otherwise harm organizational systems. Verification that the required controls have been effectively implemented can be achieved by third-party, independent assessments, attestations, or other means, depending on the assurance or confidence level required by organizations. Note that while “external” typically refers to outside of the organization’s direct supervision and authority, that is not always the case. Regarding the protection of CUI across an organization, the organization may have systems that process CUI and others that do not. And among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore, from the perspective of a given system, other systems within the organization may be considered “external" to that system. | link | count: 002 Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.21 | NIST_SP_800-171_R2_3.1.21 | NIST SP 800-171 R2 3.1.21 | Access Control | Limit use of portable storage devices on external systems. | Shared | Microsoft is responsible for implementing this requirement. | Limits on the use of organization-controlled portable storage devices in external systems include complete prohibition of the use of such devices or restrictions on how the devices may be used and under what conditions the devices may be used. Note that while “external” typically refers to outside of the organization’s direct supervision and authority, that is not always the case. Regarding the protection of CUI across an organization, the organization may have systems that process CUI and others that do not. Among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore, from the perspective of a given system, other systems within the organization may be considered “external" to that system. | link | count: 003 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.22 | NIST_SP_800-171_R2_3.1.22 | NIST SP 800-171 R2 3.1.22 | Access Control | Control CUI posted or processed on publicly accessible systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | In accordance with laws, Executive Orders, directives, policies, regulations, or standards, the public is not authorized access to nonpublic information (e.g., information protected under the Privacy Act, CUI, and proprietary information). This requirement addresses systems that are controlled by the organization and accessible to the public, typically without identification or authentication. Individuals authorized to post CUI onto publicly accessible systems are designated. The content of information is reviewed prior to posting onto publicly accessible systems to ensure that nonpublic information is not included. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Review content prior to posting publicly accessible information (9e3c505e-7aeb-2096-3417-b132242731fc), Review publicly accessible content for nonpublic information (b5244f81-6cab-3188-2412-179162294996), Train personnel on disclosure of nonpublic information (97f0d974-1486-01e2-2088-b888f46c0589) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.3 | NIST_SP_800-171_R2_3.1.3 | NIST SP 800-171 R2 3.1.3 | Access Control | Control the flow of CUI in accordance with approved authorizations. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Information flow control regulates where information can travel within a system and between systems (versus who can access the information) and without explicit regard to subsequent accesses to that information. Flow control restrictions include the following: keeping export-controlled information from being transmitted in the clear to the Internet; blocking outside traffic that claims to be from within the organization; restricting requests to the Internet that are not from the internal web proxy server; and limiting information transfers between organizations based on data structures and content. Organizations commonly use information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within systems and between interconnected systems. Flow control is based on characteristics of the information or the information path. Enforcement occurs in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, firewalls) that employ rule sets or establish configuration settings that restrict system services, provide a packet-filtering capability based on header information, or message-filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Organizations also consider the trustworthiness of filtering and inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Transferring information between systems representing different security domains with different security policies introduces risk that such transfers violate one or more domain security policies. In such situations, information owners or stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes: prohibiting information transfers between interconnected systems (i.e., allowing access only); employing hardware mechanisms to enforce one-way information flows; and implementing trustworthy regrading mechanisms to reassign security attributes and security labels. | link | count: 057 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, API Management, App Configuration, App Service, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Regulatory Compliance, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.4 | NIST_SP_800-171_R2_3.1.4 | NIST SP 800-171 R2 3.1.4 | Access Control | Separate the duties of individuals to reduce the risk of malevolent activity without collusion. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes dividing mission functions and system support functions among different individuals or roles; conducting system support functions with different individuals (e.g., configuration management, quality assurance and testing, system management, programming, and network security); and ensuring that security personnel administering access control functions do not also administer audit functions. Because separation of duty violations can span systems and application domains, organizations consider the entirety of organizational systems and system components when developing policy on separation of duties. | link | count: 006 Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Regulatory Compliance, Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.5 | NIST_SP_800-171_R2_3.1.5 | NIST SP 800-171 R2 3.1.5 | Access Control | Employ the principle of least privilege, including for specific security functions and privileged accounts. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations employ the principle of least privilege for specific duties and authorized accesses for users and processes. The principle of least privilege is applied with the goal of authorized privileges no higher than necessary to accomplish required organizational missions or business functions. Organizations consider the creation of additional processes, roles, and system accounts as necessary, to achieve least privilege. Organizations also apply least privilege to the development, implementation, and operation of organizational systems. Security functions include establishing system accounts, setting events to be logged, setting intrusion detection parameters, and configuring access authorizations (i.e., permissions, privileges). Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from having access to privileged information or functions. Organizations may differentiate in the application of this requirement between allowed privileges for local accounts and for domain accounts provided organizations retain the ability to control system configurations for key security parameters and as otherwise necessary to sufficiently mitigate risk. | link | count: 008 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
General, Regulatory Compliance, Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.7 | NIST_SP_800-171_R2_3.1.7 | NIST SP 800-171 R2 3.1.7 | Access Control | Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Privileged functions include establishing system accounts, performing system integrity checks, conducting patching operations, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. Note that this requirement represents a condition to be achieved by the definition of authorized privileges in 3.1.2. Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat. | link | count: 006 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .1.8 | NIST_SP_800-171_R2_3.1.8 | NIST SP 800-171 R2 3.1.8 | Access Control | Limit unsuccessful logon attempts. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by systems are, in most cases, temporary and automatically release after a predetermined period established by the organization (i.e., a delay algorithm). If a delay algorithm is selected, organizations may employ different algorithms for different system components based on the capabilities of the respective components. Responses to unsuccessful logon attempts may be implemented at the operating system and application levels. | link | count: 001 Enforce a limit of consecutive failed login attempts (b4409bff-2287-8407-05fd-c73175a68302) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .10.1 | NIST_SP_800-171_R2_3.10.1 | NIST SP 800-171 R2 3.10.1 | Physical Protection | Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals. | Shared | Microsoft is responsible for implementing this requirement. | This requirement applies to employees, individuals with permanent physical access authorization credentials, and visitors. Authorized individuals have credentials that include badges, identification cards, and smart cards. Organizations determine the strength of authorization credentials needed consistent with applicable laws, directives, policies, regulations, standards, procedures, and guidelines. This requirement applies only to areas within facilities that have not been designated as publicly accessible. Limiting physical access to equipment may include placing equipment in locked rooms or other secured areas and allowing access to authorized individuals only; and placing equipment in locations that can be monitored by organizational personnel. Computing devices, external disk drives, networking devices, monitors, printers, copiers, scanners, facsimile machines, and audio devices are examples of equipment. | link | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .10.2 | NIST_SP_800-171_R2_3.10.2 | NIST SP 800-171 R2 3.10.2 | Physical Protection | Protect and monitor the physical facility and support infrastructure for organizational systems. | Shared | Microsoft is responsible for implementing this requirement. | Monitoring of physical access includes publicly accessible areas within organizational facilities. This can be accomplished, for example, by the employment of guards; the use of sensor devices; or the use of video surveillance equipment such as cameras. Examples of support infrastructure include system distribution, transmission, and power lines. Security controls applied to the support infrastructure prevent accidental damage, disruption, and physical tampering. Such controls may also be necessary to prevent eavesdropping or modification of unencrypted transmissions. Physical access controls to support infrastructure include locked wiring closets; disconnected or locked spare jacks; protection of cabling by conduit or cable trays; and wiretapping sensors. | link | count: 002 Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .10.3 | NIST_SP_800-171_R2_3.10.3 | NIST SP 800-171 R2 3.10.3 | Physical Protection | Escort visitors and monitor visitor activity. | Shared | Microsoft is responsible for implementing this requirement. | Individuals with permanent physical access authorization credentials are not considered visitors. Audit logs can be used to monitor visitor activity. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .10.4 | NIST_SP_800-171_R2_3.10.4 | NIST SP 800-171 R2 3.10.4 | Physical Protection | Maintain audit logs of physical access. | Shared | Microsoft is responsible for implementing this requirement. | Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural (e.g., a written log of individuals accessing the facility), automated (e.g., capturing ID provided by a PIV card), or some combination thereof. Physical access points can include facility access points, interior access points to systems or system components requiring supplemental access controls, or both. System components (e.g., workstations, notebook computers) may be in areas designated as publicly accessible with organizations safeguarding access to such devices. | link | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .10.5 | NIST_SP_800-171_R2_3.10.5 | NIST SP 800-171 R2 3.10.5 | Physical Protection | Control and manage physical access devices. | Shared | Microsoft is responsible for implementing this requirement. | Physical access devices include keys, locks, combinations, and card readers. | link | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .10.6 | NIST_SP_800-171_R2_3.10.6 | NIST SP 800-171 R2 3.10.6 | Physical Protection | Enforce safeguarding measures for CUI at alternate work sites. | Shared | Microsoft is responsible for implementing this requirement. | Alternate work sites may include government facilities or the private residences of employees. Organizations may define different security requirements for specific alternate work sites or types of sites depending on the work-related activities conducted at those sites. [SP 800-46] and [SP 800-114] provide guidance on enterprise and user security when teleworking. | link | count: 001 Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .11.1 | NIST_SP_800-171_R2_3.11.1 | NIST SP 800-171 R2 3.11.1 | Risk Assessment | Periodically assess the risk to organizational operations, organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Clearly defined system boundaries are a prerequisite for effective risk assessments. Such risk assessments consider threats, vulnerabilities, likelihood, and impact to organizational operations, organizational assets, and individuals based on the operation and use of organizational systems. Risk assessments also consider risk from external parties (e.g., service providers, contractors operating systems on behalf of the organization, individuals accessing organizational systems, outsourcing entities). Risk assessments, either formal or informal, can be conducted at the organization level, the mission or business process level, or the system level, and at any phase in the system development life cycle. [SP 800-30] provides guidance on conducting risk assessments. | link | count: 002 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .11.2 | NIST_SP_800-171_R2_3.11.2 | NIST SP 800-171 R2 3.11.2 | Risk Assessment | Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations determine the required vulnerability scanning for all system components, ensuring that potential sources of vulnerabilities such as networked printers, scanners, and copiers are not overlooked. The vulnerabilities to be scanned are readily updated as new vulnerabilities are discovered, announced, and scanning methods developed. This process ensures that potential vulnerabilities in the system are identified and addressed as quickly as possible. Vulnerability analyses for custom software applications may require additional approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can employ these analysis approaches in source code reviews and in a variety of tools (e.g., static analysis tools, web-based application scanners, binary analyzers) and in source code reviews. Vulnerability scanning includes: scanning for patch levels; scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and scanning for improperly configured or incorrectly operating information flow control mechanisms. To facilitate interoperability, organizations consider using products that are Security Content Automated Protocol (SCAP)-validated, scanning tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention, and that employ the Open Vulnerability Assessment Language (OVAL) to determine the presence of system vulnerabilities. Sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). Security assessments, such as red team exercises, provide additional sources of potential vulnerabilities for which to scan. Organizations also consider using scanning tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS). In certain situations, the nature of the vulnerability scanning may be more intrusive or the system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system components facilitates thorough vulnerability scanning and protects the sensitive nature of such scanning. [SP 800-40] provides guidance on vulnerability management. | link | count: 022 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Implement privileged access for executing vulnerability scanning activities (5b802722-71dd-a13d-2e7e-231e09589efb), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Regulatory Compliance, Security Center, SQL, Synapse | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .11.3 | NIST_SP_800-171_R2_3.11.3 | NIST SP 800-171 R2 3.11.3 | Risk Assessment | Remediate vulnerabilities in accordance with risk assessments. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Vulnerabilities discovered, for example, via the scanning conducted in response to 3.11.2, are remediated with consideration of the related assessment of risk. The consideration of risk influences the prioritization of remediation efforts and the level of effort to be expended in the remediation for specific vulnerabilities. | link | count: 021 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Regulatory Compliance, Security Center, SQL, Synapse | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .12.1 | NIST_SP_800-171_R2_3.12.1 | NIST SP 800-171 R2 3.12.1 | Security Assessment | Periodically assess the security controls in organizational systems to determine if the controls are effective in their application. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations assess security controls in organizational systems and the environments in which those systems operate as part of the system development life cycle. Security controls are the safeguards or countermeasures organizations implement to satisfy security requirements. By assessing the implemented security controls, organizations determine if the security safeguards or countermeasures are in place and operating as intended. Security control assessments ensure that information security is built into organizational systems; identify weaknesses and deficiencies early in the development process; provide essential information needed to make risk-based decisions; and ensure compliance to vulnerability mitigation procedures. Assessments are conducted on the implemented security controls as documented in system security plans. Security assessment reports document assessment results in sufficient detail as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the security controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting security requirements. Security assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. Organizations ensure that security assessment results are current, relevant to the determination of security control effectiveness, and obtained with the appropriate level of assessor independence. Organizations can choose to use other types of assessment activities such as vulnerability scanning and system monitoring to maintain the security posture of systems during the system life cycle. [SP 800-53] provides guidance on security and privacy controls for systems and organizations. [SP 800-53A] provides guidance on developing security assessment plans and conducting assessments. | link | count: 004 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .12.2 | NIST_SP_800-171_R2_3.12.2 | NIST SP 800-171 R2 3.12.2 | Security Assessment | Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | The plan of action is a key document in the information security program. Organizations develop plans of action that describe how any unimplemented security requirements will be met and how any planned mitigations will be implemented. Organizations can document the system security plan and plan of action as separate or combined documents and in any chosen format. Federal agencies may consider the submitted system security plans and plans of action as critical inputs to an overall risk management decision to process, store, or transmit CUI on a system hosted by a nonfederal organization and whether it is advisable to pursue an agreement or contract with the nonfederal organization. [NIST CUI] provides supplemental material for Special Publication 800-171 including templates for plans of action. | link | count: 004 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement plans of action and milestones for security program process (d93fe1be-13e4-421d-9c21-3158e2fa2667), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .12.3 | NIST_SP_800-171_R2_3.12.3 | NIST SP 800-171 R2 3.12.3 | Security Assessment | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Continuous monitoring programs facilitate ongoing awareness of threats, vulnerabilities, and information security to support organizational risk management decisions. The terms continuous and ongoing imply that organizations assess and analyze security controls and information security-related risks at a frequency sufficient to support risk-based decisions. The results of continuous monitoring programs generate appropriate risk response actions by organizations. Providing access to security information on a continuing basis through reports or dashboards gives organizational officials the capability to make effective and timely risk management decisions. Automation supports more frequent updates to hardware, software, firmware inventories, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Monitoring requirements, including the need for specific monitoring, may also be referenced in other requirements. [SP 800-137] provides guidance on continuous monitoring. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .12.4 | NIST_SP_800-171_R2_3.12.4 | NIST SP 800-171 R2 3.12.4 | Security Assessment | Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | System security plans relate security requirements to a set of security controls. System security plans also describe, at a high level, how the security controls meet those security requirements, but do not provide detailed, technical descriptions of the design or implementation of the controls. System security plans contain sufficient information to enable a design and implementation that is unambiguously compliant with the intent of the plans and subsequent determinations of risk if the plan is implemented as intended. Security plans need not be single documents; the plans can be a collection of various documents including documents that already exist. Effective security plans make extensive use of references to policies, procedures, and additional documents (e.g., design and implementation specifications) where more detailed information can be obtained. This reduces the documentation requirements associated with security programs and maintains security-related information in other established management/operational areas related to enterprise architecture, system development life cycle, systems engineering, and acquisition. Federal agencies may consider the submitted system security plans and plans of action as critical inputs to an overall risk management decision to process, store, or transmit CUI on a system hosted by a nonfederal organization and whether it is advisable to pursue an agreement or contract with the nonfederal organization. [SP 800-18] provides guidance on developing security plans. [NIST CUI] provides supplemental material for Special Publication 800-171 including templates for system security plans. | link | count: 008 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.1 | NIST_SP_800-171_R2_3.13.1 | NIST SP 800-171 R2 3.13.1 | System and Communications Protection | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Communications can be monitored, controlled, and protected at boundary components and by restricting or prohibiting interfaces in organizational systems. Boundary components include gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within a system security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). Restricting or prohibiting interfaces in organizational systems includes restricting external web communications traffic to designated web servers within managed interfaces and prohibiting external traffic that appears to be spoofing internal addresses. Organizations consider the shared nature of commercial telecommunications services in the implementation of security requirements associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers and may also include third party-provided access lines and other service elements. Such transmission services may represent sources of increased risk despite contract security provisions. [SP 800-41] provides guidance on firewalls and firewall policy. [SP 800-125B] provides guidance on security for virtualization technologies. [28] There is no prescribed format or specified level of detail for system security plans. However, organizations ensure that the required information in 3.12.4 is conveyed in those plans. | link | count: 052 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.10 | NIST_SP_800-171_R2_3.13.10 | NIST SP 800-171 R2 3.13.10 | System and Communications Protection | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Cryptographic key management and establishment can be performed using manual procedures or mechanisms supported by manual procedures. Organizations define key management requirements in accordance with applicable federal laws, Executive Orders, policies, directives, regulations, and standards specifying appropriate options, levels, and parameters. [SP 800-56A] and [SP 800-57-1] provide guidance on cryptographic key management and key establishment. | link | count: 040 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) (47031206-ce96-41f8-861b-6a915f3de284), Azure API for FHIR should use a customer-managed key to encrypt data at rest (051cba44-2429-45b9-9649-46cec11c7119), Azure Automation accounts should use customer-managed keys to encrypt data at rest (56a5ee18-2ae6-4810-86f7-18e39ce5629b), Azure Batch account should use customer-managed keys to encrypt data (99e9ccd8-3db9-4592-b0d1-14b1715a4d8a), Azure Container Instance container group should use customer-managed key for encryption (0aa61e00-0a01-4a3c-9945-e93cffedf0e6), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password (86efb160-8de7-451d-bc08-5d475b0aadae), Azure Data Explorer encryption at rest should use a customer-managed key (81e74cea-30fd-40d5-802f-d72103c2aaaa), Azure data factories should be encrypted with a customer-managed key (4ec52d6d-beb7-40c4-9a9e-fe753254690e), Azure HDInsight clusters should use customer-managed keys to encrypt data at rest (64d314f6-6062-4780-a861-c23e8951bee5), Azure HDInsight clusters should use encryption at host to encrypt data at rest (1fd32ebd-e4c3-4e13-a54a-d7422d4d95f6), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Stream Analytics jobs should use customer-managed keys to encrypt data (87ba29ef-1ab3-4d82-b763-87fcd4f531f7), Azure Synapse workspaces should use customer-managed keys to encrypt data at rest (f7d52b2d-e161-4dfa-a82b-55e564167385), Bot Service should be encrypted with a customer-managed key (51522a96-0869-4791-82f3-981000c2c67f), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Event Hub namespaces should use a customer-managed key for encryption (a1ad735a-e96f-45d2-a7b2-9a4932cab7ec), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Logic Apps Integration Service Environment should be encrypted with customer-managed keys (1fafeaf6-7927-4059-a50a-8eb2a7a6f2b5), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), OS and data disks should be encrypted with a customer-managed key (702dd420-7fcc-42c5-afe8-4026edd20fe0), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Service Bus Premium namespaces should use a customer-managed key for encryption (295fc8b1-dc9f-4f53-9c61-3f313ceab40a), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
API for FHIR, Automation, Azure Data Explorer, Backup, Batch, Bot Service, Cognitive Services, Compute, Container Instance, Container Registry, Cosmos DB, Data Box, Data Factory, Event Hub, HDInsight, Internet of Things, Kubernetes, Logic Apps, Machine Learning, Monitoring, Regulatory Compliance, Service Bus, SQL, Storage, Stream Analytics, Synapse | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.11 | NIST_SP_800-171_R2_3.13.11 | NIST SP 800-171 R2 3.13.11 | System and Communications Protection | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Cryptography can be employed to support many security solutions including the protection of controlled unclassified information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Cryptographic standards include FIPS-validated cryptography and/or NSA-approved cryptography. See [NIST CRYPTO]; [NIST CAVP]; and [NIST CMVP]. | link | count: 001 Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.12 | NIST_SP_800-171_R2_3.13.12 | NIST SP 800-171 R2 3.13.12 | System and Communications Protection | Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Collaborative computing devices include networked white boards, cameras, and microphones. Indication of use includes signals to users when collaborative computing devices are activated. Dedicated video conferencing systems, which rely on one of the participants calling or connecting to the other party to activate the video conference, are excluded. Dedicated video conferencing systems, which rely on one of the participants calling or connecting to the other party to activate the video conference, are excluded. | link | count: 002 Explicitly notify use of collaborative computing devices (62fa14f0-4cbe-762d-5469-0899a99b98aa), Prohibit remote activation of collaborative computing devices (678ca228-042d-6d8e-a598-c58d5670437d) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.13 | NIST_SP_800-171_R2_3.13.13 | NIST SP 800-171 R2 3.13.13 | System and Communications Protection | Control and monitor the use of mobile code. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Mobile code technologies include Java, JavaScript, ActiveX, Postscript, PDF, Flash animations, and VBScript. Decisions regarding the use of mobile code in organizational systems are based on the potential for the code to cause damage to the systems if used maliciously. Usage restrictions and implementation guidance apply to the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations, notebook computers, and devices (e.g., smart phones). Mobile code policy and procedures address controlling or preventing the development, acquisition, or introduction of unacceptable mobile code in systems, including requiring mobile code to be digitally signed by a trusted source. [SP 800-28] provides guidance on mobile code. | link | count: 003 Authorize, monitor, and control usage of mobile code technologies (291f20d4-8d93-1d73-89f3-6ce28b825563), Define acceptable and unacceptable mobile code technologies (1afada58-8b34-7ac2-a38a-983218635201), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.14 | NIST_SP_800-171_R2_3.13.14 | NIST SP 800-171 R2 3.13.14 | System and Communications Protection | Control and monitor the use of Voice over Internet Protocol (VoIP) technologies. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | VoIP has different requirements, features, functionality, availability, and service limitations when compared with the Plain Old Telephone Service (POTS) (i.e., the standard telephone service). In contrast, other telephone services are based on high-speed, digital communications lines, such as Integrated Services Digital Network (ISDN) and Fiber Distributed Data Interface (FDDI). The main distinctions between POTS and non-POTS services are speed and bandwidth. To address the threats associated with VoIP, usage restrictions and implementation guidelines are based on the potential for the VoIP technology to cause damage to the system if it is used maliciously. Threats to VoIP are similar to those inherent with any Internet-based application. [SP 800-58] provides guidance on Voice Over IP Systems. | link | count: 002 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Establish voip usage restrictions (68a39c2b-0f17-69ee-37a3-aa10f9853a08) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.15 | NIST_SP_800-171_R2_3.13.15 | NIST SP 800-171 R2 3.13.15 | System and Communications Protection | Protect the authenticity of communications sessions. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Authenticity protection includes protecting against man-in-the-middle attacks, session hijacking, and the insertion of false information into communications sessions. This requirement addresses communications protection at the session versus packet level (e.g., sessions in service-oriented architectures providing web-based services) and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. [SP 800-77], [SP 800-95], and [SP 800-113] provide guidance on secure communications sessions. | link | count: 002 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce random unique session identifiers (c7d57a6a-7cc2-66c0-299f-83bf90558f5d) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.16 | NIST_SP_800-171_R2_3.13.16 | NIST SP 800-171 R2 3.13.16 | System and Communications Protection | Protect the confidentiality of CUI at rest. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Information at rest refers to the state of information when it is not in process or in transit and is located on storage devices as specific components of systems. The focus of protection at rest is not on the type of storage device or the frequency of access but rather the state of the information. Organizations can use different mechanisms to achieve confidentiality protections, including the use of cryptographic mechanisms and file share scanning. Organizations may also use other controls including secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved or continuous monitoring to identify malicious code at rest. See [NIST CRYPTO]. | link | count: 019 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.2 | NIST_SP_800-171_R2_3.13.2 | NIST SP 800-171 R2 3.13.2 | System and Communications Protection | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations apply systems security engineering principles to new development systems or systems undergoing major upgrades. For legacy systems, organizations apply systems security engineering principles to system upgrades and modifications to the extent feasible, given the current state of hardware, software, and firmware components within those systems. The application of systems security engineering concepts and principles helps to develop trustworthy, secure, and resilient systems and system components and reduce the susceptibility of organizations to disruptions, hazards, and threats. Examples of these concepts and principles include developing layered protections; establishing security policies, architecture, and controls as the foundation for design; incorporating security requirements into the system development life cycle; delineating physical and logical security boundaries; ensuring that developers are trained on how to build secure software; and performing threat modeling to identify use cases, threat agents, attack vectors and patterns, design patterns, and compensating controls needed to mitigate risk. Organizations that apply security engineering concepts and principles can facilitate the development of trustworthy, secure systems, system components, and system services; reduce risk to acceptable levels; and make informed risk-management decisions. [SP 800-160-1] provides guidance on systems security engineering. | link | count: 052 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.3 | NIST_SP_800-171_R2_3.13.3 | NIST SP 800-171 R2 3.13.3 | System and Communications Protection | Separate user functionality from system management functionality. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | System management functionality includes functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from system management functionality is physical or logical. Organizations can implement separation of system management functionality from user functionality by using different computers, different central processing units, different instances of operating systems, or different network addresses; virtualization techniques; or combinations of these or other methods, as appropriate. This type of separation includes web administrative interfaces that use separate authentication methods for users of any other system resources. Separation of system and user functionality may include isolating administrative interfaces on different domains and with additional access controls. | link | count: 003 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.5 | NIST_SP_800-171_R2_3.13.5 | NIST SP 800-171 R2 3.13.5 | System and Communications Protection | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones (DMZs). DMZs are typically implemented with boundary control devices and techniques that include routers, gateways, firewalls, virtualization, or cloud-based technologies. [SP 800-41] provides guidance on firewalls and firewall policy. [SP 800-125B] provides guidance on security for virtualization technologies | link | count: 052 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.6 | NIST_SP_800-171_R2_3.13.6 | NIST SP 800-171 R2 3.13.6 | System and Communications Protection | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement applies to inbound and outbound network communications traffic at the system boundary and at identified points within the system. A deny-all, permit-by-exception network communications traffic policy ensures that only those connections which are essential and approved are allowed. | link | count: 023 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Azure Ai Services, Container Registry, Cosmos DB, Key Vault, Network, Search, Security Center, SQL, Storage | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.7 | NIST_SP_800-171_R2_3.13.7 | NIST SP 800-171 R2 3.13.7 | System and Communications Protection | Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling). | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Split tunneling might be desirable by remote users to communicate with local system resources such as printers or file servers. However, split tunneling allows unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. This requirement is implemented in remote devices (e.g., notebook computers, smart phones, and tablets) through configuration settings to disable split tunneling in those devices, and by preventing configuration settings from being readily configurable by users. This requirement is implemented in the system by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling. | link | count: 001 Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.8 | NIST_SP_800-171_R2_3.13.8 | NIST SP 800-171 R2 3.13.8 | System and Communications Protection | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement applies to internal and external networks and any system components that can transmit information including servers, notebook computers, desktop computers, mobile devices, printers, copiers, scanners, and facsimile machines. Communication paths outside the physical protection of controlled boundaries are susceptible to both interception and modification. Organizations relying on commercial providers offering transmission services as commodity services rather than as fully dedicated services (i.e., services which can be highly specialized to individual customer needs), may find it difficult to obtain the necessary assurances regarding the implementation of the controls for transmission confidentiality. In such situations, organizations determine what types of confidentiality services are available in commercial telecommunication service packages. If it is infeasible or impractical to obtain the necessary safeguards and assurances of the effectiveness of the safeguards through appropriate contracting vehicles, organizations implement compensating safeguards or explicitly accept the additional risk. An example of an alternative physical safeguard is a protected distribution system (PDS) where the distribution medium is protected against electronic or physical intercept, thereby ensuring the confidentiality of the information being transmitted. See [NIST CRYPTO]. | link | count: 016 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, Regulatory Compliance, SQL, Storage | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .13.9 | NIST_SP_800-171_R2_3.13.9 | NIST SP 800-171 R2 3.13.9 | System and Communications Protection | Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement applies to internal and external networks. Terminating network connections associated with communications sessions include de-allocating associated TCP/IP address or port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. Time periods of user inactivity may be established by organizations and include time periods by type of network access or for specific network accesses | link | count: 001 Reauthenticate or terminate a user session (d6653f89-7cb5-24a4-9d71-51581038231b) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .14.1 | NIST_SP_800-171_R2_3.14.1 | NIST SP 800-171 R2 3.14.1 | System and Information Integrity | Identify, report, and correct system flaws in a timely manner. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations identify systems that are affected by announced software and firmware flaws including potential vulnerabilities resulting from those flaws and report this information to designated personnel with information security responsibilities. Security-relevant updates include patches, service packs, hot fixes, and anti-virus signatures. Organizations address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations can take advantage of available resources such as the Common Weakness Enumeration (CWE) database or Common Vulnerabilities and Exposures (CVE) database in remediating flaws discovered in organizational systems. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types of remediation. [SP 800-40] provides guidance on patch management technologies. | link | count: 023 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
App Service, Guest Configuration, Regulatory Compliance, Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .14.2 | NIST_SP_800-171_R2_3.14.2 | NIST SP 800-171 R2 3.14.2 | System and Information Integrity | Provide protection from malicious code at designated locations within organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Designated locations include system entry and exit points which may include firewalls, remote-access servers, workstations, electronic mail servers, web servers, proxy servers, notebook computers, and mobile devices. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. Malicious code protection mechanisms include anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. [SP 800-83] provides guidance on malware incident prevention. | link | count: 020 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Compute, Guest Configuration, Regulatory Compliance, Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .14.3 | NIST_SP_800-171_R2_3.14.3 | NIST SP 800-171 R2 3.14.3 | System and Information Integrity | Monitor system security alerts and advisories and take action in response. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | There are many publicly available sources of system security alerts and advisories. For example, the Department of Homeland Security’s Cybersecurity and Infrastructure Security Agency (CISA) generates security alerts and advisories to maintain situational awareness across the federal government and in nonfederal organizations. Software vendors, subscription services, and industry information sharing and analysis centers (ISACs) may also provide security alerts and advisories. Examples of response actions include notifying relevant external organizations, for example, external mission/business partners, supply chain partners, external service providers, and peer or supporting organizations. [SP 800-161] provides guidance on supply chain risk management. | link | count: 015 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Implement security directives (26d178a4-9261-6f04-a100-47ed85314c6e), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Regulatory Compliance, Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .14.4 | NIST_SP_800-171_R2_3.14.4 | NIST SP 800-171 R2 3.14.4 | System and Information Integrity | Update malicious code protection mechanisms when new releases are available. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Malicious code protection mechanisms include anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. | link | count: 011 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Compute, Guest Configuration, Regulatory Compliance, Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .14.5 | NIST_SP_800-171_R2_3.14.5 | NIST SP 800-171 R2 3.14.5 | System and Information Integrity | Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Periodic scans of organizational systems and real-time scans of files from external sources can detect malicious code. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. | link | count: 006 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Compute, Guest Configuration, Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .14.6 | NIST_SP_800-171_R2_3.14.6 | NIST SP 800-171 R2 3.14.6 | System and Information Integrity | Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | System monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at the system boundary (i.e., part of perimeter defense and boundary protection). Internal monitoring includes the observation of events occurring within the system. Organizations can monitor systems, for example, by observing audit record activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives may guide determination of the events. System monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Strategic locations for monitoring devices include selected perimeter locations and near server farms supporting critical applications, with such devices being employed at managed system interfaces. The granularity of monitoring information collected is based on organizational monitoring objectives and the capability of systems to support such objectives. System monitoring is an integral part of continuous monitoring and incident response programs. Output from system monitoring serves as input to continuous monitoring and incident response programs. A network connection is any connection with a device that communicates through a network (e.g., local area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Local, network, and remote connections can be either wired or wireless. Unusual or unauthorized activities or conditions related to inbound/outbound communications traffic include internal traffic that indicates the presence of malicious code in systems or propagating among system components, the unauthorized exporting of information, or signaling to external systems. Evidence of malicious code is used to identify potentially compromised systems or system components. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other requirements. [SP 800-94] provides guidance on intrusion detection and prevention systems. | link | count: 030 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Discover any indicators of compromise (07b42fb5-027e-5a3c-4915-9d9ef3020ec7), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .14.7 | NIST_SP_800-171_R2_3.14.7 | NIST SP 800-171 R2 3.14.7 | System and Information Integrity | Identify unauthorized use of organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | System monitoring includes external and internal monitoring. System monitoring can detect unauthorized use of organizational systems. System monitoring is an integral part of continuous monitoring and incident response programs. Monitoring is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Output from system monitoring serves as input to continuous monitoring and incident response programs. Unusual/unauthorized activities or conditions related to inbound and outbound communications traffic include internal traffic that indicates the presence of malicious code in systems or propagating among system components, the unauthorized exporting of information, or signaling to external systems. Evidence of malicious code is used to identify potentially compromised systems or system components. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other requirements. [SP 800-94] provides guidance on intrusion detection and prevention systems. | link | count: 023 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .2.1 | NIST_SP_800-171_R2_3.2.1 | NIST SP 800-171 R2 3.2.1 | Awareness and Training | Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards,& procedures related to the security of those systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations determine the content and frequency of security awareness training and security awareness techniques based on the specific organizational requirements and the systems to which personnel have authorized access. The content includes a basic understanding of the need for information security and user actions to maintain security and to respond to suspected security incidents. The content also addresses awareness of the need for operations security. Security awareness techniques include: formal training; offering supplies inscribed with security reminders; generating email advisories or notices from organizational officials; displaying logon screen messages; displaying security awareness posters; and conducting information security awareness events. [SP 800-50] provides guidance on security awareness and training programs. | link | count: 002 Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .2.2 | NIST_SP_800-171_R2_3.2.2 | NIST SP 800-171 R2 3.2.2 | Awareness and Training | Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations determine the content and frequency of security training based on the assigned duties, roles, and responsibilities of individuals and the security requirements of organizations and the systems to which personnel have authorized access. In addition, organizations provide system developers, enterprise architects, security architects, acquisition/procurement officials, software developers, system developers, systems integrators, system/network administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation, security assessors, and other personnel having access to system-level software, security-related technical training specifically tailored for their assigned duties. Comprehensive role-based training addresses management, operational, and technical roles and responsibilities covering physical, personnel, and technical controls. Such training can include policies, procedures, tools, and artifacts for the security roles defined. Organizations also provide the training necessary for individuals to carry out their responsibilities related to operations and supply chain security within the context of organizational information security programs. [SP 800-181] provides guidance on role-based information security training in the workplace. [SP 800-161] provides guidance on supply chain risk management. | link | count: 002 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .2.3 | NIST_SP_800-171_R2_3.2.3 | NIST SP 800-171 R2 3.2.3 | Awareness and Training | Provide security awareness training on recognizing and reporting potential indicators of insider threat. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Potential indicators and possible precursors of insider threat include behaviors such as: inordinate, long-term job dissatisfaction; attempts to gain access to information that is not required for job performance; unexplained access to financial resources; bullying or sexual harassment of fellow employees; workplace violence; and other serious violations of the policies, procedures, directives, rules, or practices of organizations. Security awareness training includes how to communicate employee and management concerns regarding potential indicators of insider threat through appropriate organizational channels in accordance with established organizational policies and procedures. Organizations may consider tailoring insider threat awareness topics to the role (e.g., training for managers may be focused on specific changes in behavior of team members, while training for employees may be focused on more general observations). | link | count: 002 Implement an insider threat program (35de8462-03ff-45b3-5746-9d4603c74c56), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .3.1 | NIST_SP_800-171_R2_3.3.1 | NIST SP 800-171 R2 3.3.1 | Audit and Accountability | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | An event is any observable occurrence in a system, which includes unlawful or unauthorized system activity. Organizations identify event types for which a logging functionality is needed as those events which are significant and relevant to the security of systems and the environments in which those systems operate to meet specific and ongoing auditing needs. Event types can include password changes, failed logons or failed accesses related to systems, administrative privilege usage, or third-party credential usage. In determining event types that require logging, organizations consider the monitoring and auditing appropriate for each of the CUI security requirements. Monitoring and auditing requirements can be balanced with other system needs. For example, organizations may determine that systems must have the capability to log every file access both successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit logging capability and can facilitate the identification of root causes to problems. Organizations consider in the definition of event types, the logging necessary to cover related events such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across multiple organizations) and actions that occur in service-oriented or cloud-based architectures. Audit record content that may be necessary to satisfy this requirement includes time stamps, source and destination addresses, user or process identifiers, event descriptions, success or fail indications, filenames involved, and access control or flow control rules invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the system after the event occurred). Detailed information that organizations may consider in audit records includes full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit log information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. Audit logs are reviewed and analyzed as often as needed to provide important information to organizations to facilitate risk-based decision making. [SP 800-92] provides guidance on security log management. | link | count: 053 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .3.2 | NIST_SP_800-171_R2_3.3.2 | NIST SP 800-171 R2 3.3.2 | Audit and Accountability | Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement ensures that the contents of the audit record include the information needed to link the audit event to the actions of an individual to the extent feasible. Organizations consider logging for traceability including results from monitoring of account usage, remote access, wireless connectivity, mobile device connection, communications at system boundaries, configuration settings, physical access, nonlocal maintenance, use of maintenance tools, temperature and humidity, equipment delivery and removal, system component inventory, use of mobile code, and use of Voice over Internet Protocol (VoIP). | link | count: 039 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish electronic signature and certificate requirements (6f3866e8-6e12-69cf-788c-809d426094a1), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Virtual machines should be connected to a specified workspace (f47b5582-33ec-4c5c-87c0-b010a6b2e917), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .3.3 | NIST_SP_800-171_R2_3.3.3 | NIST SP 800-171 R2 3.3.3 | Audit and Accountability | Review and update logged events. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | The intent of this requirement is to periodically re-evaluate which logged events will continue to be included in the list of events to be logged. The event types that are logged by organizations may change over time. Reviewing and updating the set of logged event types periodically is necessary to ensure that the current set remains necessary and sufficient. | link | count: 001 Review and update the events defined in AU-02 (a930f477-9dcb-2113-8aa7-45bb6fc90861) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .3.4 | NIST_SP_800-171_R2_3.3.4 | NIST SP 800-171 R2 3.3.4 | Audit and Accountability | Alert in the event of an audit logging process failure. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Audit logging process failures include software and hardware errors, failures in the audit record capturing mechanisms, and audit record storage capacity being reached or exceeded. This requirement applies to each audit record data storage repository (i.e., distinct system component where audit records are stored), the total audit record storage capacity of organizations (i.e., all audit record data storage repositories combined), or both. | link | count: 012 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Provide real-time alerts for audit event failures (0f4fa857-079d-9d3d-5c49-21f616189e03) |
Regulatory Compliance, Security Center, SQL | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .3.5 | NIST_SP_800-171_R2_3.3.5 | NIST SP 800-171 R2 3.3.5 | Audit and Accountability | Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Correlating audit record review, analysis, and reporting processes helps to ensure that they do not operate independently, but rather collectively. Regarding the assessment of a given organizational system, the requirement is agnostic as to whether this correlation is applied at the system level or at the organization level across all systems. | link | count: 013 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Integrate Audit record analysis (85335602-93f5-7730-830b-d43426fd51fa), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4) |
Regulatory Compliance, Security Center, SQL | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .3.6 | NIST_SP_800-171_R2_3.3.6 | NIST SP 800-171 R2 3.3.6 | Audit and Accountability | Provide audit record reduction and report generation to support on-demand analysis and reporting. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Audit record reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Audit record reduction and report generation capabilities do not always emanate from the same system or organizational entities conducting auditing activities. Audit record reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the system can help generate customizable reports. Time ordering of audit records can be a significant issue if the granularity of the time stamp in the record is insufficient. | link | count: 007 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Compile Audit records into system wide audit (214ea241-010d-8926-44cc-b90a96d52adc), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Provide audit review, analysis, and reporting capability (44f8a42d-739f-8030-89a8-4c2d5b3f6af3), Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .3.7 | NIST_SP_800-171_R2_3.3.7 | NIST SP 800-171 R2 3.3.7 | Audit and Accountability | Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Internal system clocks are used to generate time stamps, which include date and time. Time is expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks, for example, clocks synchronizing within hundreds of milliseconds or within tens of milliseconds. Organizations may define different time granularities for different system components. Time service can also be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities. This requirement provides uniformity of time stamps for systems with multiple system clocks and systems connected over a network. See [IETF 5905]. | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .3.8 | NIST_SP_800-171_R2_3.3.8 | NIST SP 800-171 R2 3.3.8 | Audit and Accountability | Protect audit information and audit logging tools from unauthorized access, modification, and deletion. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Audit information includes all information (e.g., audit records, audit log settings, and audit reports) needed to successfully audit system activity. Audit logging tools are those programs and devices used to conduct audit and logging activities. This requirement focuses on the technical protection of audit information and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by media protection and physical and environmental protection requirements. | link | count: 004 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Maintain integrity of audit system (c0559109-6a27-a217-6821-5a6d44f92897), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .3.9 | NIST_SP_800-171_R2_3.3.9 | NIST SP 800-171 R2 3.3.9 | Audit and Accountability | Limit management of audit logging functionality to a subset of privileged users. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Individuals with privileged access to a system and who are also the subject of an audit by that system, may affect the reliability of audit information by inhibiting audit logging activities or modifying audit records. This requirement specifies that privileged access be further defined between audit-related privileges and other privileges, thus limiting the users with audit-related privileges. | link | count: 001 Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .4.1 | NIST_SP_800-171_R2_3.4.1 | NIST SP 800-171 R2 3.4.1 | Configuration Management | Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Baseline configurations are documented, formally reviewed, and agreed-upon specifications for systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, and changes to systems. Baseline configurations include information about system components (e.g., standard software packages installed on workstations, notebook computers, servers, network components, or mobile devices; current version numbers and update and patch information on operating systems and applications; and configuration settings and parameters), network topology, and the logical placement of those components within the system architecture. Baseline configurations of systems also reflect the current enterprise architecture. Maintaining effective baseline configurations requires creating new baselines as organizational systems change over time. Baseline configuration maintenance includes reviewing and updating the baseline configuration when changes are made based on security risks and deviations from the established baseline configuration. Organizations can implement centralized system component inventories that include components from multiple organizational systems. In such situations, organizations ensure that the resulting inventories include system-specific information required for proper component accountability (e.g., system association, system owner). Information deemed necessary for effective accountability of system components includes hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include manufacturer, device type, model, serial number, and physical location. [SP 800-128] provides guidance on security-focused configuration management. | link | count: 031 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51), Retain previous versions of baseline configs (5e4e9685-3818-5934-0071-2620c4fa2ca5), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Guest Configuration, Kubernetes, Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .4.2 | NIST_SP_800-171_R2_3.4.2 | NIST SP 800-171 R2 3.4.2 | Configuration Management | Establish and enforce security configuration settings for information technology products employed in organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture or functionality of the system. Information technology products for which security-related configuration settings can be defined include mainframe computers, servers, workstations, input and output devices (e.g., scanners, copiers, and printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications. Security parameters are those parameters impacting the security state of systems including the parameters required to satisfy other security requirements. Security parameters include: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific configuration settings for systems. The established settings become part of the systems configuration baseline. Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations including information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors. [SP 800-70] and [SP 800-128] provide guidance on security configuration settings. | link | count: 025 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Guest Configuration, Kubernetes, Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .4.3 | NIST_SP_800-171_R2_3.4.3 | NIST SP 800-171 R2 3.4.3 | Configuration Management | Track, review, approve or disapprove, and log changes to organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Tracking, reviewing, approving/disapproving, and logging changes is called configuration change control. Configuration change control for organizational systems involves the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications. Configuration change control includes changes to baseline configurations for components and configuration items of systems, changes to configuration settings for information technology products (e.g., operating systems, applications, firewalls, routers, and mobile devices), unscheduled and unauthorized changes, and changes to remediate vulnerabilities. Processes for managing configuration changes to systems include Configuration Control Boards or Change Advisory Boards that review and approve proposed changes to systems. For new development systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards or Change Advisory Boards. Audit logs of changes include activities before and after changes are made to organizational systems and the activities required to implement such changes. [SP 800-128] provides guidance on configuration change control. | link | count: 015 Assign information security representative to change control (6abdf7c7-362b-3f35-099e-533ed50988f9), Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .4.4 | NIST_SP_800-171_R2_3.4.4 | NIST SP 800-171 R2 3.4.4 | Configuration Management | Analyze the security impact of changes prior to implementation. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizational personnel with information security responsibilities (e.g., system administrators, system security officers, system security managers, and systems security engineers) conduct security impact analyses. Individuals conducting security impact analyses possess the necessary skills and technical expertise to analyze the changes to systems and the associated security ramifications. Security impact analysis may include reviewing security plans to understand security requirements and reviewing system design documentation to understand the implementation of controls and how specific changes might affect the controls. Security impact analyses may also include risk assessments to better understand the impact of the changes and to determine if additional controls are required. [SP 800-128] provides guidance on configuration change control and security impact analysis. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .4.5 | NIST_SP_800-171_R2_3.4.5 | NIST SP 800-171 R2 3.4.5 | Configuration Management | Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Any changes to the hardware, software, or firmware components of systems can potentially have significant effects on the overall security of the systems. Therefore, organizations permit only qualified and authorized individuals to access systems for purposes of initiating changes, including upgrades and modifications. Access restrictions for change also include software libraries. Access restrictions include physical and logical access control requirements, workflow automation, media libraries, abstract layers (e.g., changes implemented into external interfaces rather than directly into systems), and change windows (e.g., changes occur only during certain specified times). In addition to security concerns, commonly-accepted due diligence for configuration management includes access restrictions as an essential part in ensuring the ability to effectively manage the configuration. [SP 800-128] provides guidance on configuration change control. | link | count: 006 Enforce and audit access restrictions (8cd815bf-97e1-5144-0735-11f6ddb50a59), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Restrict unauthorized software and firmware installation (4ee5975d-2507-5530-a20a-83a725889c6f), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32), Review changes for any unauthorized changes (c246d146-82b0-301f-32e7-1065dcd248b7) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .4.6 | NIST_SP_800-171_R2_3.4.6 | NIST SP 800-171 R2 3.4.6 | Configuration Management | Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Systems can provide a wide variety of functions and services. Some of the functions and services routinely provided by default, may not be necessary to support essential organizational missions, functions, or operations. It is sometimes convenient to provide multiple services from single system components. However, doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per component. Organizations review functions and services provided by systems or components of systems, to determine which functions and services are candidates for elimination. Organizations disable unused or unnecessary physical and logical ports and protocols to prevent unauthorized connection of devices, transfer of information, and tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services. | link | count: 003 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .4.7 | NIST_SP_800-171_R2_3.4.7 | NIST SP 800-171 R2 3.4.7 | Configuration Management | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Restricting the use of nonessential software (programs) includes restricting the roles allowed to approve program execution; prohibiting auto-execute; program blacklisting and whitelisting; or restricting the number of program instances executed at the same time. The organization makes a security-based determination which functions, ports, protocols, and/or services are restricted. Bluetooth, File Transfer Protocol (FTP), and peer-to-peer networking are examples of protocols organizations consider preventing the use of, restricting, or disabling. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .4.8 | NIST_SP_800-171_R2_3.4.8 | NIST SP 800-171 R2 3.4.8 | Configuration Management | Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | The process used to identify software programs that are not authorized to execute on systems is commonly referred to as blacklisting. The process used to identify software programs that are authorized to execute on systems is commonly referred to as whitelisting. Whitelisting is the stronger of the two policies for restricting software program execution. In addition to whitelisting, organizations consider verifying the integrity of whitelisted software programs using, for example, cryptographic checksums, digital signatures, or hash functions. Verification of whitelisted software can occur either prior to execution or at system startup. [SP 800-167] provides guidance on application whitelisting. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .4.9 | NIST_SP_800-171_R2_3.4.9 | NIST SP 800-171 R2 3.4.9 | Configuration Management | Control and monitor user-installed software. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Users can install software in organizational systems if provided the necessary privileges. To maintain control over the software installed, organizations identify permitted and prohibited actions regarding software installation through policies. Permitted software installations include updates and security patches to existing software and applications from organization-approved “app stores.” Prohibited software installations may include software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods, automated methods, or both. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.1 | NIST_SP_800-171_R2_3.5.1 | NIST SP 800-171 R2 3.5.1 | Identification and Authentication | Identify system users, processes acting on behalf of users, and devices. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Common device identifiers include Media Access Control (MAC), Internet Protocol (IP) addresses, or device-unique token identifiers. Management of individual identifiers is not applicable to shared system accounts. Typically, individual identifiers are the user names associated with the system accounts assigned to those individuals. Organizations may require unique identification of individuals in group accounts or for detailed accountability of individual activity. In addition, this requirement addresses individual identifiers that are not necessarily associated with system accounts. Organizational devices requiring identification may be defined by type, by device, or by a combination of type/device. [SP 800-63-3] provides guidance on digital identities. | link | count: 009 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Require use of individual authenticators (08ad71d0-52be-6503-4908-e015460a16ae), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
App Service, Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.10 | NIST_SP_800-171_R2_3.5.10 | NIST SP 800-171 R2 3.5.10 | Identification and Authentication | Store and transmit only cryptographically-protected passwords. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Cryptographically-protected passwords use salted one-way cryptographic hashes of passwords. See [NIST CRYPTO]. | link | count: 009 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Ensure authorized users protect provided authenticators (37dbe3dc-0e9c-24fa-36f2-11197cbfa207), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration, Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.11 | NIST_SP_800-171_R2_3.5.11 | NIST SP 800-171 R2 3.5.11 | Identification and Authentication | Obscure feedback of authentication information | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | The feedback from systems does not provide any information that would allow unauthorized individuals to compromise authentication mechanisms. For some types of systems or system components, for example, desktop or notebook computers with relatively large monitors, the threat (often referred to as shoulder surfing) may be significant. For other types of systems or components, for example, mobile devices with small displays, this threat may be less significant, and is balanced against the increased likelihood of typographic input errors due to the small keyboards. Therefore, the means for obscuring the authenticator feedback is selected accordingly. Obscuring authenticator feedback includes displaying asterisks when users type passwords into input devices or displaying feedback for a very limited time before fully obscuring it. | link | count: 001 Obscure feedback information during authentication process (1ff03f2a-974b-3272-34f2-f6cd51420b30) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.2 | NIST_SP_800-171_R2_3.5.2 | NIST SP 800-171 R2 3.5.2 | Identification and Authentication | Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Individual authenticators include the following: passwords, key cards, cryptographic devices, and one-time password devices. Initial authenticator content is the actual content of the authenticator, for example, the initial password. In contrast, the requirements about authenticator content include the minimum password length. Developers ship system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant security risk. Systems support authenticator management by organization-defined settings and restrictions for various authenticator characteristics including minimum password length, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication. Authenticator management includes issuing and revoking, when no longer needed, authenticators for temporary access such as that required for remote maintenance. Device authenticators include certificates and passwords. [SP 800-63-3] provides guidance on digital identities. | link | count: 024 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
App Service, Azure Ai Services, Guest Configuration, Key Vault, Regulatory Compliance, Security Center, Service Fabric, SQL | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.3 | NIST_SP_800-171_R2_3.5.3 | NIST SP 800-171 R2 3.5.3 | Identification and Authentication | Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Multifactor authentication requires the use of two or more different factors to authenticate. The factors are defined as something you know (e.g., password, personal identification number [PIN]); something you have (e.g., cryptographic identification device, token); or something you are (e.g., biometric). Multifactor authentication solutions that feature physical authenticators include hardware authenticators providing time-based or challenge-response authenticators and smart cards. In addition to authenticating users at the system level (i.e., at logon), organizations may also employ authentication mechanisms at the application level, when necessary, to provide increased information security. Access to organizational systems is defined as local access or network access. Local access is any access to organizational systems by users (or processes acting on behalf of users) where such access is obtained by direct connections without the use of networks. Network access is access to systems by users (or processes acting on behalf of users) where such access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks. The use of encrypted virtual private networks for connections between organization-controlled and non-organization controlled endpoints may be treated as internal networks with regard to protecting the confidentiality of information. [SP 800-63-3] provides guidance on digital identities. Multifactor authentication requires two or more different factors to achieve authentication. The factors include: something you know (e.g., password/PIN); something you have (e.g., cryptographic identification device, token); or something you are (e.g., biometric). The requirement for multifactor authentication should not be interpreted as requiring federal Personal Identity Verification (PIV) card or Department of Defense Common Access Card (CAC)-like solutions. A variety of multifactor solutions (including those with replay resistance) using tokens and biometrics are commercially available. Such solutions may employ hard tokens (e.g., smartcards, key fobs, or dongles) or soft tokens to store user credentials. Local access is any access to a system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network. Network access is any access to a system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, Internet). | link | count: 005 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198) |
Regulatory Compliance, Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.4 | NIST_SP_800-171_R2_3.5.4 | NIST SP 800-171 R2 3.5.4 | Identification and Authentication | Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Authentication processes resist replay attacks if it is impractical to successfully authenticate by recording or replaying previous authentication messages. Replay-resistant techniques include protocols that use nonces or challenges such as time synchronous or challenge-response one-time authenticators. [SP 800-63-3] provides guidance on digital identities. | link | count: 001 Windows machines should meet requirements for 'Security Options - Network Security' (1221c620-d201-468c-81e7-2817e6107e84) |
Guest Configuration | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.5 | NIST_SP_800-171_R2_3.5.5 | NIST SP 800-171 R2 3.5.5 | Identification and Authentication | Prevent reuse of identifiers for a defined period. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Identifiers are provided for users, processes acting on behalf of users, or devices (3.5.1). Preventing reuse of identifiers implies preventing the assignment of previously used individual, group, role, or device identifiers to different individuals, groups, roles, or devices. | link | count: 006 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Prevent identifier reuse for the defined time period (4781e5fd-76b8-7d34-6df3-a0a7fca47665), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.6 | NIST_SP_800-171_R2_3.5.6 | NIST SP 800-171 R2 3.5.6 | Identification and Authentication | Disable identifiers after a defined period of inactivity. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Inactive identifiers pose a risk to organizational information because attackers may exploit an inactive identifier to gain undetected access to organizational devices. The owners of the inactive accounts may not notice if unauthorized access to the account has been obtained. | link | count: 006 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Security Center, Service Fabric, SQL | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.7 | NIST_SP_800-171_R2_3.5.7 | NIST SP 800-171 R2 3.5.7 | Identification and Authentication | Enforce a minimum password complexity and change of characters when new passwords are created. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement applies to single-factor authentication of individuals using passwords as individual or group authenticators, and in a similar manner, when passwords are used as part of multifactor authenticators. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. To mitigate certain brute force attacks against passwords, organizations may also consider salting passwords. | link | count: 008 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d) |
Guest Configuration, Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .5.8 | NIST_SP_800-171_R2_3.5.8 | NIST SP 800-171 R2 3.5.8 | Identification and Authentication | Prohibit password reuse for a specified number of generations. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Password lifetime restrictions do not apply to temporary passwords | link | count: 004 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .6.1 | NIST_SP_800-171_R2_3.6.1 | NIST SP 800-171 R2 3.6.1 | Incident response | Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations recognize that incident handling capability is dependent on the capabilities of organizational systems and the mission/business processes being supported by those systems. Organizations consider incident handling as part of the definition, design, and development of mission/business processes and systems. Incident-related information can be obtained from a variety of sources including audit monitoring, network monitoring, physical access monitoring, user and administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including mission/business owners, system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive. As part of user response activities, incident response training is provided by organizations and is linked directly to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, regular users may only need to know who to call or how to recognize an incident on the system; system administrators may require additional training on how to handle or remediate incidents; and incident responders may receive more specific training on forensics, reporting, system recovery, and restoration. Incident response training includes user training in the identification/reporting of suspicious activities from external and internal sources. User response activities also includes incident response assistance which may consist of help desk support, assistance groups, and access to forensics services or consumer redress services, when required. [SP 800-61] provides guidance on incident handling. [SP 800-86] and [SP 800-101] provide guidance on integrating forensic techniques into incident response. [SP 800-161] provides guidance on supply chain risk management. | link | count: 012 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Coordinate with external organizations to achieve cross org perspective (d4e6a629-28eb-79a9-000b-88030e4823ca), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .6.2 | NIST_SP_800-171_R2_3.6.2 | NIST SP 800-171 R2 3.6.2 | Incident response | Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Tracking and documenting system security incidents includes maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics, evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources including incident reports, incident response teams, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports. Reporting incidents addresses specific incident reporting requirements within an organization and the formal incident reporting requirements for the organization. Suspected security incidents may also be reported and include the receipt of suspicious email communications that can potentially contain malicious code. The types of security incidents reported, the content and timeliness of the reports, and the designated reporting authorities reflect applicable laws, Executive Orders, directives, regulations, and policies. [SP 800-61] provides guidance on incident handling. | link | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .6.3 | NIST_SP_800-171_R2_3.6.3 | NIST SP 800-171 R2 3.6.3 | Incident response | Test the organizational incident response capability. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations test incident response capabilities to determine the effectiveness of the capabilities and to identify potential weaknesses or deficiencies. Incident response testing includes the use of checklists, walk-through or tabletop exercises, simulations (both parallel and full interrupt), and comprehensive exercises. Incident response testing can also include a determination of the effects on organizational operations (e.g., reduction in mission capabilities), organizational assets, and individuals due to incident response. [SP 800-84] provides guidance on testing programs for information technology capabilities. | link | count: 003 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .7.1 | NIST_SP_800-171_R2_3.7.1 | NIST SP 800-171 R2 3.7.1 | Maintenance | Perform maintenance on organizational systems.[26]. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement addresses the information security aspects of the system maintenance program and applies to all types of maintenance to any system component (including hardware, firmware, applications) conducted by any local or nonlocal entity. System maintenance also includes those components not directly associated with information processing and data or information retention such as scanners, copiers, and printers. [26] In general, system maintenance requirements tend to support the security objective of availability. However, improper system maintenance or a failure to perform maintenance can result in the unauthorized disclosure of CUI, thus compromising confidentiality of that information. | link | count: 001 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .7.2 | NIST_SP_800-171_R2_3.7.2 | NIST SP 800-171 R2 3.7.2 | Maintenance | Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement addresses security-related issues with maintenance tools that are not within the organizational system boundaries that process, store, or transmit CUI, but are used specifically for diagnostic and repair actions on those systems. Organizations have flexibility in determining the controls in place for maintenance tools, but can include approving, controlling, and monitoring the use of such tools. Maintenance tools are potential vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and into organizational systems. Maintenance tools can include hardware, software, and firmware items, for example, hardware and software diagnostic test equipment and hardware and software packet sniffers. | link | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .7.3 | NIST_SP_800-171_R2_3.7.3 | NIST SP 800-171 R2 3.7.3 | Maintenance | Ensure equipment removed for off-site maintenance is sanitized of any CUI. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement addresses the information security aspects of system maintenance that are performed off-site and applies to all types of maintenance to any system component (including applications) conducted by a local or nonlocal entity (e.g., in-contract, warranty, in- house, software maintenance agreement). [SP 800-88] provides guidance on media sanitization. | link | count: 003 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .7.4 | NIST_SP_800-171_R2_3.7.4 | NIST SP 800-171 R2 3.7.4 | Maintenance | Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | If, upon inspection of media containing maintenance diagnostic and test programs, organizations determine that the media contain malicious code, the incident is handled consistent with incident handling policies and procedures. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .7.5 | NIST_SP_800-171_R2_3.7.5 | NIST SP 800-171 R2 3.7.5 | Maintenance | Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through an external network. The authentication techniques employed in the establishment of these nonlocal maintenance and diagnostic sessions reflect the network access requirements in 3.5.3. | link | count: 001 Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .7.6 | NIST_SP_800-171_R2_3.7.6 | NIST SP 800-171 R2 3.7.6 | Maintenance | Supervise the maintenance activities of maintenance personnel without required access authorization. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | This requirement applies to individuals who are performing hardware or software maintenance on organizational systems, while 3.10.1 addresses physical access for individuals whose maintenance duties place them within the physical protection perimeter of the systems (e.g., custodial staff, physical plant maintenance personnel). Individuals not previously identified as authorized maintenance personnel, such as information technology manufacturers, vendors, consultants, and systems integrators, may require privileged access to organizational systems, for example, when required to conduct maintenance activities with little or no notice. Organizations may choose to issue temporary credentials to these individuals based on organizational risk assessments. Temporary credentials may be for one-time use or for very limited time periods. | link | count: 003 Designate personnel to supervise unauthorized maintenance activities (7a489c62-242c-5db9-74df-c073056d6fa3), Maintain list of authorized remote maintenance personnel (4ce91e4e-6dab-3c46-011a-aa14ae1561bf), Manage maintenance personnel (b273f1e3-79e7-13ee-5b5d-dca6c66c3d5d) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .8.1 | NIST_SP_800-171_R2_3.8.1 | NIST SP 800-171 R2 3.8.1 | Media Protection | Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital. | Shared | Microsoft is responsible for implementing this requirement. | System media includes digital and non-digital media. Digital media includes diskettes, magnetic tapes, external and removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes paper and microfilm. Protecting digital media includes limiting access to design specifications stored on compact disks or flash drives in the media library to the project leader and any individuals on the development team. Physically controlling system media includes conducting inventories, maintaining accountability for stored media, and ensuring procedures are in place to allow individuals to check out and return media to the media library. Secure storage includes a locked drawer, desk, or cabinet, or a controlled media library. Access to CUI on system media can be limited by physically controlling such media, which includes conducting inventories, ensuring procedures are in place to allow individuals to check out and return media to the media library, and maintaining accountability for all stored media. [SP 800-111] provides guidance on storage encryption technologies for end user devices. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .8.2 | NIST_SP_800-171_R2_3.8.2 | NIST SP 800-171 R2 3.8.2 | Media Protection | Limit access to CUI on system media to authorized users | Shared | Microsoft is responsible for implementing this requirement. | Access can be limited by physically controlling system media and secure storage areas. Physically controlling system media includes conducting inventories, ensuring procedures are in place to allow individuals to check out and return system media to the media library, and maintaining accountability for all stored media. Secure storage includes a locked drawer, desk, or cabinet, or a controlled media library. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .8.3 | NIST_SP_800-171_R2_3.8.3 | NIST SP 800-171 R2 3.8.3 | Media Protection | Sanitize or destroy system media containing CUI before disposal or release for reuse. | Shared | Microsoft is responsible for implementing this requirement. | This requirement applies to all system media, digital and non-digital, subject to disposal or reuse. Examples include: digital media found in workstations, network components, scanners, copiers, printers, notebook computers, and mobile devices; and non-digital media such as paper and microfilm. The sanitization process removes information from the media such that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, cryptographic erase, and destruction, prevent the disclosure of information to unauthorized individuals when such media is released for reuse or disposal. Organizations determine the appropriate sanitization methods, recognizing that destruction may be necessary when other methods cannot be applied to the media requiring sanitization. Organizations use discretion on the employment of sanitization techniques and procedures for media containing information that is in the public domain or publicly releasable or deemed to have no adverse impact on organizations or individuals if released for reuse or disposal. Sanitization of non-digital media includes destruction, removing CUI from documents, or redacting selected sections or words from a document by obscuring the redacted sections or words in a manner equivalent in effectiveness to removing the words or sections from the document. NARA policy and guidance control sanitization processes for controlled unclassified information. [SP 800-88] provides guidance on media sanitization. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .8.4 | NIST_SP_800-171_R2_3.8.4 | NIST SP 800-171 R2 3.8.4 | Media Protection | Mark media with necessary CUI markings and distribution limitations.[27] | Shared | Microsoft is responsible for implementing this requirement. | The term security marking refers to the application or use of human-readable security attributes. System media includes digital and non-digital media. Marking of system media reflects applicable federal laws, Executive Orders, directives, policies, and regulations. See [NARA MARK]. [27] The implementation of this requirement is per marking guidance in [32 CFR 2002] and [NARA CUI]. Standard Form (SF) 902 (approximate size 2.125” x 1.25”) and SF 903 (approximate size 2.125” x .625”) can be used on media that contains CUI such as hard drives, or USB devices. Both forms are available from https://www.gsaadvantage.gov. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .8.5 | NIST_SP_800-171_R2_3.8.5 | NIST SP 800-171 R2 3.8.5 | Media Protection | Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas. | Shared | Microsoft is responsible for implementing this requirement. | Controlled areas are areas or spaces for which organizations provide physical or procedural controls to meet the requirements established for protecting systems and information. Controls to maintain accountability for media during transport include locked containers and cryptography. Cryptographic mechanisms can provide confidentiality and integrity protections depending upon the mechanisms used. Activities associated with transport include the actual transport as well as those activities such as releasing media for transport and ensuring that media enters the appropriate transport processes. For the actual transport, authorized transport and courier personnel may include individuals external to the organization. Maintaining accountability of media during transport includes restricting transport activities to authorized personnel and tracking and obtaining explicit records of transport activities as the media moves through the transportation system to prevent and detect loss, destruction, or tampering. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .8.6 | NIST_SP_800-171_R2_3.8.6 | NIST SP 800-171 R2 3.8.6 | Media Protection | Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards. | Shared | Microsoft is responsible for implementing this requirement. | This requirement applies to portable storage devices (e.g., USB memory sticks, digital video disks, compact disks, external or removable hard disk drives). See [NIST CRYPTO]. [SP 800-111] provides guidance on storage encryption technologies for end user devices. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .8.7 | NIST_SP_800-171_R2_3.8.7 | NIST SP 800-171 R2 3.8.7 | Media Protection | Control the use of removable media on system components. | Shared | Microsoft is responsible for implementing this requirement. | In contrast to requirement 3.8.1, which restricts user access to media, this requirement restricts the use of certain types of media on systems, for example, restricting or prohibiting the use of flash drives or external hard disk drives. Organizations can employ technical and nontechnical controls (e.g., policies, procedures, and rules of behavior) to control the use of system media. Organizations may control the use of portable storage devices, for example, by using physical cages on workstations to prohibit access to certain external ports, or disabling or removing the ability to insert, read, or write to such devices. Organizations may also limit the use of portable storage devices to only approved devices including devices provided by the organization, devices provided by other approved organizations, and devices that are not personally owned. Finally, organizations may control the use of portable storage devices based on the type of device, prohibiting the use of writeable, portable devices, and implementing this restriction by disabling or removing the capability to write to such devices. | link | count: 004 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .8.8 | NIST_SP_800-171_R2_3.8.8 | NIST SP 800-171 R2 3.8.8 | Media Protection | Prohibit the use of portable storage devices when such devices have no identifiable owner. | Shared | Microsoft is responsible for implementing this requirement. | Requiring identifiable owners (e.g., individuals, organizations, or projects) for portable storage devices reduces the overall risk of using such technologies by allowing organizations to assign responsibility and accountability for addressing known vulnerabilities in the devices (e.g., insertion of malicious code). | link | count: 004 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .8.9 | NIST_SP_800-171_R2_3.8.9 | NIST SP 800-171 R2 3.8.9 | Media Protection | Protect the confidentiality of backup CUI at storage locations. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Organizations can employ cryptographic mechanisms or alternative physical controls to protect the confidentiality of backup information at designated storage locations. Backed-up information containing CUI may include system-level information and user-level information. System-level information includes system-state information, operating system software, application software, and licenses. User-level information includes information other than system-level information. | link | count: 008 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Backup, Key Vault, Regulatory Compliance, SQL | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .9.1 | NIST_SP_800-171_R2_3.9.1 | NIST SP 800-171 R2 3.9.1 | Personnel Security | Screen individuals prior to authorizing access to organizational systems containing CUI. | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Personnel security screening (vetting) activities involve the evaluation/assessment of individual’s conduct, integrity, judgment, loyalty, reliability, and stability (i.e., the trustworthiness of the individual) prior to authorizing access to organizational systems containing CUI. The screening activities reflect applicable federal laws, Executive Orders, directives, policies, regulations, and specific criteria established for the level of access required for assigned positions. | link | count: 002 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-171_R2_3 | .9.2 | NIST_SP_800-171_R2_3.9.2 | NIST SP 800-171 R2 3.9.2 | Personnel Security | Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers | Shared | Microsoft and the customer share responsibilities for implementing this requirement. | Protecting CUI during and after personnel actions may include returning system-related property and conducting exit interviews. System-related property includes hardware authentication tokens, identification cards, system administration technical manuals, keys, and building passes. Exit interviews ensure that individuals who have been terminated understand the security constraints imposed by being former employees and that proper accountability is achieved for system-related property. Security topics of interest at exit interviews can include reminding terminated individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not be possible for some terminated individuals, for example, in cases related to job abandonment, illnesses, and non-availability of supervisors. For termination actions, timely execution is essential for individuals terminated for cause. In certain situations, organizations consider disabling the system accounts of individuals that are being terminated prior to the individuals being notified. This requirement applies to reassignments or transfers of individuals when the personnel action is permanent or of such extended durations as to require protection. Organizations define the CUI protections appropriate for the types of reassignments or transfers, whether permanent or extended. Protections that may be required for transfers or reassignments to other positions within organizations include returning old and issuing new keys, identification cards, and building passes; changing system access authorizations (i.e., privileges); closing system accounts and establishing new accounts; and providing for access to official records to which individuals had access at previous work locations and in previous system accounts. | link | count: 007 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2) |
Regulatory Compliance | NIST SP 800-171 Rev. 2 (03055927-78bd-4236-86c0-f36125a10dc9) |
| NIST_SP_800-53_R4 | AC-1 | NIST_SP_800-53_R4_AC-1 | NIST SP 800-53 Rev. 4 AC-1 | Access Control | Access Control Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the access control policy and associated access controls; and b. Reviews and updates the current: 1. Access control policy [Assignment: organization-defined frequency]; and 2. Access control procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AC family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-10 | NIST_SP_800-53_R4_AC-10 | NIST SP 800-53 Rev. 4 AC-10 | Access Control | Concurrent Session Control | Shared | n/a | The information system limits the number of concurrent sessions for each [Assignment: organization-defined account and/or account type] to [Assignment: organization-defined number]. Supplemental Guidance: Organizations may define the maximum number of concurrent sessions for information system accounts globally, by account type (e.g., privileged user, non-privileged user, domain, specific application), by account, or a combination. For example, organizations may limit the number of concurrent sessions for system administrators or individuals working in particularly sensitive domains or mission-critical applications. This control addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. Control Enhancements: None. References: None. | link | count: 001 Define and enforce the limit of concurrent sessions (d8350d4c-9314-400b-288f-20ddfce04fbd) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-12 | NIST_SP_800-53_R4_AC-12 | NIST SP 800-53 Rev. 4 AC-12 | Access Control | Session Termination | Shared | n/a | The information system automatically terminates a user session after [Assignment: organization-defined conditions or trigger events requiring session disconnect]. Supplemental Guidance: This control addresses the termination of user-initiated logical sessions in contrast to SC-10 which addresses the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user’s logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, time-of-day restrictions on information system use. Related controls: SC-10, SC-23. References: None. | link | count: 001 Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-12(1) | NIST_SP_800-53_R4_AC-12(1) | NIST SP 800-53 Rev. 4 AC-12 (1) | Access Control | User-Initiated Logouts / Message Displays | Shared | n/a | The information system: (a) Provides a logout capability for user-initiated communications sessions whenever authentication is used to gain access to [Assignment: organization-defined information resources]; and (b) Displays an explicit logout message to users indicating the reliable termination of authenticated communications sessions. Supplemental Guidance: Information resources to which users gain access via authentication include, for example, local workstations, databases, and password-protected websites/web- based services. Logout messages for web page access, for example, can be displayed after authenticated sessions have been terminated. However, for some types of interactive sessions including, for example, file transfer protocol (FTP) sessions, information systems typically send logout messages as final messages prior to terminating sessions. | link | count: 002 Display an explicit logout message (0471c6b7-1588-701c-2713-1fade73b75f6), Provide the logout capability (db580551-0b3c-4ea1-8a4c-4cdb5feb340f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-14 | NIST_SP_800-53_R4_AC-14 | NIST SP 800-53 Rev. 4 AC-14 | Access Control | Permitted Actions Without Identification Or Authentication | Shared | n/a | The organization: a. Identifies [Assignment: organization-defined user actions] that can be performed on the information system without identification or authentication consistent with organizational missions/business functions; and b. Documents and provides supporting rationale in the security plan for the information system, user actions not requiring identification or authentication. Supplemental Guidance: This control addresses situations in which organizations determine that no identification or authentication is required in organizational information systems. Organizations may allow a limited number of user actions without identification or authentication including, for example, when individuals access public websites or other publicly accessible federal information systems, when individuals use mobile phones to receive calls, or when facsimiles are received. Organizations also identify actions that normally require identification or authentication but may under certain circumstances (e.g., emergencies), allow identification or authentication mechanisms to be bypassed. Such bypasses may occur, for example, via a software-readable physical switch that commands bypass of the logon functionality and is protected from accidental or unmonitored use. This control does not apply to situations where identification and authentication have already occurred and are not repeated, but rather to situations where identification and authentication have not yet occurred. Organizations may decide that there are no user actions that can be performed on organizational information systems without identification and authentication and thus, the values for assignment statements can be none. Related controls: CP-2, IA-2. Control Enhancements: None. (1) PERMITTED ACTIONS WITHOUT IDENTIFICATION OR AUTHENTICATION | NECESSARY USES [Withdrawn: Incorporated into AC-14]. References: None. | link | count: 001 Identify actions allowed without authentication (92a7591f-73b3-1173-a09c-a08882d84c70) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-16 | NIST_SP_800-53_R4_AC-16 | NIST SP 800-53 Rev. 4 AC-16 | Access Control | Security Attributes | Customer | n/a | The organization: a. Provides the means to associate [Assignment: organization-defined types of security attributes] having [Assignment: organization-defined security attribute values] with information in storage, in process, and/or in transmission; b. Ensures that the security attribute associations are made and retained with the information; c. Establishes the permitted [Assignment: organization-defined security attributes] for [Assignment: organization-defined information systems]; and d. Determines the permitted [Assignment: organization-defined values or ranges] for each of the established security attributes. | link | count: 002 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-17 | NIST_SP_800-53_R4_AC-17 | NIST SP 800-53 Rev. 4 AC-17 | Access Control | Remote Access | Shared | n/a | The organization: a. Establishes and documents usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and b. Authorizes remote access to the information system prior to allowing such connections. Supplemental Guidance: Remote access is access to organizational information systems by users (or processes acting on behalf of users) communicating through external networks (e.g., the Internet). Remote access methods include, for example, dial-up, broadband, and wireless. Organizations often employ encrypted virtual private networks (VPNs) to enhance confidentiality and integrity over remote connections. The use of encrypted VPNs does not make the access non-remote; however, the use of VPNs, when adequately provisioned with appropriate security controls (e.g., employing appropriate encryption techniques for confidentiality and integrity protection) may provide sufficient assurance to the organization that it can effectively treat such connections as internal networks. Still, VPN connections traverse external networks, and the encrypted VPN does not enhance the availability of remote connections. Also, VPNs with encrypted tunnels can affect the organizational capability to adequately monitor network communications traffic for malicious code. Remote access controls apply to information systems other than public web servers or systems designed for public access. This control addresses authorization prior to allowing remote access without specifying the formats for such authorization. While organizations may use interconnection security agreements to authorize remote access connections, such agreements are not required by this control. Enforcing access restrictions for remote connections is addressed in AC-3. Related controls: AC-2, AC-3, AC-18, AC-19, AC-20, CA-3, CA-7, CM-8, IA-2, IA-3, IA-8, MA-4, PE-17, PL-4, SC-10, SI-4. References: NIST Special Publications 800-46, 800-77, 800-113, 800-114, 800-121. | link | count: 041 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-17(1) | NIST_SP_800-53_R4_AC-17(1) | NIST SP 800-53 Rev. 4 AC-17 (1) | Access Control | Automated Monitoring / Control | Shared | n/a | The information system monitors and controls remote access methods. Supplemental Guidance: Automated monitoring and control of remote access sessions allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote users on a variety of information system components (e.g., servers, workstations, notebook computers, smart phones, and tablets). Related controls: AU-2, AU-12. | link | count: 037 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-17(2) | NIST_SP_800-53_R4_AC-17(2) | NIST SP 800-53 Rev. 4 AC-17 (2) | Access Control | Protection Of Confidentiality / Integrity Using Encryption | Shared | n/a | The information system implements cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions. Supplemental Guidance: The encryption strength of mechanism is selected based on the security categorization of the information. Related controls: SC-8, SC-12, SC-13. | link | count: 002 Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-17(3) | NIST_SP_800-53_R4_AC-17(3) | NIST SP 800-53 Rev. 4 AC-17 (3) | Access Control | Managed Access Control Points | Shared | n/a | The information system routes all remote accesses through [Assignment: organization-defined number] managed network access control points. Supplemental Guidance: Limiting the number of access control points for remote accesses reduces the attack surface for organizations. Organizations consider the Trusted Internet Connections (TIC) initiative requirements for external network connections. Related control: SC-7. | link | count: 001 Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-17(4) | NIST_SP_800-53_R4_AC-17(4) | NIST SP 800-53 Rev. 4 AC-17 (4) | Access Control | Privileged Commands / Access | Shared | n/a | The organization: (a) Authorizes the execution of privileged commands and access to security-relevant information via remote access only for [Assignment: organization-defined needs]; and (b) Documents the rationale for such access in the security plan for the information system. Supplemental Guidance: Related control: AC-6. | link | count: 005 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Authorize remote access to privileged commands (01c387ea-383d-4ca9-295a-977fab516b03), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-17(9) | NIST_SP_800-53_R4_AC-17(9) | NIST SP 800-53 Rev. 4 AC-17 (9) | Access Control | Disconnect / Disable Access | Shared | n/a | The organization provides the capability to expeditiously disconnect or disable remote access to the information system within [Assignment: organization-defined time period]. Supplemental Guidance: This control enhancement requires organizations to have the capability to rapidly disconnect current users remotely accessing the information system and/or disable further remote access. The speed of disconnect or disablement varies based on the criticality of missions/business functions and the need to eliminate immediate or future remote access to organizational information systems. | link | count: 001 Provide capability to disconnect or disable remote access (4edaca8c-0912-1ac5-9eaa-6a1057740fae) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-18 | NIST_SP_800-53_R4_AC-18 | NIST SP 800-53 Rev. 4 AC-18 | Access Control | Wireless Access | Shared | n/a | The organization: a. Establishes usage restrictions, configuration/connection requirements, and implementation guidance for wireless access; and b. Authorizes wireless access to the information system prior to allowing such connections. Supplemental Guidance: Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual authentication. Related controls: AC-2, AC-3, AC-17, AC-19, CA-3, CA-7, CM-8, IA-2, IA-3, IA-8, PL-4, SI-4. References: NIST Special Publications 800-48, 800-94, 800-97. | link | count: 002 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-18(1) | NIST_SP_800-53_R4_AC-18(1) | NIST SP 800-53 Rev. 4 AC-18 (1) | Access Control | Authentication And Encryption | Shared | n/a | The information system protects wireless access to the system using authentication of [Selection (one or more): users; devices] and encryption. Supplemental Guidance: Related controls: SC-8, SC-13. | link | count: 003 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-19 | NIST_SP_800-53_R4_AC-19 | NIST SP 800-53 Rev. 4 AC-19 | Access Control | Access Control For Mobile Devices | Shared | n/a | The organization: a. Establishes usage restrictions, configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices; and b. Authorizes the connection of mobile devices to organizational information systems. Supplemental Guidance: A mobile device is a computing device that: (i) has a small form factor such that it can easily be carried by a single individual; (ii) is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); (iii) possesses local, non- removable or removable data storage; and (iv) includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones, E-readers, and tablets. Mobile devices are typically associated with a single individual and the device is usually in close proximity to the individual; however, the degree of proximity can vary depending upon on the form factor and size of the device. The processing, storage, and transmission capability of the mobile device may be comparable to or merely a subset of desktop systems, depending upon the nature and intended purpose of the device. Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different classes/types of such devices. Usage restrictions and specific implementation guidance for mobile devices include, for example, configuration management, device identification and authentication, implementation of mandatory protective software (e.g., malicious code detection, firewall), scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting primary operating system (and possibly other resident software) integrity checks, and disabling unnecessary hardware (e.g., wireless, infrared). Organizations are cautioned that the need to provide adequate security for mobile devices goes beyond the requirements in this control. Many safeguards and countermeasures for mobile devices are reflected in other security controls in the catalog allocated in the initial control baselines as starting points for the development of security plans and overlays using the tailoring process. There may also be some degree of overlap in the requirements articulated by the security controls within the different families of controls. AC-20 addresses mobile devices that are not organization-controlled. Related controls: AC-3, AC-7, AC-18, AC-20, CA-9, CM-2, IA-2, IA-3, MP-2, MP-4, MP-5, PL-4, SC-7, SC-43, SI-3, SI-4. References: OMB Memorandum 06-16; NIST Special Publications 800-114, 800-124, 800-164. | link | count: 001 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-19(5) | NIST_SP_800-53_R4_AC-19(5) | NIST SP 800-53 Rev. 4 AC-19 (5) | Access Control | Full Device / Container-Based Encryption | Shared | n/a | The organization employs [Selection: full-device encryption; container encryption] to protect the confidentiality and integrity of information on [Assignment: organization-defined mobile devices]. Supplemental Guidance: Container-based encryption provides a more fine-grained approach to the encryption of data/information on mobile devices, including for example, encrypting selected data structures such as files, records, or fields. Related controls: MP-5, SC-13, SC-28. References: OMB Memorandum 06-16; NIST Special Publications 800-114, 800-124, 800-164. | link | count: 002 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2 | NIST_SP_800-53_R4_AC-2 | NIST SP 800-53 Rev. 4 AC-2 | Access Control | Account Management | Shared | n/a | The organization: a. Identifies and selects the following types of information system accounts to support organizational missions/business functions: [Assignment: organization-defined information system account types]; b. Assigns account managers for information system accounts; c. Establishes conditions for group and role membership; d. Specifies authorized users of the information system, group and role membership, and access authorizations (i.e., privileges) and other attributes (as required) for each account; e. Requires approvals by [Assignment: organization-defined personnel or roles] for requests to create information system accounts; f. Creates, enables, modifies, disables, and removes information system accounts in accordance with [Assignment: organization-defined procedures or conditions]; g. Monitors the use of, information system accounts; h. Notifies account managers: 1. When accounts are no longer required; 2. When users are terminated or transferred; and 3. When individual information system usage or need-to-know changes; i. Authorizes access to the information system based on: 1. A valid access authorization; 2. Intended system usage; and 3. Other attributes as required by the organization or associated missions/business functions; j. Reviews accounts for compliance with account management requirements [Assignment: organization-defined frequency]; and k. Establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group. Supplemental Guidance: Information system account types include individual, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service. Some of the account management requirements listed above can be implemented by organizational information systems. The identification of authorized users of the information system and the specification of access privileges reflects the requirements in other security controls in the security plan. Users requiring administrative privileges on information system accounts receive additional scrutiny by appropriate organizational personnel (e.g., system owner, mission/business owner, or chief information security officer) responsible for approving such accounts and privileged access. Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. Other attributes required for authorizing access include, for example, restrictions on time-of-day, day-of-week, and point-of-origin. In defining other account attributes, organizations consider system-related requirements (e.g., scheduled maintenance, system upgrades) and mission/business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements). Failure to consider these factors could affect information system availability. Temporary and emergency accounts are accounts intended for short-term use. Organizations establish temporary accounts as a part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. Organizations establish emergency accounts in response to crisis situations and with the need for rapid account activation. Therefore, emergency account activation may bypass normal account authorization processes. Emergency and temporary accounts are not to be confused with infrequently used accounts (e.g., local logon accounts used for special tasks defined by organizations or when network resources are unavailable). Such accounts remain available and are not subject to automatic disabling or removal dates. Conditions for disabling or deactivating accounts include, for example: (i) when shared/group, emergency, or temporary accounts are no longer required; or (ii) when individuals are transferred or terminated. Some types of information system accounts may require specialized training. Related controls: AC-3, AC-4, AC-5, AC-6, AC-10, AC-17, AC-19, AC-20, AU-9, IA-2, IA-4, IA-5, IA-8, CM-5, CM-6, CM-11, MA-3, MA-4, MA-5, PL-4, SC-13. References: None. | link | count: 025 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, General, Regulatory Compliance, Security Center, Service Fabric, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(1) | NIST_SP_800-53_R4_AC-2(1) | NIST SP 800-53 Rev. 4 AC-2 (1) | Access Control | Automated System Account Management | Shared | n/a | The organization employs automated mechanisms to support the management of information system accounts. Supplemental Guidance: The use of automated mechanisms can include, for example: using email or text messaging to automatically notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using telephonic notification to report atypical system account usage. | link | count: 007 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(10) | NIST_SP_800-53_R4_AC-2(10) | NIST SP 800-53 Rev. 4 AC-2 (10) | Access Control | Shared / Group Account Credential Termination | Shared | n/a | The information system terminates shared/group account credentials when members leave the group. | link | count: 001 Terminate customer controlled account credentials (76d66b5c-85e4-93f5-96a5-ebb2fad61dc6) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(11) | NIST_SP_800-53_R4_AC-2(11) | NIST SP 800-53 Rev. 4 AC-2 (11) | Access Control | Usage Conditions | Shared | n/a | The information system enforces [Assignment: organization-defined circumstances and/or usage conditions] for [Assignment: organization-defined information system accounts]. Supplemental Guidance: Organizations can describe the specific conditions or circumstances under which information system accounts can be used, for example, by restricting usage to certain days of the week, time of day, or specific durations of time. | link | count: 001 Enforce appropriate usage of all accounts (fd81a1b3-2d7a-107c-507e-29b87d040c19) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(12) | NIST_SP_800-53_R4_AC-2(12) | NIST SP 800-53 Rev. 4 AC-2 (12) | Access Control | Account Monitoring / Atypical Usage | Shared | n/a | The organization: (a) Monitors information system accounts for [Assignment: organization-defined atypical use]; and (b) Reports atypical usage of information system accounts to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Atypical usage includes, for example, accessing information systems at certain times of the day and from locations that are not consistent with the normal usage patterns of individuals working in organizations. Related control: CA-7. | link | count: 013 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81) |
Kubernetes, Regulatory Compliance, Security Center, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(13) | NIST_SP_800-53_R4_AC-2(13) | NIST SP 800-53 Rev. 4 AC-2 (13) | Access Control | Disable Accounts For High-Risk Individuals | Shared | n/a | The organization disables accounts of users posing a significant risk within [Assignment: organization-defined time period] of discovery of the risk. Supplemental Guidance: Users posing a significant risk to organizations include individuals for whom reliable evidence or intelligence indicates either the intention to use authorized access to information systems to cause harm or through whom adversaries will cause harm. Harm includes potential adverse impacts to organizational operations and assets, individuals, other organizations, or the Nation. Close coordination between authorizing officials, information system administrators, and human resource managers is essential in order for timely execution of this control enhancement. Related control: PS-4. | link | count: 001 Disable user accounts posing a significant risk (22c16ae4-19d0-29cb-422f-cb44061180ee) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(3) | NIST_SP_800-53_R4_AC-2(3) | NIST SP 800-53 Rev. 4 AC-2 (3) | Access Control | Disable Inactive Accounts | Shared | n/a | The information system automatically disables inactive accounts after [Assignment: organization-defined time period]. | link | count: 002 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(4) | NIST_SP_800-53_R4_AC-2(4) | NIST SP 800-53 Rev. 4 AC-2 (4) | Access Control | Automated Audit Actions | Shared | n/a | The information system automatically audits account creation, modification, enabling, disabling, and removal actions, and notifies [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Related controls: AU-2, AU-12. | link | count: 005 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(5) | NIST_SP_800-53_R4_AC-2(5) | NIST SP 800-53 Rev. 4 AC-2 (5) | Access Control | Inactivity Logout | Shared | n/a | The organization requires that users log out when [Assignment: organization-defined time-period of expected inactivity or description of when to log out]. Supplemental Guidance: Related control: SC-23. | link | count: 001 Define and enforce inactivity log policy (2af4640d-11a6-a64b-5ceb-a468f4341c0c) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(7) | NIST_SP_800-53_R4_AC-2(7) | NIST SP 800-53 Rev. 4 AC-2 (7) | Access Control | Role-Based Schemes | Shared | n/a | The organization: (a) Establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles; (b) Monitors privileged role assignments; and (c) Takes [Assignment: organization-defined actions] when privileged role assignments are no longer appropriate. Supplemental Guidance: Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. These privileged roles include, for example, key management, account management, network and system administration, database administration, and web administration. | link | count: 010 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Azure Ai Services, General, Regulatory Compliance, Service Fabric, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-2(9) | NIST_SP_800-53_R4_AC-2(9) | NIST SP 800-53 Rev. 4 AC-2 (9) | Access Control | Restrictions On Use Of Shared Groups / Accounts | Shared | n/a | The organization only permits the use of shared/group accounts that meet [Assignment: organization-defined conditions for establishing shared/group accounts]. | link | count: 001 Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-20 | NIST_SP_800-53_R4_AC-20 | NIST SP 800-53 Rev. 4 AC-20 | Access Control | Use Of External Information Systems | Shared | n/a | The organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to: a. Access the information system from external information systems; and b. Process, store, or transmit organization-controlled information using external information systems. Supplemental Guidance: External information systems are information systems or components of information systems that are outside of the authorization boundary established by organizations and for which organizations typically have no direct supervision and authority over the application of required security controls or the assessment of control effectiveness. External information systems include, for example: (i) personally owned information systems/devices (e.g., notebook computers, smart phones, tablets, personal digital assistants); (ii) privately owned computing and communications devices resident in commercial or public facilities (e.g., hotels, train stations, convention centers, shopping malls, or airports); (iii) information systems owned or controlled by nonfederal governmental organizations; and (iv) federal information systems that are not owned by, operated by, or under the direct supervision and authority of organizations. This control also addresses the use of external information systems for the processing, storage, or transmission of organizational information, including, for example, accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational information systems. For some external information systems (i.e., information systems operated by other federal agencies, including organizations subordinate to those agencies), the trust relationships that have been established between those organizations and the originating organization may be such, that no explicit terms and conditions are required. Information systems within these organizations would not be considered external. These situations occur when, for example, there are pre-existing sharing/trust agreements (either implicit or explicit) established between federal agencies or organizations subordinate to those agencies, or when such trust agreements are specified by applicable laws, Executive Orders, directives, or policies. Authorized individuals include, for example, organizational personnel, contractors, or other individuals with authorized access to organizational information systems and over which organizations have the authority to impose rules of behavior with regard to system access. Restrictions that organizations impose on authorized individuals need not be uniform, as those restrictions may vary depending upon the trust relationships between organizations. Therefore, organizations may choose to impose different security restrictions on contractors than on state, local, or tribal governments. This control does not apply to the use of external information systems to access public interfaces to organizational information systems (e.g., individuals accessing federal information through www.usa.gov). Organizations establish terms and conditions for the use of external information systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum: types of applications that can be accessed on organizational information systems from external information systems; and the highest security category of information that can be processed, stored, or transmitted on external information systems. If terms and conditions with the owners of external information systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems. Related controls: AC-3, AC-17, AC-19, CA-3, PL-4, SA-9. References: FIPS Publication 199. | link | count: 002 Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-20(1) | NIST_SP_800-53_R4_AC-20(1) | NIST SP 800-53 Rev. 4 AC-20 (1) | Access Control | Limits On Authorized Use | Shared | n/a | The organization permits authorized individuals to use an external information system to access the information system or to process, store, or transmit organization-controlled information only when the organization: (a) Verifies the implementation of required security controls on the external system as specified in the organization’s information security policy and security plan; or (b) Retains approved information system connection or processing agreements with the organizational entity hosting the external information system. Supplemental Guidance: This control enhancement recognizes that there are circumstances where individuals using external information systems (e.g., contractors, coalition partners) need to access organizational information systems. In those situations, organizations need confidence that the external information systems contain the necessary security safeguards (i.e., security controls), so as not to compromise, damage, or otherwise harm organizational information systems. Verification that the required security controls have been implemented can be achieved, for example, by third-party, independent assessments, attestations, or other means, depending on the confidence level required by organizations. Related control: CA-2. | link | count: 001 Verify security controls for external information systems (dc7ec756-221c-33c8-0afe-c48e10e42321) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-20(2) | NIST_SP_800-53_R4_AC-20(2) | NIST SP 800-53 Rev. 4 AC-20 (2) | Access Control | Portable Storage Devices | Shared | n/a | The organization [Selection: restricts; prohibits] the use of organization-controlled portable storage devices by authorized individuals on external information systems. Supplemental Guidance: Limits on the use of organization-controlled portable storage devices in external information systems include, for example, complete prohibition of the use of such devices or restrictions on how the devices may be used and under what conditions the devices may be used. | link | count: 003 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-21 | NIST_SP_800-53_R4_AC-21 | NIST SP 800-53 Rev. 4 AC-21 | Access Control | Information Sharing | Shared | n/a | The organization: a. Facilitates information sharing by enabling authorized users to determine whether access authorizations assigned to the sharing partner match the access restrictions on the information for [Assignment: organization-defined information sharing circumstances where user discretion is required]; and b. Employs [Assignment: organization-defined automated mechanisms or manual processes] to assist users in making information sharing/collaboration decisions. Supplemental Guidance: This control applies to information that may be restricted in some manner (e.g., privileged medical information, contract-sensitive information, proprietary information, personally identifiable information, classified information related to special access programs or compartments) based on some formal or administrative determination. Depending on the particular information-sharing circumstances, sharing partners may be defined at the individual, group, or organizational level. Information may be defined by content, type, security category, or special access program/compartment. Related control: AC-3. References: None. | link | count: 002 Automate information sharing decisions (e54901fe-42c2-7f3b-3c5f-327aa5320a69), Facilitate information sharing (a44c9fba-43f8-4b7b-7ee6-db52c96b4366) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-22 | NIST_SP_800-53_R4_AC-22 | NIST SP 800-53 Rev. 4 AC-22 | Access Control | Publicly Accessible Content | Shared | n/a | The organization: a. Designates individuals authorized to post information onto a publicly accessible information system; b. Trains authorized individuals to ensure that publicly accessible information does not contain nonpublic information; c. Reviews the proposed content of information prior to posting onto the publicly accessible information system to ensure that nonpublic information is not included; and d. Reviews the content on the publicly accessible information system for nonpublic information [Assignment: organization-defined frequency] and removes such information, if discovered. Supplemental Guidance: In accordance with federal laws, Executive Orders, directives, policies, regulations, standards, and/or guidance, the general public is not authorized access to nonpublic information (e.g., information protected under the Privacy Act and proprietary information). This control addresses information systems that are controlled by the organization and accessible to the general public, typically without identification or authentication. The posting of information on non-organization information systems is covered by organizational policy. Related controls: AC-3, AC-4, AT-2, AT-3, AU-13. Control Enhancements: None. References: None. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Review content prior to posting publicly accessible information (9e3c505e-7aeb-2096-3417-b132242731fc), Review publicly accessible content for nonpublic information (b5244f81-6cab-3188-2412-179162294996), Train personnel on disclosure of nonpublic information (97f0d974-1486-01e2-2088-b888f46c0589) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-3 | NIST_SP_800-53_R4_AC-3 | NIST SP 800-53 Rev. 4 AC-3 | Access Control | Access Enforcement | Shared | n/a | The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. Supplemental Guidance: Access control policies (e.g., identity-based policies, role-based policies, attribute-based policies) and access enforcement mechanisms (e.g., access control lists, access control matrices, cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, domains) in information systems. In addition to enforcing authorized access at the information system level and recognizing that information systems can host many applications and services in support of organizational missions and business operations, access enforcement mechanisms can also be employed at the application and service level to provide increased information security. Related controls: AC-2, AC-4, AC-5, AC-6, AC-16, AC-17, AC-18, AC-19, AC-20, AC-21, AC-22, AU-9, CM-5, CM-6, CM-11, MA-3, MA-4, MA-5, PE-3. References: None. | link | count: 021 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
App Service, Azure Ai Services, Compute, Guest Configuration, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-3(7) | NIST_SP_800-53_R4_AC-3(7) | NIST SP 800-53 Rev. 4 AC-3 (7) | Access Control | Role-based Access Control | Customer | n/a | The information system enforces a role-based access control policy over defined subjects and objects and controls access based upon [Assignment: organization-defined roles and users authorized to assume such roles]. | link | count: 001 Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-4 | NIST_SP_800-53_R4_AC-4 | NIST SP 800-53 Rev. 4 AC-4 | Access Control | Information Flow Enforcement | Shared | n/a | The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems based on [Assignment: organization-defined information flow control policies]. Supplemental Guidance: Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. Flow control restrictions include, for example, keeping export-controlled information from being transmitted in the clear to the Internet, blocking outside traffic that claims to be from within the organization, restricting web requests to the Internet that are not from the internal web proxy server, and limiting information transfers between organizations based on data structures and content. Transferring information between information systems representing different security domains with different security policies introduces risk that such transfers violate one or more domain security policies. In such situations, information owners/stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes, for example: (i) prohibiting information transfers between interconnected systems (i.e., allowing access only); (ii) employing hardware mechanisms to enforce one-way information flows; and (iii) implementing trustworthy regarding mechanisms to reassign security attributes and security labels. Organizations commonly employ information flow control policies and enforcement mechanisms to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path. Enforcement occurs, for example, in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, firewalls) that employ rule sets or establish configuration settings that restrict information system services, provide a packet-filtering capability based on header information, or message- filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Organizations also consider the trustworthiness of filtering/inspection mechanisms (i.e., hardware, firmware, and software components) that are critical to information flow enforcement. Control enhancements 3 through 22 primarily address cross-domain solution needs which focus on more advanced filtering techniques, in-depth analysis, and stronger flow enforcement mechanisms implemented in cross-domain products, for example, high-assurance guards. Such capabilities are generally not available in commercial off-the-shelf information technology products. Related controls: AC-3, AC-17, AC-19, AC-21, CM-6, CM-7, SA-8, SC-2, SC-5, SC-7, SC-18. References: None. | link | count: 053 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, API Management, App Configuration, App Service, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Regulatory Compliance, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-4(21) | NIST_SP_800-53_R4_AC-4(21) | NIST SP 800-53 Rev. 4 AC-4 (21) | Access Control | Physical / Logical Separation Of Information Flows | Shared | n/a | The information system separates information flows logically or physically using [Assignment: organization-defined mechanisms and/or techniques] to accomplish [Assignment: organization- defined required separations by types of information]. Supplemental Guidance: Enforcing the separation of information flows by type can enhance protection by ensuring that information is not commingled while in transit and by enabling flow control by transmission paths perhaps not otherwise achievable. Types of separable information include, for example, inbound and outbound communications traffic, service requests and responses, and information of differing security categories. | link | count: 004 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-4(3) | NIST_SP_800-53_R4_AC-4(3) | NIST SP 800-53 Rev. 4 AC-4 (3) | Access Control | Dynamic Information Flow Control | Customer | n/a | The information system enforces dynamic information flow control based on [Assignment: organization-defined policies]. | link | count: 002 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-4(8) | NIST_SP_800-53_R4_AC-4(8) | NIST SP 800-53 Rev. 4 AC-4 (8) | Access Control | Security Policy Filters | Shared | n/a | The information system enforces information flow control using [Assignment: organization-defined security policy filters] as a basis for flow control decisions for [Assignment: organization-defined information flows]. Supplemental Guidance: Organization-defined security policy filters can address data structures and content. For example, security policy filters for data structures can check for maximum file lengths, maximum field sizes, and data/file types (for structured and unstructured data). Security policy filters for data content can check for specific words (e.g., dirty/clean word filters), enumerated values or data value ranges, and hidden content. Structured data permits the interpretation of data content by applications. Unstructured data typically refers to digital information without a particular data structure or with a data structure that does not facilitate the development of rule sets to address the particular sensitivity of the information conveyed by the data or the associated flow enforcement decisions. Unstructured data consists of: (i) bitmap objects that are inherently non language-based (i.e., image, video, or audio files); and (ii) textual objects that are based on written or printed languages (e.g., commercial off-the- shelf word processing documents, spreadsheets, or emails). Organizations can implement more than one security policy filter to meet information flow control objectives (e.g., employing clean word lists in conjunction with dirty word lists may help to reduce false positives). | link | count: 001 Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-5 | NIST_SP_800-53_R4_AC-5 | NIST SP 800-53 Rev. 4 AC-5 | Access Control | Separation Of Duties | Shared | n/a | The organization: a. Separates [Assignment: organization-defined duties of individuals]; b. Documents separation of duties of individuals; and c. Defines information system access authorizations to support separation of duties. Supplemental Guidance: Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes, for example: (i) dividing mission functions and information system support functions among different individuals and/or roles; (ii) conducting information system support functions with different individuals (e.g., system management, programming, configuration management, quality assurance and testing, and network security); and (iii) ensuring security personnel administering access control functions do not also administer audit functions. Related controls: AC-3, AC-6, PE-3, PE-4, PS-2. Control Enhancements: None. References: None. | link | count: 004 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-6 | NIST_SP_800-53_R4_AC-6 | NIST SP 800-53 Rev. 4 AC-6 | Access Control | Least Privilege | Shared | n/a | The organization employs the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions. Supplemental Guidance: Organizations employ least privilege for specific duties and information systems. The principle of least privilege is also applied to information system processes, ensuring that the processes operate at privilege levels no higher than necessary to accomplish required organizational missions/business functions. Organizations consider the creation of additional processes, roles, and information system accounts as necessary, to achieve least privilege. Organizations also apply least privilege to the development, implementation, and operation of organizational information systems. Related controls: AC-2, AC-3, AC-5, CM-6, CM-7, PL-2. References: None. | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f) |
General, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-6(1) | NIST_SP_800-53_R4_AC-6(1) | NIST SP 800-53 Rev. 4 AC-6 (1) | Access Control | Authorize Access To Security Functions | Shared | n/a | The organization explicitly authorizes access to [Assignment: organization-defined security functions (deployed in hardware, software, and firmware) and security-relevant information]. Supplemental Guidance: Security functions include, for example, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Security-relevant information includes, for example, filtering rules for routers/firewalls, cryptographic key management information, configuration parameters for security services, and access control lists. Explicitly authorized personnel include, for example, security administrators, system and network administrators, system security officers, system maintenance personnel, system programmers, and other privileged users. Related controls: AC-17, AC-18, AC-19. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-6(5) | NIST_SP_800-53_R4_AC-6(5) | NIST SP 800-53 Rev. 4 AC-6 (5) | Access Control | Privileged Accounts | Shared | n/a | The organization restricts privileged accounts on the information system to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from having access to privileged information/functions. Organizations may differentiate in the application of this control enhancement between allowed privileges for local accounts and for domain accounts provided organizations retain the ability to control information system configurations for key security parameters and as otherwise necessary to sufficiently mitigate risk. Related control: CM-6. | link | count: 001 Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-6(7) | NIST_SP_800-53_R4_AC-6(7) | NIST SP 800-53 Rev. 4 AC-6 (7) | Access Control | Review Of User Privileges | Shared | n/a | The organization: (a) Reviews [Assignment: organization-defined frequency] the privileges assigned to [Assignment: organization-defined roles or classes of users] to validate the need for such privileges; and (b) Reassigns or removes privileges, if necessary, to correctly reflect organizational mission/business needs. Supplemental Guidance: The need for certain assigned user privileges may change over time reflecting changes in organizational missions/business function, environments of operation, technologies, or threat. Periodic review of assigned user privileges is necessary to determine if the rationale for assigning such privileges remains valid. If the need cannot be revalidated, organizations take appropriate corrective actions. Related control: CA-7. | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
General, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-6(8) | NIST_SP_800-53_R4_AC-6(8) | NIST SP 800-53 Rev. 4 AC-6 (8) | Access Control | Privilege Levels For Code Execution | Shared | n/a | The information system prevents [Assignment: organization-defined software] from executing at higher privilege levels than users executing the software. Supplemental Guidance: In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. | link | count: 001 Enforce software execution privileges (68d2e478-3b19-23eb-1357-31b296547457) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-6(9) | NIST_SP_800-53_R4_AC-6(9) | NIST SP 800-53 Rev. 4 AC-6 (9) | Access Control | Auditing Use Of Privileged Functions | Shared | n/a | The information system audits the execution of privileged functions. Supplemental Guidance: Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat (APT). Related control: AU-2. | link | count: 006 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AC-7 | NIST_SP_800-53_R4_AC-7 | NIST SP 800-53 Rev. 4 AC-7 | Access Control | Unsuccessful Logon Attempts | Shared | n/a | The information system: a. Enforces a limit of [Assignment: organization-defined number] consecutive invalid logon attempts by a user during a [Assignment: organization-defined time period]; and b. Automatically [Selection: locks the account/node for an [Assignment: organization-defined time period]; locks the account/node until released by an administrator; delays next logon prompt according to [Assignment: organization-defined delay algorithm]] when the maximum number of unsuccessful attempts is exceeded. Supplemental Guidance: This control applies regardless of whether the logon occurs via a local or network connection. Due to the potential for denial of service, automatic lockouts initiated by information systems are usually temporary and automatically release after a predetermined time period established by organizations. If a delay algorithm is selected, organizations may choose to employ different algorithms for different information system components based on the capabilities of those components. Responses to unsuccessful logon attempts may be implemented at both the operating system and the application levels. Related controls: AC-2, AC-9, AC-14, IA-5. References: None. | link | count: 001 Enforce a limit of consecutive failed login attempts (b4409bff-2287-8407-05fd-c73175a68302) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AT-1 | NIST_SP_800-53_R4_AT-1 | NIST SP 800-53 Rev. 4 AT-1 | Awareness And Training | Security Awareness And Training Policy Andprocedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A security awareness and training policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the security awareness and training policy and associated security awareness and training controls; and b. Reviews and updates the current: 1. Security awareness and training policy [Assignment: organization-defined frequency]; and 2. Security awareness and training procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AT family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-16, 800-50, 800-100. | link | count: 002 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AT-2 | NIST_SP_800-53_R4_AT-2 | NIST SP 800-53 Rev. 4 AT-2 | Awareness And Training | Security Awareness Training | Shared | n/a | The organization provides basic security awareness training to information system users (including managers, senior executives, and contractors): a. As part of initial training for new users; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Organizations determine the appropriate content of security awareness training and security awareness techniques based on the specific organizational requirements and the information systems to which personnel have authorized access. The content includes a basic understanding of the need for information security and user actions to maintain security and to respond to suspected security incidents. The content also addresses awareness of the need for operations security. Security awareness techniques can include, for example, displaying posters, offering supplies inscribed with security reminders, generating email advisories/notices from senior organizational officials, displaying logon screen messages, and conducting information security awareness events. Related controls: AT-3, AT-4, PL-4. References: C.F.R. Part 5 Subpart C (5 C.F.R. 930.301); Executive Order 13587; NIST Special Publication 800-50. | link | count: 003 Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AT-2(2) | NIST_SP_800-53_R4_AT-2(2) | NIST SP 800-53 Rev. 4 AT-2 (2) | Awareness And Training | Insider Threat | Shared | n/a | The organization includes security awareness training on recognizing and reporting potential indicators of insider threat. Supplemental Guidance: Potential indicators and possible precursors of insider threat can include behaviors such as inordinate, long-term job dissatisfaction, attempts to gain access to information not required for job performance, unexplained access to financial resources, bullying or sexual harassment of fellow employees, workplace violence, and other serious violations of organizational policies, procedures, directives, rules, or practices. Security awareness training includes how to communicate employee and management concerns regarding potential indicators of insider threat through appropriate organizational channels in accordance with established organizational policies and procedures. Related controls: PL-4, PM-12, PS-3, PS-6. References: C.F.R. Part 5 Subpart C (5 C.F.R 930.301); Executive Order 13587; NIST Special Publication 800-50. | link | count: 001 Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AT-3 | NIST_SP_800-53_R4_AT-3 | NIST SP 800-53 Rev. 4 AT-3 | Awareness And Training | Role-Based Security Training | Shared | n/a | The organization provides role-based security training to personnel with assigned security roles and responsibilities: a. Before authorizing access to the information system or performing assigned duties; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Organizations determine the appropriate content of security training based on the assigned roles and responsibilities of individuals and the specific security requirements of organizations and the information systems to which personnel have authorized access. In addition, organizations provide enterprise architects, information system developers, software developers, acquisition/procurement officials, information system managers, system/network administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation activities, security control assessors, and other personnel having access to system-level software, adequate security-related technical training specifically tailored for their assigned duties. Comprehensive role-based training addresses management, operational, and technical roles and responsibilities covering physical, personnel, and technical safeguards and countermeasures. Such training can include for example, policies, procedures, tools, and artifacts for the organizational security roles defined. Organizations also provide the training necessary for individuals to carry out their responsibilities related to operations and supply chain security within the context of organizational information security programs. Role-based security training also applies to contractors providing services to federal agencies. Related controls: AT-2, AT-4, PL-4, PS-7, SA-3, SA-12, SA-16. References: C.F.R. Part 5 Subpart C (5 C.F.R. 930.301); NIST Special Publications 800-16, 800-50. | link | count: 003 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AT-3(3) | NIST_SP_800-53_R4_AT-3(3) | NIST SP 800-53 Rev. 4 AT-3 (3) | Awareness And Training | Practical Exercises | Shared | n/a | The organization includes practical exercises in security training that reinforce training objectives. Supplemental Guidance: Practical exercises may include, for example, security training for software developers that includes simulated cyber attacks exploiting common software vulnerabilities (e.g., buffer overflows), or spear/whale phishing attacks targeted at senior leaders/executives. These types of practical exercises help developers better understand the effects of such vulnerabilities and appreciate the need for security coding standards and processes. | link | count: 001 Provide role-based practical exercises (d041726f-00e0-41ca-368c-b1a122066482) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AT-3(4) | NIST_SP_800-53_R4_AT-3(4) | NIST SP 800-53 Rev. 4 AT-3 (4) | Awareness And Training | Suspicious Communications And Anomalous System Behavior | Shared | n/a | The organization provides training to its personnel on [Assignment: organization-defined indicators of malicious code] to recognize suspicious communications and anomalous behavior in organizational information systems. Supplemental Guidance: A well-trained workforce provides another organizational safeguard that can be employed as part of a defense-in-depth strategy to protect organizations against malicious code coming in to organizations via email or the web applications. Personnel are trained to look for indications of potentially suspicious email (e.g., receiving an unexpected email, receiving an email containing strange or poor grammar, or receiving an email from an unfamiliar sender but who appears to be from a known sponsor or contractor). Personnel are also trained on how to respond to such suspicious email or web communications (e.g., not opening attachments, not clicking on embedded web links, and checking the source of email addresses). For this process to work effectively, all organizational personnel are trained and made aware of what constitutes suspicious communications. Training personnel on how to recognize anomalous behaviors in organizational information systems can potentially provide early warning for the presence of malicious code. Recognition of such anomalous behavior by organizational personnel can supplement automated malicious code detection and protection tools and systems employed by organizations. | link | count: 001 Provide role-based training on suspicious activities (f6794ab8-9a7d-3b24-76ab-265d3646232b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AT-4 | NIST_SP_800-53_R4_AT-4 | NIST SP 800-53 Rev. 4 AT-4 | Awareness And Training | Security Training Records | Shared | n/a | The organization: a. Documents and monitors individual information system security training activities including basic security awareness training and specific information system security training; and b. Retains individual training records for [Assignment: organization-defined time period]. Supplemental Guidance: Documentation for specialized training may be maintained by individual supervisors at the option of the organization. Related controls: AT-2, AT-3, PM-14. Control Enhancements: None. References: None. | link | count: 003 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a), Retain training records (3153d9c0-2584-14d3-362d-578b01358aeb) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-1 | NIST_SP_800-53_R4_AU-1 | NIST SP 800-53 Rev. 4 AU-1 | Audit And Accountability | Audit And Accountability Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls; and b. Reviews and updates the current: 1. Audit and accountability policy [Assignment: organization-defined frequency]; and 2. Audit and accountability procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the AU family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 004 Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-10 | NIST_SP_800-53_R4_AU-10 | NIST SP 800-53 Rev. 4 AU-10 | Audit And Accountability | Non-Repudiation | Shared | n/a | The information system protects against an individual (or process acting on behalf of an individual) falsely denying having performed [Assignment: organization-defined actions to be covered by non-repudiation]. Supplemental Guidance: Types of individual actions covered by non-repudiation include, for example, creating information, sending and receiving messages, approving information (e.g., indicating concurrence or signing a contract). Non-repudiation protects individuals against later claims by: (i) authors of not having authored particular documents; (ii) senders of not having transmitted messages; (iii) receivers of not having received messages; or (iv) signatories of not having signed documents. Non-repudiation services can be used to determine if information originated from a particular individual, or if an individual took specific actions (e.g., sending an email, signing a contract, approving a procurement request) or received specific information. Organizations obtain non-repudiation services by employing various techniques or mechanisms (e.g., digital signatures, digital message receipts). Related controls: SC-12, SC-8, SC-13, SC-16, SC-17, SC-23. References: None. | link | count: 001 Establish electronic signature and certificate requirements (6f3866e8-6e12-69cf-788c-809d426094a1) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-11 | NIST_SP_800-53_R4_AU-11 | NIST SP 800-53 Rev. 4 AU-11 | Audit And Accountability | Audit Record Retention | Shared | n/a | The organization retains audit records for [Assignment: organization-defined time period consistent with records retention policy] to provide support for after-the-fact investigations of security incidents and to meet regulatory and organizational information retention requirements. Supplemental Guidance: Organizations retain audit records until it is determined that they are no longer needed for administrative, legal, audit, or other operational purposes. This includes, for example, retention and availability of audit records relative to Freedom of Information Act (FOIA) requests, subpoenas, and law enforcement actions. Organizations develop standard categories of audit records relative to such types of actions and standard response processes for each type of action. The National Archives and Records Administration (NARA) General Records Schedules provide federal policy on record retention. Related controls: AU-4, AU-5, AU-9, MP-6. References: None. | link | count: 004 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
Regulatory Compliance, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-12 | NIST_SP_800-53_R4_AU-12 | NIST SP 800-53 Rev. 4 AU-12 | Audit And Accountability | Audit Generation | Shared | n/a | The information system: a. Provides audit record generation capability for the auditable events defined in AU-2 a. at [Assignment: organization-defined information system components]; b. Allows [Assignment: organization-defined personnel or roles] to select which auditable events are to be audited by specific components of the information system; and c. Generates audit records for the events defined in AU-2 d. with the content defined in AU-3. Supplemental Guidance: Audit records can be generated from many different information system components. The list of audited events is the set of events for which audits are to be generated. These events are typically a subset of all events for which the information system is capable of generating audit records. Related controls: AC-3, AU-2, AU-3, AU-6, AU-7. References: None. | link | count: 037 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-12(1) | NIST_SP_800-53_R4_AU-12(1) | NIST SP 800-53 Rev. 4 AU-12 (1) | Audit And Accountability | System-Wide / Time-Correlated Audit Trail | Shared | n/a | The information system compiles audit records from [Assignment: organization-defined information system components] into a system-wide (logical or physical) audit trail that is time- correlated to within [Assignment: organization-defined level of tolerance for relationship between time stamps of individual records in the audit trail]. Supplemental Guidance: Audit trails are time-correlated if the time stamps in the individual audit records can be reliably related to the time stamps in other audit records to achieve a time ordering of the records within organizational tolerances. Related controls: AU-8, AU-12. | link | count: 034 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Compile Audit records into system wide audit (214ea241-010d-8926-44cc-b90a96d52adc), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-12(3) | NIST_SP_800-53_R4_AU-12(3) | NIST SP 800-53 Rev. 4 AU-12 (3) | Audit And Accountability | Changes By Authorized Individuals | Shared | n/a | The information system provides the capability for [Assignment: organization-defined individuals or roles] to change the auditing to be performed on [Assignment: organization-defined information system components] based on [Assignment: organization-defined selectable event criteria] within [Assignment: organization-defined time thresholds]. Supplemental Guidance: This control enhancement enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve information system resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting. Organizations can establish time thresholds in which audit actions are changed, for example, near real-time, within minutes, or within hours. Related control: AU-7. | link | count: 001 Provide the capability to extend or limit auditing on customer-deployed resources (d200f199-69f4-95a6-90b0-37ff0cf1040c) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-2 | NIST_SP_800-53_R4_AU-2 | NIST SP 800-53 Rev. 4 AU-2 | Audit And Accountability | Audit Events | Shared | n/a | The organization: a. Determines that the information system is capable of auditing the following events: [Assignment: organization-defined auditable events]; b. Coordinates the security audit function with other organizational entities requiring audit- related information to enhance mutual support and to help guide the selection of auditable events; c. Provides a rationale for why the auditable events are deemed to be adequate to support after- the-fact investigations of security incidents; and d. Determines that the following events are to be audited within the information system: [Assignment: organization-defined audited events (the subset of the auditable events defined in AU-2 a.) along with the frequency of (or situation requiring) auditing for each identified event]. Supplemental Guidance: An event is any observable occurrence in an organizational information system. Organizations identify audit events as those events which are significant and relevant to the security of information systems and the environments in which those systems operate in order to meet specific and ongoing audit needs. Audit events can include, for example, password changes, failed logons, or failed accesses related to information systems, administrative privilege usage, PIV credential usage, or third-party credential usage. In determining the set of auditable events, organizations consider the auditing appropriate for each of the security controls to be implemented. To balance auditing requirements with other information system needs, this control also requires identifying that subset of auditable events that are audited at a given point in time. For example, organizations may determine that information systems must have the capability to log every file access both successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. Auditing requirements, including the need for auditable events, may be referenced in other security controls and control enhancements. Organizations also include auditable events that are required by applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit capability and can facilitate the identification of root causes to problems. Organizations consider in the definition of auditable events, the auditing necessary to cover related events such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across multiple organizations) and actions that occur in service-oriented architectures. Related controls: AC-6, AC-17, AU-3, AU-12, MA-4, MP-2, MP-4, SI-4. References: NIST Special Publication 800-92; Web: http://idmanagement.gov. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-2(3) | NIST_SP_800-53_R4_AU-2(3) | NIST SP 800-53 Rev. 4 AU-2 (3) | Audit And Accountability | Reviews And Updates | Shared | n/a | The organization reviews and updates the audited events [Assignment: organization-defined frequency]. Supplemental Guidance: Over time, the events that organizations believe should be audited may change. Reviewing and updating the set of audited events periodically is necessary to ensure that the current set is still necessary and sufficient. | link | count: 001 Review and update the events defined in AU-02 (a930f477-9dcb-2113-8aa7-45bb6fc90861) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-3 | NIST_SP_800-53_R4_AU-3 | NIST SP 800-53 Rev. 4 AU-3 | Audit And Accountability | Content Of Audit Records | Shared | n/a | The information system generates audit records containing information that establishes what type of event occurred, when the event occurred, where the event occurred, the source of the event, the outcome of the event, and the identity of any individuals or subjects associated with the event. Supplemental Guidance: Audit record content that may be necessary to satisfy the requirement of this control, includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred). Related controls: AU-2, AU-8, AU-12, SI-11. References: None. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-3(1) | NIST_SP_800-53_R4_AU-3(1) | NIST SP 800-53 Rev. 4 AU-3 (1) | Audit And Accountability | Additional Audit Information | Shared | n/a | The information system generates audit records containing the following additional information: [Assignment: organization-defined additional, more detailed information]. Supplemental Guidance: Detailed information that organizations may consider in audit records includes, for example, full text recording of privileged commands or the individual identities of group account users. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. This facilitates the use of audit trails and audit logs by not including information that could potentially be misleading or could make it more difficult to locate information of interest. | link | count: 001 Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-4 | NIST_SP_800-53_R4_AU-4 | NIST SP 800-53 Rev. 4 AU-4 | Audit And Accountability | Audit Storage Capacity | Shared | n/a | The organization allocates audit record storage capacity in accordance with [Assignment: organization-defined audit record storage requirements]. Supplemental Guidance: Organizations consider the types of auditing to be performed and the audit processing requirements when allocating audit storage capacity. Allocating sufficient audit storage capacity reduces the likelihood of such capacity being exceeded and resulting in the potential loss or reduction of auditing capability. Related controls: AU-2, AU-5, AU-6, AU-7, AU-11, SI-4. References: None. | link | count: 001 Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-5 | NIST_SP_800-53_R4_AU-5 | NIST SP 800-53 Rev. 4 AU-5 | Audit And Accountability | Response To Audit Processing Failures | Shared | n/a | The information system: a. Alerts [Assignment: organization-defined personnel or roles] in the event of an audit processing failure; and b. Takes the following additional actions: [Assignment: organization-defined actions to be taken (e.g., shut down information system, overwrite oldest audit records, stop generating audit records)]. Supplemental Guidance: Audit processing failures include, for example, software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. Organizations may choose to define additional actions for different audit processing failures (e.g., by type, by location, by severity, or a combination of such factors). This control applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the total audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both. Related controls: AU-4, SI-12. References: None. | link | count: 001 Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-5(2) | NIST_SP_800-53_R4_AU-5(2) | NIST SP 800-53 Rev. 4 AU-5 (2) | Audit And Accountability | Real-Time Alerts | Shared | n/a | The information system provides an alert in [Assignment: organization-defined real-time period] to [Assignment: organization-defined personnel, roles, and/or locations] when the following audit failure events occur: [Assignment: organization-defined audit failure events requiring real-time alerts]. Supplemental Guidance: Alerts provide organizations with urgent messages. Real-time alerts provide these messages at information technology speed (i.e., the time from event detection to alert occurs in seconds or less). | link | count: 001 Provide real-time alerts for audit event failures (0f4fa857-079d-9d3d-5c49-21f616189e03) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-6 | NIST_SP_800-53_R4_AU-6 | NIST SP 800-53 Rev. 4 AU-6 | Audit And Accountability | Audit Review, Analysis, And Reporting | Shared | n/a | The organization: a. Reviews and analyzes information system audit records [Assignment: organization-defined frequency] for indications of [Assignment: organization-defined inappropriate or unusual activity]; and b. Reports findings to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Audit review, analysis, and reporting covers information security-related auditing performed by organizations including, for example, auditing that results from monitoring of account usage, remote access, wireless connectivity, mobile device connection, configuration settings, system component inventory, use of maintenance tools and nonlocal maintenance, physical access, temperature and humidity, equipment delivery and removal, communications at the information system boundaries, use of mobile code, and use of VoIP. Findings can be reported to organizational entities that include, for example, incident response team, help desk, information security group/department. If organizations are prohibited from reviewing and analyzing audit information or unable to conduct such activities (e.g., in certain national security applications or systems), the review/analysis may be carried out by other organizations granted such authority. Related controls: AC-2, AC-3, AC-6, AC-17, AT-3, AU-7, AU-16, CA-7, CM-5, CM-10, CM-11, IA-3, IA-5, IR-5, IR-6, MA-4, MP-4, PE-3, PE-6, PE-14, PE-16, RA-5, SC-7, SC-18, SC-19, SI-3, SI-4, SI-7. References: None. | link | count: 025 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-6(1) | NIST_SP_800-53_R4_AU-6(1) | NIST SP 800-53 Rev. 4 AU-6 (1) | Audit And Accountability | Process Integration | Shared | n/a | The organization employs automated mechanisms to integrate audit review, analysis, and reporting processes to support organizational processes for investigation and response to suspicious activities. Supplemental Guidance: Organizational processes benefiting from integrated audit review, analysis, and reporting include, for example, incident response, continuous monitoring, contingency planning, and Inspector General audits. Related controls: AU-12, PM-7. | link | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-6(10) | NIST_SP_800-53_R4_AU-6(10) | NIST SP 800-53 Rev. 4 AU-6 (10) | Audit And Accountability | Audit Level Adjustment | Shared | n/a | The organization adjusts the level of audit review, analysis, and reporting within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information. Supplemental Guidance: The frequency, scope, and/or depth of the audit review, analysis, and reporting may be adjusted to meet organizational needs based on new information received. | link | count: 001 Adjust level of audit review, analysis, and reporting (de251b09-4a5e-1204-4bef-62ac58d47999) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-6(3) | NIST_SP_800-53_R4_AU-6(3) | NIST SP 800-53 Rev. 4 AU-6 (3) | Audit And Accountability | Correlate Audit Repositories | Shared | n/a | The organization analyzes and correlates audit records across different repositories to gain organization-wide situational awareness. Supplemental Guidance: Organization-wide situational awareness includes awareness across all three tiers of risk management (i.e., organizational, mission/business process, and information system) and supports cross-organization awareness. Related controls: AU-12, IR-4. | link | count: 002 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-6(4) | NIST_SP_800-53_R4_AU-6(4) | NIST SP 800-53 Rev. 4 AU-6 (4) | Audit And Accountability | Central Review And Analysis | Shared | n/a | The information system provides the capability to centrally review and analyze audit records from multiple components within the system. Supplemental Guidance: Automated mechanisms for centralized reviews and analyses include, for example, Security Information Management products. Related controls: AU-2, AU-12. | link | count: 033 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-6(5) | NIST_SP_800-53_R4_AU-6(5) | NIST SP 800-53 Rev. 4 AU-6 (5) | Audit And Accountability | Integration / Scanning And Monitoring Capabilities | Shared | n/a | The organization integrates analysis of audit records with analysis of [Selection (one or more): vulnerability scanning information; performance data; information system monitoring information; [Assignment: organization-defined data/information collected from other sources]] to further enhance the ability to identify inappropriate or unusual activity. Supplemental Guidance: This control enhancement does not require vulnerability scanning, the generation of performance data, or information system monitoring. Rather, the enhancement requires that the analysis of information being otherwise produced in these areas is integrated with the analysis of audit information. Security Event and Information Management System tools can facilitate audit record aggregation/consolidation from multiple information system components as well as audit record correlation and analysis. The use of standardized audit record analysis scripts developed by organizations (with localized script adjustments, as necessary) provides more cost-effective approaches for analyzing audit record information collected. The correlation of audit record information with vulnerability scanning information is important in determining the veracity of vulnerability scans and correlating attack detection events with scanning results. Correlation with performance data can help uncover denial of service attacks or cyber attacks resulting in unauthorized use of resources. Correlation with system monitoring information can assist in uncovering attacks and in better relating audit information to operational situations. Related controls: AU-12, IR-4, RA-5. | link | count: 034 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Integrate Audit record analysis (85335602-93f5-7730-830b-d43426fd51fa), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-6(7) | NIST_SP_800-53_R4_AU-6(7) | NIST SP 800-53 Rev. 4 AU-6 (7) | Audit And Accountability | Permitted Actions | Shared | n/a | The organization specifies the permitted actions for each [Selection (one or more): information system process; role; user] associated with the review, analysis, and reporting of audit information. Supplemental Guidance: Organizations specify permitted actions for information system processes, roles, and/or users associated with the review, analysis, and reporting of audit records through account management techniques. Specifying permitted actions on audit information is a way to enforce the principle of least privilege. Permitted actions are enforced by the information system and include, for example, read, write, execute, append, and delete. | link | count: 001 Specify permitted actions associated with customer audit information (3eecf628-a1c8-1b48-1b5c-7ca781e97970) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-7 | NIST_SP_800-53_R4_AU-7 | NIST SP 800-53 Rev. 4 AU-7 | Audit And Accountability | Audit Reduction And Report Generation | Shared | n/a | The information system provides an audit reduction and report generation capability that: a. Supports on-demand audit review, analysis, and reporting requirements and after-the-fact investigations of security incidents; and b. Does not alter the original content or time ordering of audit records. Supplemental Guidance: Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Audit reduction and report generation capabilities do not always emanate from the same information system or from the same organizational entities conducting auditing activities. Audit reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the information system can generate customizable reports. Time ordering of audit records can be a significant issue if the granularity of the timestamp in the record is insufficient. Related control: AU-6. References: None. | link | count: 002 Ensure audit records are not altered (27ce30dd-3d56-8b54-6144-e26d9a37a541), Provide audit review, analysis, and reporting capability (44f8a42d-739f-8030-89a8-4c2d5b3f6af3) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-7(1) | NIST_SP_800-53_R4_AU-7(1) | NIST SP 800-53 Rev. 4 AU-7 (1) | Audit And Accountability | Automatic Processing | Shared | n/a | The information system provides the capability to process audit records for events of interest based on [Assignment: organization-defined audit fields within audit records]. Supplemental Guidance: Events of interest can be identified by the content of specific audit record fields including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations may define audit event criteria to any degree of granularity required, for example, locations selectable by general networking location (e.g., by network or subnetwork) or selectable by specific information system component. Related controls: AU-2, AU-12. | link | count: 001 Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-8 | NIST_SP_800-53_R4_AU-8 | NIST SP 800-53 Rev. 4 AU-8 | Audit And Accountability | Time Stamps | Shared | n/a | The information system: a. Uses internal system clocks to generate time stamps for audit records; and b. Records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT) and meets [Assignment: organization-defined granularity of time measurement]. Supplemental Guidance: Time stamps generated by the information system include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Granularity of time measurements refers to the degree of synchronization between information system clocks and reference clocks, for example, clocks synchronizing within hundreds of milliseconds or within tens of milliseconds. Organizations may define different time granularities for different system components. Time service can also be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities. Related controls: AU-3, AU-12. References: None. | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-8(1) | NIST_SP_800-53_R4_AU-8(1) | NIST SP 800-53 Rev. 4 AU-8 (1) | Audit And Accountability | Synchronization With Authoritative Time Source | Shared | n/a | The information system: (a) Compares the internal information system clocks [Assignment: organization-defined frequency] with [Assignment: organization-defined authoritative time source]; and (b) Synchronizes the internal system clocks to the authoritative time source when the time difference is greater than [Assignment: organization-defined time period]. Supplemental Guidance: This control enhancement provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-9 | NIST_SP_800-53_R4_AU-9 | NIST SP 800-53 Rev. 4 AU-9 | Audit And Accountability | Protection Of Audit Information | Shared | n/a | The information system protects audit information and audit tools from unauthorized access, modification, and deletion. Supplemental Guidance: Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. This control focuses on technical protection of audit information. Physical protection of audit information is addressed by media protection controls and physical and environmental protection controls. Related controls: AC-3, AC-6, MP-2, MP-4, PE-2, PE-3, PE-6. References: None. | link | count: 002 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-9(2) | NIST_SP_800-53_R4_AU-9(2) | NIST SP 800-53 Rev. 4 AU-9 (2) | Audit And Accountability | Audit Backup On Separate Physical Systems / Components | Shared | n/a | The information system backs up audit records [Assignment: organization-defined frequency] onto a physically different system or system component than the system or component being audited. Supplemental Guidance: This control enhancement helps to ensure that a compromise of the information system being audited does not also result in a compromise of the audit records. Related controls: AU-4, AU-5, AU-11. | link | count: 001 Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-9(3) | NIST_SP_800-53_R4_AU-9(3) | NIST SP 800-53 Rev. 4 AU-9 (3) | Audit And Accountability | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to protect the integrity of audit information and audit tools. Supplemental Guidance: Cryptographic mechanisms used for protecting the integrity of audit information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. Related controls: AU-10, SC-12, SC-13. | link | count: 001 Maintain integrity of audit system (c0559109-6a27-a217-6821-5a6d44f92897) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | AU-9(4) | NIST_SP_800-53_R4_AU-9(4) | NIST SP 800-53 Rev. 4 AU-9 (4) | Audit And Accountability | Access By Subset Of Privileged Users | Shared | n/a | The organization authorizes access to management of audit functionality to only [Assignment: organization-defined subset of privileged users]. Supplemental Guidance: Individuals with privileged access to an information system and who are also the subject of an audit by that system, may affect the reliability of audit information by inhibiting audit activities or modifying audit records. This control enhancement requires that privileged access be further defined between audit-related privileges and other privileges, thus limiting the users with audit-related privileges. Related control: AC-5. | link | count: 001 Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-1 | NIST_SP_800-53_R4_CA-1 | NIST SP 800-53 Rev. 4 CA-1 | Security Assessment And Authorization | Security Assessment And Authorization Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A security assessment and authorization policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the security assessment and authorization policy and associated security assessment and authorization controls; and b. Reviews and updates the current: 1. Security assessment and authorization policy [Assignment: organization-defined frequency]; and 2. Security assessment and authorization procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-37, 800-53A, 800-100. | link | count: 001 Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-2 | NIST_SP_800-53_R4_CA-2 | NIST SP 800-53 Rev. 4 CA-2 | Security Assessment And Authorization | Security Assessments | Shared | n/a | The organization: a. Develops a security assessment plan that describes the scope of the assessment including: 1. Security controls and control enhancements under assessment; 2. Assessment procedures to be used to determine security control effectiveness; and 3. Assessment environment, assessment team, and assessment roles and responsibilities; b. Assesses the security controls in the information system and its environment of operation [Assignment: organization-defined frequency] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security requirements; c. Produces a security assessment report that documents the results of the assessment; and d. Provides the results of the security control assessment to [Assignment: organization-defined individuals or roles]. Supplemental Guidance: Organizations assess security controls in organizational information systems and the environments in which those systems operate as part of: (i) initial and ongoing security authorizations; (ii) FISMA annual assessments; (iii) continuous monitoring; and (iv) system development life cycle activities. Security assessments: (i) ensure that information security is built into organizational information systems; (ii) identify weaknesses and deficiencies early in the development process; (iii) provide essential information needed to make risk-based decisions as part of security authorization processes; and (iv) ensure compliance to vulnerability mitigation procedures. Assessments are conducted on the implemented security controls from Appendix F (main catalog) and Appendix G (Program Management controls) as documented in System Security Plans and Information Security Program Plans. Organizations can use other types of assessment activities such as vulnerability scanning and system monitoring to maintain the security posture of information systems during the entire life cycle. Security assessment reports document assessment results in sufficient detail as deemed necessary by organizations, to determine the accuracy and completeness of the reports and whether the security controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting security requirements. The FISMA requirement for assessing security controls at least annually does not require additional assessment activities to those activities already in place in organizational security authorization processes. Security assessment results are provided to the individuals or roles appropriate for the types of assessments being conducted. For example, assessments conducted in support of security authorization decisions are provided to authorizing officials or authorizing official designated representatives. To satisfy annual assessment requirements, organizations can use assessment results from the following sources: (i) initial or ongoing information system authorizations; (ii) continuous monitoring; or (iii) system development life cycle activities. Organizations ensure that security assessment results are current, relevant to the determination of security control effectiveness, and obtained with the appropriate level of assessor independence. Existing security control assessment results can be reused to the extent that the results are still valid and can also be supplemented with additional assessments as needed. Subsequent to initial authorizations and in accordance with OMB policy, organizations assess security controls during continuous monitoring. Organizations establish the frequency for ongoing security control assessments in accordance with organizational continuous monitoring strategies. Information Assurance Vulnerability Alerts provide useful examples of vulnerability mitigation procedures. External audits (e.g., audits by external entities such as regulatory agencies) are outside the scope of this control. Related controls: CA-5, CA-6, CA-7, PM-9, RA-5, SA-11, SA-12, SI-4. References: Executive Order 13587; FIPS Publication 199; NIST Special Publications 800-37, 800-39, 800-53A, 800-115, 800-137. | link | count: 004 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-2(1) | NIST_SP_800-53_R4_CA-2(1) | NIST SP 800-53 Rev. 4 CA-2 (1) | Security Assessment And Authorization | Independent Assessors | Shared | n/a | The organization employs assessors or assessment teams with [Assignment: organization-defined level of independence] to conduct security control assessments. Supplemental Guidance: Independent assessors or assessment teams are individuals or groups who conduct impartial assessments of organizational information systems. Impartiality implies that assessors are free from any perceived or actual conflicts of interest with regard to the development, operation, or management of the organizational information systems under assessment or to the determination of security control effectiveness. To achieve impartiality, assessors should not: (i) create a mutual or conflicting interest with the organizations where the assessments are being conducted; (ii) assess their own work; (iii) act as management or employees of the organizations they are serving; or (iv) place themselves in positions of advocacy for the organizations acquiring their services. Independent assessments can be obtained from elements within organizations or can be contracted to public or private sector entities outside of organizations. Authorizing officials determine the required level of independence based on the security categories of information systems and/or the ultimate risk to organizational operations, organizational assets, or individuals. Authorizing officials also determine if the level of assessor independence provides sufficient assurance that the results are sound and can be used to make credible, risk-based decisions. This includes determining whether contracted security assessment services have sufficient independence, for example, when information system owners are not directly involved in contracting processes or cannot unduly influence the impartiality of assessors conducting assessments. In special situations, for example, when organizations that own the information systems are small or organizational structures require that assessments are conducted by individuals that are in the developmental, operational, or management chain of system owners, independence in assessment processes can be achieved by ensuring that assessment results are carefully reviewed and analyzed by independent teams of experts to validate the completeness, accuracy, integrity, and reliability of the results. Organizations recognize that assessments performed for purposes other than direct support to authorization decisions are, when performed by assessors with sufficient independence, more likely to be useable for such decisions, thereby reducing the need to repeat assessments. | link | count: 001 Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-2(2) | NIST_SP_800-53_R4_CA-2(2) | NIST SP 800-53 Rev. 4 CA-2 (2) | Security Assessment And Authorization | Specialized Assessments | Shared | n/a | The organization includes as part of security control assessments, [Assignment: organization- defined frequency], [Selection: announced; unannounced], [Selection (one or more): in-depth monitoring; vulnerability scanning; malicious user testing; insider threat assessment; performance/load testing; [Assignment: organization-defined other forms of security assessment]]. Supplemental Guidance: Organizations can employ information system monitoring, insider threat assessments, malicious user testing, and other forms of testing (e.g., verification and validation) to improve readiness by exercising organizational capabilities and indicating current performance levels as a means of focusing actions to improve security. Organizations conduct assessment activities in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Authorizing officials approve the assessment methods in coordination with the organizational risk executive function. Organizations can incorporate vulnerabilities uncovered during assessments into vulnerability remediation processes. Related controls: PE-3, SI-2. | link | count: 001 Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-2(3) | NIST_SP_800-53_R4_CA-2(3) | NIST SP 800-53 Rev. 4 CA-2 (3) | Security Assessment And Authorization | External Organizations | Shared | n/a | The organization accepts the results of an assessment of [Assignment: organization-defined information system] performed by [Assignment: organization-defined external organization] when the assessment meets [Assignment: organization-defined requirements]. Supplemental Guidance: Organizations may often rely on assessments of specific information systems by other (external) organizations. Utilizing such existing assessments (i.e., reusing existing assessment evidence) can significantly decrease the time and resources required for organizational assessments by limiting the amount of independent assessment activities that organizations need to perform. The factors that organizations may consider in determining whether to accept assessment results from external organizations can vary. Determinations for accepting assessment results can be based on, for example, past assessment experiences one organization has had with another organization, the reputation that organizations have with regard to assessments, the level of detail of supporting assessment documentation provided, or mandates imposed upon organizations by federal legislation, policies, or directives. | link | count: 001 Accept assessment results (3054c74b-9b45-2581-56cf-053a1a716c39) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-3 | NIST_SP_800-53_R4_CA-3 | NIST SP 800-53 Rev. 4 CA-3 | Security Assessment And Authorization | System Interconnections | Shared | n/a | The organization: a. Authorizes connections from the information system to other information systems through the use of Interconnection Security Agreements; b. Documents, for each interconnection, the interface characteristics, security requirements, and the nature of the information communicated; and c. Reviews and updates Interconnection Security Agreements [Assignment: organization-defined frequency]. Supplemental Guidance: This control applies to dedicated connections between information systems (i.e., system interconnections) and does not apply to transitory, user-controlled connections such as email and website browsing. Organizations carefully consider the risks that may be introduced when information systems are connected to other systems with different security requirements and security controls, both within organizations and external to organizations. Authorizing officials determine the risk associated with information system connections and the appropriate controls employed. If interconnecting systems have the same authorizing official, organizations do not need to develop Interconnection Security Agreements. Instead, organizations can describe the interface characteristics between those interconnecting systems in their respective security plans. If interconnecting systems have different authorizing officials within the same organization, organizations can either develop Interconnection Security Agreements or describe the interface characteristics between systems in the security plans for the respective systems. Organizations may also incorporate Interconnection Security Agreement information into formal contracts, especially for interconnections established between federal agencies and nonfederal (i.e., private sector) organizations. Risk considerations also include information systems sharing the same networks. For certain technologies (e.g., space, unmanned aerial vehicles, and medical devices), there may be specialized connections in place during preoperational testing. Such connections may require Interconnection Security Agreements and be subject to additional security controls. Related controls: AC-3, AC-4, AC-20, AU-2, AU-12, AU-16, CA-7, IA-3, SA-9, SC-7, SI-4. References: FIPS Publication 199; NIST Special Publication 800-47. | link | count: 002 Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-3(3) | NIST_SP_800-53_R4_CA-3(3) | NIST SP 800-53 Rev. 4 CA-3 (3) | Security Assessment And Authorization | Unclassified Non-National Security System Connections | Shared | n/a | The organization prohibits the direct connection of an [Assignment: organization-defined unclassified, non-national security system] to an external network without the use of [Assignment; organization-defined boundary protection device]. Supplemental Guidance: Organizations typically do not have control over external networks (e.g., the Internet). Approved boundary protection devices (e.g., routers, firewalls) mediate communications (i.e., information flows) between unclassified non-national security systems and external networks. This control enhancement is required for organizations processing, storing, or transmitting Controlled Unclassified Information (CUI). | link | count: 001 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-3(5) | NIST_SP_800-53_R4_CA-3(5) | NIST SP 800-53 Rev. 4 CA-3 (5) | Security Assessment And Authorization | Restrictions On External System Connections | Shared | n/a | The organization employs [Selection: allow-all, deny-by-exception; deny-all, permit-by-exception] policy for allowing [Assignment: organization-defined information systems] to connect to external information systems. Supplemental Guidance: Organizations can constrain information system connectivity to external domains (e.g., websites) by employing one of two policies with regard to such connectivity: (i) allow-all, deny by exception, also known as blacklisting (the weaker of the two policies); or (ii) deny-all, allow by exception, also known as whitelisting (the stronger of the two policies). For either policy, organizations determine what exceptions, if any, are acceptable. Related control: CM-7. | link | count: 001 Employ restrictions on external system interconnections (80029bc5-834f-3a9c-a2d8-acbc1aab4e9f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-5 | NIST_SP_800-53_R4_CA-5 | NIST SP 800-53 Rev. 4 CA-5 | Security Assessment And Authorization | Plan Of Action And Milestones | Shared | n/a | The organization: a. Develops a plan of action and milestones for the information system to document the organization’s planned remedial actions to correct weaknesses or deficiencies noted during the assessment of the security controls and to reduce or eliminate known vulnerabilities in the system; and b. Updates existing plan of action and milestones [Assignment: organization-defined frequency] based on the findings from security controls assessments, security impact analyses, and continuous monitoring activities. Supplemental Guidance: Plans of action and milestones are key documents in security authorization packages and are subject to federal reporting requirements established by OMB. Related controls: CA-2, CA-7, CM-4, PM-4. References: OMB Memorandum 02-01; NIST Special Publication 800-37. | link | count: 002 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-6 | NIST_SP_800-53_R4_CA-6 | NIST SP 800-53 Rev. 4 CA-6 | Security Assessment And Authorization | Security Authorization | Shared | n/a | The organization: a. Assigns a senior-level executive or manager as the authorizing official for the information system; b. Ensures that the authorizing official authorizes the information system for processing before commencing operations; and c. Updates the security authorization [Assignment: organization-defined frequency]. Supplemental Guidance: Security authorizations are official management decisions, conveyed through authorization decision documents, by senior organizational officials or executives (i.e., authorizing officials) to authorize operation of information systems and to explicitly accept the risk to organizational operations and assets, individuals, other organizations, and the Nation based on the implementation of agreed-upon security controls. Authorizing officials provide budgetary oversight for organizational information systems or assume responsibility for the mission/business operations supported by those systems. The security authorization process is an inherently federal responsibility and therefore, authorizing officials must be federal employees. Through the security authorization process, authorizing officials assume responsibility and are accountable for security risks associated with the operation and use of organizational information systems. Accordingly, authorizing officials are in positions with levels of authority commensurate with understanding and accepting such information security-related risks. OMB policy requires that organizations conduct ongoing authorizations of information systems by implementing continuous monitoring programs. Continuous monitoring programs can satisfy three-year reauthorization requirements, so separate reauthorization processes are not necessary. Through the employment of comprehensive continuous monitoring processes, critical information contained in authorization packages (i.e., security plans, security assessment reports, and plans of action and milestones) is updated on an ongoing basis, providing authorizing officials and information system owners with an up-to-date status of the security state of organizational information systems and environments of operation. To reduce the administrative cost of security reauthorization, authorizing officials use the results of continuous monitoring processes to the maximum extent possible as the basis for rendering reauthorization decisions. Related controls: CA-2, CA-7, PM-9, PM-10. Control Enhancements: None. References: OMB Circular A-130; OMB Memorandum 11-33; NIST Special Publications 800-37, 800-137. | link | count: 003 Assign an authorizing official (AO) (e29a8f1b-149b-2fa3-969d-ebee1baa9472), Ensure resources are authorized (0716f0f5-4955-2ccb-8d5e-c6be14d57c0f), Update the security authorization (449ebb52-945b-36e5-3446-af6f33770f8f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-7 | NIST_SP_800-53_R4_CA-7 | NIST SP 800-53 Rev. 4 CA-7 | Security Assessment And Authorization | Continuous Monitoring | Shared | n/a | The organization develops a continuous monitoring strategy and implements a continuous monitoring program that includes: a. Establishment of [Assignment: organization-defined metrics] to be monitored; b. Establishment of [Assignment: organization-defined frequencies] for monitoring and [Assignment: organization-defined frequencies] for assessments supporting such monitoring; c. Ongoing security control assessments in accordance with the organizational continuous monitoring strategy; d. Ongoing security status monitoring of organization-defined metrics in accordance with the organizational continuous monitoring strategy; e. Correlation and analysis of security-related information generated by assessments and monitoring; f. Response actions to address results of the analysis of security-related information; and g. Reporting the security status of organization and the information system to [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency]. Supplemental Guidance: Continuous monitoring programs facilitate ongoing awareness of threats, vulnerabilities, and information security to support organizational risk management decisions. The terms continuous and ongoing imply that organizations assess/analyze security controls and information security-related risks at a frequency sufficient to support organizational risk-based decisions. The results of continuous monitoring programs generate appropriate risk response actions by organizations. Continuous monitoring programs also allow organizations to maintain the security authorizations of information systems and common controls over time in highly dynamic environments of operation with changing mission/business needs, threats, vulnerabilities, and technologies. Having access to security-related information on a continuing basis through reports/dashboards gives organizational officials the capability to make more effective and timely risk management decisions, including ongoing security authorization decisions. Automation supports more frequent updates to security authorization packages, hardware/software/firmware inventories, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Continuous monitoring activities are scaled in accordance with the security categories of information systems. Related controls: CA-2, CA-5, CA-6, CM-3, CM-4, PM-6, PM-9, RA-5, SA-11, SA-12, SI-2, SI-4. References: OMB Memorandum 11-33; NIST Special Publications 800-37, 800-39, 800-53A, 800-115, 800-137; US-CERT Technical Cyber Security Alerts; DoD Information Assurance Vulnerability Alerts. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-7(1) | NIST_SP_800-53_R4_CA-7(1) | NIST SP 800-53 Rev. 4 CA-7 (1) | Security Assessment And Authorization | Independent Assessment | Shared | n/a | The organization employs assessors or assessment teams with [Assignment: organization-defined level of independence] to monitor the security controls in the information system on an ongoing basis. Supplemental Guidance: Organizations can maximize the value of assessments of security controls during the continuous monitoring process by requiring that such assessments be conducted by assessors or assessment teams with appropriate levels of independence based on continuous monitoring strategies. Assessor independence provides a degree of impartiality to the monitoring process. To achieve such impartiality, assessors should not: (i) create a mutual or conflicting interest with the organizations where the assessments are being conducted; (ii) assess their own work; (iii) act as management or employees of the organizations they are serving; or (iv) place themselves in advocacy positions for the organizations acquiring their services. | link | count: 001 Employ independent assessors for continuous monitoring (3baee3fd-30f5-882c-018c-cc78703a0106) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-7(3) | NIST_SP_800-53_R4_CA-7(3) | NIST SP 800-53 Rev. 4 CA-7 (3) | Security Assessment And Authorization | Trend Analyses | Shared | n/a | The organization employs trend analyses to determine if security control implementations, the frequency of continuous monitoring activities, and/or the types of activities used in the continuous monitoring process need to be modified based on empirical data. Supplemental Guidance: Trend analyses can include, for example, examining recent threat information regarding the types of threat events that have occurred within the organization or across the federal government, success rates of certain types of cyber attacks, emerging vulnerabilities in information technologies, evolving social engineering techniques, results from multiple security control assessments, the effectiveness of configuration settings, and findings from Inspectors General or auditors. | link | count: 001 Analyse data obtained from continuous monitoring (6a379d74-903b-244a-4c44-838728bea6b0) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-8(1) | NIST_SP_800-53_R4_CA-8(1) | NIST SP 800-53 Rev. 4 CA-8 (1) | Security Assessment And Authorization | Independent Penetration Agent Or Team | Shared | n/a | The organization employs an independent penetration agent or penetration team to perform penetration testing on the information system or system components. Supplemental Guidance: Independent penetration agents or teams are individuals or groups who conduct impartial penetration testing of organizational information systems. Impartiality implies that penetration agents or teams are free from any perceived or actual conflicts of interest with regard to the development, operation, or management of the information systems that are the targets of the penetration testing. Supplemental guidance for CA-2 (1) provides additional information regarding independent assessments that can be applied to penetration testing. Related control: CA-2. | link | count: 001 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CA-9 | NIST_SP_800-53_R4_CA-9 | NIST SP 800-53 Rev. 4 CA-9 | Security Assessment And Authorization | Internal System Connections | Shared | n/a | The organization: a. Authorizes internal connections of [Assignment: organization-defined information system components or classes of components] to the information system; and b. Documents, for each internal connection, the interface characteristics, security requirements, and the nature of the information communicated. Supplemental Guidance: This control applies to connections between organizational information systems and (separate) constituent system components (i.e., intra-system connections) including, for example, system connections with mobile devices, notebook/desktop computers, printers, copiers, facsimile machines, scanners, sensors, and servers. Instead of authorizing each individual internal connection, organizations can authorize internal connections for a class of components with common characteristics and/or configurations, for example, all digital printers, scanners, and copiers with a specified processing, storage, and transmission capability or all smart phones with a specific baseline configuration. Related controls: AC-3, AC-4, AC-18, AC-19, AU-2, AU-12, CA-7, CM-2, IA-3, SC-7, SI-4. References: None. | link | count: 001 Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-1 | NIST_SP_800-53_R4_CM-1 | NIST SP 800-53 Rev. 4 CM-1 | Configuration Management | Configuration Management Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the configuration management policy and associated configuration management controls; and b. Reviews and updates the current: 1. Configuration management policy [Assignment: organization-defined frequency]; and 2. Configuration management procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CM family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-10 | NIST_SP_800-53_R4_CM-10 | NIST SP 800-53 Rev. 4 CM-10 | Configuration Management | Software Usage Restrictions | Shared | n/a | The organization: a. Uses software and associated documentation in accordance with contract agreements and copyright laws; b. Tracks the use of software and associated documentation protected by quantity licenses to control copying and distribution; and c. Controls and documents the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work. Supplemental Guidance: Software license tracking can be accomplished by manual methods (e.g., simple spreadsheets) or automated methods (e.g., specialized tracking applications) depending on organizational needs. Related controls: AC-17, CM-8, SC-7. References: None. | link | count: 004 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Require compliance with intellectual property rights (725164e5-3b21-1ec2-7e42-14f077862841), Track software license usage (77cc89bb-774f-48d7-8a84-fb8c322c3000) |
Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-10(1) | NIST_SP_800-53_R4_CM-10(1) | NIST SP 800-53 Rev. 4 CM-10 (1) | Configuration Management | Open Source Software | Shared | n/a | The organization establishes the following restrictions on the use of open source software: [Assignment: organization-defined restrictions]. Supplemental Guidance: Open source software refers to software that is available in source code form. Certain software rights normally reserved for copyright holders are routinely provided under software license agreements that permit individuals to study, change, and improve the software. From a security perspective, the major advantage of open source software is that it provides organizations with the ability to examine the source code. However, there are also various licensing issues associated with open source software including, for example, the constraints on derivative use of such software. | link | count: 001 Restrict use of open source software (08c11b48-8745-034d-1c1b-a144feec73b9) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-11 | NIST_SP_800-53_R4_CM-11 | NIST SP 800-53 Rev. 4 CM-11 | Configuration Management | User-Installed Software | Shared | n/a | The organization: a. Establishes [Assignment: organization-defined policies] governing the installation of software by users; b. Enforces software installation policies through [Assignment: organization-defined methods]; and c. Monitors policy compliance at [Assignment: organization-defined frequency]. Supplemental Guidance: If provided the necessary privileges, users have the ability to install software in organizational information systems. To maintain control over the types of software installed, organizations identify permitted and prohibited actions regarding software installation. Permitted software installations may include, for example, updates and security patches to existing software and downloading applications from organization-approved “app stores.” Prohibited software installations may include, for example, software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods (e.g., periodic examination of user accounts), automated methods (e.g., configuration settings implemented on organizational information systems), or both. Related controls: AC-3, CM-2, CM-3, CM-5, CM-6, CM-7, PL-4. References: None. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-2 | NIST_SP_800-53_R4_CM-2 | NIST SP 800-53 Rev. 4 CM-2 | Configuration Management | Baseline Configuration | Shared | n/a | The organization develops, documents, and maintains under configuration control, a current baseline configuration of the information system. Supplemental Guidance: This control establishes baseline configurations for information systems and system components including communications and connectivity-related aspects of systems. Baseline configurations are documented, formally reviewed and agreed-upon sets of specifications for information systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, and/or changes to information systems. Baseline configurations include information about information system components (e.g., standard software packages installed on workstations, notebook computers, servers, network components, or mobile devices; current version numbers and patch information on operating systems and applications; and configuration settings/parameters), network topology, and the logical placement of those components within the system architecture. Maintaining baseline configurations requires creating new baselines as organizational information systems change over time. Baseline configurations of information systems reflect the current enterprise architecture. Related controls: CM-3, CM-6, CM-8, CM-9, SA-10, PM-5, PM-7. References: NIST Special Publication 800-128. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-2(2) | NIST_SP_800-53_R4_CM-2(2) | NIST SP 800-53 Rev. 4 CM-2 (2) | Configuration Management | Automation Support For Accuracy / Currency | Shared | n/a | The organization employs automated mechanisms to maintain an up-to-date, complete, accurate, and readily available baseline configuration of the information system. Supplemental Guidance: Automated mechanisms that help organizations maintain consistent baseline configurations for information systems include, for example, hardware and software inventory tools, configuration management tools, and network management tools. Such tools can be deployed and/or allocated as common controls, at the information system level, or at the operating system or component level (e.g., on workstations, servers, notebook computers, network components, or mobile devices). Tools can be used, for example, to track version numbers on operating system applications, types of software installed, and current patch levels. This control enhancement can be satisfied by the implementation of CM-8 (2) for organizations that choose to combine information system component inventory and baseline configuration activities. Related controls: CM-7, RA-5. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-2(3) | NIST_SP_800-53_R4_CM-2(3) | NIST SP 800-53 Rev. 4 CM-2 (3) | Configuration Management | Retention Of Previous Configurations | Shared | n/a | The organization retains [Assignment: organization-defined previous versions of baseline configurations of the information system] to support rollback. Supplemental Guidance: Retaining previous versions of baseline configurations to support rollback may include, for example, hardware, software, firmware, configuration files, and configuration records. | link | count: 001 Retain previous versions of baseline configs (5e4e9685-3818-5934-0071-2620c4fa2ca5) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-2(7) | NIST_SP_800-53_R4_CM-2(7) | NIST SP 800-53 Rev. 4 CM-2 (7) | Configuration Management | Configure Systems, Components, Or Devices For High-Risk Areas | Shared | n/a | The organization: (a) Issues [Assignment: organization-defined information systems, system components, or devices] with [Assignment: organization-defined configurations] to individuals traveling to locations that the organization deems to be of significant risk; and (b) Applies [Assignment: organization-defined security safeguards] to the devices when the individuals return. Supplemental Guidance: When it is known that information systems, system components, or devices (e.g., notebook computers, mobile devices) will be located in high-risk areas, additional security controls may be implemented to counter the greater threat in such areas coupled with the lack of physical security relative to organizational-controlled areas. For example, organizational policies and procedures for notebook computers used by individuals departing on and returning from travel include, for example, determining which locations are of concern, defining required configurations for the devices, ensuring that the devices are configured as intended before travel is initiated, and applying specific safeguards to the device after travel is completed. Specially configured notebook computers include, for example, computers with sanitized hard drives, limited applications, and additional hardening (e.g., more stringent configuration settings). Specified safeguards applied to mobile devices upon return from travel include, for example, examining the device for signs of physical tampering and purging/reimaging the hard disk drive. Protecting information residing on mobile devices is covered in the media protection family..\ | link | count: 002 Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-3 | NIST_SP_800-53_R4_CM-3 | NIST SP 800-53 Rev. 4 CM-3 | Configuration Management | Configuration Change Control | Shared | n/a | The organization: a. Determines the types of changes to the information system that are configuration-controlled; b. Reviews proposed configuration-controlled changes to the information system and approves or disapproves such changes with explicit consideration for security impact analyses; c. Documents configuration change decisions associated with the information system; d. Implements approved configuration-controlled changes to the information system; e. Retains records of configuration-controlled changes to the information system for [Assignment: organization-defined time period]; f. Audits and reviews activities associated with configuration-controlled changes to the information system; and g. Coordinates and provides oversight for configuration change control activities through [Assignment: organization-defined configuration change control element (e.g., committee, board] that convenes [Selection (one or more): [Assignment: organization-defined frequency]; [Assignment: organization-defined configuration change conditions]]. Supplemental Guidance: Configuration change controls for organizational information systems involve the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications. Configuration change control includes changes to baseline configurations for components and configuration items of information systems, changes to configuration settings for information technology products (e.g., operating systems, applications, firewalls, routers, and mobile devices), unscheduled/unauthorized changes, and changes to remediate vulnerabilities. Typical processes for managing configuration changes to information systems include, for example, Configuration Control Boards that approve proposed changes to systems. For new development information systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards. Auditing of changes includes activities before and after changes are made to organizational information systems and the auditing activities required to implement such changes. Related controls: CM-2, CM-4, CM-5, CM-6, CM-9, SA-10, SI-2, SI-12. References: NIST Special Publication 800-128. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-3(1) | NIST_SP_800-53_R4_CM-3(1) | NIST SP 800-53 Rev. 4 CM-3 (1) | Configuration Management | Automated Document / Notification / Prohibition Of Changes | Shared | n/a | The organization employs automated mechanisms to: (a) Document proposed changes to the information system; (b) Notify [Assignment: organized-defined approval authorities] of proposed changes to the information system and request change approval; (c) Highlight proposed changes to the information system that have not been approved or disapproved by [Assignment: organization-defined time period]; (d) Prohibit changes to the information system until designated approvals are received; (e) Document all changes to the information system; and (f) Notify [Assignment: organization-defined personnel] when approved changes to the information system are completed. | link | count: 006 Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-3(2) | NIST_SP_800-53_R4_CM-3(2) | NIST SP 800-53 Rev. 4 CM-3 (2) | Configuration Management | Test / Validate / Document Changes | Shared | n/a | The organization tests, validates, and documents changes to the information system before implementing the changes on the operational system. Supplemental Guidance: Changes to information systems include modifications to hardware, software, or firmware components and configuration settings defined in CM-6. Organizations ensure that testing does not interfere with information system operations. Individuals/groups conducting tests understand organizational security policies and procedures, information system security policies and procedures, and the specific health, safety, and environmental risks associated with particular facilities/processes. Operational systems may need to be taken off-line, or replicated to the extent feasible, before testing can be conducted. If information systems must be taken off-line for testing, the tests are scheduled to occur during planned system outages whenever possible. If testing cannot be conducted on operational systems, organizations employ compensating controls (e.g., testing on replicated systems). | link | count: 003 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-3(4) | NIST_SP_800-53_R4_CM-3(4) | NIST SP 800-53 Rev. 4 CM-3 (4) | Configuration Management | Security Representative | Shared | n/a | The organization requires an information security representative to be a member of the [Assignment: organization-defined configuration change control element]. Supplemental Guidance: Information security representatives can include, for example, senior agency information security officers, information system security officers, or information system security managers. Representation by personnel with information security expertise is important because changes to information system configurations can have unintended side effects, some of which may be security-relevant. Detecting such changes early in the process can help avoid unintended, negative consequences that could ultimately affect the security state of organizational information systems. The configuration change control element in this control enhancement reflects the change control elements defined by organizations in CM-3. | link | count: 001 Assign information security representative to change control (6abdf7c7-362b-3f35-099e-533ed50988f9) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-3(6) | NIST_SP_800-53_R4_CM-3(6) | NIST SP 800-53 Rev. 4 CM-3 (6) | Configuration Management | Cryptography Management | Shared | n/a | The organization ensures that cryptographic mechanisms used to provide [Assignment: organization-defined security safeguards] are under configuration management. Supplemental Guidance: Regardless of the cryptographic means employed (e.g., public key, private key, shared secrets), organizations ensure that there are processes and procedures in place to effectively manage those means. For example, if devices use certificates as a basis for identification and authentication, there needs to be a process in place to address the expiration of those certificates. Related control: SC-13. | link | count: 001 Ensure cryptographic mechanisms are under configuration management (b8dad106-6444-5f55-307e-1e1cc9723e39) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-4 | NIST_SP_800-53_R4_CM-4 | NIST SP 800-53 Rev. 4 CM-4 | Configuration Management | Security Impact Analysis | Shared | n/a | The organization analyzes changes to the information system to determine potential security impacts prior to change implementation. Supplemental Guidance: Organizational personnel with information security responsibilities (e.g., Information System Administrators, Information System Security Officers, Information System Security Managers, and Information System Security Engineers) conduct security impact analyses. Individuals conducting security impact analyses possess the necessary skills/technical expertise to analyze the changes to information systems and the associated security ramifications. Security impact analysis may include, for example, reviewing security plans to understand security control requirements and reviewing system design documentation to understand control implementation and how specific changes might affect the controls. Security impact analyses may also include assessments of risk to better understand the impact of the changes and to determine if additional security controls are required. Security impact analyses are scaled in accordance with the security categories of the information systems. Related controls: CA-2, CA-7, CM-3, CM-9, SA-4, SA-5, SA-10, SI-2. References: NIST Special Publication 800-128. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-4(1) | NIST_SP_800-53_R4_CM-4(1) | NIST SP 800-53 Rev. 4 CM-4 (1) | Configuration Management | Separate Test Environments | Shared | n/a | The organization analyzes changes to the information system in a separate test environment before implementation in an operational environment, looking for security impacts due to flaws, weaknesses, incompatibility, or intentional malice. Supplemental Guidance: Separate test environment in this context means an environment that is physically or logically isolated and distinct from the operational environment. The separation is sufficient to ensure that activities in the test environment do not impact activities in the operational environment, and information in the operational environment is not inadvertently transmitted to the test environment. Separate environments can be achieved by physical or logical means. If physically separate test environments are not used, organizations determine the strength of mechanism required when implementing logical separation (e.g., separation achieved through virtual machines). Related controls: SA-11, SC-3, SC-7. | link | count: 005 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-5 | NIST_SP_800-53_R4_CM-5 | NIST SP 800-53 Rev. 4 CM-5 | Configuration Management | Access Restrictions For Change | Shared | n/a | The organization defines, documents, approves, and enforces physical and logical access restrictions associated with changes to the information system. Supplemental Guidance: Any changes to the hardware, software, and/or firmware components of information systems can potentially have significant effects on the overall security of the systems. Therefore, organizations permit only qualified and authorized individuals to access information systems for purposes of initiating changes, including upgrades and modifications. Organizations maintain records of access to ensure that configuration change control is implemented and to support after-the-fact actions should organizations discover any unauthorized changes. Access restrictions for change also include software libraries. Access restrictions include, for example, physical and logical access controls (see AC-3 and PE-3), workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into information systems), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover). Related controls: AC-3, AC-6, PE-3. References: None. | link | count: 001 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-5(1) | NIST_SP_800-53_R4_CM-5(1) | NIST SP 800-53 Rev. 4 CM-5 (1) | Configuration Management | Automated Access Enforcement / Auditing | Shared | n/a | The information system enforces access restrictions and supports auditing of the enforcement actions. Supplemental Guidance: Related controls: AU-2, AU-12, AU-6, CM-3, CM-6. | link | count: 001 Enforce and audit access restrictions (8cd815bf-97e1-5144-0735-11f6ddb50a59) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-5(2) | NIST_SP_800-53_R4_CM-5(2) | NIST SP 800-53 Rev. 4 CM-5 (2) | Configuration Management | Review System Changes | Shared | n/a | The organization reviews information system changes [Assignment: organization-defined frequency] and [Assignment: organization-defined circumstances] to determine whether unauthorized changes have occurred. Supplemental Guidance: Indications that warrant review of information system changes and the specific circumstances justifying such reviews may be obtained from activities carried out by organizations during the configuration change process. Related controls: AU-6, AU-7, CM-3, CM-5, PE-6, PE-8. | link | count: 001 Review changes for any unauthorized changes (c246d146-82b0-301f-32e7-1065dcd248b7) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-5(3) | NIST_SP_800-53_R4_CM-5(3) | NIST SP 800-53 Rev. 4 CM-5 (3) | Configuration Management | Signed Components | Shared | n/a | The information system prevents the installation of [Assignment: organization-defined software and firmware components] without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization. Supplemental Guidance: Software and firmware components prevented from installation unless signed with recognized and approved certificates include, for example, software and firmware version updates, patches, service packs, device drivers, and basic input output system (BIOS) updates. Organizations can identify applicable software and firmware components by type, by specific items, or a combination of both. Digital signatures and organizational verification of such signatures, is a method of code authentication. Related controls: CM-7, SC-13, SI-7. | link | count: 001 Restrict unauthorized software and firmware installation (4ee5975d-2507-5530-a20a-83a725889c6f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-5(5) | NIST_SP_800-53_R4_CM-5(5) | NIST SP 800-53 Rev. 4 CM-5 (5) | Configuration Management | Limit Production / Operational Privileges | Shared | n/a | The organization: (a) Limits privileges to change information system components and system-related information within a production or operational environment; and (b) Reviews and reevaluates privileges [Assignment: organization-defined frequency]. Supplemental Guidance: In many organizations, information systems support multiple core missions/business functions. Limiting privileges to change information system components with respect to operational systems is necessary because changes to a particular information system component may have far-reaching effects on mission/business processes supported by the system where the component resides. The complex, many-to-many relationships between systems and mission/business processes are in some cases, unknown to developers. Related control: AC-2. | link | count: 002 Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-6 | NIST_SP_800-53_R4_CM-6 | NIST SP 800-53 Rev. 4 CM-6 | Configuration Management | Configuration Settings | Shared | n/a | The organization: a. Establishes and documents configuration settings for information technology products employed within the information system using [Assignment: organization-defined security configuration checklists] that reflect the most restrictive mode consistent with operational requirements; b. Implements the configuration settings; c. Identifies, documents, and approves any deviations from established configuration settings for [Assignment: organization-defined information system components] based on [Assignment: organization-defined operational requirements]; and d. Monitors and controls changes to the configuration settings in accordance with organizational policies and procedures. Supplemental Guidance: Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the information system that affect the security posture and/or functionality of the system. Information technology products for which security- related configuration settings can be defined include, for example, mainframe computers, servers (e.g., database, electronic mail, authentication, web, proxy, file, domain name), workstations, input/output devices (e.g., scanners, copiers, and printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications. Security-related parameters are those parameters impacting the security state of information systems including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: (i) registry settings; (ii) account, file, directory permission settings; and (iii) settings for functions, ports, protocols, services, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific settings for information systems. The established settings become part of the systems configuration baseline. Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those information system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations including, for example, information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors. Common secure configurations include the United States Government Configuration Baseline (USGCB) which affects the implementation of CM-6 and other controls such as AC-19 and CM-7. The Security Content Automation Protocol (SCAP) and the defined standards within the protocol (e.g., Common Configuration Enumeration) provide an effective method to uniquely identify, track, and control configuration settings. OMB establishes federal policy on configuration requirements for federal information systems. Related controls: AC-19, CM-2, CM-3, CM-7, SI-4. References: OMB Memoranda 07-11, 07-18, 08-22; NIST Special Publications 800-70, 800-128; Web: http://nvd.nist.gov, http://checklists.nist.gov, http://www.nsa.gov. | link | count: 023 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Guest Configuration, Kubernetes, Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-6(1) | NIST_SP_800-53_R4_CM-6(1) | NIST SP 800-53 Rev. 4 CM-6 (1) | Configuration Management | Automated Central Management / Application / Verification | Shared | n/a | The organization employs automated mechanisms to centrally manage, apply, and verify configuration settings for [Assignment: organization-defined information system components]. Supplemental Guidance: Related controls: CA-7, CM-4. | link | count: 003 Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-7 | NIST_SP_800-53_R4_CM-7 | NIST SP 800-53 Rev. 4 CM-7 | Configuration Management | Least Functionality | Shared | n/a | The organization: a. Configures the information system to provide only essential capabilities; and b. Prohibits or restricts the use of the following functions, ports, protocols, and/or services: [Assignment: organization-defined prohibited or restricted functions, ports, protocols, and/or services]. Supplemental Guidance: Information systems can provide a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Additionally, it is sometimes convenient to provide multiple services from single information system components, but doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per device (e.g., email servers or web servers, but not both). Organizations review functions and services provided by information systems or individual components of information systems, to determine which functions and services are candidates for elimination (e.g., Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing). Organizations consider disabling unused or unnecessary physical and logical ports/protocols (e.g., Universal Serial Bus, File Transfer Protocol, and Hyper Text Transfer Protocol) on information systems to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services. Related controls: AC-6, CM-2, RA-5, SA-5, SC-7. References: DoD Instruction 8551.01. | link | count: 003 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-7(2) | NIST_SP_800-53_R4_CM-7(2) | NIST SP 800-53 Rev. 4 CM-7 (2) | Configuration Management | Prevent Program Execution | Shared | n/a | The information system prevents program execution in accordance with [Selection (one or more): [Assignment: organization-defined policies regarding software program usage and restrictions]; rules authorizing the terms and conditions of software program usage]. Supplemental Guidance: Related controls: CM-8, PM-5. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-7(5) | NIST_SP_800-53_R4_CM-7(5) | NIST SP 800-53 Rev. 4 CM-7 (5) | Configuration Management | Authorized Software / Whitelisting | Shared | n/a | The organization: (a) Identifies [Assignment: organization-defined software programs authorized to execute on the information system]; (b) Employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the information system; and (c) Reviews and updates the list of authorized software programs [Assignment: organization- defined frequency]. Supplemental Guidance: The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting. In addition to whitelisting, organizations consider verifying the integrity of white-listed software programs using, for example, cryptographic checksums, digital signatures, or hash functions. Verification of white-listed software can occur either prior to execution or at system startup. Related controls: CM-2, CM-6, CM-8, PM-5, SA-10, SC-34, SI-7. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-8 | NIST_SP_800-53_R4_CM-8 | NIST SP 800-53 Rev. 4 CM-8 | Configuration Management | Information System Component Inventory | Shared | n/a | The organization: a. Develops and documents an inventory of information system components that: 1. Accurately reflects the current information system; 2. Includes all components within the authorization boundary of the information system; 3. Is at the level of granularity deemed necessary for tracking and reporting; and 4. Includes [Assignment: organization-defined information deemed necessary to achieve effective information system component accountability]; and b. Reviews and updates the information system component inventory [Assignment: organization-defined frequency]. Supplemental Guidance: Organizations may choose to implement centralized information system component inventories that include components from all organizational information systems. In such situations, organizations ensure that the resulting inventories include system-specific information required for proper component accountability (e.g., information system association, information system owner). Information deemed necessary for effective accountability of information system components includes, for example, hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include, for example, manufacturer, device type, model, serial number, and physical location. Related controls: CM-2, CM-6, PM-5. References: NIST Special Publication 800-128. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-8(1) | NIST_SP_800-53_R4_CM-8(1) | NIST SP 800-53 Rev. 4 CM-8 (1) | Configuration Management | Updates During Installations / Removals | Shared | n/a | The organization updates the inventory of information system components as an integral part of component installations, removals, and information system updates. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-8(3) | NIST_SP_800-53_R4_CM-8(3) | NIST SP 800-53 Rev. 4 CM-8 (3) | Configuration Management | Automated Unauthorized Component Detection | Shared | n/a | The organization: (a) Employs automated mechanisms [Assignment: organization-defined frequency] to detect the presence of unauthorized hardware, software, and firmware components within the information system; and (b) Takes the following actions when unauthorized components are detected: [Selection (one or more): disables network access by such components; isolates the components; notifies [Assignment: organization-defined personnel or roles]]. Supplemental Guidance: This control enhancement is applied in addition to the monitoring for unauthorized remote connections and mobile devices. Monitoring for unauthorized system components may be accomplished on an ongoing basis or by the periodic scanning of systems for that purpose. Automated mechanisms can be implemented within information systems or in other separate devices. Isolation can be achieved, for example, by placing unauthorized information system components in separate domains or subnets or otherwise quarantining such components. This type of component isolation is commonly referred to as sandboxing. Related controls: AC-17, AC-18, AC-19, CA-7, SI-3, SI-4, SI-7, RA-5. | link | count: 002 Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-8(4) | NIST_SP_800-53_R4_CM-8(4) | NIST SP 800-53 Rev. 4 CM-8 (4) | Configuration Management | Accountability Information | Shared | n/a | The organization includes in the information system component inventory information, a means for identifying by [Selection (one or more): name; position; role], individuals responsible/accountable for administering those components. Supplemental Guidance: Identifying individuals who are both responsible and accountable for administering information system components helps to ensure that the assigned components are properly administered and organizations can contact those individuals if some action is required (e.g., component is determined to be the source of a breach/compromise, component needs to be recalled/replaced, or component needs to be relocated). | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CM-9 | NIST_SP_800-53_R4_CM-9 | NIST SP 800-53 Rev. 4 CM-9 | Configuration Management | Configuration Management Plan | Shared | n/a | The organization develops, documents, and implements a configuration management plan for the information system that: a. Addresses roles, responsibilities, and configuration management processes and procedures; b. Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items; c. Defines the configuration items for the information system and places the configuration items under configuration management; and d. Protects the configuration management plan from unauthorized disclosure and modification. Supplemental Guidance: Configuration management plans satisfy the requirements in configuration management policies while being tailored to individual information systems. Such plans define detailed processes and procedures for how configuration management is used to support system development life cycle activities at the information system level. Configuration management plans are typically developed during the development/acquisition phase of the system development life cycle. The plans describe how to move changes through change management processes, how to update configuration settings and baselines, how to maintain information system component inventories, how to control development, test, and operational environments, and how to develop, release, and update key documents. Organizations can employ templates to help ensure consistent and timely development and implementation of configuration management plans. Such templates can represent a master configuration management plan for the organization at large with subsets of the plan implemented on a system by system basis. Configuration management approval processes include designation of key management stakeholders responsible for reviewing and approving proposed changes to information systems, and personnel that conduct security impact analyses prior to the implementation of changes to the systems. Configuration items are the information system items (hardware, software, firmware, and documentation) to be configuration-managed. As information systems continue through the system development life cycle, new configuration items may be identified and some existing configuration items may no longer need to be under configuration control. Related controls: CM-2, CM-3, CM-4, CM-5, CM-8, SA-10. References: NIST Special Publication 800-128. | link | count: 006 Create configuration plan protection (874a6f2e-2098-53bc-3a16-20dcdc425a7e), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-1 | NIST_SP_800-53_R4_CP-1 | NIST SP 800-53 Rev. 4 CP-1 | Contingency Planning | Contingency Planning Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A contingency planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls; and b. Reviews and updates the current: 1. Contingency planning policy [Assignment: organization-defined frequency]; and 2. Contingency planning procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the CP family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: Federal Continuity Directive 1; NIST Special Publications 800-12, 800-34, 800-100. | link | count: 001 Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-10 | NIST_SP_800-53_R4_CP-10 | NIST SP 800-53 Rev. 4 CP-10 | Contingency Planning | Information System Recovery And Reconstitution | Shared | n/a | The organization provides for the recovery and reconstitution of the information system to a known state after a disruption, compromise, or failure. Supplemental Guidance: Recovery is executing information system contingency plan activities to restore organizational missions/business functions. Reconstitution takes place following recovery and includes activities for returning organizational information systems to fully operational states. Recovery and reconstitution operations reflect mission and business priorities, recovery point/time and reconstitution objectives, and established organizational metrics consistent with contingency plan requirements. Reconstitution includes the deactivation of any interim information system capabilities that may have been needed during recovery operations. Reconstitution also includes assessments of fully restored information system capabilities, reestablishment of continuous monitoring activities, potential information system reauthorizations, and activities to prepare the systems against future disruptions, compromises, or failures. Recovery/reconstitution capabilities employed by organizations can include both automated mechanisms and manual procedures. Related controls: CA-2, CA-6, CA-7, CP-2, CP-6, CP-7, CP-9, SC-24. References: Federal Continuity Directive 1; NIST Special Publication 800-34. | link | count: 001 Recover and reconstitute resources after any disruption (f33c3238-11d2-508c-877c-4262ec1132e1) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-10(2) | NIST_SP_800-53_R4_CP-10(2) | NIST SP 800-53 Rev. 4 CP-10 (2) | Contingency Planning | Transaction Recovery | Shared | n/a | The information system implements transaction recovery for systems that are transaction-based. Supplemental Guidance: Transaction-based information systems include, for example, database management systems and transaction processing systems. Mechanisms supporting transaction recovery include, for example, transaction rollback and transaction journaling. | link | count: 001 Implement transaction based recovery (ba02d0a0-566a-25dc-73f1-101c726a19c5) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-10(4) | NIST_SP_800-53_R4_CP-10(4) | NIST SP 800-53 Rev. 4 CP-10 (4) | Contingency Planning | Restore Within Time Period | Shared | n/a | The organization provides the capability to restore information system components within [Assignment: organization-defined restoration time-periods] from configuration-controlled and integrity-protected information representing a known, operational state for the components. Supplemental Guidance: Restoration of information system components includes, for example, reimaging which restores components to known, operational states. Related control: CM-2. | link | count: 001 Restore resources to operational state (f801d58e-5659-9a4a-6e8d-02c9334732e5) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-2 | NIST_SP_800-53_R4_CP-2 | NIST SP 800-53 Rev. 4 CP-2 | Contingency Planning | Contingency Plan | Shared | n/a | The organization: a. Develops a contingency plan for the information system that: 1. Identifies essential missions and business functions and associated contingency requirements; 2. Provides recovery objectives, restoration priorities, and metrics; 3. Addresses contingency roles, responsibilities, assigned individuals with contact information; 4. Addresses maintaining essential missions and business functions despite an information system disruption, compromise, or failure; 5. Addresses eventual, full information system restoration without deterioration of the security safeguards originally planned and implemented; and 6. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; b. Distributes copies of the contingency plan to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements]; c. Coordinates contingency planning activities with incident handling activities; d. Reviews the contingency plan for the information system [Assignment: organization-defined frequency]; e. Updates the contingency plan to address changes to the organization, information system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing; f. Communicates contingency plan changes to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements]; and g. Protects the contingency plan from unauthorized disclosure and modification. Supplemental Guidance: Contingency planning for information systems is part of an overall organizational program for achieving continuity of operations for mission/business functions. Contingency planning addresses both information system restoration and implementation of alternative mission/business processes when systems are compromised. The effectiveness of contingency planning is maximized by considering such planning throughout the phases of the system development life cycle. Performing contingency planning on hardware, software, and firmware development can be an effective means of achieving information system resiliency. Contingency plans reflect the degree of restoration required for organizational information systems since not all systems may need to fully recover to achieve the level of continuity of operations desired. Information system recovery objectives reflect applicable laws, Executive Orders, directives, policies, standards, regulations, and guidelines. In addition to information system availability, contingency plans also address other security-related events resulting in a reduction in mission and/or business effectiveness, such as malicious attacks compromising the confidentiality or integrity of information systems. Actions addressed in contingency plans include, for example, orderly/graceful degradation, information system shutdown, fallback to a manual mode, alternate information flows, and operating in modes reserved for when systems are under attack. By closely coordinating contingency planning with incident handling activities, organizations can ensure that the necessary contingency planning activities are in place and activated in the event of a security incident. Related controls: AC-14, CP-6, CP-7, CP-8, CP-9, CP-10, IR-4, IR-8, MP-2, MP-4, MP-5, PM-8, PM-11. References: Federal Continuity Directive 1; NIST Special Publication 800-34. | link | count: 008 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82), Review contingency plan (53fc1282-0ee3-2764-1319-e20143bb0ea5), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-2(1) | NIST_SP_800-53_R4_CP-2(1) | NIST SP 800-53 Rev. 4 CP-2 (1) | Contingency Planning | Coordinate With Related Plans | Shared | n/a | The organization coordinates contingency plan development with organizational elements responsible for related plans. Supplemental Guidance: Plans related to contingency plans for organizational information systems include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, Insider Threat Implementation Plan, and Occupant Emergency Plans. | link | count: 001 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-2(2) | NIST_SP_800-53_R4_CP-2(2) | NIST SP 800-53 Rev. 4 CP-2 (2) | Contingency Planning | Capacity Planning | Shared | n/a | The organization conducts capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations. Supplemental Guidance: Capacity planning is needed because different types of threats (e.g., natural disasters, targeted cyber attacks) can result in a reduction of the available processing, telecommunications, and support services originally intended to support the organizational missions/business functions. Organizations may need to anticipate degraded operations during contingency operations and factor such degradation into capacity planning. | link | count: 001 Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-2(3) | NIST_SP_800-53_R4_CP-2(3) | NIST SP 800-53 Rev. 4 CP-2 (3) | Contingency Planning | Resume Essential Missions / Business Functions | Shared | n/a | The organization plans for the resumption of essential missions and business functions within [Assignment: organization-defined time period] of contingency plan activation. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. The time period for resumption of essential missions/business functions may be dependent on the severity/extent of disruptions to the information system and its supporting infrastructure. Related control: PE-12. | link | count: 001 Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-2(4) | NIST_SP_800-53_R4_CP-2(4) | NIST SP 800-53 Rev. 4 CP-2 (4) | Contingency Planning | Resume All Missions / Business Functions | Shared | n/a | The organization plans for the resumption of all missions and business functions within [Assignment: organization-defined time period] of contingency plan activation. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. The time period for resumption of all missions/business functions may be dependent on the severity/extent of disruptions to the information system and its supporting infrastructure. Related control: PE-12. | link | count: 001 Resume all mission and business functions (91a54089-2d69-0f56-62dc-b6371a1671c0) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-2(5) | NIST_SP_800-53_R4_CP-2(5) | NIST SP 800-53 Rev. 4 CP-2 (5) | Contingency Planning | Continue Essential Missions / Business Functions | Shared | n/a | The organization plans for the continuance of essential missions and business functions with little or no loss of operational continuity and sustains that continuity until full information system restoration at primary processing and/or storage sites. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. Primary processing and/or storage sites defined by organizations as part of contingency planning may change depending on the circumstances associated with the contingency (e.g., backup sites may become primary sites). Related control: PE-12. | link | count: 001 Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-2(8) | NIST_SP_800-53_R4_CP-2(8) | NIST SP 800-53 Rev. 4 CP-2 (8) | Contingency Planning | Identify Critical Assets | Shared | n/a | The organization identifies critical information system assets supporting essential missions and business functions. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. Organizations identify critical information system assets so that additional safeguards and countermeasures can be employed (above and beyond those safeguards and countermeasures routinely implemented) to help ensure that organizational missions/business functions can continue to be conducted during contingency operations. In addition, the identification of critical information assets facilitates the prioritization of organizational resources. Critical information system assets include technical and operational aspects. Technical aspects include, for example, information technology services, information system components, information technology products, and mechanisms. Operational aspects include, for example, procedures (manually executed operations) and personnel (individuals operating technical safeguards and/or executing manual procedures). Organizational program protection plans can provide assistance in identifying critical assets. Related controls: SA-14, SA-15. | link | count: 001 Perform a business impact assessment and application criticality assessment (cb8841d4-9d13-7292-1d06-ba4d68384681) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-3 | NIST_SP_800-53_R4_CP-3 | NIST SP 800-53 Rev. 4 CP-3 | Contingency Planning | Contingency Training | Shared | n/a | The organization provides contingency training to information system users consistent with assigned roles and responsibilities: a. Within [Assignment: organization-defined time period] of assuming a contingency role or responsibility; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Contingency training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, regular users may only need to know when and where to report for duty during contingency operations and if normal duties are affected; system administrators may require additional training on how to set up information systems at alternate processing and storage sites; and managers/senior leaders may receive more specific training on how to conduct mission-essential functions in designated off-site locations and how to establish communications with other governmental entities for purposes of coordination on contingency-related activities. Training for contingency roles/responsibilities reflects the specific continuity requirements in the contingency plan. Related controls: AT-2, AT-3, CP-2, IR-2. References: Federal Continuity Directive 1; NIST Special Publications 800-16, 800-50. | link | count: 001 Provide contingency training (de936662-13dc-204c-75ec-1af80f994088) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-3(1) | NIST_SP_800-53_R4_CP-3(1) | NIST SP 800-53 Rev. 4 CP-3 (1) | Contingency Planning | Simulated Events | Shared | n/a | The organization incorporates simulated events into contingency training to facilitate effective response by personnel in crisis situations. | link | count: 001 Incorporate simulated contingency training (9c954fcf-6dd8-81f1-41b5-832ae5c62caf) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-4 | NIST_SP_800-53_R4_CP-4 | NIST SP 800-53 Rev. 4 CP-4 | Contingency Planning | Contingency Plan Testing | Shared | n/a | The organization: a. Tests the contingency plan for the information system [Assignment: organization-defined frequency] using [Assignment: organization-defined tests] to determine the effectiveness of the plan and the organizational readiness to execute the plan; b. Reviews the contingency plan test results; and c. Initiates corrective actions, if needed. Supplemental Guidance: Methods for testing contingency plans to determine the effectiveness of the plans and to identify potential weaknesses in the plans include, for example, walk-through and tabletop exercises, checklists, simulations (parallel, full interrupt), and comprehensive exercises. Organizations conduct testing based on the continuity requirements in contingency plans and include a determination of the effects on organizational operations, assets, and individuals arising due to contingency operations. Organizations have flexibility and discretion in the breadth, depth, and timelines of corrective actions. Related controls: CP-2, CP-3, IR-3. References: Federal Continuity Directive 1; FIPS Publication 199; NIST Special Publications 800-34, 800-84. | link | count: 003 Initiate contingency plan testing corrective actions (8bfdbaa6-6824-3fec-9b06-7961bf7389a6), Review the results of contingency plan testing (5d3abfea-a130-1208-29c0-e57de80aa6b0), Test the business continuity and disaster recovery plan (58a51cde-008b-1a5d-61b5-d95849770677) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-4(1) | NIST_SP_800-53_R4_CP-4(1) | NIST SP 800-53 Rev. 4 CP-4 (1) | Contingency Planning | Coordinate With Related Plans | Shared | n/a | The organization coordinates contingency plan testing with organizational elements responsible for related plans. Supplemental Guidance: Plans related to contingency plans for organizational information systems include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, and Occupant Emergency Plans. This control enhancement does not require organizations to create organizational elements to handle related plans or to align such elements with specific plans. It does require, however, that if such organizational elements are responsible for related plans, organizations should coordinate with those elements. Related controls: IR-8, PM-8. | link | count: 001 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-4(2) | NIST_SP_800-53_R4_CP-4(2) | NIST SP 800-53 Rev. 4 CP-4 (2) | Contingency Planning | Alternate Processing Site | Shared | n/a | The organization tests the contingency plan at the alternate processing site: (a) To familiarize contingency personnel with the facility and available resources; and (b) To evaluate the capabilities of the alternate processing site to support contingency operations. Supplemental Guidance: Related control: CP-7. | link | count: 002 Evaluate alternate processing site capabilities (60442979-6333-85f0-84c5-b887bac67448), Test contingency plan at an alternate processing location (ba99d512-3baa-1c38-8b0b-ae16bbd34274) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-6 | NIST_SP_800-53_R4_CP-6 | NIST SP 800-53 Rev. 4 CP-6 | Contingency Planning | Alternate Storage Site | Shared | n/a | The organization: a. Establishes an alternate storage site including necessary agreements to permit the storage and retrieval of information system backup information; and b. Ensures that the alternate storage site provides information security safeguards equivalent to that of the primary site. Supplemental Guidance: Alternate storage sites are sites that are geographically distinct from primary storage sites. An alternate storage site maintains duplicate copies of information and data in the event that the primary storage site is not available. Items covered by alternate storage site agreements include, for example, environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and coordination of delivery/retrieval of backup media. Alternate storage sites reflect the requirements in contingency plans so that organizations can maintain essential missions/business functions despite disruption, compromise, or failure in organizational information systems. Related controls: CP-2, CP-7, CP-9, CP-10, MP-4. References: NIST Special Publication 800-34. | link | count: 007 Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Regulatory Compliance, SQL, Storage | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-6(1) | NIST_SP_800-53_R4_CP-6(1) | NIST SP 800-53 Rev. 4 CP-6 (1) | Contingency Planning | Separation From Primary Site | Shared | n/a | The organization identifies an alternate storage site that is separated from the primary storage site to reduce susceptibility to the same threats. Supplemental Guidance: Threats that affect alternate storage sites are typically defined in organizational assessments of risk and include, for example, natural disasters, structural failures, hostile cyber attacks, and errors of omission/commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate storage sites based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites is less relevant. Related control: RA-3. | link | count: 006 Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Regulatory Compliance, SQL, Storage | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-6(2) | NIST_SP_800-53_R4_CP-6(2) | NIST SP 800-53 Rev. 4 CP-6 (2) | Contingency Planning | Recovery Time / Point Objectives | Shared | n/a | The organization configures the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives. | link | count: 001 Establish alternate storage site that facilitates recovery operations (245fe58b-96f8-9f1e-48c5-7f49903f66fd) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-6(3) | NIST_SP_800-53_R4_CP-6(3) | NIST SP 800-53 Rev. 4 CP-6 (3) | Contingency Planning | Accessibility | Shared | n/a | The organization identifies potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions. Supplemental Guidance: Area-wide disruptions refer to those types of disruptions that are broad in geographic scope (e.g., hurricane, regional power outage) with such determinations made by organizations based on organizational assessments of risk. Explicit mitigation actions include, for example: (i) duplicating backup information at other alternate storage sites if access problems occur at originally designated alternate sites; or (ii) planning for physical access to retrieve backup information if electronic accessibility to the alternate site is disrupted. Related control: RA-3. | link | count: 001 Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-7 | NIST_SP_800-53_R4_CP-7 | NIST SP 800-53 Rev. 4 CP-7 | Contingency Planning | Alternate Processing Site | Shared | n/a | The organization: a. Establishes an alternate processing site including necessary agreements to permit the transfer and resumption of [Assignment: organization-defined information system operations] for essential missions/business functions within [Assignment: organization-defined time period consistent with recovery time and recovery point objectives] when the primary processing capabilities are unavailable; b. Ensures that equipment and supplies required to transfer and resume operations are available at the alternate processing site or contracts are in place to support delivery to the site within the organization-defined time period for transfer/resumption; and c. Ensures that the alternate processing site provides information security safeguards equivalent to that of the primary site. Supplemental Guidance: Alternate processing sites are sites that are geographically distinct from primary processing sites. An alternate processing site provides processing capability in the event that the primary processing site is not available. Items covered by alternate processing site agreements include, for example, environmental conditions at alternate sites, access rules, physical and environmental protection requirements, and coordination for the transfer/assignment of personnel. Requirements are specifically allocated to alternate processing sites that reflect the requirements in contingency plans to maintain essential missions/business functions despite disruption, compromise, or failure in organizational information systems. Related controls: CP-2, CP-6, CP-8, CP-9, CP-10, MA-6. References: NIST Special Publication 800-34. | link | count: 002 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Compute, Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-7(1) | NIST_SP_800-53_R4_CP-7(1) | NIST SP 800-53 Rev. 4 CP-7 (1) | Contingency Planning | Separation From Primary Site | Shared | n/a | The organization identifies an alternate processing site that is separated from the primary processing site to reduce susceptibility to the same threats. Supplemental Guidance: Threats that affect alternate processing sites are typically defined in organizational assessments of risk and include, for example, natural disasters, structural failures, hostile cyber attacks, and errors of omission/commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate processing sites based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites is less relevant. Related control: RA-3. | link | count: 001 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-7(2) | NIST_SP_800-53_R4_CP-7(2) | NIST SP 800-53 Rev. 4 CP-7 (2) | Contingency Planning | Accessibility | Shared | n/a | The organization identifies potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions. Supplemental Guidance: Area-wide disruptions refer to those types of disruptions that are broad in geographic scope (e.g., hurricane, regional power outage) with such determinations made by organizations based on organizational assessments of risk. Related control: RA-3. | link | count: 001 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-7(3) | NIST_SP_800-53_R4_CP-7(3) | NIST SP 800-53 Rev. 4 CP-7 (3) | Contingency Planning | Priority Of Service | Shared | n/a | The organization develops alternate processing site agreements that contain priority-of-service provisions in accordance with organizational availability requirements (including recovery time objectives). Supplemental Guidance: Priority-of-service agreements refer to negotiated agreements with service providers that ensure that organizations receive priority treatment consistent with their availability requirements and the availability of information resources at the alternate processing site. | link | count: 002 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-7(4) | NIST_SP_800-53_R4_CP-7(4) | NIST SP 800-53 Rev. 4 CP-7 (4) | Contingency Planning | Preparation For Use | Shared | n/a | The organization prepares the alternate processing site so that the site is ready to be used as the operational site supporting essential missions and business functions. Supplemental Guidance: Site preparation includes, for example, establishing configuration settings for information system components at the alternate processing site consistent with the requirements for such settings at the primary site and ensuring that essential supplies and other logistical considerations are in place. Related controls: CM-2, CM-6. | link | count: 001 Prepare alternate processing site for use as operational site (0f31d98d-5ce2-705b-4aa5-b4f6705110dd) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-8(1) | NIST_SP_800-53_R4_CP-8(1) | NIST SP 800-53 Rev. 4 CP-8 (1) | Contingency Planning | Priority Of Service Provisions | Shared | n/a | The organization: (a) Develops primary and alternate telecommunications service agreements that contain priority- of-service provisions in accordance with organizational availability requirements (including recovery time objectives); and (b) Requests Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness in the event that the primary and/or alternate telecommunications services are provided by a common carrier. Supplemental Guidance: Organizations consider the potential mission/business impact in situations where telecommunications service providers are servicing other organizations with similar priority-of-service provisions. | link | count: 001 Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-9 | NIST_SP_800-53_R4_CP-9 | NIST SP 800-53 Rev. 4 CP-9 | Contingency Planning | Information System Backup | Shared | n/a | The organization: a. Conducts backups of user-level information contained in the information system [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; b. Conducts backups of system-level information contained in the information system [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; c. Conducts backups of information system documentation including security-related documentation [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; and d. Protects the confidentiality, integrity, and availability of backup information at storage locations. Supplemental Guidance: System-level information includes, for example, system-state information, operating system and application software, and licenses. User-level information includes any information other than system-level information. Mechanisms employed by organizations to protect the integrity of information system backups include, for example, digital signatures and cryptographic hashes. Protection of system backup information while in transit is beyond the scope of this control. Information system backups reflect the requirements in contingency plans as well as other organizational requirements for backing up information. Related controls: CP-2, CP-6, MP-4, MP-5, SC-13. References: NIST Special Publication 800-34. | link | count: 009 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Backup, Key Vault, Regulatory Compliance, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-9(3) | NIST_SP_800-53_R4_CP-9(3) | NIST SP 800-53 Rev. 4 CP-9 (3) | Contingency Planning | Separate Storage For Critical Information | Shared | n/a | The organization stores backup copies of [Assignment: organization-defined critical information system software and other security-related information] in a separate facility or in a fire-rated container that is not collocated with the operational system. Supplemental Guidance: Critical information system software includes, for example, operating systems, cryptographic key management systems, and intrusion detection/prevention systems. Security-related information includes, for example, organizational inventories of hardware, software, and firmware components. Alternate storage sites typically serve as separate storage facilities for organizations. Related controls: CM-2, CM-8. | link | count: 001 Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | CP-9(5) | NIST_SP_800-53_R4_CP-9(5) | NIST SP 800-53 Rev. 4 CP-9 (5) | Contingency Planning | Transfer To Alternate Storage Site | Shared | n/a | The organization transfers information system backup information to the alternate storage site [Assignment: organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives]. Supplemental Guidance: Information system backup information can be transferred to alternate storage sites either electronically or by physical shipment of storage media. | link | count: 001 Transfer backup information to an alternate storage site (7bdb79ea-16b8-453e-4ca4-ad5b16012414) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-1 | NIST_SP_800-53_R4_IA-1 | NIST SP 800-53 Rev. 4 IA-1 | Identification And Authentication | Identification And Authentication Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls; and b. Reviews and updates the current: 1. Identification and authentication policy [Assignment: organization-defined frequency]; and 2. Identification and authentication procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the IA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: FIPS Publication 201; NIST Special Publications 800-12, 800-63, 800-73, 800-76, 800-78, 800-100. | link | count: 001 Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-2 | NIST_SP_800-53_R4_IA-2 | NIST SP 800-53 Rev. 4 IA-2 | Identification And Authentication | Identification And Authentication (Organizational Users) | Shared | n/a | The information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users). Supplemental Guidance: Organizational users include employees or individuals that organizations deem to have equivalent status of employees (e.g., contractors, guest researchers). This control applies to all accesses other than: (i) accesses that are explicitly identified and documented in AC-14; and (ii) accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity. Organizations employ passwords, tokens, or biometrics to authenticate user identities, or in the case multifactor authentication, or some combination thereof. Access to organizational information systems is defined as either local access or network access. Local access is any access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained by direct connections without the use of networks. Network access is access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks (e.g., the Internet). Internal networks include local area networks and wide area networks. In addition, the use of encrypted virtual private networks (VPNs) for network connections between organization- controlled endpoints and non-organization controlled endpoints may be treated as internal networks from the perspective of protecting the confidentiality and integrity of information traversing the network. Organizations can satisfy the identification and authentication requirements in this control by complying with the requirements in Homeland Security Presidential Directive 12 consistent with the specific organizational implementation plans. Multifactor authentication requires the use of two or more different factors to achieve authentication. The factors are defined as: (i) something you know (e.g., password, personal identification number [PIN]); (ii) something you have (e.g., cryptographic identification device, token); or (iii) something you are (e.g., biometric). Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card. In addition to identifying and authenticating users at the information system level (i.e., at logon), organizations also employ identification and authentication mechanisms at the application level, when necessary, to provide increased information security. Identification and authentication requirements for other than organizational users are described in IA-8. Related controls: AC-2, AC-3, AC-14, AC-17, AC-18, IA-4, IA-5, IA-8. References: HSPD-12; OMB Memoranda 04-04, 06-16, 11-11; FIPS Publication 201; NIST Special Publications 800-63, 800-73, 800-76, 800-78; FICAM Roadmap and Implementation Guidance; Web: http://idmanagement.gov. | link | count: 010 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
App Service, Azure Ai Services, Regulatory Compliance, Security Center, Service Fabric, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-2(1) | NIST_SP_800-53_R4_IA-2(1) | NIST SP 800-53 Rev. 4 IA-2 (1) | Identification And Authentication | Network Access To Privileged Accounts | Shared | n/a | The information system implements multifactor authentication for network access to privileged accounts. Supplemental Guidance: Related control: AC-6. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-2(11) | NIST_SP_800-53_R4_IA-2(11) | NIST SP 800-53 Rev. 4 IA-2 (11) | Identification And Authentication | Remote Access - Separate Device | Shared | n/a | The information system implements multifactor authentication for remote access to privileged and non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access and the device meets [Assignment: organization-defined strength of mechanism requirements]. Supplemental Guidance: For remote access to privileged/non-privileged accounts, the purpose of requiring a device that is separate from the information system gaining access for one of the factors during multifactor authentication is to reduce the likelihood of compromising authentication credentials stored on the system. For example, adversaries deploying malicious code on organizational information systems can potentially compromise such credentials resident on the system and subsequently impersonate authorized users. Related control: AC-6. | link | count: 002 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-2(12) | NIST_SP_800-53_R4_IA-2(12) | NIST SP 800-53 Rev. 4 IA-2 (12) | Identification And Authentication | Acceptance Of Piv Credentials | Shared | n/a | The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials. Supplemental Guidance: This control enhancement applies to organizations implementing logical access control systems (LACS) and physical access control systems (PACS). Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 requires federal agencies to continue implementing the requirements specified in HSPD-12 to enable agency-wide use of PIV credentials. Related controls: AU-2, PE-3, SA-4. | link | count: 001 Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-2(2) | NIST_SP_800-53_R4_IA-2(2) | NIST SP 800-53 Rev. 4 IA-2 (2) | Identification And Authentication | Network Access To Non-Privileged Accounts | Shared | n/a | The information system implements multifactor authentication for network access to non- privileged accounts. | link | count: 002 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-2(3) | NIST_SP_800-53_R4_IA-2(3) | NIST SP 800-53 Rev. 4 IA-2 (3) | Identification And Authentication | Local Access To Privileged Accounts | Shared | n/a | The information system implements multifactor authentication for local access to privileged accounts. Supplemental Guidance: Related control: AC-6. | link | count: 001 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-2(5) | NIST_SP_800-53_R4_IA-2(5) | NIST SP 800-53 Rev. 4 IA-2 (5) | Identification And Authentication | Group Authentication | Shared | n/a | The organization requires individuals to be authenticated with an individual authenticator when a group authenticator is employed. Supplemental Guidance: Requiring individuals to use individual authenticators as a second level of authentication helps organizations to mitigate the risk of using group authenticators. | link | count: 001 Require use of individual authenticators (08ad71d0-52be-6503-4908-e015460a16ae) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-4 | NIST_SP_800-53_R4_IA-4 | NIST SP 800-53 Rev. 4 IA-4 | Identification And Authentication | Identifier Management | Shared | n/a | The organization manages information system identifiers by: a. Receiving authorization from [Assignment: organization-defined personnel or roles] to assign an individual, group, role, or device identifier; b. Selecting an identifier that identifies an individual, group, role, or device; c. Assigning the identifier to the intended individual, group, role, or device; d. Preventing reuse of identifiers for [Assignment: organization-defined time period]; and e. Disabling the identifier after [Assignment: organization-defined time period of inactivity]. Supplemental Guidance: Common device identifiers include, for example, media access control (MAC), Internet protocol (IP) addresses, or device-unique token identifiers. Management of individual identifiers is not applicable to shared information system accounts (e.g., guest and anonymous accounts). Typically, individual identifiers are the user names of the information system accounts assigned to those individuals. In such instances, the account management activities of AC-2 use account names provided by IA-4. This control also addresses individual identifiers not necessarily associated with information system accounts (e.g., identifiers used in physical security control databases accessed by badge reader systems for access to information systems). Preventing reuse of identifiers implies preventing the assignment of previously used individual, group, role, or device identifiers to different individuals, groups, roles, or devices. Related controls: AC-2, IA-2, IA-3, IA-5, IA-8, SC-37. References: FIPS Publication 201; NIST Special Publications 800-73, 800-76, 800-78. | link | count: 007 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Prevent identifier reuse for the defined time period (4781e5fd-76b8-7d34-6df3-a0a7fca47665), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-4(4) | NIST_SP_800-53_R4_IA-4(4) | NIST SP 800-53 Rev. 4 IA-4 (4) | Identification And Authentication | Identify User Status | Shared | n/a | The organization manages individual identifiers by uniquely identifying each individual as [Assignment: organization-defined characteristic identifying individual status]. Supplemental Guidance: Characteristics identifying the status of individuals include, for example, contractors and foreign nationals. Identifying the status of individuals by specific characteristics provides additional information about the people with whom organizational personnel are communicating. For example, it might be useful for a government employee to know that one of the individuals on an email message is a contractor. Related control: AT-2. | link | count: 001 Identify status of individual users (ca748dfe-3e28-1d18-4221-89aea30aa0a5) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-5 | NIST_SP_800-53_R4_IA-5 | NIST SP 800-53 Rev. 4 IA-5 | Identification And Authentication | Authenticator Management | Shared | n/a | The organization manages information system authenticators by: a. Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, or device receiving the authenticator; b. Establishing initial authenticator content for authenticators defined by the organization; c. Ensuring that authenticators have sufficient strength of mechanism for their intended use; d. Establishing and implementing administrative procedures for initial authenticator distribution, for lost/compromised or damaged authenticators, and for revoking authenticators; e. Changing default content of authenticators prior to information system installation; f. Establishing minimum and maximum lifetime restrictions and reuse conditions for authenticators; g. Changing/refreshing authenticators [Assignment: organization-defined time period by authenticator type]; h. Protecting authenticator content from unauthorized disclosure and modification; i. Requiring individuals to take, and having devices implement, specific security safeguards to protect authenticators; and j. Changing authenticators for group/role accounts when membership to those accounts changes. Supplemental Guidance: Individual authenticators include, for example, passwords, tokens, biometrics, PKI certificates, and key cards. Initial authenticator content is the actual content (e.g., the initial password) as opposed to requirements about authenticator content (e.g., minimum password length). In many cases, developers ship information system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant security risk. The requirement to protect individual authenticators may be implemented via control PL-4 or PS-6 for authenticators in the possession of individuals and by controls AC-3, AC-6, and SC-28 for authenticators stored within organizational information systems (e.g., passwords stored in hashed or encrypted formats, files containing encrypted or hashed passwords accessible with administrator privileges). Information systems support individual authenticator management by organization-defined settings and restrictions for various authenticator characteristics including, for example, minimum password length, password composition, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication. Specific actions that can be taken to safeguard authenticators include, for example, maintaining possession of individual authenticators, not loaning or sharing individual authenticators with others, and reporting lost, stolen, or compromised authenticators immediately. Authenticator management includes issuing and revoking, when no longer needed, authenticators for temporary access such as that required for remote maintenance. Device authenticators include, for example, certificates and passwords. Related controls: AC-2, AC-3, AC-6, CM-6, IA-2, IA-4, IA-8, PL-4, PS-5, PS-6, SC-12, SC-13, SC-17, SC-28. References: OMB Memoranda 04-04, 11-11; FIPS Publication 201; NIST Special Publications 800-73, 800-63, 800-76, 800-78; FICAM Roadmap and Implementation Guidance | link | count: 018 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Guest Configuration, Key Vault, Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-5(1) | NIST_SP_800-53_R4_IA-5(1) | NIST SP 800-53 Rev. 4 IA-5 (1) | Identification And Authentication | Password-Based Authentication | Shared | n/a | The information system, for password-based authentication: (a) Enforces minimum password complexity of [Assignment: organization-defined requirements for case sensitivity, number of characters, mix of upper-case letters, lower-case letters, numbers, and special characters, including minimum requirements for each type]; (b) Enforces at least the following number of changed characters when new passwords are created: [Assignment: organization-defined number]; (c) Stores and transmits only encrypted representations of passwords; (d) Enforces password minimum and maximum lifetime restrictions of [Assignment: organization- defined numbers for lifetime minimum, lifetime maximum]; (e) Prohibits password reuse for [Assignment: organization-defined number] generations; and (f) Allows the use of a temporary password for system logons with an immediate change to a permanent password. Supplemental Guidance: This control enhancement applies to single-factor authentication of individuals using passwords as individual or group authenticators, and in a similar manner, when passwords are part of multifactor authenticators. This control enhancement does not apply when passwords are used to unlock hardware authenticators (e.g., Personal Identity Verification cards). The implementation of such password mechanisms may not meet all of the requirements in the enhancement. Encrypted representations of passwords include, for example, encrypted versions of passwords and one-way cryptographic hashes of passwords. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. Password lifetime restrictions do not apply to temporary passwords. Related control: IA-6. | link | count: 015 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Guest Configuration, Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-5(11) | NIST_SP_800-53_R4_IA-5(11) | NIST SP 800-53 Rev. 4 IA-5 (11) | Identification And Authentication | Hardware Token-Based Authentication | Shared | n/a | The information system, for hardware token-based authentication, employs mechanisms that satisfy [Assignment: organization-defined token quality requirements]. Supplemental Guidance: Hardware token-based authentication typically refers to the use of PKI-based tokens, such as the U.S. Government Personal Identity Verification (PIV) card. Organizations define specific requirements for tokens, such as working with a particular PKI. | link | count: 001 Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-5(13) | NIST_SP_800-53_R4_IA-5(13) | NIST SP 800-53 Rev. 4 IA-5 (13) | Identification And Authentication | Expiration Of Cached Authenticators | Shared | n/a | The information system prohibits the use of cached authenticators after [Assignment: organization-defined time period]. | link | count: 001 Enforce expiration of cached authenticators (c7e8ddc1-14aa-1814-7fe1-aad1742b27da) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-5(2) | NIST_SP_800-53_R4_IA-5(2) | NIST SP 800-53 Rev. 4 IA-5 (2) | Identification And Authentication | Pki-Based Authentication | Shared | n/a | The information system, for PKI-based authentication: (a) Validates certifications by constructing and verifying a certification path to an accepted trust anchor including checking certificate status information; (b) Enforces authorized access to the corresponding private key; (c) Maps the authenticated identity to the account of the individual or group; and (d) Implements a local cache of revocation data to support path discovery and validation in case of inability to access revocation information via the network. Supplemental Guidance: Status information for certification paths includes, for example, certificate revocation lists or certificate status protocol responses. For PIV cards, validation of certifications involves the construction and verification of a certification path to the Common Policy Root trust anchor including certificate policy processing. Related control: IA-6. | link | count: 007 Bind authenticators and identities dynamically (6f311b49-9b0d-8c67-3d6e-db80ae528173), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish parameters for searching secret authenticators and verifiers (0065241c-72e9-3b2c-556f-75de66332a94), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Map authenticated identities to individuals (4012c2b7-4e0e-a7ab-1688-4aab43f14420), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-5(3) | NIST_SP_800-53_R4_IA-5(3) | NIST SP 800-53 Rev. 4 IA-5 (3) | Identification And Authentication | In-Person Or Trusted Third-Party Registration | Shared | n/a | The organization requires that the registration process to receive [Assignment: organization- defined types of and/or specific authenticators] be conducted [Selection: in person; by a trusted third party] before [Assignment: organization-defined registration authority] with authorization by [Assignment: organization-defined personnel or roles]. | link | count: 001 Distribute authenticators (098dcde7-016a-06c3-0985-0daaf3301d3a) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-5(4) | NIST_SP_800-53_R4_IA-5(4) | NIST SP 800-53 Rev. 4 IA-5 (4) | Identification And Authentication | Automated Support For Password Strength Determination | Shared | n/a | The organization employs automated tools to determine if password authenticators are sufficiently strong to satisfy [Assignment: organization-defined requirements]. Supplemental Guidance: This control enhancement focuses on the creation of strong passwords and the characteristics of such passwords (e.g., complexity) prior to use, the enforcement of which is carried out by organizational information systems in IA-5 (1). Related controls: CA-2, CA-7, RA-5. | link | count: 003 Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-5(6) | NIST_SP_800-53_R4_IA-5(6) | NIST SP 800-53 Rev. 4 IA-5 (6) | Identification And Authentication | Protection Of Authenticators | Shared | n/a | The organization protects authenticators commensurate with the security category of the information to which use of the authenticator permits access. Supplemental Guidance: For information systems containing multiple security categories of information without reliable physical or logical separation between categories, authenticators used to grant access to the systems are protected commensurate with the highest security category of information on the systems. | link | count: 001 Ensure authorized users protect provided authenticators (37dbe3dc-0e9c-24fa-36f2-11197cbfa207) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-5(7) | NIST_SP_800-53_R4_IA-5(7) | NIST SP 800-53 Rev. 4 IA-5 (7) | Identification And Authentication | No Embedded Unencrypted Static Authenticators | Shared | n/a | The organization ensures that unencrypted static authenticators are not embedded in applications or access scripts or stored on function keys. Supplemental Guidance: Organizations exercise caution in determining whether embedded or stored authenticators are in encrypted or unencrypted form. If authenticators are used in the manner stored, then those representations are considered unencrypted authenticators. This is irrespective of whether that representation is perhaps an encrypted version of something else (e.g., a password). | link | count: 001 Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-6 | NIST_SP_800-53_R4_IA-6 | NIST SP 800-53 Rev. 4 IA-6 | Identification And Authentication | Authenticator Feedback | Shared | n/a | The information system obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. Supplemental Guidance: The feedback from information systems does not provide information that would allow unauthorized individuals to compromise authentication mechanisms. For some types of information systems or system components, for example, desktops/notebooks with relatively large monitors, the threat (often referred to as shoulder surfing) may be significant. For other types of systems or components, for example, mobile devices with 2-4 inch screens, this threat may be less significant, and may need to be balanced against the increased likelihood of typographic input errors due to the small keyboards. Therefore, the means for obscuring the authenticator feedback is selected accordingly. Obscuring the feedback of authentication information includes, for example, displaying asterisks when users type passwords into input devices, or displaying feedback for a very limited time before fully obscuring it. Related control: PE-18. Control Enhancements: None. References: None. | link | count: 001 Obscure feedback information during authentication process (1ff03f2a-974b-3272-34f2-f6cd51420b30) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-7 | NIST_SP_800-53_R4_IA-7 | NIST SP 800-53 Rev. 4 IA-7 | Identification And Authentication | Cryptographic Module Authentication | Shared | n/a | The information system implements mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication. Supplemental Guidance: Authentication mechanisms may be required within a cryptographic module to authenticate an operator accessing the module and to verify that the operator is authorized to assume the requested role and perform services within that role. Related controls: SC-12, SC-13. Control Enhancements: None. References: FIPS Publication 140; Web: csrc.nist.gov/groups/STM/cmvp/index.html. | link | count: 001 Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-8 | NIST_SP_800-53_R4_IA-8 | NIST SP 800-53 Rev. 4 IA-8 | Identification And Authentication | Identification And Authentication (Non- Organizational Users) | Shared | n/a | The information system uniquely identifies and authenticates non-organizational users (or processes acting on behalf of non-organizational users). Supplemental Guidance: Non-organizational users include information system users other than organizational users explicitly covered by IA-2. These individuals are uniquely identified and authenticated for accesses other than those accesses explicitly identified and documented in AC-14. In accordance with the E-Authentication E-Government initiative, authentication of non- organizational users accessing federal information systems may be required to protect federal, proprietary, or privacy-related information (with exceptions noted for national security systems). Organizations use risk assessments to determine authentication needs and consider scalability, practicality, and security in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk. IA-2 addresses identification and authentication requirements for access to information systems by organizational users. Related controls: AC-2, AC-14, AC-17, AC-18, IA-2, IA-4, IA-5, MA-4, RA-3, SA-12, SC-8. References: OMB Memoranda 04-04, 11-11, 10-06-2011; FICAM Roadmap and Implementation Guidance; FIPS Publication 201; NIST Special Publications 800-63, 800-116; National Strategy for Trusted Identities in Cyberspace; Web: http://idmanagement.gov. | link | count: 001 Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-8(1) | NIST_SP_800-53_R4_IA-8(1) | NIST SP 800-53 Rev. 4 IA-8 (1) | Identification And Authentication | Acceptance Of Piv Credentials From Other Agencies | Shared | n/a | The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials from other federal agencies. Supplemental Guidance: This control enhancement applies to logical access control systems (LACS) and physical access control systems (PACS). Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 requires federal agencies to continue implementing the requirements specified in HSPD-12 to enable agency-wide use of PIV credentials. Related controls: AU-2, PE-3, SA-4. | link | count: 001 Accept PIV credentials (55be3260-a7a2-3c06-7fe6-072d07525ab7) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-8(2) | NIST_SP_800-53_R4_IA-8(2) | NIST SP 800-53 Rev. 4 IA-8 (2) | Identification And Authentication | Acceptance Of Third-Party Credentials | Shared | n/a | The information system accepts only FICAM-approved third-party credentials. Supplemental Guidance: This control enhancement typically applies to organizational information systems that are accessible to the general public, for example, public-facing websites. Third-party credentials are those credentials issued by nonfederal government entities approved by the Federal Identity, Credential, and Access Management (FICAM) Trust Framework Solutions initiative. Approved third-party credentials meet or exceed the set of minimum federal government-wide technical, security, privacy, and organizational maturity requirements. This allows federal government relying parties to trust such credentials at their approved assurance levels. Related control: AU-2. | link | count: 001 Accept only FICAM-approved third-party credentials (2d2ca910-7957-23ee-2945-33f401606efc) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-8(3) | NIST_SP_800-53_R4_IA-8(3) | NIST SP 800-53 Rev. 4 IA-8 (3) | Identification And Authentication | Use Of Ficam-Approved Products | Shared | n/a | The organization employs only FICAM-approved information system components in [Assignment: organization-defined information systems] to accept third-party credentials. Supplemental Guidance: This control enhancement typically applies to information systems that are accessible to the general public, for example, public-facing websites. FICAM-approved information system components include, for example, information technology products and software libraries that have been approved by the Federal Identity, Credential, and Access Management conformance program. Related control: SA-4. | link | count: 001 Employ FICAM-approved resources to accept third-party credentials (db8b35d6-8adb-3f51-44ff-c648ab5b1530) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IA-8(4) | NIST_SP_800-53_R4_IA-8(4) | NIST SP 800-53 Rev. 4 IA-8 (4) | Identification And Authentication | Use Of Ficam-Issued Profiles | Shared | n/a | The information system conforms to FICAM-issued profiles. Supplemental Guidance: This control enhancement addresses open identity management standards. To ensure that these standards are viable, robust, reliable, sustainable (e.g., available in commercial information technology products), and interoperable as documented, the United States Government assesses and scopes identity management standards and technology implementations against applicable federal legislation, directives, policies, and requirements. The result is FICAM-issued implementation profiles of approved protocols (e.g., FICAM authentication protocols such as SAML 2.0 and OpenID 2.0, as well as other protocols such as the FICAM Backend Attribute Exchange). Related control: SA-4. | link | count: 001 Conform to FICAM-issued profiles (a8df9c78-4044-98be-2c05-31a315ac8957) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-1 | NIST_SP_800-53_R4_IR-1 | NIST SP 800-53 Rev. 4 IR-1 | Incident Response | Incident Response Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. An incident response policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the incident response policy and associated incident response controls; and b. Reviews and updates the current: 1. Incident response policy [Assignment: organization-defined frequency]; and 2. Incident response procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the IR family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-61, 800-83, 800-100. | link | count: 001 Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-2 | NIST_SP_800-53_R4_IR-2 | NIST SP 800-53 Rev. 4 IR-2 | Incident Response | Incident Response Training | Shared | n/a | The organization provides incident response training to information system users consistent with assigned roles and responsibilities: a. Within [Assignment: organization-defined time period] of assuming an incident response role or responsibility; b. When required by information system changes; and c. [Assignment: organization-defined frequency] thereafter. Supplemental Guidance: Incident response training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure the appropriate content and level of detail is included in such training. For example, regular users may only need to know who to call or how to recognize an incident on the information system; system administrators may require additional training on how to handle/remediate incidents; and incident responders may receive more specific training on forensics, reporting, system recovery, and restoration. Incident response training includes user training in the identification and reporting of suspicious activities, both from external and internal sources. Related controls: AT-3, CP-3, IR-8. References: NIST Special Publications 800-16, 800-50. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-2(1) | NIST_SP_800-53_R4_IR-2(1) | NIST SP 800-53 Rev. 4 IR-2 (1) | Incident Response | Simulated Events | Shared | n/a | The organization incorporates simulated events into incident response training to facilitate effective response by personnel in crisis situations. | link | count: 001 Incorporate simulated events into incident response training (1fdeb7c4-4c93-8271-a135-17ebe85f1cc7) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-2(2) | NIST_SP_800-53_R4_IR-2(2) | NIST SP 800-53 Rev. 4 IR-2 (2) | Incident Response | Automated Training Environments | Shared | n/a | The organization employs automated mechanisms to provide a more thorough and realistic incident response training environment. | link | count: 001 Employ automated training environment (c8aa992d-76b7-7ca0-07b3-31a58d773fa9) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-3 | NIST_SP_800-53_R4_IR-3 | NIST SP 800-53 Rev. 4 IR-3 | Incident Response | Incident Response Testing | Shared | n/a | The organization tests the incident response capability for the information system [Assignment: organization-defined frequency] using [Assignment: organization-defined tests] to determine the incident response effectiveness and documents the results. Supplemental Guidance: Organizations test incident response capabilities to determine the overall effectiveness of the capabilities and to identify potential weaknesses or deficiencies. Incident response testing includes, for example, the use of checklists, walk-through or tabletop exercises, simulations (parallel/full interrupt), and comprehensive exercises. Incident response testing can also include a determination of the effects on organizational operations (e.g., reduction in mission capabilities), organizational assets, and individuals due to incident response. Related controls: CP-4, IR-8. References: NIST Special Publications 800-84, 800-115. | link | count: 003 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-3(2) | NIST_SP_800-53_R4_IR-3(2) | NIST SP 800-53 Rev. 4 IR-3 (2) | Incident Response | Coordination With Related Plans | Shared | n/a | The organization coordinates incident response testing with organizational elements responsible for related plans. Supplemental Guidance: Organizational plans related to incident response testing include, for example, Business Continuity Plans, Contingency Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, and Occupant Emergency Plans. | link | count: 003 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-4 | NIST_SP_800-53_R4_IR-4 | NIST SP 800-53 Rev. 4 IR-4 | Incident Response | Incident Handling | Shared | n/a | The organization: a. Implements an incident handling capability for security incidents that includes preparation, detection and analysis, containment, eradication, and recovery; b. Coordinates incident handling activities with contingency planning activities; and c. Incorporates lessons learned from ongoing incident handling activities into incident response procedures, training, and testing/exercises, and implements the resulting changes accordingly. Supplemental Guidance: Organizations recognize that incident response capability is dependent on the capabilities of organizational information systems and the mission/business processes being supported by those systems. Therefore, organizations consider incident response as part of the definition, design, and development of mission/business processes and information systems. Incident-related information can be obtained from a variety of sources including, for example, audit monitoring, network monitoring, physical access monitoring, user/administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including, for example, mission/business owners, information system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive (function). Related controls: AU-6, CM-6, CP-2, CP-4, IR-2, IR-3, IR-8, PE-6, SC-5, SC-7, SI-3, SI-4, SI-7. References: Executive Order 13587; NIST Special Publication 800-61. | link | count: 024 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance, Security Center, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-4(1) | NIST_SP_800-53_R4_IR-4(1) | NIST SP 800-53 Rev. 4 IR-4 (1) | Incident Response | Automated Incident Handling Processes | Shared | n/a | The organization employs automated mechanisms to support the incident handling process. Supplemental Guidance: Automated mechanisms supporting incident handling processes include, for example, online incident management systems. | link | count: 003 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-4(2) | NIST_SP_800-53_R4_IR-4(2) | NIST SP 800-53 Rev. 4 IR-4 (2) | Incident Response | Dynamic Reconfiguration | Shared | n/a | The organization includes dynamic reconfiguration of [Assignment: organization-defined information system components] as part of the incident response capability. Supplemental Guidance: Dynamic reconfiguration includes, for example, changes to router rules, access control lists, intrusion detection/prevention system parameters, and filter rules for firewalls and gateways. Organizations perform dynamic reconfiguration of information systems, for example, to stop attacks, to misdirect attackers, and to isolate components of systems, thus limiting the extent of the damage from breaches or compromises. Organizations include time frames for achieving the reconfiguration of information systems in the definition of the reconfiguration capability, considering the potential need for rapid response in order to effectively address sophisticated cyber threats. Related controls: AC-2, AC-4, AC-16, CM-2, CM-3, CM-4. | link | count: 001 Include dynamic reconfig of customer deployed resources (1e0d5ba8-a433-01aa-829c-86b06c9631ec) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-4(3) | NIST_SP_800-53_R4_IR-4(3) | NIST SP 800-53 Rev. 4 IR-4 (3) | Incident Response | Continuity Of Operations | Shared | n/a | The organization identifies [Assignment: organization-defined classes of incidents] and [Assignment: organization-defined actions to take in response to classes of incidents] to ensure continuation of organizational missions and business functions. Supplemental Guidance: Classes of incidents include, for example, malfunctions due to design/implementation errors and omissions, targeted malicious attacks, and untargeted malicious attacks. Appropriate incident response actions include, for example, graceful degradation, information system shutdown, fall back to manual mode/alternative technology whereby the system operates differently, employing deceptive measures, alternate information flows, or operating in a mode that is reserved solely for when systems are under attack. | link | count: 001 Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-4(4) | NIST_SP_800-53_R4_IR-4(4) | NIST SP 800-53 Rev. 4 IR-4 (4) | Incident Response | Information Correlation | Shared | n/a | The organization correlates incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response. Supplemental Guidance: Sometimes the nature of a threat event, for example, a hostile cyber attack, is such that it can only be observed by bringing together information from different sources including various reports and reporting procedures established by organizations. | link | count: 001 Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-4(6) | NIST_SP_800-53_R4_IR-4(6) | NIST SP 800-53 Rev. 4 IR-4 (6) | Incident Response | Insider Threats - Specific Capabilities | Shared | n/a | The organization implements incident handling capability for insider threats. Supplemental Guidance: While many organizations address insider threat incidents as an inherent part of their organizational incident response capability, this control enhancement provides additional emphasis on this type of threat and the need for specific incident handling capabilities (as defined within organizations) to provide appropriate and timely responses. | link | count: 001 Implement Incident handling capability (98e33927-8d7f-6d5f-44f5-2469b40b7215) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-4(8) | NIST_SP_800-53_R4_IR-4(8) | NIST SP 800-53 Rev. 4 IR-4 (8) | Incident Response | Correlation With External Organizations | Shared | n/a | The organization coordinates with [Assignment: organization-defined external organizations] to correlate and share [Assignment: organization-defined incident information] to achieve a cross- organization perspective on incident awareness and more effective incident responses. Supplemental Guidance: The coordination of incident information with external organizations including, for example, mission/business partners, military/coalition partners, customers, and multitiered developers, can provide significant benefits. Cross-organizational coordination with respect to incident handling can serve as an important risk management capability. This capability allows organizations to leverage critical information from a variety of sources to effectively respond to information security-related incidents potentially affecting the organization’s operations, assets, and individuals. | link | count: 001 Coordinate with external organizations to achieve cross org perspective (d4e6a629-28eb-79a9-000b-88030e4823ca) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-5 | NIST_SP_800-53_R4_IR-5 | NIST SP 800-53 Rev. 4 IR-5 | Incident Response | Incident Monitoring | Shared | n/a | The organization tracks and documents information system security incidents. Supplemental Guidance: Documenting information system security incidents includes, for example, maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics, evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources including, for example, incident reports, incident response teams, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports. Related controls: AU-6, IR-8, PE-6, SC-5, SC-7, SI-3, SI-4, SI-7. References: NIST Special Publication 800-61. | link | count: 013 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-6(1) | NIST_SP_800-53_R4_IR-6(1) | NIST SP 800-53 Rev. 4 IR-6 (1) | Incident Response | Automated Reporting | Shared | n/a | The organization employs automated mechanisms to assist in the reporting of security incidents. Supplemental Guidance: Related control: IR-7. | link | count: 001 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-6(2) | NIST_SP_800-53_R4_IR-6(2) | NIST SP 800-53 Rev. 4 IR-6 (2) | Incident Response | Vulnerabilities Related to Incidents | Customer | n/a | The organization reports information system vulnerabilities associated with reported security incidents to [Assignment: organization-defined personnel or roles]. | link | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-7 | NIST_SP_800-53_R4_IR-7 | NIST SP 800-53 Rev. 4 IR-7 | Incident Response | Incident Response Assistance | Shared | n/a | The organization provides an incident response support resource, integral to the organizational incident response capability that offers advice and assistance to users of the information system for the handling and reporting of security incidents. Supplemental Guidance: Incident response support resources provided by organizations include, for example, help desks, assistance groups, and access to forensics services, when required. Related controls: AT-2, IR-4, IR-6, IR-8, SA-9. | link | count: 001 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-7(1) | NIST_SP_800-53_R4_IR-7(1) | NIST SP 800-53 Rev. 4 IR-7 (1) | Incident Response | Automation Support For Availability Of Information / Support | Shared | n/a | The organization employs automated mechanisms to increase the availability of incident response- related information and support. Supplemental Guidance: Automated mechanisms can provide a push and/or pull capability for users to obtain incident response assistance. For example, individuals might have access to a website to query the assistance capability, or conversely, the assistance capability may have the ability to proactively send information to users (general distribution or targeted) as part of increasing understanding of current response capabilities and support. | link | count: 007 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-7(2) | NIST_SP_800-53_R4_IR-7(2) | NIST SP 800-53 Rev. 4 IR-7 (2) | Incident Response | Coordination With External Providers | Shared | n/a | The organization: (a) Establishes a direct, cooperative relationship between its incident response capability and external providers of information system protection capability; and (b) Identifies organizational incident response team members to the external providers. Supplemental Guidance: External providers of information system protection capability include, for example, the Computer Network Defense program within the U.S. Department of Defense. External providers help to protect, monitor, analyze, detect, and respond to unauthorized activity within organizational information systems and networks. | link | count: 002 Establish relationship between incident response capability and external providers (b470a37a-7a47-3792-34dd-7a793140702e), Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-8 | NIST_SP_800-53_R4_IR-8 | NIST SP 800-53 Rev. 4 IR-8 | Incident Response | Incident Response Plan | Shared | n/a | The organization: a. Develops an incident response plan that: 1. Provides the organization with a roadmap for implementing its incident response capability; 2. Describes the structure and organization of the incident response capability; 3. Provides a high-level approach for how the incident response capability fits into the overall organization; 4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions; 5. Defines reportable incidents; 6. Provides metrics for measuring the incident response capability within the organization; 7. Defines the resources and management support needed to effectively maintain and mature an incident response capability; and 8. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; b. Distributes copies of the incident response plan to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; c. Reviews the incident response plan [Assignment: organization-defined frequency]; d. Updates the incident response plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing; e. Communicates incident response plan changes to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and f. Protects the incident response plan from unauthorized disclosure and modification. Supplemental Guidance: It is important that organizations develop and implement a coordinated approach to incident response. Organizational missions, business functions, strategies, goals, and objectives for incident response help to determine the structure of incident response capabilities. As part of a comprehensive incident response capability, organizations consider the coordination and sharing of information with external organizations, including, for example, external service providers and organizations involved in the supply chain for organizational information systems. Related controls: MP-2, MP-4, MP-5. Control Enhancements: None. References: NIST Special Publication 800-61. | link | count: 006 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-9 | NIST_SP_800-53_R4_IR-9 | NIST SP 800-53 Rev. 4 IR-9 | Incident Response | Information Spillage Response | Shared | n/a | The organization responds to information spills by: a. Identifying the specific information involved in the information system contamination; b. Alerting [Assignment: organization-defined personnel or roles] of the information spill using a method of communication not associated with the spill; c. Isolating the contaminated information system or system component; d. Eradicating the information from the contaminated information system or component; e. Identifying other information systems or system components that may have been subsequently contaminated; and f. Performing other [Assignment: organization-defined actions]. Supplemental Guidance: Information spillage refers to instances where either classified or sensitive information is inadvertently placed on information systems that are not authorized to process such information. Such information spills often occur when information that is initially thought to be of lower sensitivity is transmitted to an information system and then is subsequently determined to be of higher sensitivity. At that point, corrective action is required. The nature of the organizational response is generally based upon the degree of sensitivity of the spilled information (e.g., security category or classification level), the security capabilities of the information system, the specific nature of contaminated storage media, and the access authorizations (e.g., security clearances) of individuals with authorized access to the contaminated system. The methods used to communicate information about the spill after the fact do not involve methods directly associated with the actual spill to minimize the risk of further spreading the contamination before such contamination is isolated and eradicated. References: None. | link | count: 007 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify contaminated systems and components (279052a0-8238-694d-9661-bf649f951747), Identify spilled information (69d90ee6-9f9f-262a-2038-d909fb4e5723), Isolate information spills (22457e81-3ec6-5271-a786-c3ca284601dd) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-9(1) | NIST_SP_800-53_R4_IR-9(1) | NIST SP 800-53 Rev. 4 IR-9 (1) | Incident Response | Responsible Personnel | Shared | n/a | The organization assigns [Assignment: organization-defined personnel or roles] with responsibility for responding to information spills. | link | count: 001 Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-9(2) | NIST_SP_800-53_R4_IR-9(2) | NIST SP 800-53 Rev. 4 IR-9 (2) | Incident Response | Training | Shared | n/a | The organization provides information spillage response training [Assignment: organization- defined frequency]. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-9(3) | NIST_SP_800-53_R4_IR-9(3) | NIST SP 800-53 Rev. 4 IR-9 (3) | Incident Response | Post-Spill Operations | Shared | n/a | The organization implements [Assignment: organization-defined procedures] to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions. Supplemental Guidance: Correction actions for information systems contaminated due to information spillages may be very time-consuming. During those periods, personnel may not have access to the contaminated systems, which may potentially affect their ability to conduct organizational business. | link | count: 001 Develop spillage response procedures (bb048641-6017-7272-7772-a008f285a520) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | IR-9(4) | NIST_SP_800-53_R4_IR-9(4) | NIST SP 800-53 Rev. 4 IR-9 (4) | Incident Response | Exposure To Unauthorized Personnel | Shared | n/a | The organization employs [Assignment: organization-defined security safeguards] for personnel exposed to information not within assigned access authorizations. Supplemental Guidance: Security safeguards include, for example, making personnel exposed to spilled information aware of the federal laws, directives, policies, and/or regulations regarding the information and the restrictions imposed based on exposure to such information. | link | count: 001 Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-1 | NIST_SP_800-53_R4_MA-1 | NIST SP 800-53 Rev. 4 MA-1 | Maintenance | System Maintenance Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls; and b. Reviews and updates the current: 1. System maintenance policy [Assignment: organization-defined frequency]; and 2. System maintenance procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the MA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-2 | NIST_SP_800-53_R4_MA-2 | NIST SP 800-53 Rev. 4 MA-2 | Maintenance | Controlled Maintenance | Shared | n/a | The organization: a. Schedules, performs, documents, and reviews records of maintenance and repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements; b. Approves and monitors all maintenance activities, whether performed on site or remotely and whether the equipment is serviced on site or removed to another location; c. Requires that [Assignment: organization-defined personnel or roles] explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs; d. Sanitizes equipment to remove all information from associated media prior to removal from organizational facilities for off-site maintenance or repairs; e. Checks all potentially impacted security controls to verify that the controls are still functioning properly following maintenance or repair actions; and f. Includes [Assignment: organization-defined maintenance-related information] in organizational maintenance records. Supplemental Guidance: This control addresses the information security aspects of the information system maintenance program and applies to all types of maintenance to any system component (including applications) conducted by any local or nonlocal entity (e.g., in-contract, warranty, in- house, software maintenance agreement). System maintenance also includes those components not directly associated with information processing and/or data/information retention such as scanners, copiers, and printers. Information necessary for creating effective maintenance records includes, for example: (i) date and time of maintenance; (ii) name of individuals or group performing the maintenance; (iii) name of escort, if necessary; (iv) a description of the maintenance performed; and (v) information system components/equipment removed or replaced (including identification numbers, if applicable). The level of detail included in maintenance records can be informed by the security categories of organizational information systems. Organizations consider supply chain issues associated with replacement components for information systems. Related controls: CM-3, CM-4, MA-4, MP-6, PE-16, SA-12, SI-2. References: None. | link | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-2(2) | NIST_SP_800-53_R4_MA-2(2) | NIST SP 800-53 Rev. 4 MA-2 (2) | Maintenance | Automated Maintenance Activities | Shared | n/a | The organization: (a) Employs automated mechanisms to schedule, conduct, and document maintenance and repairs; and (b) Produces up-to date, accurate, and complete records of all maintenance and repair actions requested, scheduled, in process, and completed. Supplemental Guidance: Related controls: CA-7, MA-3. References: None. | link | count: 002 Automate remote maintenance activities (b8587fce-138f-86e8-33a3-c60768bf1da6), Produce complete records of remote maintenance activities (74041cfe-3f87-1d17-79ec-34ca5f895542) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-3 | NIST_SP_800-53_R4_MA-3 | NIST SP 800-53 Rev. 4 MA-3 | Maintenance | Maintenance Tools | Shared | n/a | The organization approves, controls, and monitors information system maintenance tools. Supplemental Guidance: This control addresses security-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems. Maintenance tools can include hardware, software, and firmware items. Maintenance tools are potential vehicles for transporting malicious code, either intentionally or unintentionally, into a facility and subsequently into organizational information systems. Maintenance tools can include, for example, hardware/software diagnostic test equipment and hardware/software packet sniffers. This control does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing “ping,” “ls,” “ipconfig,” or the hardware and software implementing the monitoring port of an Ethernet switch. Related controls: MA-2, MA-5, MP-6. References: NIST Special Publication 800-88. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-3(1) | NIST_SP_800-53_R4_MA-3(1) | NIST SP 800-53 Rev. 4 MA-3 (1) | Maintenance | Inspect Tools | Shared | n/a | The organization inspects the maintenance tools carried into a facility by maintenance personnel for improper or unauthorized modifications. Supplemental Guidance: If, upon inspection of maintenance tools, organizations determine that the tools have been modified in an improper/unauthorized manner or contain malicious code, the incident is handled consistent with organizational policies and procedures for incident handling. Related control: SI-7. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-3(2) | NIST_SP_800-53_R4_MA-3(2) | NIST SP 800-53 Rev. 4 MA-3 (2) | Maintenance | Inspect Media | Shared | n/a | The organization checks media containing diagnostic and test programs for malicious code before the media are used in the information system. Supplemental Guidance: If, upon inspection of media containing maintenance diagnostic and test programs, organizations determine that the media contain malicious code, the incident is handled consistent with organizational incident handling policies and procedures. Related control: SI-3. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-3(3) | NIST_SP_800-53_R4_MA-3(3) | NIST SP 800-53 Rev. 4 MA-3 (3) | Maintenance | Prevent Unauthorized Removal | Shared | n/a | The organization prevents the unauthorized removal of maintenance equipment containing organizational information by: (a) Verifying that there is no organizational information contained on the equipment; (b) Sanitizing or destroying the equipment; (c) Retaining the equipment within the facility; or (d) Obtaining an exemption from [Assignment: organization-defined personnel or roles] explicitly authorizing removal of the equipment from the facility. Supplemental Guidance: Organizational information includes all information specifically owned by organizations and information provided to organizations in which organizations serve as information stewards. | link | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-4 | NIST_SP_800-53_R4_MA-4 | NIST SP 800-53 Rev. 4 MA-4 | Maintenance | Nonlocal Maintenance | Shared | n/a | The organization: a. Approves and monitors nonlocal maintenance and diagnostic activities; b. Allows the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the information system; c. Employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions; d. Maintains records for nonlocal maintenance and diagnostic activities; and e. Terminates session and network connections when nonlocal maintenance is completed. Supplemental Guidance: Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Authentication techniques used in the establishment of nonlocal maintenance and diagnostic sessions reflect the network access requirements in IA-2. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric. Enforcing requirements in MA-4 is accomplished in part by other controls. Related controls: AC-2, AC-3, AC-6, AC-17, AU-2, AU-3, IA-2, IA-4, IA-5, IA-8, MA-2, MA-5, MP-6, PL-2, SC-7, SC-10, SC-17. References: FIPS Publications 140-2, 197, 201; NIST Special Publications 800-63, 800-88; CNSS Policy 15. | link | count: 001 Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-4(2) | NIST_SP_800-53_R4_MA-4(2) | NIST SP 800-53 Rev. 4 MA-4 (2) | Maintenance | Document Nonlocal Maintenance | Shared | n/a | The organization documents in the security plan for the information system, the policies and procedures for the establishment and use of nonlocal maintenance and diagnostic connections. | link | count: 001 Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-4(3) | NIST_SP_800-53_R4_MA-4(3) | NIST SP 800-53 Rev. 4 MA-4 (3) | Maintenance | Comparable Security / Sanitization | Shared | n/a | The organization: (a) Requires that nonlocal maintenance and diagnostic services be performed from an information system that implements a security capability comparable to the capability implemented on the system being serviced; or (b) Removes the component to be serviced from the information system and prior to nonlocal maintenance or diagnostic services, sanitizes the component (with regard to organizational information) before removal from organizational facilities, and after the service is performed, inspects and sanitizes the component (with regard to potentially malicious software) before reconnecting the component to the information system. Supplemental Guidance: Comparable security capability on information systems, diagnostic tools, and equipment providing maintenance services implies that the implemented security controls on those systems, tools, and equipment are at least as comprehensive as the controls on the information system being serviced. Related controls: MA-3, SA-12, SI-3, SI-7. | link | count: 001 Perform all non-local maintenance (5bac5fb7-7735-357b-767d-02264bfe5c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-4(6) | NIST_SP_800-53_R4_MA-4(6) | NIST SP 800-53 Rev. 4 MA-4 (6) | Maintenance | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications. Supplemental Guidance: Related controls: SC-8, SC-13. | link | count: 001 Implement cryptographic mechanisms (10c3a1b1-29b0-a2d5-8f4c-a284b0f07830) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-5 | NIST_SP_800-53_R4_MA-5 | NIST SP 800-53 Rev. 4 MA-5 | Maintenance | Maintenance Personnel | Shared | n/a | The organization: a. Establishes a process for maintenance personnel authorization and maintains a list of authorized maintenance organizations or personnel; b. Ensures that non-escorted personnel performing maintenance on the information system have required access authorizations; and c. Designates organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations. Supplemental Guidance: This control applies to individuals performing hardware or software maintenance on organizational information systems, while PE-2 addresses physical access for individuals whose maintenance duties place them within the physical protection perimeter of the systems (e.g., custodial staff, physical plant maintenance personnel). Technical competence of supervising individuals relates to the maintenance performed on the information systems while having required access authorizations refers to maintenance on and near the systems. Individuals not previously identified as authorized maintenance personnel, such as information technology manufacturers, vendors, systems integrators, and consultants, may require privileged access to organizational information systems, for example, when required to conduct maintenance activities with little or no notice. Based on organizational assessments of risk, organizations may issue temporary credentials to these individuals. Temporary credentials may be for one-time use or for very limited time periods. Related controls: AC-2, IA-8, MP-2, PE-2, PE-3, PE-4, RA-3. References: None. | link | count: 003 Designate personnel to supervise unauthorized maintenance activities (7a489c62-242c-5db9-74df-c073056d6fa3), Maintain list of authorized remote maintenance personnel (4ce91e4e-6dab-3c46-011a-aa14ae1561bf), Manage maintenance personnel (b273f1e3-79e7-13ee-5b5d-dca6c66c3d5d) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-5(1) | NIST_SP_800-53_R4_MA-5(1) | NIST SP 800-53 Rev. 4 MA-5 (1) | Maintenance | Individuals Without Appropriate Access | Shared | n/a | The organization: (a) Implements procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements: (1) Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the information system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified; (2) Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the information system are sanitized and all nonvolatile storage media are removed or physically disconnected from the system and secured; and (b) Develops and implements alternate security safeguards in the event an information system component cannot be sanitized, removed, or disconnected from the system. Supplemental Guidance: This control enhancement denies individuals who lack appropriate security clearances (i.e., individuals who do not possess security clearances or possess security clearances at a lower level than required) or who are not U.S. citizens, visual and electronic access to any classified information, Controlled Unclassified Information (CUI), or any other sensitive information contained on organizational information systems. Procedures for the use of maintenance personnel can be documented in security plans for the information systems. Related controls: MP-6, PL-2. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MA-6 | NIST_SP_800-53_R4_MA-6 | NIST SP 800-53 Rev. 4 MA-6 | Maintenance | Timely Maintenance | Shared | n/a | The organization obtains maintenance support and/or spare parts for [Assignment: organization-defined information system components] within [Assignment: organization-defined time period] of failure. Supplemental Guidance: Organizations specify the information system components that result in increased risk to organizational operations and assets, individuals, other organizations, or the Nation when the functionality provided by those components is not operational. Organizational actions to obtain maintenance support typically include having appropriate contracts in place. Related controls: CM-8, CP-2, CP-7, SA-14, SA-15. References: None. | link | count: 001 Provide timely maintenance support (eb598832-4bcc-658d-4381-3ecbe17b9866) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-1 | NIST_SP_800-53_R4_MP-1 | NIST SP 800-53 Rev. 4 MP-1 | Media Protection | Media Protection Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A media protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the media protection policy and associated media protection controls; and b. Reviews and updates the current: 1. Media protection policy [Assignment: organization-defined frequency]; and 2. Media protection procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the MP family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-2 | NIST_SP_800-53_R4_MP-2 | NIST SP 800-53 Rev. 4 MP-2 | Media Protection | Media Access | Shared | n/a | The organization restricts access to [Assignment: organization-defined types of digital and/or non-digital media] to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Restricting non-digital media access includes, for example, denying access to patient medical records in a community hospital unless the individuals seeking access to such records are authorized healthcare providers. Restricting access to digital media includes, for example, limiting access to design specifications stored on compact disks in the media library to the project leader and the individuals on the development team. Related controls: AC-3, IA-2, MP-4, PE-2, PE-3, PL-2. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-3 | NIST_SP_800-53_R4_MP-3 | NIST SP 800-53 Rev. 4 MP-3 | Media Protection | Media Marking | Shared | n/a | The organization: a. Marks information system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and b. Exempts [Assignment: organization-defined types of information system media] from marking as long as the media remain within [Assignment: organization-defined controlled areas]. Supplemental Guidance: The term security marking refers to the application/use of human-readable security attributes. The term security labeling refers to the application/use of security attributes with regard to internal data structures within information systems (see AC-16). Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Security marking is generally not required for media containing information determined by organizations to be in the public domain or to be publicly releasable. However, some organizations may require markings for public information indicating that the information is publicly releasable. Marking of information system media reflects applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Related controls: AC-16, PL-2, RA-3. Control Enhancements: None. References: FIPS Publication 199. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-4 | NIST_SP_800-53_R4_MP-4 | NIST SP 800-53 Rev. 4 MP-4 | Media Protection | Media Storage | Shared | n/a | The organization: a. Physically controls and securely stores [Assignment: organization-defined types of digital and/or non-digital media] within [Assignment: organization-defined controlled areas]; and b. Protects information system media until the media are destroyed or sanitized using approved equipment, techniques, and procedures. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. Physically controlling information system media includes, for example, conducting inventories, ensuring procedures are in place to allow individuals to check out and return media to the media library, and maintaining accountability for all stored media. Secure storage includes, for example, a locked drawer, desk, or cabinet, or a controlled media library. The type of media storage is commensurate with the security category and/or classification of the information residing on the media. Controlled areas are areas for which organizations provide sufficient physical and procedural safeguards to meet the requirements established for protecting information and/or information systems. For media containing information determined by organizations to be in the public domain, to be publicly releasable, or to have limited or no adverse impact on organizations or individuals if accessed by other than authorized personnel, fewer safeguards may be needed. In these situations, physical access controls provide adequate protection. Related controls: CP-6, CP-9, MP-2, MP-7, PE-3. References: FIPS Publication 199; NIST Special Publications 800-56, 800-57, 800-111. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-5 | NIST_SP_800-53_R4_MP-5 | NIST SP 800-53 Rev. 4 MP-5 | Media Protection | Media Transport | Shared | n/a | The organization: a. Protects and controls [Assignment: organization-defined types of information system media] during transport outside of controlled areas using [Assignment: organization-defined security safeguards]; b. Maintains accountability for information system media during transport outside of controlled areas; c. Documents activities associated with the transport of information system media; and d. Restricts the activities associated with the transport of information system media to authorized personnel. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. This control also applies to mobile devices with information storage capability (e.g., smart phones, tablets, E-readers), that are transported outside of controlled areas. Controlled areas are areas or spaces for which organizations provide sufficient physical and/or procedural safeguards to meet the requirements established for protecting information and/or information systems. Physical and technical safeguards for media are commensurate with the security category or classification of the information residing on the media. Safeguards to protect media during transport include, for example, locked containers and cryptography. Cryptographic mechanisms can provide confidentiality and integrity protections depending upon the mechanisms used. Activities associated with transport include the actual transport as well as those activities such as releasing media for transport and ensuring that media enters the appropriate transport processes. For the actual transport, authorized transport and courier personnel may include individuals from outside the organization (e.g., U.S. Postal Service or a commercial transport or delivery service). Maintaining accountability of media during transport includes, for example, restricting transport activities to authorized personnel, and tracking and/or obtaining explicit records of transport activities as the media moves through the transportation system to prevent and detect loss, destruction, or tampering. Organizations establish documentation requirements for activities associated with the transport of information system media in accordance with organizational assessments of risk to include the flexibility to define different record-keeping methods for the different types of media transport as part of an overall system of transport-related records. Related controls: AC-19, CP-9, MP-3, MP-4, RA-3, SC-8, SC-13, SC-28. References: FIPS Publication 199; NIST Special Publication 800-60. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-5(4) | NIST_SP_800-53_R4_MP-5(4) | NIST SP 800-53 Rev. 4 MP-5 (4) | Media Protection | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to protect the confidentiality and integrity of information stored on digital media during transport outside of controlled areas. Supplemental Guidance: This control enhancement applies to both portable storage devices (e.g., USB memory sticks, compact disks, digital video disks, external/removable hard disk drives) and mobile devices with storage capability (e.g., smart phones, tablets, E-readers). Related control: MP-2. References: FIPS Publication 199; NIST Special Publication 800-60. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-6 | NIST_SP_800-53_R4_MP-6 | NIST SP 800-53 Rev. 4 MP-6 | Media Protection | Media Sanitization | Shared | n/a | The organization: a. Sanitizes [Assignment: organization-defined information system media] prior to disposal, release out of organizational control, or release for reuse using [Assignment: organization- defined sanitization techniques and procedures] in accordance with applicable federal and organizational standards and policies; and b. Employs sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information. Supplemental Guidance: This control applies to all information system media, both digital and non- digital, subject to disposal or reuse, whether or not the media is considered removable. Examples include media found in scanners, copiers, printers, notebook computers, workstations, network components, and mobile devices. The sanitization process removes information from the media such that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, cryptographic erase, and destruction, prevent the disclosure of information to unauthorized individuals when such media is reused or released for disposal. Organizations determine the appropriate sanitization methods recognizing that destruction is sometimes necessary when other methods cannot be applied to media requiring sanitization. Organizations use discretion on the employment of approved sanitization techniques and procedures for media containing information deemed to be in the public domain or publicly releasable, or deemed to have no adverse impact on organizations or individuals if released for reuse or disposal. Sanitization of non-digital media includes, for example, removing a classified appendix from an otherwise unclassified document, or redacting selected sections or words from a document by obscuring the redacted sections/words in a manner equivalent in effectiveness to removing them from the document. NSA standards and policies control the sanitization process for media containing classified information. Related controls: MA-2, MA-4, RA-3, SC-4. References: FIPS Publication 199; NIST Special Publications 800-60, 800-88; Web: http://www.nsa.gov/ia/mitigation_guidance/media_destruction_guidance/index.shtml. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-6(1) | NIST_SP_800-53_R4_MP-6(1) | NIST SP 800-53 Rev. 4 MP-6 (1) | Media Protection | Review / Approve / Track / Document / Verify | Shared | n/a | The organization reviews, approves, tracks, documents, and verifies media sanitization and disposal actions. Supplemental Guidance: Organizations review and approve media to be sanitized to ensure compliance with records-retention policies. Tracking/documenting actions include, for example, listing personnel who reviewed and approved sanitization and disposal actions, types of media sanitized, specific files stored on the media, sanitization methods used, date and time of the sanitization actions, personnel who performed the sanitization, verification actions taken, personnel who performed the verification, and disposal action taken. Organizations verify that the sanitization of the media was effective prior to disposal. Related control: SI-12. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-6(2) | NIST_SP_800-53_R4_MP-6(2) | NIST SP 800-53 Rev. 4 MP-6 (2) | Media Protection | Equipment Testing | Shared | n/a | The organization tests sanitization equipment and procedures [Assignment: organization-defined frequency] to verify that the intended sanitization is being achieved. Supplemental Guidance: Testing of sanitization equipment and procedures may be conducted by qualified and authorized external entities (e.g., other federal agencies or external service providers). | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-7 | NIST_SP_800-53_R4_MP-7 | NIST SP 800-53 Rev. 4 MP-7 | Media Protection | Media Use | Shared | n/a | The organization [Selection: restricts; prohibits] the use of [Assignment: organization- defined types of information system media] on [Assignment: organization-defined information systems or system components] using [Assignment: organization-defined security safeguards]. Supplemental Guidance: Information system media includes both digital and non-digital media. Digital media includes, for example, diskettes, magnetic tapes, external/removable hard disk drives, flash drives, compact disks, and digital video disks. Non-digital media includes, for example, paper and microfilm. This control also applies to mobile devices with information storage capability (e.g., smart phones, tablets, E-readers). In contrast to MP-2, which restricts user access to media, this control restricts the use of certain types of media on information systems, for example, restricting/prohibiting the use of flash drives or external hard disk drives. Organizations can employ technical and nontechnical safeguards (e.g., policies, procedures, rules of behavior) to restrict the use of information system media. Organizations may restrict the use of portable storage devices, for example, by using physical cages on workstations to prohibit access to certain external ports, or disabling/removing the ability to insert, read or write to such devices. Organizations may also limit the use of portable storage devices to only approved devices including, for example, devices provided by the organization, devices provided by other approved organizations, and devices that are not personally owned. Finally, organizations may restrict the use of portable storage devices based on the type of device, for example, prohibiting the use of writeable, portable storage devices, and implementing this restriction by disabling or removing the capability to write to such devices. Related controls: AC-19, PL-4. References: None. | link | count: 004 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | MP-7(1) | NIST_SP_800-53_R4_MP-7(1) | NIST SP 800-53 Rev. 4 MP-7 (1) | Media Protection | Prohibit Use Without Owner | Shared | n/a | The organization prohibits the use of portable storage devices in organizational information systems when such devices have no identifiable owner. Supplemental Guidance: Requiring identifiable owners (e.g., individuals, organizations, or projects) for portable storage devices reduces the risk of using such technologies by allowing organizations to assign responsibility and accountability for addressing known vulnerabilities in the devices (e.g., malicious code insertion). Related control: PL-4. | link | count: 004 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-1 | NIST_SP_800-53_R4_PE-1 | NIST SP 800-53 Rev. 4 PE-1 | Physical And Environmental Protection | Physical And Environmental Protection Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A physical and environmental protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls; and b. Reviews and updates the current: 1. Physical and environmental protection policy [Assignment: organization-defined frequency]; and 2. Physical and environmental protection procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PE family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-12 | NIST_SP_800-53_R4_PE-12 | NIST SP 800-53 Rev. 4 PE-12 | Physical And Environmental Protection | Emergency Lighting | Shared | n/a | The organization employs and maintains automatic emergency lighting for the information system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Related controls: CP-2, CP-7. References: None. | link | count: 001 Employ automatic emergency lighting (aa892c0d-2c40-200c-0dd8-eac8c4748ede) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-13 | NIST_SP_800-53_R4_PE-13 | NIST SP 800-53 Rev. 4 PE-13 | Physical And Environmental Protection | Fire Protection | Shared | n/a | The organization employs and maintains fire suppression and detection devices/systems for the information system that are supported by an independent energy source. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Fire suppression and detection devices/systems include, for example, sprinkler systems, handheld fire extinguishers, fixed fire hoses, and smoke detectors. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-13(1) | NIST_SP_800-53_R4_PE-13(1) | NIST SP 800-53 Rev. 4 PE-13 (1) | Physical And Environmental Protection | Detection Devices / Systems | Shared | n/a | The organization employs fire detection devices/systems for the information system that activate automatically and notify [Assignment: organization-defined personnel or roles] and [Assignment: organization-defined emergency responders] in the event of a fire. Supplemental Guidance: Organizations can identify specific personnel, roles, and emergency responders in the event that individuals on the notification list must have appropriate access authorizations and/or clearances, for example, to obtain access to facilities where classified operations are taking place or where there are information systems containing classified information. | link | count: 003 Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-13(2) | NIST_SP_800-53_R4_PE-13(2) | NIST SP 800-53 Rev. 4 PE-13 (2) | Physical And Environmental Protection | Suppression Devices / Systems | Shared | n/a | The organization employs fire suppression devices/systems for the information system that provide automatic notification of any activation to Assignment: organization-defined personnel or roles] and [Assignment: organization-defined emergency responders]. Supplemental Guidance: Organizations can identify specific personnel, roles, and emergency responders in the event that individuals on the notification list must have appropriate access authorizations and/or clearances, for example, to obtain access to facilities where classified operations are taking place or where there are information systems containing classified information. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-13(3) | NIST_SP_800-53_R4_PE-13(3) | NIST SP 800-53 Rev. 4 PE-13 (3) | Physical And Environmental Protection | Automatic Fire Suppression | Shared | n/a | The organization employs an automatic fire suppression capability for the information system when the facility is not staffed on a continuous basis. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-14 | NIST_SP_800-53_R4_PE-14 | NIST SP 800-53 Rev. 4 PE-14 | Physical And Environmental Protection | Temperature And Humidity Controls | Shared | n/a | The organization: a. Maintains temperature and humidity levels within the facility where the information system resides at [Assignment: organization-defined acceptable levels]; and b. Monitors temperature and humidity levels [Assignment: organization-defined frequency]. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources, for example, data centers, server rooms, and mainframe computer rooms. Related control: AT-3. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-14(2) | NIST_SP_800-53_R4_PE-14(2) | NIST SP 800-53 Rev. 4 PE-14 (2) | Physical And Environmental Protection | Monitoring With Alarms / Notifications | Shared | n/a | The organization employs temperature and humidity monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment. | link | count: 002 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-15 | NIST_SP_800-53_R4_PE-15 | NIST SP 800-53 Rev. 4 PE-15 | Physical And Environmental Protection | Water Damage Protection | Shared | n/a | The organization protects the information system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible, working properly, and known to key personnel. Supplemental Guidance: This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Isolation valves can be employed in addition to or in lieu of master shutoff valves to shut off water supplies in specific areas of concern, without affecting entire organizations. Related control: AT-3. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-16 | NIST_SP_800-53_R4_PE-16 | NIST SP 800-53 Rev. 4 PE-16 | Physical And Environmental Protection | Delivery And Removal | Shared | n/a | The organization authorizes, monitors, and controls [Assignment: organization-defined types of information system components] entering and exiting the facility and maintains records of those items. Supplemental Guidance: Effectively enforcing authorizations for entry and exit of information system components may require restricting access to delivery areas and possibly isolating the areas from the information system and media libraries. Related controls: CM-3, MA-2, MA-3, MP-5, SA-12. References: None. | link | count: 002 Define requirements for managing assets (25a1f840-65d0-900a-43e4-bee253de04de), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-17 | NIST_SP_800-53_R4_PE-17 | NIST SP 800-53 Rev. 4 PE-17 | Physical And Environmental Protection | Alternate Work Site | Shared | n/a | The organization: a. Employs [Assignment: organization-defined security controls] at alternate work sites; b. Assesses as feasible, the effectiveness of security controls at alternate work sites; and c. Provides a means for employees to communicate with information security personnel in case of security incidents or problems. Supplemental Guidance: Alternate work sites may include, for example, government facilities or private residences of employees. While commonly distinct from alternative processing sites, alternate work sites may provide readily available alternate locations as part of contingency operations. Organizations may define different sets of security controls for specific alternate work sites or types of sites depending on the work-related activities conducted at those sites. This control supports the contingency planning activities of organizations and the federal telework initiative. Related controls: AC-17, CP-7. Control Enhancements: None. References: NIST Special Publication 800-46. | link | count: 001 Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-18 | NIST_SP_800-53_R4_PE-18 | NIST SP 800-53 Rev. 4 PE-18 | Physical And Environmental Protection | Location Of Information System Components | Shared | n/a | The organization positions information system components within the facility to minimize potential damage from [Assignment: organization-defined physical and environmental hazards] and to minimize the opportunity for unauthorized access. Supplemental Guidance: Physical and environmental hazards include, for example, flooding, fire, tornados, earthquakes, hurricanes, acts of terrorism, vandalism, electromagnetic pulse, electrical interference, and other forms of incoming electromagnetic radiation. In addition, organizations consider the location of physical entry points where unauthorized individuals, while not being granted access, might nonetheless be in close proximity to information systems and therefore increase the potential for unauthorized access to organizational communications (e.g., through the use of wireless sniffers or microphones). Related controls: CP-2, PE-19, RA-3. References: None. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-2 | NIST_SP_800-53_R4_PE-2 | NIST SP 800-53 Rev. 4 PE-2 | Physical And Environmental Protection | Physical Access Authorizations | Shared | n/a | The organization: a. Develops, approves, and maintains a list of individuals with authorized access to the facility where the information system resides; b. Issues authorization credentials for facility access; c. Reviews the access list detailing authorized facility access by individuals [Assignment: organization-defined frequency]; and d. Removes individuals from the facility access list when access is no longer required. Supplemental Guidance: This control applies to organizational employees and visitors. Individuals (e.g., employees, contractors, and others) with permanent physical access authorization credentials are not considered visitors. Authorization credentials include, for example, badges, identification cards, and smart cards. Organizations determine the strength of authorization credentials needed (including level of forge-proof badges, smart cards, or identification cards) consistent with federal standards, policies, and procedures. This control only applies to areas within facilities that have not been designated as publicly accessible. Related controls: PE-3, PE-4, PS-3. References: None | link | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-3 | NIST_SP_800-53_R4_PE-3 | NIST SP 800-53 Rev. 4 PE-3 | Physical And Environmental Protection | Physical Access Control | Shared | n/a | The organization: a. Enforces physical access authorizations at [Assignment: organization-defined entry/exit points to the facility where the information system resides] by; 1. Verifying individual access authorizations before granting access to the facility; and 2. Controlling ingress/egress to the facility using [Selection (one or more): [Assignment: organization-defined physical access control systems/devices]; guards]; b. Maintains physical access audit logs for [Assignment: organization-defined entry/exit points]; c. Provides [Assignment: organization-defined security safeguards] to control access to areas within the facility officially designated as publicly accessible; d. Escorts visitors and monitors visitor activity [Assignment: organization-defined circumstances requiring visitor escorts and monitoring]; e. Secures keys, combinations, and other physical access devices; f. Inventories [Assignment: organization-defined physical access devices] every [Assignment: organization-defined frequency]; and g. Changes combinations and keys [Assignment: organization-defined frequency] and/or when keys are lost, combinations are compromised, or individuals are transferred or terminated. Supplemental Guidance: This control applies to organizational employees and visitors. Individuals (e.g., employees, contractors, and others) with permanent physical access authorization credentials are not considered visitors. Organizations determine the types of facility guards needed including, for example, professional physical security staff or other personnel such as administrative staff or information system users. Physical access devices include, for example, keys, locks, combinations, and card readers. Safeguards for publicly accessible areas within organizational facilities include, for example, cameras, monitoring by guards, and isolating selected information systems and/or system components in secured areas. Physical access control systems comply with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The Federal Identity, Credential, and Access Management Program provides implementation guidance for identity, credential, and access management capabilities for physical access control systems. Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural (e.g., a written log of individuals accessing the facility and when such access occurred), automated (e.g., capturing ID provided by a PIV card), or some combination thereof. Physical access points can include facility access points, interior access points to information systems and/or components requiring supplemental access controls, or both. Components of organizational information systems (e.g., workstations, terminals) may be located in areas designated as publicly accessible with organizations safeguarding access to such devices. Related controls: AU-2, AU-6, MP-2, MP-4, PE-2, PE-4, PE-5, PS-3, RA-3. Supplemental Guidance: Related controls: CA-2, CA-7. | link | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-4 | NIST_SP_800-53_R4_PE-4 | NIST SP 800-53 Rev. 4 PE-4 | Physical And Environmental Protection | Access Control For Transmission Medium | Shared | n/a | The organization controls physical access to [Assignment: organization-defined information system distribution and transmission lines] within organizational facilities using [Assignment: organization-defined security safeguards]. Supplemental Guidance: Physical security safeguards applied to information system distribution and transmission lines help to prevent accidental damage, disruption, and physical tampering. In addition, physical safeguards may be necessary to help prevent eavesdropping or in transit modification of unencrypted transmissions. Security safeguards to control physical access to system distribution and transmission lines include, for example: (i) locked wiring closets; (ii) disconnected or locked spare jacks; and/or (iii) protection of cabling by conduit or cable trays. Related controls: MP-2, MP-4, PE-2, PE-3, PE-5, SC-7, SC-8. Control Enhancements: None. References: NSTISSI No. 7003. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-5 | NIST_SP_800-53_R4_PE-5 | NIST SP 800-53 Rev. 4 PE-5 | Physical And Environmental Protection | Access Control For Output Devices | Shared | n/a | The organization controls physical access to information system output devices to prevent unauthorized individuals from obtaining the output. Supplemental Guidance: Controlling physical access to output devices includes, for example, placing output devices in locked rooms or other secured areas and allowing access to authorized individuals only, and placing output devices in locations that can be monitored by organizational personnel. Monitors, printers, copiers, scanners, facsimile machines, and audio devices are examples of information system output devices. Related controls: PE-2, PE-3, PE-4, PE-18. References: None. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-6(1) | NIST_SP_800-53_R4_PE-6(1) | NIST SP 800-53 Rev. 4 PE-6 (1) | Physical And Environmental Protection | Intrusion Alarms / Surveillance Equipment | Shared | n/a | The organization monitors physical intrusion alarms and surveillance equipment. | link | count: 002 Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PE-8 | NIST_SP_800-53_R4_PE-8 | NIST SP 800-53 Rev. 4 PE-8 | Physical And Environmental Protection | Visitor Access Records | Shared | n/a | The organization: a. Maintains visitor access records to the facility where the information system resides for [Assignment: organization-defined time period]; and b. Reviews visitor access records [Assignment: organization-defined frequency]. Supplemental Guidance: Visitor access records include, for example, names and organizations of persons visiting, visitor signatures, forms of identification, dates of access, entry and departure times, purposes of visits, and names and organizations of persons visited. Visitor access records are not required for publicly accessible areas. References: None. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PL-1 | NIST_SP_800-53_R4_PL-1 | NIST SP 800-53 Rev. 4 PL-1 | Planning | Security Planning Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A security planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the security planning policy and associated security planning controls; and b. Reviews and updates the current: 1. Security planning policy [Assignment: organization-defined frequency]; and 2. Security planning procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PL family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-18, 800-100. | link | count: 001 Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PL-2 | NIST_SP_800-53_R4_PL-2 | NIST SP 800-53 Rev. 4 PL-2 | Planning | System Security Plan | Shared | n/a | The organization: a. Develops a security plan for the information system that: 1. Is consistent with the organization’s enterprise architecture; 2. Explicitly defines the authorization boundary for the system; 3. Describes the operational context of the information system in terms of missions and business processes; 4. Provides the security categorization of the information system including supporting rationale; 5. Describes the operational environment for the information system and relationships with or connections to other information systems; 6. Provides an overview of the security requirements for the system; 7. Identifies any relevant overlays, if applicable; 8. Describes the security controls in place or planned for meeting those requirements including a rationale for the tailoring and supplementation decisions; and 9. Is reviewed and approved by the authorizing official or designated representative prior to plan implementation; b. Distributes copies of the security plan and communicates subsequent changes to the plan to [Assignment: organization-defined personnel or roles]; c. Reviews the security plan for the information system [Assignment: organization-defined frequency]; d. Updates the plan to address changes to the information system/environment of operation or problems identified during plan implementation or security control assessments; and e. Protects the security plan from unauthorized disclosure and modification. Supplemental Guidance: Security plans relate security requirements to a set of security controls and control enhancements. Security plans also describe, at a high level, how the security controls and control enhancements meet those security requirements, but do not provide detailed, technical descriptions of the specific design or implementation of the controls/enhancements. Security plans contain sufficient information (including the specification of parameter values for assignment and selection statements either explicitly or by reference) to enable a design and implementation that is unambiguously compliant with the intent of the plans and subsequent determinations of risk to organizational operations and assets, individuals, other organizations, and the Nation if the plan is implemented as intended. Organizations can also apply tailoring guidance to the security control baselines in Appendix D and CNSS Instruction 1253 to develop overlays for community-wide use or to address specialized requirements, technologies, or missions/environments of operation (e.g., DoD-tactical, Federal Public Key Infrastructure, or Federal Identity, Credential, and Access Management, space operations). Appendix I provides guidance on developing overlays. Security plans need not be single documents; the plans can be a collection of various documents including documents that already exist. Effective security plans make extensive use of references to policies, procedures, and additional documents (e.g., design and implementation specifications) where more detailed information can be obtained. This reduces the documentation requirements associated with security programs and maintains security-related information in other established management/operational areas related to enterprise architecture, system development life cycle, systems engineering, and acquisition. For example, security plans do not contain detailed contingency plan or incident response plan information but instead provide explicitly or by reference, sufficient information to define what needs to be accomplished by those plans. Related controls: AC-2, AC-6, AC-14, AC-17, AC-20, CA-2, CA-3, CA-7, CM-9, CP-2, IR-8, MA-4, MA-5, MP-2, MP-4, MP-5, PL-7, PM-1, PM-7, PM-8, PM-9, PM-11, SA-5, SA-17. References: NIST Special Publication 800-18. | link | count: 006 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PL-2(3) | NIST_SP_800-53_R4_PL-2(3) | NIST SP 800-53 Rev. 4 PL-2 (3) | Planning | Plan / Coordinate With Other Organizational Entities | Shared | n/a | The organization plans and coordinates security-related activities affecting the information system with [Assignment: organization-defined individuals or groups] before conducting such activities in order to reduce the impact on other organizational entities. Supplemental Guidance: Security-related activities include, for example, security assessments, audits, hardware and software maintenance, patch management, and contingency plan testing. Advance planning and coordination includes emergency and nonemergency (i.e., planned or nonurgent unplanned) situations. The process defined by organizations to plan and coordinate security-related activities can be included in security plans for information systems or other documents, as appropriate. Related controls: CP-4, IR-4. | link | count: 003 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PL-4 | NIST_SP_800-53_R4_PL-4 | NIST SP 800-53 Rev. 4 PL-4 | Planning | Rules Of Behavior | Shared | n/a | The organization: a. Establishes and makes readily available to individuals requiring access to the information system, the rules that describe their responsibilities and expected behavior with regard to information and information system usage; b. Receives a signed acknowledgment from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the information system; c. Reviews and updates the rules of behavior [Assignment: organization-defined frequency]; and d. Requires individuals who have signed a previous version of the rules of behavior to read and resign when the rules of behavior are revised/updated. Supplemental Guidance: This control enhancement applies to organizational users. Organizations consider rules of behavior based on individual user roles and responsibilities, differentiating, for example, between rules that apply to privileged users and rules that apply to general users. Establishing rules of behavior for some types of non-organizational users including, for example, individuals who simply receive data/information from federal information systems, is often not feasible given the large number of such users and the limited nature of their interactions with the systems. Rules of behavior for both organizational and non-organizational users can also be established in AC-8, System Use Notification. PL-4 b. (the signed acknowledgment portion of this control) may be satisfied by the security awareness training and role-based security training programs conducted by organizations if such training includes rules of behavior. Organizations can use electronic signatures for acknowledging rules of behavior. Related controls: AC-2, AC-6, AC-8, AC-9, AC-17, AC-18, AC-19, AC-20, AT-2, AT-3, CM-11, IA-2, IA-4, IA-5, MP-7, PS-6, PS-8, SA-5. References: NIST Special Publication 800-18. | link | count: 009 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PL-4(1) | NIST_SP_800-53_R4_PL-4(1) | NIST SP 800-53 Rev. 4 PL-4 (1) | Planning | Social Media And Networking Restrictions | Shared | n/a | The organization includes in the rules of behavior, explicit restrictions on the use of social media/networking sites and posting organizational information on public websites. Supplemental Guidance: This control enhancement addresses rules of behavior related to the use of social media/networking sites: (i) when organizational personnel are using such sites for official duties or in the conduct of official business; (ii) when organizational information is involved in social media/networking transactions; and (iii) when personnel are accessing social media/networking sites from organizational information systems. Organizations also address specific rules that prevent unauthorized entities from obtaining and/or inferring non- public organizational information (e.g., system account information, personally identifiable information) from social media/networking sites. | link | count: 001 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PL-8 | NIST_SP_800-53_R4_PL-8 | NIST SP 800-53 Rev. 4 PL-8 | Planning | Information Security Architecture | Shared | n/a | The organization: a. Develops an information security architecture for the information system that: 1. Describes the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information; 2. Describes how the information security architecture is integrated into and supports the enterprise architecture; and 3. Describes any information security assumptions about, and dependencies on, external services; b. Reviews and updates the information security architecture [Assignment: organization-defined frequency] to reflect updates in the enterprise architecture; and c. Ensures that planned information security architecture changes are reflected in the security plan, the security Concept of Operations (CONOPS), and organizational procurements/acquisitions. Supplemental Guidance: This control addresses actions taken by organizations in the design and development of information systems. The information security architecture at the individual information system level is consistent with and complements the more global, organization-wide information security architecture described in PM-7 that is integral to and developed as part of the enterprise architecture. The information security architecture includes an architectural description, the placement/allocation of security functionality (including security controls), security-related information for external interfaces, information being exchanged across the interfaces, and the protection mechanisms associated with each interface. In addition, the security architecture can include other important security-related information, for example, user roles and access privileges assigned to each role, unique security requirements, the types of information processed, stored, and transmitted by the information system, restoration priorities of information and information system services, and any other specific protection needs. In today’s modern architecture, it is becoming less common for organizations to control all information resources. There are going to be key dependencies on external information services and service providers. Describing such dependencies in the information security architecture is important to developing a comprehensive mission/business protection strategy. Establishing, developing, documenting, and maintaining under configuration control, a baseline configuration for organizational information systems is critical to implementing and maintaining an effective information security architecture. The development of the information security architecture is coordinated with the Senior Agency Official for Privacy (SAOP)/Chief Privacy Officer (CPO) to ensure that security controls needed to support privacy requirements are identified and effectively implemented. PL-8 is primarily directed at organizations (i.e., internally focused) to help ensure that organizations develop an information security architecture for the information system, and that the security architecture is integrated with or tightly coupled to the enterprise architecture through the organization-wide information security architecture. In contrast, SA-17 is primarily directed at external information technology product/system developers and integrators (although SA-17 could be used internally within organizations for in-house system development). SA-17, which is complementary to PL-8, is selected when organizations outsource the development of information systems or information system components to external entities, and there is a need to demonstrate/show consistency with the organization’s enterprise architecture and information security architecture. Related controls: CM-2, CM-6, PL-2, PM-7, SA-5, SA-17, Appendix J. References: None. | link | count: 002 Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-1 | NIST_SP_800-53_R4_PS-1 | NIST SP 800-53 Rev. 4 PS-1 | Personnel Security | Personnel Security Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A personnel security policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the personnel security policy and associated personnel security controls; and b. Reviews and updates the current: 1. Personnel security policy [Assignment: organization-defined frequency]; and 2. Personnel security procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the PS family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-2 | NIST_SP_800-53_R4_PS-2 | NIST SP 800-53 Rev. 4 PS-2 | Personnel Security | Position Risk Designation | Shared | n/a | The organization: a. Assigns a risk designation to all organizational positions; b. Establishes screening criteria for individuals filling those positions; and c. Reviews and updates position risk designations [Assignment: organization-defined frequency]. Supplemental Guidance: Position risk designations reflect Office of Personnel Management policy and guidance. Risk designations can guide and inform the types of authorizations individuals receive when accessing organizational information and information systems. Position screening criteria include explicit information security role appointment requirements (e.g., training, security clearances). Related controls: AT-3, PL-2, PS-3. Control Enhancements: None. References: 5 C.F.R. 731.106(a). | link | count: 001 Assign risk designations (b7897ddc-9716-2460-96f7-7757ad038cc4) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-3 | NIST_SP_800-53_R4_PS-3 | NIST SP 800-53 Rev. 4 PS-3 | Personnel Security | Personnel Screening | Shared | n/a | The organization: a. Screens individuals prior to authorizing access to the information system; and b. Rescreens individuals according to [Assignment: organization-defined conditions requiring rescreening and, where rescreening is so indicated, the frequency of such rescreening]. Supplemental Guidance: Personnel screening and rescreening activities reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, guidance, and specific criteria established for the risk designations of assigned positions. Organizations may define different rescreening conditions and frequencies for personnel accessing information systems based on types of information processed, stored, or transmitted by the systems. Related controls: AC-2, IA-4, PE-2, PS-2. References: 5 C.F.R. 731.106; FIPS Publications 199, 201; NIST Special Publications 800-60, 800-73, 800-76, 800-78; ICD 704. | link | count: 003 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Rescreen individuals at a defined frequency (c6aeb800-0b19-944d-92dc-59b893722329) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-3(3) | NIST_SP_800-53_R4_PS-3(3) | NIST SP 800-53 Rev. 4 PS-3 (3) | Personnel Security | Information With Special Protection Measures | Shared | n/a | The organization ensures that individuals accessing an information system processing, storing, or transmitting information requiring special protection: (a) Have valid access authorizations that are demonstrated by assigned official government duties; and (b) Satisfy [Assignment: organization-defined additional personnel screening criteria]. Supplemental Guidance: Organizational information requiring special protection includes, for example, Controlled Unclassified Information (CUI) and Sources and Methods Information (SAMI). Personnel security criteria include, for example, position sensitivity background screening requirements. | link | count: 001 Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-4 | NIST_SP_800-53_R4_PS-4 | NIST SP 800-53 Rev. 4 PS-4 | Personnel Security | Personnel Termination | Shared | n/a | The organization, upon termination of individual employment: a. Disables information system access within [Assignment: organization-defined time period]; b. Terminates/revokes any authenticators/credentials associated with the individual; c. Conducts exit interviews that include a discussion of [Assignment: organization-defined information security topics]; d. Retrieves all security-related organizational information system-related property; e. Retains access to organizational information and information systems formerly controlled by terminated individual; and f. Notifies [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period]. Supplemental Guidance: Information system-related property includes, for example, hardware authentication tokens, system administration technical manuals, keys, identification cards, and building passes. Exit interviews ensure that terminated individuals understand the security constraints imposed by being former employees and that proper accountability is achieved for information system-related property. Security topics of interest at exit interviews can include, for example, reminding terminated individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not be possible for some terminated individuals, for example, in cases related to job abandonment, illnesses, and nonavailability of supervisors. Exit interviews are important for individuals with security clearances. Timely execution of termination actions is essential for individuals terminated for cause. In certain situations, organizations consider disabling the information system accounts of individuals that are being terminated prior to the individuals being notified. Related controls: AC-2, IA-4, PE-2, PS-5, PS-6. References: None. | link | count: 005 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-4(2) | NIST_SP_800-53_R4_PS-4(2) | NIST SP 800-53 Rev. 4 PS-4 (2) | Personnel Security | Automated Notification | Shared | n/a | The organization employs automated mechanisms to notify [Assignment: organization-defined personnel or roles] upon termination of an individual. Supplemental Guidance: In organizations with a large number of employees, not all personnel who need to know about termination actions receive the appropriate notifications—or, if such notifications are received, they may not occur in a timely manner. Automated mechanisms can be used to send automatic alerts or notifications to specific organizational personnel or roles (e.g., management personnel, supervisors, personnel security officers, information security officers, systems administrators, or information technology administrators) when individuals are terminated. Such automatic alerts or notifications can be conveyed in a variety of ways, including, for example, telephonically, via electronic mail, via text message, or via websites. | link | count: 001 Automate notification of employee termination (729c8708-2bec-093c-8427-2e87d2cd426d) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-5 | NIST_SP_800-53_R4_PS-5 | NIST SP 800-53 Rev. 4 PS-5 | Personnel Security | Personnel Transfer | Shared | n/a | The organization: a. Reviews and confirms ongoing operational need for current logical and physical access authorizations to information systems/facilities when individuals are reassigned or transferred to other positions within the organization; b. Initiates [Assignment: organization-defined transfer or reassignment actions] within [Assignment: organization-defined time period following the formal transfer action]; c. Modifies access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and d. Notifies [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period]. Supplemental Guidance: This control applies when reassignments or transfers of individuals are permanent or of such extended durations as to make the actions warranted. Organizations define actions appropriate for the types of reassignments or transfers, whether permanent or extended. Actions that may be required for personnel transfers or reassignments to other positions within organizations include, for example: (i) returning old and issuing new keys, identification cards, and building passes; (ii) closing information system accounts and establishing new accounts; (iii) changing information system access authorizations (i.e., privileges); and (iv) providing for access to official records to which individuals had access at previous work locations and in previous information system accounts. Related controls: AC-2, IA-4, PE-2, PS-4. Control Enhancements: None. References: None. | link | count: 004 Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-6 | NIST_SP_800-53_R4_PS-6 | NIST SP 800-53 Rev. 4 PS-6 | Personnel Security | Access Agreements | Shared | n/a | The organization: a. Develops and documents access agreements for organizational information systems; b. Reviews and updates the access agreements [Assignment: organization-defined frequency]; and c. Ensures that individuals requiring access to organizational information and information systems: 1. Sign appropriate access agreements prior to being granted access; and 2. Re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or [Assignment: organization-defined frequency]. Supplemental Guidance: Access agreements include, for example, nondisclosure agreements, acceptable use agreements, rules of behavior, and conflict-of-interest agreements. Signed access agreements include an acknowledgement that individuals have read, understand, and agree to abide by the constraints associated with organizational information systems to which access is authorized. Organizations can use electronic signatures to acknowledge access agreements unless specifically prohibited by organizational policy. Related control: PL-4, PS-2, PS-3, PS-4, PS-8. References: None. | link | count: 005 Document organizational access agreements (c981fa70-2e58-8141-1457-e7f62ebc2ade), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Ensure access agreements are signed or resigned timely (e7589f4e-1e8b-72c2-3692-1e14d7f3699f), Require users to sign access agreement (3af53f59-979f-24a8-540f-d7cdbc366607), Update organizational access agreements (e21f91d1-2803-0282-5f2d-26ebc4b170ef) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-7 | NIST_SP_800-53_R4_PS-7 | NIST SP 800-53 Rev. 4 PS-7 | Personnel Security | Third-Party Personnel Security | Shared | n/a | The organization: a. Establishes personnel security requirements including security roles and responsibilities for third-party providers; b. Requires third-party providers to comply with personnel security policies and procedures established by the organization; c. Documents personnel security requirements; d. Requires third-party providers to notify [Assignment: organization-defined personnel or roles] of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges within [Assignment: organization-defined time period]; and e. Monitors provider compliance. Supplemental Guidance: Third-party providers include, for example, service bureaus, contractors, and other organizations providing information system development, information technology services, outsourced applications, and network and security management. Organizations explicitly include personnel security requirements in acquisition-related documents. Third-party providers may have personnel working at organizational facilities with credentials, badges, or information system privileges issued by organizations. Notifications of third-party personnel changes ensure appropriate termination of privileges and credentials. Organizations define the transfers and terminations deemed reportable by security-related characteristics that include, for example, functions, roles, and nature of credentials/privileges associated with individuals transferred or terminated. Related controls: PS-2, PS-3, PS-4, PS-5, PS-6, SA-9, SA-21. Control Enhancements: None. References: NIST Special Publication 800-35. | link | count: 005 Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | PS-8 | NIST_SP_800-53_R4_PS-8 | NIST SP 800-53 Rev. 4 PS-8 | Personnel Security | Personnel Sanctions | Shared | n/a | The organization: a. Employs a formal sanctions process for individuals failing to comply with established information security policies and procedures; and b. Notifies [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period] when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction. Supplemental Guidance: Organizational sanctions processes reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Sanctions processes are described in access agreements and can be included as part of general personnel policies and procedures for organizations. Organizations consult with the Office of the General Counsel regarding matters of employee sanctions. Related controls: PL-4, PS-6. Control Enhancements: None. References: None. | link | count: 002 Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-1 | NIST_SP_800-53_R4_RA-1 | NIST SP 800-53 Rev. 4 RA-1 | Risk Assessment | Risk Assessment Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A risk assessment policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls; and b. Reviews and updates the current: 1. Risk assessment policy [Assignment: organization-defined frequency]; and 2. Risk assessment procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the RA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-30, 800-100. | link | count: 001 Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-2 | NIST_SP_800-53_R4_RA-2 | NIST SP 800-53 Rev. 4 RA-2 | Risk Assessment | Security Categorization | Shared | n/a | The organization: a. Categorizes information and the information system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance; b. Documents the security categorization results (including supporting rationale) in the security plan for the information system; and c. Ensures that the security categorization decision is reviewed and approved by the authorizing official or authorizing official designated representative. Supplemental Guidance: Clearly defined authorization boundaries are a prerequisite for effective security categorization decisions. Security categories describe the potential adverse impacts to organizational operations, organizational assets, and individuals if organizational information and information systems are comprised through a loss of confidentiality, integrity, or availability. Organizations conduct the security categorization process as an organization-wide activity with the involvement of chief information officers, senior information security officers, information system owners, mission/business owners, and information owners/stewards. Organizations also consider the potential adverse impacts to other organizations and, in accordance with the USA PATRIOT Act of 2001 and Homeland Security Presidential Directives, potential national-level adverse impacts. Security categorization processes carried out by organizations facilitate the development of inventories of information assets, and along with CM-8, mappings to specific information system components where information is processed, stored, or transmitted. Related controls: CM-8, MP-4, RA-3, SC-7. Control Enhancements: None. References: FIPS Publication 199; NIST Special Publications 800-30, 800-39, 800-60. | link | count: 004 Categorize information (93fa357f-2e38-22a9-5138-8cc5124e1923), Develop business classification schemes (11ba0508-58a8-44de-5f3a-9e05d80571da), Ensure security categorization is approved (6c79c3e5-5f7b-a48a-5c7b-8c158bc01115), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-3 | NIST_SP_800-53_R4_RA-3 | NIST SP 800-53 Rev. 4 RA-3 | Risk Assessment | Risk Assessment | Shared | n/a | The organization: a. Conducts an assessment of risk, including the likelihood and magnitude of harm, from the unauthorized access, use, disclosure, disruption, modification, or destruction of the information system and the information it processes, stores, or transmits; b. Documents risk assessment results in [Selection: security plan; risk assessment report; [Assignment: organization-defined document]]; c. Reviews risk assessment results [Assignment: organization-defined frequency]; d. Disseminates risk assessment results to [Assignment: organization-defined personnel or roles]; and e. Updates the risk assessment [Assignment: organization-defined frequency] or whenever there are significant changes to the information system or environment of operation (including the identification of new threats and vulnerabilities), or other conditions that may impact the security state of the system. Supplemental Guidance: Clearly defined authorization boundaries are a prerequisite for effective risk assessments. Risk assessments take into account threats, vulnerabilities, likelihood, and impact to organizational operations and assets, individuals, other organizations, and the Nation based on the operation and use of information systems. Risk assessments also take into account risk from external parties (e.g., service providers, contractors operating information systems on behalf of the organization, individuals accessing organizational information systems, outsourcing entities). In accordance with OMB policy and related E-authentication initiatives, authentication of public users accessing federal information systems may also be required to protect nonpublic or privacy-related information. As such, organizational assessments of risk also address public access to federal information systems. Risk assessments (either formal or informal) can be conducted at all three tiers in the risk management hierarchy (i.e., organization level, mission/business process level, or information system level) and at any phase in the system development life cycle. Risk assessments can also be conducted at various steps in the Risk Management Framework, including categorization, security control selection, security control implementation, security control assessment, information system authorization, and security control monitoring. RA-3 is noteworthy in that the control must be partially implemented prior to the implementation of other controls in order to complete the first two steps in the Risk Management Framework. Risk assessments can play an important role in security control selection processes, particularly during the application of tailoring guidance, which includes security control supplementation. Related controls: RA-2, PM-9. Control Enhancements: None. References: OMB Memorandum 04-04; NIST Special Publication 800-30, 800-39; Web:idmanagement.gov. | link | count: 004 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-5 | NIST_SP_800-53_R4_RA-5 | NIST SP 800-53 Rev. 4 RA-5 | Risk Assessment | Vulnerability Scanning | Shared | n/a | The organization: a. Scans for vulnerabilities in the information system and hosted applications [Assignment: organization-defined frequency and/or randomly in accordance with organization-defined process] and when new vulnerabilities potentially affecting the system/applications are identified and reported; b. Employs vulnerability scanning tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: 1. Enumerating platforms, software flaws, and improper configurations; 2. Formatting checklists and test procedures; and 3. Measuring vulnerability impact; c. Analyzes vulnerability scan reports and results from security control assessments; d. Remediates legitimate vulnerabilities [Assignment: organization-defined response times], in accordance with an organizational assessment of risk; and e. Shares information obtained from the vulnerability scanning process and security control assessments with [Assignment: organization-defined personnel or roles] to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies). Supplemental Guidance: Security categorization of information systems guides the frequency and comprehensiveness of vulnerability scans. Organizations determine the required vulnerability scanning for all information system components, ensuring that potential sources of vulnerabilities such as networked printers, scanners, and copiers are not overlooked. Vulnerability analyses for custom software applications may require additional approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can employ these analysis approaches in a variety of tools (e.g., web-based application scanners, static analysis tools, binary analyzers) and in source code reviews. Vulnerability scanning includes, for example: (i) scanning for patch levels; (ii) scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and (iii) scanning for improperly configured or incorrectly operating information flow control mechanisms. Organizations consider using tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention and that use the Open Vulnerability Assessment Language (OVAL) to determine/test for the presence of vulnerabilities. Suggested sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). In addition, security control assessments such as red team exercises provide other sources of potential vulnerabilities for which to scan. Organizations also consider using tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS). Related controls: CA-2, CA-7, CM-4, CM-6, RA-2, RA-3, SA-11, SI-2. References: NIST Special Publications 800-40, 800-70, 800-115; Web: http://cwe.mitre.org, http://nvd.nist.gov. | link | count: 021 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Regulatory Compliance, Security Center, SQL, Synapse | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-5(1) | NIST_SP_800-53_R4_RA-5(1) | NIST SP 800-53 Rev. 4 RA-5 (1) | Risk Assessment | Update Tool Capability | Shared | n/a | The organization employs vulnerability scanning tools that include the capability to readily update the information system vulnerabilities to be scanned. Supplemental Guidance: The vulnerabilities to be scanned need to be readily updated as new vulnerabilities are discovered, announced, and scanning methods developed. This updating process helps to ensure that potential vulnerabilities in the information system are identified and addressed as quickly as possible. Related controls: SI-3, SI-7. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-5(10) | NIST_SP_800-53_R4_RA-5(10) | NIST SP 800-53 Rev. 4 RA-5 (10) | Risk Assessment | Correlate Scanning Information | Shared | n/a | The organization correlates the output from vulnerability scanning tools to determine the presence of multi-vulnerability/multi-hop attack vectors. | link | count: 001 Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-5(2) | NIST_SP_800-53_R4_RA-5(2) | NIST SP 800-53 Rev. 4 RA-5 (2) | Risk Assessment | Update By Frequency / Prior To New Scan / When Identified | Shared | n/a | The organization updates the information system vulnerabilities scanned [Selection (one or more): [Assignment: organization-defined frequency]; prior to a new scan; when new vulnerabilities are identified and reported]. Supplemental Guidance: Related controls: SI-3, SI-5. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-5(3) | NIST_SP_800-53_R4_RA-5(3) | NIST SP 800-53 Rev. 4 RA-5 (3) | Risk Assessment | Breadth / Depth Of Coverage | Shared | n/a | The organization employs vulnerability scanning procedures that can identify the breadth and depth of coverage (i.e., information system components scanned and vulnerabilities checked). | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-5(4) | NIST_SP_800-53_R4_RA-5(4) | NIST SP 800-53 Rev. 4 RA-5 (4) | Risk Assessment | Discoverable Information | Shared | n/a | The organization determines what information about the information system is discoverable by adversaries and subsequently takes [Assignment: organization-defined corrective actions]. Supplemental Guidance: Discoverable information includes information that adversaries could obtain without directly compromising or breaching the information system, for example, by collecting information the system is exposing or by conducting extensive searches of the web. Corrective actions can include, for example, notifying appropriate organizational personnel, removing designated information, or changing the information system to make designated information less relevant or attractive to adversaries. Related control: AU-13. | link | count: 001 Take action in response to customer information (d25cbded-121e-0ed6-1857-dc698c9095b1) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-5(5) | NIST_SP_800-53_R4_RA-5(5) | NIST SP 800-53 Rev. 4 RA-5 (5) | Risk Assessment | Privileged Access | Shared | n/a | The information system implements privileged access authorization to [Assignment: organization- identified information system components] for selected [Assignment: organization-defined vulnerability scanning activities]. Supplemental Guidance: In certain situations, the nature of the vulnerability scanning may be more intrusive or the information system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system components facilitates more thorough vulnerability scanning and also protects the sensitive nature of such scanning. | link | count: 001 Implement privileged access for executing vulnerability scanning activities (5b802722-71dd-a13d-2e7e-231e09589efb) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-5(6) | NIST_SP_800-53_R4_RA-5(6) | NIST SP 800-53 Rev. 4 RA-5 (6) | Risk Assessment | Automated Trend Analyses | Shared | n/a | The organization employs automated mechanisms to compare the results of vulnerability scans over time to determine trends in information system vulnerabilities. Supplemental Guidance: Related controls: IR-4, IR-5, SI-4. | link | count: 005 Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | RA-5(8) | NIST_SP_800-53_R4_RA-5(8) | NIST SP 800-53 Rev. 4 RA-5 (8) | Risk Assessment | Review Historic Audit Logs | Shared | n/a | The organization reviews historic audit logs to determine if a vulnerability identified in the information system has been previously exploited. Supplemental Guidance: Related control: AU-6. | link | count: 015 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review exploit protection events (a30bd8e9-7064-312a-0e1f-e1b485d59f6e), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-1 | NIST_SP_800-53_R4_SA-1 | NIST SP 800-53 Rev. 4 SA-1 | System And Services Acquisition | System And Services Acquisition Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system and services acquisition policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls; and b. Reviews and updates the current: 1. System and services acquisition policy [Assignment: organization-defined frequency]; and 2. System and services acquisition procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-10 | NIST_SP_800-53_R4_SA-10 | NIST SP 800-53 Rev. 4 SA-10 | System And Services Acquisition | Developer Configuration Management | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to: a. Perform configuration management during system, component, or service [Selection (one or more): design; development; implementation; operation]; b. Document, manage, and control the integrity of changes to [Assignment: organization-defined configuration items under configuration management]; c. Implement only organization-approved changes to the system, component, or service; d. Document approved changes to the system, component, or service and the potential security impacts of such changes; and e. Track security flaws and flaw resolution within the system, component, or service and report findings to [Assignment: organization-defined personnel]. Supplemental Guidance: This control also applies to organizations conducting internal information systems development and integration. Organizations consider the quality and completeness of the configuration management activities conducted by developers as evidence of applying effective security safeguards. Safeguards include, for example, protecting from unauthorized modification or destruction, the master copies of all material used to generate security-relevant portions of the system hardware, software, and firmware. Maintaining the integrity of changes to the information system, information system component, or information system service requires configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes. Configuration items that are placed under configuration management (if existence/use is required by other security controls) include: the formal model; the functional, high-level, and low-level design specifications; other design data; implementation documentation; source code and hardware schematics; the running version of the object code; tools for comparing new versions of security-relevant hardware descriptions and software/firmware source code with previous versions; and test fixtures and documentation. Depending on the mission/business needs of organizations and the nature of the contractual relationships in place, developers may provide configuration management support during the operations and maintenance phases of the life cycle. Related controls: CM-3, CM-4, CM-9, SA-12, SI-2. References: NIST Special Publication 800-128. | link | count: 009 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-10(1) | NIST_SP_800-53_R4_SA-10(1) | NIST SP 800-53 Rev. 4 SA-10 (1) | System And Services Acquisition | Software / Firmware Integrity Verification | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to enable integrity verification of software and firmware components. Supplemental Guidance: This control enhancement allows organizations to detect unauthorized changes to software and firmware components through the use of tools, techniques, and/or mechanisms provided by developers. Integrity checking mechanisms can also address counterfeiting of software and firmware components. Organizations verify the integrity of software and firmware components, for example, through secure one-way hashes provided by developers. Delivered software and firmware components also include any updates to such components. Related control: SI-7. | link | count: 001 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-11 | NIST_SP_800-53_R4_SA-11 | NIST SP 800-53 Rev. 4 SA-11 | System And Services Acquisition | Developer Security Testing And Evaluation | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to: a. Create and implement a security assessment plan; b. Perform [Selection (one or more): unit; integration; system; regression] testing/evaluation at [Assignment: organization-defined depth and coverage]; c. Produce evidence of the execution of the security assessment plan and the results of the security testing/evaluation; d. Implement a verifiable flaw remediation process; and e. Correct flaws identified during security testing/evaluation. Supplemental Guidance: Developmental security testing/evaluation occurs at all post‐design phases of the system development life cycle. Such testing/evaluation confirms that the required security controls are implemented correctly, operating as intended, enforcing the desired security policy, and meeting established security requirements. Security properties of information systems may be affected by the interconnection of system components or changes to those components. These interconnections or changes (e.g., upgrading or replacing applications and operating systems) may adversely affect previously implemented security controls. This control provides additional types of security testing/evaluation that developers can conduct to reduce or eliminate potential flaws. Testing custom software applications may require approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Developers can employ these analysis approaches in a variety of tools (e.g., web-based application scanners, static analysis tools, binary analyzers) and in source code reviews. Security assessment plans provide the specific activities that developers plan to carry out including the types of analyses, testing, evaluation, and reviews of software and firmware components, the degree of rigor to be applied, and the types of artifacts produced during those processes. The depth of security testing/evaluation refers to the rigor and level of detail associated with the assessment process (e.g., black box, gray box, or white box testing). The coverage of security testing/evaluation refers to the scope (i.e., number and type) of the artifacts included in the assessment process. Contracts specify the acceptance criteria for security assessment plans, flaw remediation processes, and the evidence that the plans/processes have been diligently applied. Methods for reviewing and protecting assessment plans, evidence, and documentation are commensurate with the security category or classification level of the information system. Contracts may specify documentation protection requirements. Related controls: CA-2, CM-4, SA-3, SA-4, SA-5, SI-2. References: ISO/IEC 15408; NIST Special Publication 800-53A; Web: http://nvd.nist.gov, http://cwe.mitre.org, http://cve.mitre.org, http://capec.mitre.org. | link | count: 003 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-12 | NIST_SP_800-53_R4_SA-12 | NIST SP 800-53 Rev. 4 SA-12 | System And Services Acquisition | Supply Chain Protection | Shared | n/a | The organization protects against supply chain threats to the information system, system component, or information system service by employing [Assignment: organization-defined security safeguards] as part of a comprehensive, defense-in-breadth information security strategy. Supplemental Guidance: Information systems (including system components that compose those systems) need to be protected throughout the system development life cycle (i.e., during design, development, manufacturing, packaging, assembly, distribution, system integration, operations, maintenance, and retirement). Protection of organizational information systems is accomplished through threat awareness, by the identification, management, and reduction of vulnerabilities at each phase of the life cycle and the use of complementary, mutually reinforcing strategies to respond to risk. Organizations consider implementing a standardized process to address supply chain risk with respect to information systems and system components, and to educate the acquisition workforce on threats, risk, and required security controls. Organizations use the acquisition/procurement processes to require supply chain entities to implement necessary security safeguards to: (i) reduce the likelihood of unauthorized modifications at each stage in the supply chain; and (ii) protect information systems and information system components, prior to taking delivery of such systems/components. This control enhancement also applies to information system services. Security safeguards include, for example: (i) security controls for development systems, development facilities, and external connections to development systems; (ii) vetting development personnel; and (iii) use of tamper-evident packaging during shipping/warehousing. Methods for reviewing and protecting development plans, evidence, and documentation are commensurate with the security category or classification level of the information system. Contracts may specify documentation protection requirements. Related controls: AT-3, CM-8, IR- 4, PE-16, PL-8, SA-3, SA-4, SA-8, SA-10, SA-14, SA-15, SA-18, SA-19, SC-29, SC-30, SC-38, SI-7. References: NIST Special Publication 800-161; NIST Interagency Report 7622. | link | count: 004 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-15 | NIST_SP_800-53_R4_SA-15 | NIST SP 800-53 Rev. 4 SA-15 | System And Services Acquisition | Development Process, Standards, And Tools | Shared | n/a | The organization: a. Requires the developer of the information system, system component, or information system service to follow a documented development process that: 1. Explicitly addresses security requirements; 2. Identifies the standards and tools used in the development process; 3. Documents the specific tool options and tool configurations used in the development process; and 4. Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and b. Reviews the development process, standards, tools, and tool options/configurations [Assignment: organization-defined frequency] to determine if the process, standards, tools, and tool options/configurations selected and employed can satisfy [Assignment: organization- defined security requirements]. Supplemental Guidance: Development tools include, for example, programming languages and computer-aided design (CAD) systems. Reviews of development processes can include, for example, the use of maturity models to determine the potential effectiveness of such processes. Maintaining the integrity of changes to tools and processes enables accurate supply chain risk assessment and mitigation, and requires robust configuration control throughout the life cycle (including design, development, transport, delivery, integration, and maintenance) to track authorized changes and prevent unauthorized changes. Related controls: SA-3, SA-8. References: None. | link | count: 001 Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-16 | NIST_SP_800-53_R4_SA-16 | NIST SP 800-53 Rev. 4 SA-16 | System And Services Acquisition | Developer-Provided Training | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to provide [Assignment: organization-defined training] on the correct use and operation of the implemented security functions, controls, and/or mechanisms. Supplemental Guidance: This control applies to external and internal (in-house) developers. Training of personnel is an essential element to ensure the effectiveness of security controls implemented within organizational information systems. Training options include, for example, classroom-style training, web-based/computer-based training, and hands-on training. Organizations can also request sufficient training materials from developers to conduct in-house training or offer self- training to organizational personnel. Organizations determine the type of training necessary and may require different types of training for different security functions, controls, or mechanisms. Related controls: AT-2, AT-3, SA-5. References: None. | link | count: 001 Require developers to provide training (676c3c35-3c36-612c-9523-36d266a65000) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-17 | NIST_SP_800-53_R4_SA-17 | NIST SP 800-53 Rev. 4 SA-17 | System And Services Acquisition | Developer Security Architecture And Design | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to produce a design specification and security architecture that: a. Is consistent with and supportive of the organization’s security architecture which is established within and is an integrated part of the organization’s enterprise architecture; b. Accurately and completely describes the required security functionality, and the allocation of security controls among physical and logical components; and c. Expresses how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection. Supplemental Guidance: This control is primarily directed at external developers, although it could also be used for internal (in-house) development. In contrast, PL-8 is primarily directed at internal developers to help ensure that organizations develop an information security architecture and such security architecture is integrated or tightly coupled to the enterprise architecture. This distinction is important if/when organizations outsource the development of information systems, information system components, or information system services to external entities, and there is a requirement to demonstrate consistency with the organization’s enterprise architecture and information security architecture. Related controls: PL-8, PM-7, SA-3, SA-8. References: None. | link | count: 003 Require developers to build security architecture (f131c8c5-a54a-4888-1efc-158928924bc1), Require developers to describe accurate security functionality (3e37c891-840c-3eb4-78d2-e2e0bb5063e0), Require developers to provide unified security protection approach (7a114735-a420-057d-a651-9a73cd0416ef) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-2 | NIST_SP_800-53_R4_SA-2 | NIST SP 800-53 Rev. 4 SA-2 | System And Services Acquisition | Allocation Of Resources | Shared | n/a | The organization: a. Determines information security requirements for the information system or information system service in mission/business process planning; b. Determines, documents, and allocates the resources required to protect the information system or information system service as part of its capital planning and investment control process; and c. Establishes a discrete line item for information security in organizational programming and budgeting documentation. Supplemental Guidance: Resource allocation for information security includes funding for the initial information system or information system service acquisition and funding for the sustainment of the system/service. Related controls: PM-3, PM-11. Control Enhancements: None. References: NIST Special Publication 800-65. | link | count: 006 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Allocate resources in determining information system requirements (90a156a6-49ed-18d1-1052-69aac27c05cd), Establish a discrete line item in budgeting documentation (06af77de-02ca-0f3e-838a-a9420fe466f5), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-3 | NIST_SP_800-53_R4_SA-3 | NIST SP 800-53 Rev. 4 SA-3 | System And Services Acquisition | System Development Life Cycle | Shared | n/a | The organization: a. Manages the information system using [Assignment: organization-defined system development life cycle] that incorporates information security considerations; b. Defines and documents information security roles and responsibilities throughout the system development life cycle; c. Identifies individuals having information security roles and responsibilities; and d. Integrates the organizational information security risk management process into system development life cycle activities. Supplemental Guidance: A well-defined system development life cycle provides the foundation for the successful development, implementation, and operation of organizational information systems. To apply the required security controls within the system development life cycle requires a basic understanding of information security, threats, vulnerabilities, adverse impacts, and risk to critical missions/business functions. The security engineering principles in SA-8 cannot be properly applied if individuals that design, code, and test information systems and system components (including information technology products) do not understand security. Therefore, organizations include qualified personnel, for example, chief information security officers, security architects, security engineers, and information system security officers in system development life cycle activities to ensure that security requirements are incorporated into organizational information systems. It is equally important that developers include individuals on the development team that possess the requisite security expertise and skills to ensure that needed security capabilities are effectively integrated into the information system. Security awareness and training programs can help ensure that individuals having key security roles and responsibilities have the appropriate experience, skills, and expertise to conduct assigned system development life cycle activities. The effective integration of security requirements into enterprise architecture also helps to ensure that important security considerations are addressed early in the system development life cycle and that those considerations are directly related to the organizational mission/business processes. This process also facilitates the integration of the information security architecture into the enterprise architecture, consistent with organizational risk management and information security strategies. Related controls: AT-3, PM-7, SA-8. Control Enhancements: None. References: NIST Special Publications 800-37, 800-64. | link | count: 003 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-4 | NIST_SP_800-53_R4_SA-4 | NIST SP 800-53 Rev. 4 SA-4 | System And Services Acquisition | Acquisition Process | Shared | n/a | The organization includes the following requirements, descriptions, and criteria, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs: a. Security functional requirements; b. Security strength requirements; c. Security assurance requirements; d. Security-related documentation requirements; e. Requirements for protecting security-related documentation; f. Description of the information system development environment and environment in which the system is intended to operate; and g. Acceptance criteria. Supplemental Guidance: Information system components are discrete, identifiable information technology assets (e.g., hardware, software, or firmware) that represent the building blocks of an information system. Information system components include commercial information technology products. Security functional requirements include security capabilities, security functions, and security mechanisms. Security strength requirements associated with such capabilities, functions, and mechanisms include degree of correctness, completeness, resistance to direct attack, and resistance to tampering or bypass. Security assurance requirements include: (i) development processes, procedures, practices, and methodologies; and (ii) evidence from development and assessment activities providing grounds for confidence that the required security functionality has been implemented and the required security strength has been achieved. Security documentation requirements address all phases of the system development life cycle. Security functionality, assurance, and documentation requirements are expressed in terms of security controls and control enhancements that have been selected through the tailoring process. The security control tailoring process includes, for example, the specification of parameter values through the use of assignment and selection statements and the specification of platform dependencies and implementation information. Security documentation provides user and administrator guidance regarding the implementation and operation of security controls. The level of detail required in security documentation is based on the security category or classification level of the information system and the degree to which organizations depend on the stated security capability, functions, or mechanisms to meet overall risk response expectations (as defined in the organizational risk management strategy). Security requirements can also include organizationally mandated configuration settings specifying allowed functions, ports, protocols, and services. Acceptance criteria for information systems, information system components, and information system services are defined in the same manner as such criteria for any organizational acquisition or procurement. The Federal Acquisition Regulation (FAR) Section 7.103 contains information security requirements from FISMA. Related controls: CM-6, PL-2, PS-7, SA-3, SA-5, SA-8, SA-11, SA-12. References: HSPD-12; ISO/IEC 15408; FIPS Publications 140-2, 201; NIST Special Publications 800-23, 800-35, 800-36, 800-37, 800-64, 800-70, 800-137; Federal Acquisition Regulation; Web: http://www.niap-ccevs.org, http://fips201ep.cio.gov, http://www.acquisition.gov/far. | link | count: 011 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-4(1) | NIST_SP_800-53_R4_SA-4(1) | NIST SP 800-53 Rev. 4 SA-4 (1) | System And Services Acquisition | Functional Properties Of Security Controls | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to provide a description of the functional properties of the security controls to be employed. Supplemental Guidance: Functional properties of security controls describe the functionality (i.e., security capability, functions, or mechanisms) visible at the interfaces of the controls and specifically exclude functionality and data structures internal to the operation of the controls. Related control: SA-5. | link | count: 001 Obtain functional properties of security controls (44b71aa8-099d-8b97-1557-0e853ec38e0d) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-4(10) | NIST_SP_800-53_R4_SA-4(10) | NIST SP 800-53 Rev. 4 SA-4 (10) | System And Services Acquisition | Use Of Approved Piv Products | Shared | n/a | The organization employs only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational information systems. Supplemental Guidance: Related controls: IA-2; IA-8. | link | count: 001 Employ FIPS 201-approved technology for PIV (8b333332-6efd-7c0d-5a9f-d1eb95105214) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-4(2) | NIST_SP_800-53_R4_SA-4(2) | NIST SP 800-53 Rev. 4 SA-4 (2) | System And Services Acquisition | Design / Implementation Information For Security Controls | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to provide design and implementation information for the security controls to be employed that includes: [Selection (one or more): security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [Assignment: organization-defined design/implementation information]] at [Assignment: organization-defined level of detail]. Supplemental Guidance: Organizations may require different levels of detail in design and implementation documentation for security controls employed in organizational information systems, system components, or information system services based on mission/business requirements, requirements for trustworthiness/resiliency, and requirements for analysis and testing. Information systems can be partitioned into multiple subsystems. Each subsystem within the system can contain one or more modules. The high-level design for the system is expressed in terms of multiple subsystems and the interfaces between subsystems providing security-relevant functionality. The low-level design for the system is expressed in terms of modules with particular emphasis on software and firmware (but not excluding hardware) and the interfaces between modules providing security-relevant functionality. Source code and hardware schematics are typically referred to as the implementation representation of the information system. Related control: SA-5. | link | count: 001 Obtain design and implementation information for the security controls (22a02c9a-49e4-5dc9-0d14-eb35ad717154) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-4(8) | NIST_SP_800-53_R4_SA-4(8) | NIST SP 800-53 Rev. 4 SA-4 (8) | System And Services Acquisition | Continuous Monitoring Plan | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to produce a plan for the continuous monitoring of security control effectiveness that contains [Assignment: organization-defined level of detail]. Supplemental Guidance: The objective of continuous monitoring plans is to determine if the complete set of planned, required, and deployed security controls within the information system, system component, or information system service continue to be effective over time based on the inevitable changes that occur. Developer continuous monitoring plans include a sufficient level of detail such that the information can be incorporated into the continuous monitoring strategies and programs implemented by organizations. Related control: CA-7. | link | count: 001 Obtain continuous monitoring plan for security controls (ca6d7878-3189-1833-4620-6c7254ed1607) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-4(9) | NIST_SP_800-53_R4_SA-4(9) | NIST SP 800-53 Rev. 4 SA-4 (9) | System And Services Acquisition | Functions / Ports / Protocols / Services In Use | Shared | n/a | The organization requires the developer of the information system, system component, or information system service to identify early in the system development life cycle, the functions, ports, protocols, and services intended for organizational use. Supplemental Guidance: The identification of functions, ports, protocols, and services early in the system development life cycle (e.g., during the initial requirements definition and design phases) allows organizations to influence the design of the information system, information system component, or information system service. This early involvement in the life cycle helps organizations to avoid or minimize the use of functions, ports, protocols, or services that pose unnecessarily high risks and understand the trade-offs involved in blocking specific ports, protocols, or services (or when requiring information system service providers to do so). Early identification of functions, ports, protocols, and services avoids costly retrofitting of security controls after the information system, system component, or information system service has been implemented. SA-9 describes requirements for external information system services with organizations identifying which functions, ports, protocols, and services are provided from external sources. Related controls: CM-7, SA-9. | link | count: 001 Require developer to identify SDLC ports, protocols, and services (f6da5cca-5795-60ff-49e1-4972567815fe) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-5 | NIST_SP_800-53_R4_SA-5 | NIST SP 800-53 Rev. 4 SA-5 | System And Services Acquisition | Information System Documentation | Shared | n/a | The organization: a. Obtains administrator documentation for the information system, system component, or information system service that describes: 1. Secure configuration, installation, and operation of the system, component, or service; 2. Effective use and maintenance of security functions/mechanisms; and 3. Known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions; b. Obtains user documentation for the information system, system component, or information system service that describes: 1. User-accessible security functions/mechanisms and how to effectively use those security functions/mechanisms; 2. Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner; and 3. User responsibilities in maintaining the security of the system, component, or service; c. Documents attempts to obtain information system, system component, or information system service documentation when such documentation is either unavailable or nonexistent and [Assignment: organization-defined actions] in response; d. Protects documentation as required, in accordance with the risk management strategy; and e. Distributes documentation to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: This control helps organizational personnel understand the implementation and operation of security controls associated with information systems, system components, and information system services. Organizations consider establishing specific measures to determine the quality/completeness of the content provided. The inability to obtain needed documentation may occur, for example, due to the age of the information system/component or lack of support from developers and contractors. In those situations, organizations may need to recreate selected documentation if such documentation is essential to the effective implementation or operation of security controls. The level of protection provided for selected information system, component, or service documentation is commensurate with the security category or classification of the system. For example, documentation associated with a key DoD weapons system or command and control system would typically require a higher level of protection than a routine administrative system. Documentation that addresses information system vulnerabilities may also require an increased level of protection. Secure operation of the information system, includes, for example, initially starting the system and resuming secure system operation after any lapse in system operation. Related controls: CM-6, CM-8, PL-2, PL-4, PS-2, SA-3, SA-4. References: None. | link | count: 005 Distribute information system documentation (84a01872-5318-049e-061e-d56734183e84), Document customer-defined actions (8c44a0ea-9b09-4d9c-0e91-f9bee3d05bfb), Obtain Admin documentation (3f1216b0-30ee-1ac9-3899-63eb744e85f5), Obtain user security function documentation (be1c34ab-295a-07a6-785c-36f63c1d223e), Protect administrator and user documentation (09960521-759e-5d12-086f-4192a72a5e92) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-9 | NIST_SP_800-53_R4_SA-9 | NIST SP 800-53 Rev. 4 SA-9 | System And Services Acquisition | External Information System Services | Shared | n/a | The organization: a. Requires that providers of external information system services comply with organizational information security requirements and employ [Assignment: organization-defined security controls] in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance; b. Defines and documents government oversight and user roles and responsibilities with regard to external information system services; and c. Employs [Assignment: organization-defined processes, methods, and techniques] to monitor security control compliance by external service providers on an ongoing basis. Supplemental Guidance: External information system services are services that are implemented outside of the authorization boundaries of organizational information systems. This includes services that are used by, but not a part of, organizational information systems. FISMA and OMB policy require that organizations using external service providers that are processing, storing, or transmitting federal information or operating information systems on behalf of the federal government ensure that such providers meet the same security requirements that federal agencies are required to meet. Organizations establish relationships with external service providers in a variety of ways including, for example, through joint ventures, business partnerships, contracts, interagency agreements, lines of business arrangements, licensing agreements, and supply chain exchanges. The responsibility for managing risks from the use of external information system services remains with authorizing officials. For services external to organizations, a chain of trust requires that organizations establish and retain a level of confidence that each participating provider in the potentially complex consumer-provider relationship provides adequate protection for the services rendered. The extent and nature of this chain of trust varies based on the relationships between organizations and the external providers. Organizations document the basis for trust relationships so the relationships can be monitored over time. External information system services documentation includes government, service providers, end user security roles and responsibilities, and service-level agreements. Service-level agreements define expectations of performance for security controls, describe measurable outcomes, and identify remedies and response requirements for identified instances of noncompliance. Related controls: CA-3, IR-7, PS-7. References: NIST Special Publication 800-35. | link | count: 004 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-9(1) | NIST_SP_800-53_R4_SA-9(1) | NIST SP 800-53 Rev. 4 SA-9 (1) | System And Services Acquisition | Risk Assessments / Organizational Approvals | Shared | n/a | The organization: (a) Conducts an organizational assessment of risk prior to the acquisition or outsourcing of dedicated information security services; and (b) Ensures that the acquisition or outsourcing of dedicated information security services is approved by [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Dedicated information security services include, for example, incident monitoring, analysis and response, operation of information security-related devices such as firewalls, or key management services. Related controls: CA-6, RA-3. | link | count: 002 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Obtain approvals for acquisitions and outsourcing (92b94485-1c49-3350-9ada-dffe94f08e87) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-9(2) | NIST_SP_800-53_R4_SA-9(2) | NIST SP 800-53 Rev. 4 SA-9 (2) | System And Services Acquisition | Identification Of Functions / Ports / Protocols / Services | Shared | n/a | The organization requires providers of [Assignment: organization-defined external information system services] to identify the functions, ports, protocols, and other services required for the use of such services. Supplemental Guidance: Information from external service providers regarding the specific functions, ports, protocols, and services used in the provision of such services can be particularly useful when the need arises to understand the trade-offs involved in restricting certain functions/services or blocking certain ports/protocols. Related control: CM-7. | link | count: 001 Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-9(4) | NIST_SP_800-53_R4_SA-9(4) | NIST SP 800-53 Rev. 4 SA-9 (4) | System And Services Acquisition | Consistent Interests Of Consumers And Providers | Shared | n/a | The organization employs [Assignment: organization-defined security safeguards] to ensure that the interests of [Assignment: organization-defined external service providers] are consistent with and reflect organizational interests. Supplemental Guidance: As organizations increasingly use external service providers, the possibility exists that the interests of the service providers may diverge from organizational interests. In such situations, simply having the correct technical, procedural, or operational safeguards in place may not be sufficient if the service providers that implement and control those safeguards are not operating in a manner consistent with the interests of the consuming organizations. Possible actions that organizations might take to address such concerns include, for example, requiring background checks for selected service provider personnel, examining ownership records, employing only trustworthy service providers (i.e., providers with which organizations have had positive experiences), and conducting periodic/unscheduled visits to service provider facilities. | link | count: 001 Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SA-9(5) | NIST_SP_800-53_R4_SA-9(5) | NIST SP 800-53 Rev. 4 SA-9 (5) | System And Services Acquisition | Processing, Storage, And Service Location | Shared | n/a | The organization restricts the location of [Selection (one or more): information processing; information/data; information system services] to [Assignment: organization-defined locations] based on [Assignment: organization-defined requirements or conditions]. Supplemental Guidance: The location of information processing, information/data storage, or information system services that are critical to organizations can have a direct impact on the ability of those organizations to successfully execute their missions/business functions. This situation exists when external providers control the location of processing, storage or services. The criteria external providers use for the selection of processing, storage, or service locations may be different from organizational criteria. For example, organizations may want to ensure that data/information storage locations are restricted to certain locations to facilitate incident response activities (e.g., forensic analyses, after-the-fact investigations) in case of information security breaches/compromises. Such incident response activities may be adversely affected by the governing laws or protocols in the locations where processing and storage occur and/or the locations from which information system services emanate. | link | count: 001 Restrict location of information processing, storage and services (0040d2e5-2779-170d-6a2c-1f5fca353335) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-1 | NIST_SP_800-53_R4_SC-1 | NIST SP 800-53 Rev. 4 SC-1 | System And Communications Protection | System And Communications Protection Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system and communications protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls; and b. Reviews and updates the current: 1. System and communications protection policy [Assignment: organization-defined frequency]; and 2. System and communications protection procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SC family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-10 | NIST_SP_800-53_R4_SC-10 | NIST SP 800-53 Rev. 4 SC-10 | System And Communications Protection | Network Disconnect | Shared | n/a | The information system terminates the network connection associated with a communications session at the end of the session or after [Assignment: organization-defined time period] of inactivity. Supplemental Guidance: This control applies to both internal and external networks. Terminating network connections associated with communications sessions include, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. Time periods of inactivity may be established by organizations and include, for example, time periods by type of network access or for specific network accesses. Control Enhancements: None. References: None. | link | count: 001 Reauthenticate or terminate a user session (d6653f89-7cb5-24a4-9d71-51581038231b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-12 | NIST_SP_800-53_R4_SC-12 | NIST SP 800-53 Rev. 4 SC-12 | System And Communications Protection | Cryptographic Key Establishment And Management | Shared | n/a | The organization establishes and manages cryptographic keys for required cryptography employed within the information system in accordance with [Assignment: organization-defined requirements for key generation, distribution, storage, access, and destruction]. Supplemental Guidance: Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. Organizations define key management requirements in accordance with applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance, specifying appropriate options, levels, and parameters. Organizations manage trust stores to ensure that only approved trust anchors are in such trust stores. This includes certificates with visibility external to organizational information systems and certificates related to the internal operations of systems. Related controls: SC-13, SC-17. References: NIST Special Publications 800-56, 800-57. | link | count: 040 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) (47031206-ce96-41f8-861b-6a915f3de284), Azure API for FHIR should use a customer-managed key to encrypt data at rest (051cba44-2429-45b9-9649-46cec11c7119), Azure Automation accounts should use customer-managed keys to encrypt data at rest (56a5ee18-2ae6-4810-86f7-18e39ce5629b), Azure Batch account should use customer-managed keys to encrypt data (99e9ccd8-3db9-4592-b0d1-14b1715a4d8a), Azure Container Instance container group should use customer-managed key for encryption (0aa61e00-0a01-4a3c-9945-e93cffedf0e6), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password (86efb160-8de7-451d-bc08-5d475b0aadae), Azure Data Explorer encryption at rest should use a customer-managed key (81e74cea-30fd-40d5-802f-d72103c2aaaa), Azure data factories should be encrypted with a customer-managed key (4ec52d6d-beb7-40c4-9a9e-fe753254690e), Azure HDInsight clusters should use customer-managed keys to encrypt data at rest (64d314f6-6062-4780-a861-c23e8951bee5), Azure HDInsight clusters should use encryption at host to encrypt data at rest (1fd32ebd-e4c3-4e13-a54a-d7422d4d95f6), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Stream Analytics jobs should use customer-managed keys to encrypt data (87ba29ef-1ab3-4d82-b763-87fcd4f531f7), Azure Synapse workspaces should use customer-managed keys to encrypt data at rest (f7d52b2d-e161-4dfa-a82b-55e564167385), Bot Service should be encrypted with a customer-managed key (51522a96-0869-4791-82f3-981000c2c67f), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Event Hub namespaces should use a customer-managed key for encryption (a1ad735a-e96f-45d2-a7b2-9a4932cab7ec), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Logic Apps Integration Service Environment should be encrypted with customer-managed keys (1fafeaf6-7927-4059-a50a-8eb2a7a6f2b5), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), OS and data disks should be encrypted with a customer-managed key (702dd420-7fcc-42c5-afe8-4026edd20fe0), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Service Bus Premium namespaces should use a customer-managed key for encryption (295fc8b1-dc9f-4f53-9c61-3f313ceab40a), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
API for FHIR, Automation, Azure Data Explorer, Backup, Batch, Bot Service, Cognitive Services, Compute, Container Instance, Container Registry, Cosmos DB, Data Box, Data Factory, Event Hub, HDInsight, Internet of Things, Kubernetes, Logic Apps, Machine Learning, Monitoring, Regulatory Compliance, Service Bus, SQL, Storage, Stream Analytics, Synapse | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-12(1) | NIST_SP_800-53_R4_SC-12(1) | NIST SP 800-53 Rev. 4 SC-12 (1) | System And Communications Protection | Availability | Shared | n/a | The organization maintains availability of information in the event of the loss of cryptographic keys by users. Supplemental Guidance: Escrowing of encryption keys is a common practice for ensuring availability in the event of loss of keys (e.g., due to forgotten passphrase). | link | count: 001 Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-12(2) | NIST_SP_800-53_R4_SC-12(2) | NIST SP 800-53 Rev. 4 SC-12 (2) | System And Communications Protection | Symmetric Keys | Shared | n/a | The organization produces, controls, and distributes symmetric cryptographic keys using [Selection: NIST FIPS-compliant; NSA-approved] key management technology and processes. | link | count: 001 Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-12(3) | NIST_SP_800-53_R4_SC-12(3) | NIST SP 800-53 Rev. 4 SC-12 (3) | System And Communications Protection | Asymmetric Keys | Shared | n/a | The organization produces, controls, and distributes asymmetric cryptographic keys using [Selection: NSA-approved key management technology and processes; approved PKI Class 3 certificates or prepositioned keying material; approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user’s private key]. | link | count: 001 Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-13 | NIST_SP_800-53_R4_SC-13 | NIST SP 800-53 Rev. 4 SC-13 | System And Communications Protection | Cryptographic Protection | Shared | n/a | The information system implements [Assignment: organization-defined cryptographic uses and type of cryptography required for each use] in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Supplemental Guidance: Cryptography can be employed to support a variety of security solutions including, for example, the protection of classified and Controlled Unclassified Information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Generally applicable cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. This control does not impose any requirements on organizations to use cryptography. However, if cryptography is required based on the selection of other security controls, organizations define each type of cryptographic use and the type of cryptography required (e.g., protection of classified information: NSA-approved cryptography; provision of digital signatures: FIPS-validated cryptography). Related controls: AC-2, AC-3, AC-7, AC-17, AC-18, AU-9, AU-10, CM-11, CP-9, IA-3, IA-7, MA-4, MP-2, MP-4, MP-5, SA-4, SC-8, SC-12, SC-28, SI-7. References: FIPS Publication 140; Web: http://csrc.nist.gov/cryptval, http://www.cnss.gov. | link | count: 001 Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-15 | NIST_SP_800-53_R4_SC-15 | NIST SP 800-53 Rev. 4 SC-15 | System And Communications Protection | Collaborative Computing Devices | Shared | n/a | The information system: a. Prohibits remote activation of collaborative computing devices with the following exceptions: [Assignment: organization-defined exceptions where remote activation is to be allowed]; and b. Provides an explicit indication of use to users physically present at the devices. Supplemental Guidance: Collaborative computing devices include, for example, networked white boards, cameras, and microphones. Explicit indication of use includes, for example, signals to users when collaborative computing devices are activated. Related control: AC-21. References: None. | link | count: 002 Explicitly notify use of collaborative computing devices (62fa14f0-4cbe-762d-5469-0899a99b98aa), Prohibit remote activation of collaborative computing devices (678ca228-042d-6d8e-a598-c58d5670437d) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-17 | NIST_SP_800-53_R4_SC-17 | NIST SP 800-53 Rev. 4 SC-17 | System And Communications Protection | Public Key Infrastructure Certificates | Shared | n/a | The organization issues public key certificates under an [Assignment: organization- defined certificate policy] or obtains public key certificates from an approved service provider. Supplemental Guidance: For all certificates, organizations manage information system trust stores to ensure only approved trust anchors are in the trust stores. This control addresses both certificates with visibility external to organizational information systems and certificates related to the internal operations of systems, for example, application-specific time services. Related control: SC-12. Control Enhancements: None. References: OMB Memorandum 05-24; NIST Special Publications 800-32, 800-63. | link | count: 001 Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-18 | NIST_SP_800-53_R4_SC-18 | NIST SP 800-53 Rev. 4 SC-18 | System And Communications Protection | Mobile Code | Shared | n/a | The organization: a. Defines acceptable and unacceptable mobile code and mobile code technologies; b. Establishes usage restrictions and implementation guidance for acceptable mobile code and mobile code technologies; and c. Authorizes, monitors, and controls the use of mobile code within the information system. Supplemental Guidance: Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include, for example, Java, JavaScript, ActiveX, Postscript, PDF, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices (e.g., smart phones). Mobile code policy and procedures address preventing the development, acquisition, or introduction of unacceptable mobile code within organizational information systems. Related controls: AU-2, AU-12, CM-2, CM-6, SI-3. References: NIST Special Publication 800-28; DoD Instruction 8552.01. | link | count: 003 Authorize, monitor, and control usage of mobile code technologies (291f20d4-8d93-1d73-89f3-6ce28b825563), Define acceptable and unacceptable mobile code technologies (1afada58-8b34-7ac2-a38a-983218635201), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-19 | NIST_SP_800-53_R4_SC-19 | NIST SP 800-53 Rev. 4 SC-19 | System And Communications Protection | Voice Over Internet Protocol | Shared | n/a | The organization: a. Establishes usage restrictions and implementation guidance for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously; and b. Authorizes, monitors, and controls the use of VoIP within the information system. Supplemental Guidance: Related controls: CM-6, SC-7, SC-15. References: NIST Special Publication 800-58. | link | count: 002 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Establish voip usage restrictions (68a39c2b-0f17-69ee-37a3-aa10f9853a08) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-2 | NIST_SP_800-53_R4_SC-2 | NIST SP 800-53 Rev. 4 SC-2 | System And Communications Protection | Application Partitioning | Shared | n/a | The information system separates user functionality (including user interface services) from information system management functionality. Supplemental Guidance: Information system management functionality includes, for example, functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical. Organizations implement separation of system management-related functionality from user functionality by using different computers, different central processing units, different instances of operating systems, different network addresses, virtualization techniques, or combinations of these or other methods, as appropriate. This type of separation includes, for example, web administrative interfaces that use separate authentication methods for users of any other information system resources. Separation of system and user functionality may include isolating administrative interfaces on different domains and with additional access controls. Related controls: SA-4, SA-8, SC-3. References: None. | link | count: 003 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-20 | NIST_SP_800-53_R4_SC-20 | NIST SP 800-53 Rev. 4 SC-20 | System And Communications Protection | Secure Name /Address Resolution Service (Authoritative Source) | Shared | n/a | The information system: a. Provides additional data origin and integrity artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries; and b. Provides the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace. Supplemental Guidance: This control enables external clients including, for example, remote Internet clients, to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. Information systems that provide name and address resolution services include, for example, domain name system (DNS) servers. Additional artifacts include, for example, DNS Security (DNSSEC) digital signatures and cryptographic keys. DNS resource records are examples of authoritative data. The means to indicate the security status of child zones includes, for example, the use of delegation signer resource records in the DNS. The DNS security controls reflect (and are referenced from) OMB Memorandum 08-23. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to assure the authenticity and integrity of response data. Related controls: AU-10, SC-8, SC-12, SC-13, SC-21, SC-22. References: OMB Memorandum 08-23; NIST Special Publication 800-81. | link | count: 002 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-21 | NIST_SP_800-53_R4_SC-21 | NIST SP 800-53 Rev. 4 SC-21 | System And Communications Protection | Secure Name /Address Resolution Service (Recursive Or Caching Resolver) | Shared | n/a | The information system requests and performs data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources. Supplemental Guidance: Each client of name resolution services either performs this validation on its own, or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching domain name system (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to enable clients to verify the authenticity and integrity of response data. Related controls: SC-20, SC-22. References: NIST Special Publication 800-81. | link | count: 002 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-22 | NIST_SP_800-53_R4_SC-22 | NIST SP 800-53 Rev. 4 SC-22 | System And Communications Protection | Architecture And Provisioning For Name/Address Resolution Service | Shared | n/a | The information systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal/external role separation. Supplemental Guidance: Information systems that provide name and address resolution services include, for example, domain name system (DNS) servers. To eliminate single points of failure and to enhance redundancy, organizations employ at least two authoritative domain name system servers, one configured as the primary server and the other configured as the secondary server. Additionally, organizations typically deploy the servers in two geographically separated network subnetworks (i.e., not located in the same physical facility). For role separation, DNS servers with internal roles only process name and address resolution requests from within organizations (i.e., from internal clients). DNS servers with external roles only process name and address resolution information requests from clients external to organizations (i.e., on external networks including the Internet). Organizations specify clients that can access authoritative DNS servers in particular roles (e.g., by address ranges, explicit lists). Related controls: SC-2, SC-20, SC-21, SC-24. Control Enhancements: None. References: NIST Special Publication 800-81. | link | count: 001 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-23 | NIST_SP_800-53_R4_SC-23 | NIST SP 800-53 Rev. 4 SC-23 | System And Communications Protection | Session Authenticity | Shared | n/a | The information system protects the authenticity of communications sessions. Supplemental Guidance: This control addresses communications protection at the session, versus packet level (e.g., sessions in service-oriented architectures providing web-based services) and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. Authenticity protection includes, for example, protecting against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. Related controls: SC-8, SC-10, SC-11. References: NIST Special Publications 800-52, 800-77, 800-95. | link | count: 002 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce random unique session identifiers (c7d57a6a-7cc2-66c0-299f-83bf90558f5d) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-23(1) | NIST_SP_800-53_R4_SC-23(1) | NIST SP 800-53 Rev. 4 SC-23 (1) | System And Communications Protection | Invalidate Session Identifiers At Logout | Shared | n/a | The information system invalidates session identifiers upon user logout or other session termination. Supplemental Guidance: This control enhancement curtails the ability of adversaries from capturing and continuing to employ previously valid session IDs. | link | count: 001 Invalidate session identifiers at logout (396f465d-375e-57de-58ba-021adb008191) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-24 | NIST_SP_800-53_R4_SC-24 | NIST SP 800-53 Rev. 4 SC-24 | System And Communications Protection | Fail In Known State | Shared | n/a | The information system fails to a [Assignment: organization-defined known-state] for [Assignment: organization-defined types of failures] preserving [Assignment: organization-defined system state information] in failure. Supplemental Guidance: Failure in a known state addresses security concerns in accordance with the mission/business needs of organizations. Failure in a known secure state helps to prevent the loss of confidentiality, integrity, or availability of information in the event of failures of organizational information systems or system components. Failure in a known safe state helps to prevent systems from failing to a state that may cause injury to individuals or destruction to property. Preserving information system state information facilitates system restart and return to the operational mode of organizations with less disruption of mission/business processes. Related controls: CP-2, CP- 10, CP-12, SC-7, SC-22. Control Enhancements: None. References: None. | link | count: 001 Ensure information system fails in known state (12af7c7a-92af-9e96-0d0c-5e732d1a3751) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-28 | NIST_SP_800-53_R4_SC-28 | NIST SP 800-53 Rev. 4 SC-28 | System And Communications Protection | Protection Of Information At Rest | Shared | n/a | The information system protects the [Selection (one or more): confidentiality; integrity] of [Assignment: organization-defined information at rest]. Supplemental Guidance: This control addresses the confidentiality and integrity of information at rest and covers user information and system information. Information at rest refers to the state of information when it is located on storage devices as specific components of information systems. System-related information requiring protection includes, for example, configurations or rule sets for firewalls, gateways, intrusion detection/prevention systems, filtering routers, and authenticator content. Organizations may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms and file share scanning. Integrity protection can be achieved, for example, by implementing Write-Once-Read-Many (WORM) technologies. Organizations may also employ other security controls including, for example, secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved and/or continuous monitoring to identify malicious code at rest. Related controls: AC-3, AC-6, CA-7, CM-3, CM-5, CM-6, PE-3, SC-8, SC-13, SI-3, SI-7. References: NIST Special Publications 800-56, 800-57, 800-111. | link | count: 017 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-28(1) | NIST_SP_800-53_R4_SC-28(1) | NIST SP 800-53 Rev. 4 SC-28 (1) | System And Communications Protection | Cryptographic Protection | Shared | n/a | The information system implements cryptographic mechanisms to prevent unauthorized disclosure and modification of [Assignment: organization-defined information] on [Assignment: organization-defined information system components]. Supplemental Guidance: Selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of organizational information. The strength of mechanism is commensurate with the security category and/or classification of the information. This control enhancement applies to significant concentrations of digital media in organizational areas designated for media storage and also to limited quantities of media generally associated with information system components in operational environments (e.g., portable storage devices, mobile devices). Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). Organizations employing cryptographic mechanisms to protect information at rest also consider cryptographic key management solutions. Related controls: AC-19, SC-12. | link | count: 017 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-3 | NIST_SP_800-53_R4_SC-3 | NIST SP 800-53 Rev. 4 SC-3 | System And Communications Protection | Security Function Isolation | Shared | n/a | The information system isolates security functions from nonsecurity functions. Supplemental Guidance: The information system isolates security functions from nonsecurity functions by means of an isolation boundary (implemented via partitions and domains). Such isolation controls access to and protects the integrity of the hardware, software, and firmware that perform those security functions. Information systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including, for example, through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk, and address space protections that protect executing code. Information systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities. While the ideal is for all of the code within the security function isolation boundary to only contain security-relevant code, it is sometimes necessary to include nonsecurity functions within the isolation boundary as an exception. Related controls: AC- 3, AC-6, SA-4, SA-5, SA-8, SA-13, SC-2, SC-7, SC-39. References: None. | link | count: 004 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-39 | NIST_SP_800-53_R4_SC-39 | NIST SP 800-53 Rev. 4 SC-39 | System And Communications Protection | Process Isolation | Shared | n/a | The information system maintains a separate execution domain for each executing process. Supplemental Guidance: Information systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each information system process has a distinct address space so that communication between processes is performed in a manner controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces. This capability is available in most commercial operating systems that employ multi-state processor technologies. Related controls: AC-3, AC-4, AC-6, SA-4, SA-5, SA-8, SC-2, SC-3. References: None. | link | count: 001 Maintain separate execution domains for running processes (bfc540fe-376c-2eef-4355-121312fa4437) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-5 | NIST_SP_800-53_R4_SC-5 | NIST SP 800-53 Rev. 4 SC-5 | System And Communications Protection | Denial Of Service Protection | Shared | n/a | The information system protects against or limits the effects of the following types of denial of service attacks: [Assignment: organization-defined types of denial of service attacks or reference to source for such information] by employing [Assignment: organization-defined security safeguards]. Supplemental Guidance: A variety of technologies exist to limit, or in some cases, eliminate the effects of denial of service attacks. For example, boundary protection devices can filter certain types of packets to protect information system components on internal organizational networks from being directly affected by denial of service attacks. Employing increased capacity and bandwidth combined with service redundancy may also reduce the susceptibility to denial of service attacks. Related controls: SC-6, SC-7. References: None. | link | count: 005 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Develop and document a DDoS response plan (b7306e73-0494-83a2-31f5-280e934a8f70), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Network, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-6 | NIST_SP_800-53_R4_SC-6 | NIST SP 800-53 Rev. 4 SC-6 | System And Communications Protection | Resource Availability | Shared | n/a | The information system protects the availability of resources by allocating [Assignment: organization-defined resources] by [Selection (one or more); priority; quota; [Assignment: organization-defined security safeguards]]. Supplemental Guidance: Priority protection helps prevent lower-priority processes from delaying or interfering with the information system servicing any higher-priority processes. Quotas prevent users or processes from obtaining more than predetermined amounts of resources. This control does not apply to information system components for which there are only single users/roles. Control Enhancements: None. References: None. | link | count: 003 Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Manage availability and capacity (edcc36f1-511b-81e0-7125-abee29752fe7), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7 | NIST_SP_800-53_R4_SC-7 | NIST SP 800-53 Rev. 4 SC-7 | System And Communications Protection | Boundary Protection | Shared | n/a | The information system: a. Monitors and controls communications at the external boundary of the system and at key internal boundaries within the system; b. Implements subnetworks for publicly accessible system components that are [Selection: physically; logically] separated from internal organizational networks; and c. Connects to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture. Supplemental Guidance: Managed interfaces include, for example, gateways, routers, firewalls, guards, network-based malicious code analysis and virtualization systems, or encrypted tunnels implemented within a security architecture (e.g., routers protecting firewalls or application gateways residing on protected subnetworks). Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational information systems includes, for example, restricting external web traffic to designated web servers within managed interfaces and prohibiting external traffic that appears to be spoofing internal addresses. Organizations consider the shared nature of commercial telecommunications services in the implementation of security controls associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers, and may also include third party-provided access lines and other service elements. Such transmission services may represent sources of increased risk despite contract security provisions. Related controls: AC-4, AC-17, CA-3, CM-7, CP-8, IR-4, RA-3, SC-5, SC-13. References: FIPS Publication 199; NIST Special Publications 800-41, 800-77. | link | count: 053 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Regulatory Compliance, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7(12) | NIST_SP_800-53_R4_SC-7(12) | NIST SP 800-53 Rev. 4 SC-7 (12) | System And Communications Protection | Host-Based Protection | Shared | n/a | The organization implements [Assignment: organization-defined host-based boundary protection mechanisms] at [Assignment: organization-defined information system components]. Supplemental Guidance: Host-based boundary protection mechanisms include, for example, host-based firewalls. Information system components employing host-based boundary protection mechanisms include, for example, servers, workstations, and mobile devices. | link | count: 001 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7(13) | NIST_SP_800-53_R4_SC-7(13) | NIST SP 800-53 Rev. 4 SC-7 (13) | System And Communications Protection | Isolation Of Security Tools / Mechanisms / Support Components | Shared | n/a | The organization isolates [Assignment: organization-defined information security tools, mechanisms, and support components] from other internal information system components by implementing physically separate subnetworks with managed interfaces to other components of the system. Supplemental Guidance: Physically separate subnetworks with managed interfaces are useful, for example, in isolating computer network defenses from critical operational processing networks to prevent adversaries from discovering the analysis and forensics techniques of organizations. Related controls: SA-8, SC-2, SC-3. | link | count: 001 Isolate SecurID systems, Security Incident Management systems (dd6d00a8-701a-5935-a22b-c7b9c0c698b2) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7(18) | NIST_SP_800-53_R4_SC-7(18) | NIST SP 800-53 Rev. 4 SC-7 (18) | System And Communications Protection | Fail Secure | Shared | n/a | The information system fails securely in the event of an operational failure of a boundary protection device. Supplemental Guidance: Fail secure is a condition achieved by employing information system mechanisms to ensure that in the event of operational failures of boundary protection devices at managed interfaces (e.g., routers, firewalls, guards, and application gateways residing on protected subnetworks commonly referred to as demilitarized zones), information systems do not enter into unsecure states where intended security properties no longer hold. Failures of boundary protection devices cannot lead to, or cause information external to the devices to enter the devices, nor can failures permit unauthorized information releases. Related controls: CP-2, SC-24. | link | count: 002 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage transfers between standby and active system components (df54d34f-65f3-39f1-103c-a0464b8615df) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7(20) | NIST_SP_800-53_R4_SC-7(20) | NIST SP 800-53 Rev. 4 SC-7 (20) | System And Communications Protection | Dynamic Isolation / Segregation | Shared | n/a | The information system provides the capability to dynamically isolate/segregate [Assignment: organization-defined information system components] from other components of the system. Supplemental Guidance: The capability to dynamically isolate or segregate certain internal components of organizational information systems is useful when it is necessary to partition or separate certain components of dubious origin from those components possessing greater trustworthiness. Component isolation reduces the attack surface of organizational information systems. Isolation of selected information system components is also a means of limiting the damage from successful cyber attacks when those attacks occur. | link | count: 001 Ensure system capable of dynamic isolation of resources (83eea3d3-0d2c-9ccd-1021-2111b29b2a62) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7(21) | NIST_SP_800-53_R4_SC-7(21) | NIST SP 800-53 Rev. 4 SC-7 (21) | System And Communications Protection | Isolation Of Information System Components | Shared | n/a | The organization employs boundary protection mechanisms to separate [Assignment: organization-defined information system components] supporting [Assignment: organization- defined missions and/or business functions]. Supplemental Guidance: Organizations can isolate information system components performing different missions and/or business functions. Such isolation limits unauthorized information flows among system components and also provides the opportunity to deploy greater levels of protection for selected components. Separating system components with boundary protection mechanisms provides the capability for increased protection of individual components and to more effectively control information flows between those components. This type of enhanced protection limits the potential harm from cyber attacks and errors. The degree of separation provided varies depending upon the mechanisms chosen. Boundary protection mechanisms include, for example, routers, gateways, and firewalls separating system components into physically separate networks or subnetworks, cross-domain devices separating subnetworks, virtualization techniques, and encrypting information flows among system components using distinct encryption keys. Related controls: CA-9, SC-3. | link | count: 001 Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7(3) | NIST_SP_800-53_R4_SC-7(3) | NIST SP 800-53 Rev. 4 SC-7 (3) | System And Communications Protection | Access Points | Shared | n/a | The organization limits the number of external network connections to the information system. Supplemental Guidance: Limiting the number of external network connections facilitates more comprehensive monitoring of inbound and outbound communications traffic. The Trusted Internet Connection (TIC) initiative is an example of limiting the number of external network connections. | link | count: 052 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7(4) | NIST_SP_800-53_R4_SC-7(4) | NIST SP 800-53 Rev. 4 SC-7 (4) | System And Communications Protection | External Telecommunications Services | Shared | n/a | The organization: (a) Implements a managed interface for each external telecommunication service; (b) Establishes a traffic flow policy for each managed interface; (c) Protects the confidentiality and integrity of the information being transmitted across each interface; (d) Documents each exception to the traffic flow policy with a supporting mission/business need and duration of that need; and (e) Reviews exceptions to the traffic flow policy [Assignment: organization-defined frequency] and removes exceptions that are no longer supported by an explicit mission/business need. Supplemental Guidance: Related control: SC-8. | link | count: 003 Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7(7) | NIST_SP_800-53_R4_SC-7(7) | NIST SP 800-53 Rev. 4 SC-7 (7) | System And Communications Protection | Prevent Split Tunneling For Remote Devices | Shared | n/a | The information system, in conjunction with a remote device, prevents the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks. Supplemental Guidance: This control enhancement is implemented within remote devices (e.g., notebook computers) through configuration settings to disable split tunneling in those devices, and by preventing those configuration settings from being readily configurable by users. This control enhancement is implemented within the information system by the detection of split tunneling (or of configuration settings that allow split tunneling) in the remote device, and by prohibiting the connection if the remote device is using split tunneling. Split tunneling might be desirable by remote users to communicate with local information system resources such as printers/file servers. However, split tunneling would in effect allow unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. The use of VPNs for remote connections, when adequately provisioned with appropriate security controls, may provide the organization with sufficient assurance that it can effectively treat such connections as non-remote connections from the confidentiality and integrity perspective. VPNs thus provide a means for allowing non-remote communications paths from remote devices. The use of an adequately provisioned VPN does not eliminate the need for preventing split tunneling. | link | count: 001 Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-7(8) | NIST_SP_800-53_R4_SC-7(8) | NIST SP 800-53 Rev. 4 SC-7 (8) | System And Communications Protection | Route Traffic To Authenticated Proxy Servers | Shared | n/a | The information system routes [Assignment: organization-defined internal communications traffic] to [Assignment: organization-defined external networks] through authenticated proxy servers at managed interfaces. Supplemental Guidance: External networks are networks outside of organizational control. A proxy server is a server (i.e., information system or application) that acts as an intermediary for clients requesting information system resources (e.g., files, connections, web pages, or services) from other organizational servers. Client requests established through an initial connection to the proxy server are evaluated to manage complexity and to provide additional protection by limiting direct connectivity. Web content filtering devices are one of the most common proxy servers providing access to the Internet. Proxy servers support logging individual Transmission Control Protocol (TCP) sessions and blocking specific Uniform Resource Locators (URLs), domain names, and Internet Protocol (IP) addresses. Web proxies can be configured with organization-defined lists of authorized and unauthorized websites. Related controls: AC-3, AU-2. | link | count: 001 Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-8 | NIST_SP_800-53_R4_SC-8 | NIST SP 800-53 Rev. 4 SC-8 | System And Communications Protection | Transmission Confidentiality And Integrity | Shared | n/a | The information system protects the [Selection (one or more): confidentiality; integrity] of transmitted information. Supplemental Guidance: This control applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and/or integrity of organizational information can be accomplished by physical means (e.g., by employing physical distribution systems) or by logical means (e.g., employing encryption techniques). Organizations relying on commercial providers offering transmission services as commodity services rather than as fully dedicated services (i.e., services which can be highly specialized to individual customer needs), may find it difficult to obtain the necessary assurances regarding the implementation of needed security controls for transmission confidentiality/integrity. In such situations, organizations determine what types of confidentiality/integrity services are available in standard, commercial telecommunication service packages. If it is infeasible or impractical to obtain the necessary security controls and assurances of control effectiveness through appropriate contracting vehicles, organizations implement appropriate compensating security controls or explicitly accept the additional risk. Related controls: AC-17, PE-4. References: FIPS Publications 140-2, 197; NIST Special Publications 800-52, 800-77, 800-81, 800-113; CNSS Policy 15; NSTISSI No. 7003. | link | count: 015 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, Regulatory Compliance, SQL, Storage | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SC-8(1) | NIST_SP_800-53_R4_SC-8(1) | NIST SP 800-53 Rev. 4 SC-8 (1) | System And Communications Protection | Cryptographic Or Alternate Physical Protection | Shared | n/a | The information system implements cryptographic mechanisms to [Selection (one or more): prevent unauthorized disclosure of information; detect changes to information] during transmission unless otherwise protected by [Assignment: organization-defined alternative physical safeguards]. Supplemental Guidance: Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions which have common application in digital signatures, checksums, and message authentication codes. Alternative physical security safeguards include, for example, protected distribution systems. Related control: SC-13. | link | count: 014 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, Regulatory Compliance, SQL, Storage | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-1 | NIST_SP_800-53_R4_SI-1 | NIST SP 800-53 Rev. 4 SI-1 | System And Information Integrity | System And Information Integrity Policy And Procedures | Shared | n/a | The organization: a. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]: 1. A system and information integrity policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and 2. Procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls; and b. Reviews and updates the current: 1. System and information integrity policy [Assignment: organization-defined frequency]; and 2. System and information integrity procedures [Assignment: organization-defined frequency]. Supplemental Guidance: This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SI family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9. Control Enhancements: None. References: NIST Special Publications 800-12, 800-100. | link | count: 001 Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-10 | NIST_SP_800-53_R4_SI-10 | NIST SP 800-53 Rev. 4 SI-10 | System And Information Integrity | Information Input Validation | Shared | n/a | The information system checks the validity of [Assignment: organization-defined information inputs]. Supplemental Guidance: Checking the valid syntax and semantics of information system inputs (e.g., character set, length, numerical range, and acceptable values) verifies that inputs match specified definitions for format and content. Software applications typically follow well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If software applications use attacker- supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the tainted output will perform the wrong operations or otherwise interpret the data incorrectly. Prescreening inputs prior to passing to interpreters prevents the content from being unintentionally interpreted as commands. Input validation helps to ensure accurate and correct inputs and prevent attacks such as cross-site scripting and a variety of injection attacks. References: None. | link | count: 001 Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-11 | NIST_SP_800-53_R4_SI-11 | NIST SP 800-53 Rev. 4 SI-11 | System And Information Integrity | Error Handling | Shared | n/a | The information system: a. Generates error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries; and b. Reveals error messages only to [Assignment: organization-defined personnel or roles]. Supplemental Guidance: Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information such as account numbers, social security numbers, and credit card numbers. In addition, error messages may provide a covert channel for transmitting information. Related controls: AU-2, AU-3, SC-31. Control Enhancements: None. References: None. | link | count: 002 Generate error messages (c2cb4658-44dc-9d11-3dad-7c6802dd5ba3), Reveal error messages (20762f1e-85fb-31b0-a600-e833633f10fe) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-12 | NIST_SP_800-53_R4_SI-12 | NIST SP 800-53 Rev. 4 SI-12 | System And Information Integrity | Information Handling And Retention | Shared | n/a | The organization handles and retains information within the information system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements. Supplemental Guidance: Information handling and retention requirements cover the full life cycle of information, in some cases extending beyond the disposal of information systems. The National Archives and Records Administration provides guidance on records retention. Related controls: AC-16, AU-5, AU-11, MP-2, MP-4. Control Enhancements: None. References: None. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-16 | NIST_SP_800-53_R4_SI-16 | NIST SP 800-53 Rev. 4 SI-16 | System And Information Integrity | Memory Protection | Shared | n/a | The information system implements [Assignment: organization-defined security safeguards] to protect its memory from unauthorized code execution. Supplemental Guidance: Some adversaries launch attacks with the intent of executing code in non- executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. Related controls: AC-25, SC-3. Control Enhancements: None. References: None. | link | count: 002 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-2 | NIST_SP_800-53_R4_SI-2 | NIST SP 800-53 Rev. 4 SI-2 | System And Information Integrity | Flaw Remediation | Shared | n/a | The organization: a. Identifies, reports, and corrects information system flaws; b. Tests software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation; c. Installs security-relevant software and firmware updates within [Assignment: organization- defined time period] of the release of the updates; and d. Incorporates flaw remediation into the organizational configuration management process. Supplemental Guidance: Organizations identify information systems affected by announced software flaws including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security responsibilities. Security-relevant software updates include, for example, patches, service packs, hot fixes, and anti-virus signatures. Organizations also address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations take advantage of available resources such as the Common Weakness Enumeration (CWE) or Common Vulnerabilities and Exposures (CVE) databases in remediating flaws discovered in organizational information systems. By incorporating flaw remediation into ongoing configuration management processes, required/anticipated remediation actions can be tracked and verified. Flaw remediation actions that can be tracked and verified include, for example, determining whether organizations follow US-CERT guidance and Information Assurance Vulnerability Alerts. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types. Organizations determine the degree and type of testing needed for the specific type of flaw remediation activity under consideration and also the types of changes that are to be configuration-managed. In some situations, organizations may determine that the testing of software and/or firmware updates is not necessary or practical, for example, when implementing simple anti-virus signature updates. Organizations may also consider in testing decisions, whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures. Related controls: CA-2, CA-7, CM-3, CM-5, CM-8, MA-2, IR-4, RA-5, SA-10, SA-11, SI-11. | link | count: 019 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
App Service, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-2(2) | NIST_SP_800-53_R4_SI-2(2) | NIST SP 800-53 Rev. 4 SI-2 (2) | System And Information Integrity | Automated Flaw Remediation Status | Shared | n/a | The organization employs automated mechanisms [Assignment: organization-defined frequency] to determine the state of information system components with regard to flaw remediation. Supplemental Guidance: Related controls: CM-6, SI-4. | link | count: 002 Automate flaw remediation (a90c4d44-7fac-8e02-6d5b-0d92046b20e6), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-2(3) | NIST_SP_800-53_R4_SI-2(3) | NIST SP 800-53 Rev. 4 SI-2 (3) | System And Information Integrity | Time To Remediate Flaws / Benchmarks For Corrective Actions | Shared | n/a | The organization: (a) Measures the time between flaw identification and flaw remediation; and (b) Establishes [Assignment: organization-defined benchmarks] for taking corrective actions. Supplemental Guidance: This control enhancement requires organizations to determine the current time it takes on the average to correct information system flaws after such flaws have been identified, and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by type of flaw and/or severity of the potential vulnerability if the flaw can be exploited. | link | count: 002 Establish benchmarks for flaw remediation (dd2523d5-2db3-642b-a1cf-83ac973b32c2), Measure the time between flaw identification and flaw remediation (dad1887d-161b-7b61-2e4d-5124a7b5724e) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-2(6) | NIST_SP_800-53_R4_SI-2(6) | NIST SP 800-53 Rev. 4 SI-2 (6) | System and Information Integrity | Removal of Previous Versions of Software / Firmware | Customer | n/a | The organization removes [Assignment: organization-defined software and firmware components] after updated versions have been installed. | link | count: 003 App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c) |
App Service, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-3 | NIST_SP_800-53_R4_SI-3 | NIST SP 800-53 Rev. 4 SI-3 | System And Information Integrity | Malicious Code Protection | Shared | n/a | The organization: a. Employs malicious code protection mechanisms at information system entry and exit points to detect and eradicate malicious code; b. Updates malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures; c. Configures malicious code protection mechanisms to: 1. Perform periodic scans of the information system [Assignment: organization-defined frequency] and real-time scans of files from external sources at [Selection (one or more); endpoint; network entry/exit points] as the files are downloaded, opened, or executed in accordance with organizational security policy; and 2. [Selection (one or more): block malicious code; quarantine malicious code; send alert to administrator; [Assignment: organization-defined action]] in response to malicious code detection; and d. Addresses the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the information system. Supplemental Guidance: Information system entry and exit points include, for example, firewalls, electronic mail servers, web servers, proxy servers, remote-access servers, workstations, notebook computers, and mobile devices. Malicious code includes, for example, viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using steganography. Malicious code can be transported by different means including, for example, web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of information system vulnerabilities. Malicious code protection mechanisms include, for example, anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include, for example, logic bombs, back doors, and other types of cyber attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including, for example, secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. Organizations may determine that in response to the detection of malicious code, different actions may be warranted. For example, organizations can define actions in response to malicious code detection during periodic scans, actions in response to detection of malicious downloads, and/or actions in response to detection of maliciousness when attempting to open or execute files. Related controls: CM-3, MP-2, SA-4, SA-8, SA-12, SA-13, SC-7, SC-26, SC-44, SI-2, SI-4, SI-7. References: NIST Special Publication 800-83. | link | count: 011 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-3(1) | NIST_SP_800-53_R4_SI-3(1) | NIST SP 800-53 Rev. 4 SI-3 (1) | System And Information Integrity | Central Management | Shared | n/a | The organization centrally manages malicious code protection mechanisms. Supplemental Guidance: Central management is the organization-wide management and implementation of malicious code protection mechanisms. Central management includes planning, implementing, assessing, authorizing, and monitoring the organization-defined, centrally managed flaw malicious code protection security controls. Related controls: AU-2, SI-8. | link | count: 010 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-3(2) | NIST_SP_800-53_R4_SI-3(2) | NIST SP 800-53 Rev. 4 SI-3 (2) | System And Information Integrity | Automatic Updates | Shared | n/a | The information system automatically updates malicious code protection mechanisms. Supplemental Guidance: Malicious code protection mechanisms include, for example, signature definitions. Due to information system integrity and availability concerns, organizations give careful consideration to the methodology used to carry out automatic updates. Related control: SI-8. | link | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-3(7) | NIST_SP_800-53_R4_SI-3(7) | NIST SP 800-53 Rev. 4 SI-3 (7) | System And Information Integrity | Nonsignature-Based Detection | Shared | n/a | The information system implements nonsignature-based malicious code detection mechanisms. Supplemental Guidance: Nonsignature-based detection mechanisms include, for example, the use of heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide safeguards against malicious code for which signatures do not yet exist or for which existing signatures may not be effective. This includes polymorphic malicious code (i.e., code that changes signatures when it replicates). This control enhancement does not preclude the use of signature-based detection mechanisms. | link | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-4 | NIST_SP_800-53_R4_SI-4 | NIST SP 800-53 Rev. 4 SI-4 | System And Information Integrity | Information System Monitoring | Shared | n/a | The organization: a. Monitors the information system to detect: 1. Attacks and indicators of potential attacks in accordance with [Assignment: organization- defined monitoring objectives]; and 2. Unauthorized local, network, and remote connections; b. Identifies unauthorized use of the information system through [Assignment: organization- defined techniques and methods]; c. Deploys monitoring devices: (i) strategically within the information system to collect organization-determined essential information; and (ii) at ad hoc locations within the system to track specific types of transactions of interest to the organization; d. Protects information obtained from intrusion-monitoring tools from unauthorized access, modification, and deletion; e. Heightens the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information; f. Obtains legal opinion with regard to information system monitoring activities in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations; and g. Provides [Assignment: or ganization-defined information system monitoring information] to [Assignment: organization-defined personnel or roles] [Selection (one or more): as needed; [Assignment: organization-defined frequency]]. Supplemental Guidance: Information system monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at the information system boundary (i.e., part of perimeter defense and boundary protection). Internal monitoring includes the observation of events occurring within the information system. Organizations can monitor information systems, for example, by observing audit activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives may guide determination of the events. Information system monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, audit record monitoring software, network monitoring software). Strategic locations for monitoring devices include, for example, selected perimeter locations and near server farms supporting critical applications, with such devices typically being employed at the managed interfaces associated with controls SC-7 and AC-17. Einstein network monitoring devices from the Department of Homeland Security can also be included as monitoring devices. The granularity of monitoring information collected is based on organizational monitoring objectives and the capability of information systems to support such objectives. Specific types of transactions of interest include, for example, Hyper Text Transfer Protocol (HTTP) traffic that bypasses HTTP proxies. Information system monitoring is an integral part of organizational continuous monitoring and incident response programs. Output from system monitoring serves as input to continuous monitoring and incident response programs. A network connection is any connection with a device that communicates through a network (e.g., local area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Local, network, and remote connections can be either wired or wireless. Related controls: AC-3, AC-4, AC-8, AC-17, AU-2, AU-6, AU-7, AU-9, AU-12, CA-7, IR-4, PE-3, RA-5, SC-7, SC-26, SC-35, SI-3, SI-7. References: NIST Special Publications 800-61, 800-83, 800-92, 800-94, 800-137. | link | count: 025 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-4(12) | NIST_SP_800-53_R4_SI-4(12) | NIST SP 800-53 Rev. 4 SI-4 (12) | System and Information Integrity | Automated Alerts | Customer | n/a | The organization employs automated mechanisms to alert security personnel of the following inappropriate or unusual activities with security implications: [Assignment: organization-defined activities that trigger alerts]. | link | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-4(14) | NIST_SP_800-53_R4_SI-4(14) | NIST SP 800-53 Rev. 4 SI-4 (14) | System And Information Integrity | Wireless Intrusion Detection | Shared | n/a | The organization employs a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises/breaches to the information system. Supplemental Guidance: Wireless signals may radiate beyond the confines of organization- controlled facilities. Organizations proactively search for unauthorized wireless connections including the conduct of thorough scans for unauthorized wireless access points. Scans are not limited to those areas within facilities containing information systems, but also include areas outside of facilities as needed, to verify that unauthorized wireless access points are not connected to the systems. Related controls: AC-18, IA-3. | link | count: 001 Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-4(2) | NIST_SP_800-53_R4_SI-4(2) | NIST SP 800-53 Rev. 4 SI-4 (2) | System And Information Integrity | Automated Tools For Real-Time Analysis | Shared | n/a | The organization employs automated tools to support near real-time analysis of events. Supplemental Guidance: Automated tools include, for example, host-based, network-based, transport-based, or storage-based event monitoring tools or Security Information and Event Management (SIEM) technologies that provide real time analysis of alerts and/or notifications generated by organizational information systems. | link | count: 002 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-4(22) | NIST_SP_800-53_R4_SI-4(22) | NIST SP 800-53 Rev. 4 SI-4 (22) | System And Information Integrity | Unauthorized Network Services | Shared | n/a | The information system detects network services that have not been authorized or approved by [Assignment: organization-defined authorization or approval processes] and [Selection (one or more): audits; alerts [Assignment: organization-defined personnel or roles]]. Supplemental Guidance: Unauthorized or unapproved network services include, for example, services in service-oriented architectures that lack organizational verification or validation and therefore may be unreliable or serve as malicious rogues for valid services. Related controls: AC-6, CM-7, SA-5, SA-9. | link | count: 001 Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-4(24) | NIST_SP_800-53_R4_SI-4(24) | NIST SP 800-53 Rev. 4 SI-4 (24) | System And Information Integrity | Indicators Of Compromise | Shared | n/a | The information system discovers, collects, distributes, and uses indicators of compromise. Supplemental Guidance: Indicators of compromise (IOC) are forensic artifacts from intrusions that are identified on organizational information systems (at the host or network level). IOCs provide organizations with valuable information on objects or information systems that have been compromised. IOCs for the discovery of compromised hosts can include for example, the creation of registry key values. IOCs for network traffic include, for example, Universal Resource Locator (URL) or protocol elements that indicate malware command and control servers. The rapid distribution and adoption of IOCs can improve information security by reducing the time that information systems and organizations are vulnerable to the same exploit or attack. | link | count: 001 Discover any indicators of compromise (07b42fb5-027e-5a3c-4915-9d9ef3020ec7) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-4(4) | NIST_SP_800-53_R4_SI-4(4) | NIST SP 800-53 Rev. 4 SI-4 (4) | System And Information Integrity | Inbound And Outbound Communications Traffic | Shared | n/a | The information system monitors inbound and outbound communications traffic [Assignment: organization-defined frequency] for unusual or unauthorized activities or conditions. Supplemental Guidance: Unusual/unauthorized activities or conditions related to information system inbound and outbound communications traffic include, for example, internal traffic that indicates the presence of malicious code within organizational information systems or propagating among system components, the unauthorized exporting of information, or signaling to external information systems. Evidence of malicious code is used to identify potentially compromised information systems or information system components. | link | count: 004 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-4(5) | NIST_SP_800-53_R4_SI-4(5) | NIST SP 800-53 Rev. 4 SI-4 (5) | System And Information Integrity | System-Generated Alerts | Shared | n/a | The information system alerts [Assignment: organization-defined personnel or roles] when the following indications of compromise or potential compromise occur: [Assignment: organization- defined compromise indicators]. Supplemental Guidance: Alerts may be generated from a variety of sources, including, for example, audit records or inputs from malicious code protection mechanisms, intrusion detection or prevention mechanisms, or boundary protection devices such as firewalls, gateways, and routers. Alerts can be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. Organizational personnel on the notification list can include, for example, system administrators, mission/business owners, system owners, or information system security officers. Related controls: AU-5, PE-6. | link | count: 003 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-5 | NIST_SP_800-53_R4_SI-5 | NIST SP 800-53 Rev. 4 SI-5 | System And Information Integrity | Security Alerts, Advisories, And Directives | Shared | n/a | The organization: a. Receives information system security alerts, advisories, and directives from [Assignment: organization-defined external organizations] on an ongoing basis; b. Generates internal security alerts, advisories, and directives as deemed necessary; c. Disseminates security alerts, advisories, and directives to: [Selection (one or more): [Assignment: organization-defined personnel or roles]; [Assignment: organization-defined elements within the organization]; [Assignment: organization-defined external organizations]]; and d. Implements security directives in accordance with established time frames, or notifies the issuing organization of the degree of noncompliance. Supplemental Guidance: The United States Computer Emergency Readiness Team (US-CERT) generates security alerts and advisories to maintain situational awareness across the federal government. Security directives are issued by OMB or other designated organizations with the responsibility and authority to issue such directives. Compliance to security directives is essential due to the critical nature of many of these directives and the potential immediate adverse effects on organizational operations and assets, individuals, other organizations, and the Nation should the directives not be implemented in a timely manner. External organizations include, for example, external mission/business partners, supply chain partners, external service providers, and other peer/supporting organizations. Related control: SI-2. References: NIST Special Publication 800-40. | link | count: 004 Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Generate internal security alerts (171e377b-5224-4a97-1eaa-62a3b5231dac), Implement security directives (26d178a4-9261-6f04-a100-47ed85314c6e) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-5(1) | NIST_SP_800-53_R4_SI-5(1) | NIST SP 800-53 Rev. 4 SI-5 (1) | System And Information Integrity | Automated Alerts And Advisories | Shared | n/a | The organization employs automated mechanisms to make security alert and advisory information available throughout the organization. Supplemental Guidance: The significant number of changes to organizational information systems and the environments in which those systems operate requires the dissemination of security-related information to a variety of organizational entities that have a direct interest in the success of organizational missions and business functions. Based on the information provided by the security alerts and advisories, changes may be required at one or more of the three tiers related to the management of information security risk including the governance level, mission/business process/enterprise architecture level, and the information system level. | link | count: 001 Use automated mechanisms for security alerts (b8689b2e-4308-a58b-a0b4-6f3343a000df) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-6 | NIST_SP_800-53_R4_SI-6 | NIST SP 800-53 Rev. 4 SI-6 | System And Information Integrity | Security Function Verification | Shared | n/a | The information system: a. Verifies the correct operation of [Assignment: organization-defined security functions]; b. Performs this verification [Selection (one or more): [Assignment: organization-defined system transitional states]; upon command by user with appropriate privilege; [Assignment: organization-defined frequency]]; c. Notifies [Assignment: organization-defined personnel or roles] of failed security verification tests; and d. [Selection (one or more): shuts the information system down; restarts the information system; [Assignment: organization-defined alternative action(s)]] when anomalies are discovered. Supplemental Guidance: Transitional states for information systems include, for example, system startup, restart, shutdown, and abort. Notifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications such as lights. Related controls: CA-7, CM-6. References: None. | link | count: 004 Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Notify personnel of any failed security verification tests (18e9d748-73d4-0c96-55ab-b108bfbd5bc3), Perform security function verification at a defined frequency (f30edfad-4e1d-1eef-27ee-9292d6d89842), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-7 | NIST_SP_800-53_R4_SI-7 | NIST SP 800-53 Rev. 4 SI-7 | System And Information Integrity | Software, Firmware, And Information Integrity | Shared | n/a | The organization employs integrity verification tools to detect unauthorized changes to [Assignment: organization-defined software, firmware, and information]. Supplemental Guidance: Unauthorized changes to software, firmware, and information can occur due to errors or malicious activity (e.g., tampering). Software includes, for example, operating systems (with key internal components such as kernels, drivers), middleware, and applications. Firmware includes, for example, the Basic Input Output System (BIOS). Information includes metadata such as security attributes associated with information. State-of-the-practice integrity- checking mechanisms (e.g., parity checks, cyclical redundancy checks, cryptographic hashes) and associated tools can automatically monitor the integrity of information systems and hosted applications. Related controls: SA-12, SC-8, SC-13, SI-3. References: NIST Special Publications 800-147, 800-155. | link | count: 001 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-7(1) | NIST_SP_800-53_R4_SI-7(1) | NIST SP 800-53 Rev. 4 SI-7 (1) | System And Information Integrity | Integrity Checks | Shared | n/a | The information system performs an integrity check of [Assignment: organization-defined software, firmware, and information] [Selection (one or more): at startup; at [Assignment: organization-defined transitional states or security-relevant events]; [Assignment: organization- defined frequency]]. Supplemental Guidance: Security-relevant events include, for example, the identification of a new threat to which organizational information systems are susceptible, and the installation of new hardware, software, or firmware. Transitional states include, for example, system startup, restart, shutdown, and abort. | link | count: 002 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-7(14) | NIST_SP_800-53_R4_SI-7(14) | NIST SP 800-53 Rev. 4 SI-7 (14) | System And Information Integrity | Binary Or Machine Executable Code | Shared | n/a | The organization: (a) Prohibits the use of binary or machine-executable code from sources with limited or no warranty and without the provision of source code; and (b) Provides exceptions to the source code requirement only for compelling mission/operational requirements and with the approval of the authorizing official. Supplemental Guidance: This control enhancement applies to all sources of binary or machine- executable code including, for example, commercial software/firmware and open source software. Organizations assess software products without accompanying source code from sources with limited or no warranty for potential security impacts. The assessments address the fact that these types of software products may be very difficult to review, repair, or extend, given that organizations, in most cases, do not have access to the original source code, and there may be no owners who could make such repairs on behalf of organizations. Related control: SA-5. | link | count: 001 Prohibit binary/machine-executable code (8e920169-739d-40b5-3f99-c4d855327bb2) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R4 | SI-7(5) | NIST_SP_800-53_R4_SI-7(5) | NIST SP 800-53 Rev. 4 SI-7 (5) | System And Information Integrity | Automated Response To Integrity Violations | Shared | n/a | The information system automatically [Selection (one or more): shuts the information system down; restarts the information system; implements [Assignment: organization-defined security safeguards]] when integrity violations are discovered. Supplemental Guidance: Organizations may define different integrity checking and anomaly responses: (i) by type of information (e.g., firmware, software, user data); (ii) by specific information (e.g., boot firmware, boot firmware for a specific types of machines); or (iii) a combination of both. Automatic implementation of specific safeguards within organizational information systems includes, for example, reversing the changes, halting the information system, or triggering audit alerts when unauthorized modifications to critical security files occur. | link | count: 001 Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4) |
Regulatory Compliance | NIST SP 800-53 Rev. 4 (cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f) |
| NIST_SP_800-53_R5 | AC-1 | NIST_SP_800-53_R5_AC-1 | NIST SP 800-53 Rev. 5 AC-1 | Access Control | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] access control policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the access control policy and the associated access controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the access control policy and procedures; and c. Review and update the current access control: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-10 | NIST_SP_800-53_R5_AC-10 | NIST SP 800-53 Rev. 5 AC-10 | Access Control | Concurrent Session Control | Shared | n/a | Limit the number of concurrent sessions for each [Assignment: organization-defined account and/or account type] to [Assignment: organization-defined number]. | link | count: 001 Define and enforce the limit of concurrent sessions (d8350d4c-9314-400b-288f-20ddfce04fbd) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-12 | NIST_SP_800-53_R5_AC-12 | NIST SP 800-53 Rev. 5 AC-12 | Access Control | Session Termination | Shared | n/a | Automatically terminate a user session after [Assignment: organization-defined conditions or trigger events requiring session disconnect]. | link | count: 001 Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-12(1) | NIST_SP_800-53_R5_AC-12(1) | NIST SP 800-53 Rev. 5 AC-12 (1) | Access Control | User-initiated Logouts | Shared | n/a | Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to [Assignment: organization-defined information resources]. | link | count: 002 Display an explicit logout message (0471c6b7-1588-701c-2713-1fade73b75f6), Provide the logout capability (db580551-0b3c-4ea1-8a4c-4cdb5feb340f) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-14 | NIST_SP_800-53_R5_AC-14 | NIST SP 800-53 Rev. 5 AC-14 | Access Control | Permitted Actions Without Identification or Authentication | Shared | n/a | a. Identify [Assignment: organization-defined user actions] that can be performed on the system without identification or authentication consistent with organizational mission and business functions; and b. Document and provide supporting rationale in the security plan for the system, user actions not requiring identification or authentication. | link | count: 001 Identify actions allowed without authentication (92a7591f-73b3-1173-a09c-a08882d84c70) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-16 | NIST_SP_800-53_R5_AC-16 | NIST SP 800-53 Rev. 5 AC-16 | Access Control | Security and Privacy Attributes | Customer | n/a | a. Provide the means to associate [Assignment: organization-defined types of security and privacy attributes] with [Assignment: organization-defined security and privacy attribute values] for information in storage, in process, and/or in transmission; b. Ensure that the attribute associations are made and retained with the information; c. Establish the following permitted security and privacy attributes from the attributes defined in [AC-16a](#ac-16_smt.a) for [Assignment: organization-defined systems]: [Assignment: organization-defined security and privacy attributes]; d. Determine the following permitted attribute values or ranges for each of the established attributes: [Assignment: organization-defined attribute values or ranges for established attributes]; e. Audit changes to attributes; and f. Review [Assignment: organization-defined security and privacy attributes] for applicability [Assignment: organization-defined frequency]. | link | count: 002 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-17 | NIST_SP_800-53_R5_AC-17 | NIST SP 800-53 Rev. 5 AC-17 | Access Control | Remote Access | Shared | n/a | a. Establish and document usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and b. Authorize each type of remote access to the system prior to allowing such connections. | link | count: 041 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-17(1) | NIST_SP_800-53_R5_AC-17(1) | NIST SP 800-53 Rev. 5 AC-17 (1) | Access Control | Monitoring and Control | Shared | n/a | Employ automated mechanisms to monitor and control remote access methods. | link | count: 037 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, App Configuration, App Platform, App Service, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Guest Configuration, Internet of Things, Key Vault, Machine Learning, Regulatory Compliance, Search, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-17(2) | NIST_SP_800-53_R5_AC-17(2) | NIST SP 800-53 Rev. 5 AC-17 (2) | Access Control | Protection of Confidentiality and Integrity Using Encryption | Shared | n/a | Implement cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions. | link | count: 002 Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-17(3) | NIST_SP_800-53_R5_AC-17(3) | NIST SP 800-53 Rev. 5 AC-17 (3) | Access Control | Managed Access Control Points | Shared | n/a | Route remote accesses through authorized and managed network access control points. | link | count: 001 Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-17(4) | NIST_SP_800-53_R5_AC-17(4) | NIST SP 800-53 Rev. 5 AC-17 (4) | Access Control | Privileged Commands and Access | Shared | n/a | (a) Authorize the execution of privileged commands and access to security-relevant information via remote access only in a format that provides assessable evidence and for the following needs: [Assignment: organization-defined needs]; and (b) Document the rationale for remote access in the security plan for the system. | link | count: 005 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Authorize remote access to privileged commands (01c387ea-383d-4ca9-295a-977fab516b03), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-17(9) | NIST_SP_800-53_R5_AC-17(9) | NIST SP 800-53 Rev. 5 AC-17 (9) | Access Control | Disconnect or Disable Access | Shared | n/a | Provide the capability to disconnect or disable remote access to the system within [Assignment: organization-defined time period]. | link | count: 001 Provide capability to disconnect or disable remote access (4edaca8c-0912-1ac5-9eaa-6a1057740fae) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-18 | NIST_SP_800-53_R5_AC-18 | NIST SP 800-53 Rev. 5 AC-18 | Access Control | Wireless Access | Shared | n/a | a. Establish configuration requirements, connection requirements, and implementation guidance for each type of wireless access; and b. Authorize each type of wireless access to the system prior to allowing such connections. | link | count: 002 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-18(1) | NIST_SP_800-53_R5_AC-18(1) | NIST SP 800-53 Rev. 5 AC-18 (1) | Access Control | Authentication and Encryption | Shared | n/a | Protect wireless access to the system using authentication of [Selection (OneOrMore): users;devices] and encryption. | link | count: 003 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-19 | NIST_SP_800-53_R5_AC-19 | NIST SP 800-53 Rev. 5 AC-19 | Access Control | Access Control for Mobile Devices | Shared | n/a | a. Establish configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices, to include when such devices are outside of controlled areas; and b. Authorize the connection of mobile devices to organizational systems. | link | count: 001 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-19(5) | NIST_SP_800-53_R5_AC-19(5) | NIST SP 800-53 Rev. 5 AC-19 (5) | Access Control | Full Device or Container-based Encryption | Shared | n/a | Employ [Selection: full-device encryption;container-based encryption] to protect the confidentiality and integrity of information on [Assignment: organization-defined mobile devices]. | link | count: 002 Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2 | NIST_SP_800-53_R5_AC-2 | NIST SP 800-53 Rev. 5 AC-2 | Access Control | Account Management | Shared | n/a | a. Define and document the types of accounts allowed and specifically prohibited for use within the system; b. Assign account managers; c. Require [Assignment: organization-defined prerequisites and criteria] for group and role membership; d. Specify: 1. Authorized users of the system; 2. Group and role membership; and 3. Access authorizations (i.e., privileges) and [Assignment: organization-defined attributes (as required)] for each account; e. Require approvals by [Assignment: organization-defined personnel or roles] for requests to create accounts; f. Create, enable, modify, disable, and remove accounts in accordance with [Assignment: organization-defined policy, procedures, prerequisites, and criteria]; g. Monitor the use of accounts; h. Notify account managers and [Assignment: organization-defined personnel or roles] within: 1. [Assignment: organization-defined time period] when accounts are no longer required; 2. [Assignment: organization-defined time period] when users are terminated or transferred; and 3. [Assignment: organization-defined time period] when system usage or need-to-know changes for an individual; i. Authorize access to the system based on: 1. A valid access authorization; 2. Intended system usage; and 3. [Assignment: organization-defined attributes (as required)]; j. Review accounts for compliance with account management requirements [Assignment: organization-defined frequency]; k. Establish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group; and l. Align account management processes with personnel termination and transfer processes. | link | count: 025 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Notify Account Managers of customer controlled accounts (4b8fd5da-609b-33bf-9724-1c946285a14c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, General, Regulatory Compliance, Security Center, Service Fabric, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2(1) | NIST_SP_800-53_R5_AC-2(1) | NIST SP 800-53 Rev. 5 AC-2 (1) | Access Control | Automated System Account Management | Shared | n/a | Support the management of system accounts using [Assignment: organization-defined automated mechanisms]. | link | count: 007 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2(11) | NIST_SP_800-53_R5_AC-2(11) | NIST SP 800-53 Rev. 5 AC-2 (11) | Access Control | Usage Conditions | Shared | n/a | Enforce [Assignment: organization-defined circumstances and/or usage conditions] for [Assignment: organization-defined system accounts]. | link | count: 001 Enforce appropriate usage of all accounts (fd81a1b3-2d7a-107c-507e-29b87d040c19) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2(12) | NIST_SP_800-53_R5_AC-2(12) | NIST SP 800-53 Rev. 5 AC-2 (12) | Access Control | Account Monitoring for Atypical Usage | Shared | n/a | (a) Monitor system accounts for [Assignment: organization-defined atypical usage]; and (b) Report atypical usage of system accounts to [Assignment: organization-defined personnel or roles]. | link | count: 013 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Report atypical behavior of user accounts (e4054c0e-1184-09e6-4c5e-701e0bc90f81) |
Kubernetes, Regulatory Compliance, Security Center, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2(13) | NIST_SP_800-53_R5_AC-2(13) | NIST SP 800-53 Rev. 5 AC-2 (13) | Access Control | Disable Accounts for High-risk Individuals | Shared | n/a | Disable accounts of individuals within [Assignment: organization-defined time period] of discovery of [Assignment: organization-defined significant risks]. | link | count: 001 Disable user accounts posing a significant risk (22c16ae4-19d0-29cb-422f-cb44061180ee) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2(3) | NIST_SP_800-53_R5_AC-2(3) | NIST SP 800-53 Rev. 5 AC-2 (3) | Access Control | Disable Accounts | Shared | n/a | Disable accounts within [Assignment: organization-defined time period] when the accounts: (a) Have expired; (b) Are no longer associated with a user or individual; (c) Are in violation of organizational policy; or (d) Have been inactive for [Assignment: organization-defined time period]. | link | count: 002 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2(4) | NIST_SP_800-53_R5_AC-2(4) | NIST SP 800-53 Rev. 5 AC-2 (4) | Access Control | Automated Audit Actions | Shared | n/a | Automatically audit account creation, modification, enabling, disabling, and removal actions. | link | count: 005 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2(5) | NIST_SP_800-53_R5_AC-2(5) | NIST SP 800-53 Rev. 5 AC-2 (5) | Access Control | Inactivity Logout | Shared | n/a | Require that users log out when [Assignment: organization-defined time period of expected inactivity or description of when to log out]. | link | count: 001 Define and enforce inactivity log policy (2af4640d-11a6-a64b-5ceb-a468f4341c0c) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2(7) | NIST_SP_800-53_R5_AC-2(7) | NIST SP 800-53 Rev. 5 AC-2 (7) | Access Control | Privileged User Accounts | Shared | n/a | (a) Establish and administer privileged user accounts in accordance with [Selection: a role-based access scheme;an attribute-based access scheme] ; (b) Monitor privileged role or attribute assignments; (c) Monitor changes to roles or attributes; and (d) Revoke access when privileged role or attribute assignments are no longer appropriate. | link | count: 010 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Azure Ai Services, General, Regulatory Compliance, Service Fabric, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-2(9) | NIST_SP_800-53_R5_AC-2(9) | NIST SP 800-53 Rev. 5 AC-2 (9) | Access Control | Restrictions on Use of Shared and Group Accounts | Shared | n/a | Only permit the use of shared and group accounts that meet [Assignment: organization-defined conditions for establishing shared and group accounts]. | link | count: 001 Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-20 | NIST_SP_800-53_R5_AC-20 | NIST SP 800-53 Rev. 5 AC-20 | Access Control | Use of External Systems | Shared | n/a | a. [Selection (OneOrMore): Establish [Assignment: organization-defined terms and conditions] ;Identify [Assignment: organization-defined controls asserted to be implemented on external systems] ] , consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to: 1. Access the system from external systems; and 2. Process, store, or transmit organization-controlled information using external systems; or b. Prohibit the use of [Assignment: organizationally-defined types of external systems]. | link | count: 002 Establish terms and conditions for accessing resources (3c93dba1-84fd-57de-33c7-ef0400a08134), Establish terms and conditions for processing resources (5715bf33-a5bd-1084-4e19-bc3c83ec1c35) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-20(1) | NIST_SP_800-53_R5_AC-20(1) | NIST SP 800-53 Rev. 5 AC-20 (1) | Access Control | Limits on Authorized Use | Shared | n/a | Permit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after: (a) Verification of the implementation of controls on the external system as specified in the organization???s security and privacy policies and security and privacy plans; or (b) Retention of approved system connection or processing agreements with the organizational entity hosting the external system. | link | count: 001 Verify security controls for external information systems (dc7ec756-221c-33c8-0afe-c48e10e42321) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-20(2) | NIST_SP_800-53_R5_AC-20(2) | NIST SP 800-53 Rev. 5 AC-20 (2) | Access Control | Portable Storage Devices ??? Restricted Use | Shared | n/a | Restrict the use of organization-controlled portable storage devices by authorized individuals on external systems using [Assignment: organization-defined restrictions]. | link | count: 003 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-21 | NIST_SP_800-53_R5_AC-21 | NIST SP 800-53 Rev. 5 AC-21 | Access Control | Information Sharing | Shared | n/a | a. Enable authorized users to determine whether access authorizations assigned to a sharing partner match the information???s access and use restrictions for [Assignment: organization-defined information sharing circumstances where user discretion is required]; and b. Employ [Assignment: organization-defined automated mechanisms or manual processes] to assist users in making information sharing and collaboration decisions. | link | count: 002 Automate information sharing decisions (e54901fe-42c2-7f3b-3c5f-327aa5320a69), Facilitate information sharing (a44c9fba-43f8-4b7b-7ee6-db52c96b4366) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-22 | NIST_SP_800-53_R5_AC-22 | NIST SP 800-53 Rev. 5 AC-22 | Access Control | Publicly Accessible Content | Shared | n/a | a. Designate individuals authorized to make information publicly accessible; b. Train authorized individuals to ensure that publicly accessible information does not contain nonpublic information; c. Review the proposed content of information prior to posting onto the publicly accessible system to ensure that nonpublic information is not included; and d. Review the content on the publicly accessible system for nonpublic information [Assignment: organization-defined frequency] and remove such information, if discovered. | link | count: 004 Designate authorized personnel to post publicly accessible information (b4512986-80f5-1656-0c58-08866bd2673a), Review content prior to posting publicly accessible information (9e3c505e-7aeb-2096-3417-b132242731fc), Review publicly accessible content for nonpublic information (b5244f81-6cab-3188-2412-179162294996), Train personnel on disclosure of nonpublic information (97f0d974-1486-01e2-2088-b888f46c0589) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-3 | NIST_SP_800-53_R5_AC-3 | NIST SP 800-53 Rev. 5 AC-3 | Access Control | Access Enforcement | Shared | n/a | Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. | link | count: 021 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
App Service, Azure Ai Services, Compute, Guest Configuration, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-3(7) | NIST_SP_800-53_R5_AC-3(7) | NIST SP 800-53 Rev. 5 AC-3 (7) | Access Control | Role-based Access Control | Customer | n/a | Enforce a role-based access control policy over defined subjects and objects and control access based upon [Assignment: organization-defined roles and users authorized to assume such roles]. | link | count: 001 Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-4 | NIST_SP_800-53_R5_AC-4 | NIST SP 800-53 Rev. 5 AC-4 | Access Control | Information Flow Enforcement | Shared | n/a | Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on [Assignment: organization-defined information flow control policies]. | link | count: 053 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API for FHIR, API Management, App Configuration, App Service, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Regulatory Compliance, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-4(21) | NIST_SP_800-53_R5_AC-4(21) | NIST SP 800-53 Rev. 5 AC-4 (21) | Access Control | Physical or Logical Separation of Information Flows | Shared | n/a | Separate information flows logically or physically using [Assignment: organization-defined mechanisms and/or techniques] to accomplish [Assignment: organization-defined required separations by types of information]. | link | count: 004 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-4(3) | NIST_SP_800-53_R5_AC-4(3) | NIST SP 800-53 Rev. 5 AC-4 (3) | Access Control | Dynamic Information Flow Control | Customer | n/a | Enforce [Assignment: organization-defined information flow control policies]. | link | count: 002 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-4(8) | NIST_SP_800-53_R5_AC-4(8) | NIST SP 800-53 Rev. 5 AC-4 (8) | Access Control | Security and Privacy Policy Filters | Shared | n/a | (a) Enforce information flow control using [Assignment: organization-defined security or privacy policy filters] as a basis for flow control decisions for [Assignment: organization-defined information flows]; and (b) [Selection (OneOrMore): Block;Strip;Modify;Quarantine] data after a filter processing failure in accordance with [Assignment: organization-defined security or privacy policy]. | link | count: 001 Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-5 | NIST_SP_800-53_R5_AC-5 | NIST SP 800-53 Rev. 5 AC-5 | Access Control | Separation of Duties | Shared | n/a | a. Identify and document [Assignment: organization-defined duties of individuals requiring separation]; and b. Define system access authorizations to support separation of duties. | link | count: 004 Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-6 | NIST_SP_800-53_R5_AC-6 | NIST SP 800-53 Rev. 5 AC-6 | Access Control | Least Privilege | Shared | n/a | Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks. | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f) |
General, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-6(1) | NIST_SP_800-53_R5_AC-6(1) | NIST SP 800-53 Rev. 5 AC-6 (1) | Access Control | Authorize Access to Security Functions | Shared | n/a | Authorize access for [Assignment: organization-defined individuals or roles] to: (a) [Assignment: organization-defined security functions (deployed in hardware, software, and firmware)]; and (b) [Assignment: organization-defined security-relevant information]. | link | count: 003 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-6(5) | NIST_SP_800-53_R5_AC-6(5) | NIST SP 800-53 Rev. 5 AC-6 (5) | Access Control | Privileged Accounts | Shared | n/a | Restrict privileged accounts on the system to [Assignment: organization-defined personnel or roles]. | link | count: 001 Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-6(7) | NIST_SP_800-53_R5_AC-6(7) | NIST SP 800-53 Rev. 5 AC-6 (7) | Access Control | Review of User Privileges | Shared | n/a | (a) Review [Assignment: organization-defined frequency] the privileges assigned to [Assignment: organization-defined roles or classes of users] to validate the need for such privileges; and (b) Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs. | link | count: 004 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
General, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-6(8) | NIST_SP_800-53_R5_AC-6(8) | NIST SP 800-53 Rev. 5 AC-6 (8) | Access Control | Privilege Levels for Code Execution | Shared | n/a | Prevent the following software from executing at higher privilege levels than users executing the software: [Assignment: organization-defined software]. | link | count: 001 Enforce software execution privileges (68d2e478-3b19-23eb-1357-31b296547457) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-6(9) | NIST_SP_800-53_R5_AC-6(9) | NIST SP 800-53 Rev. 5 AC-6 (9) | Access Control | Log Use of Privileged Functions | Shared | n/a | Log the execution of privileged functions. | link | count: 006 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AC-7 | NIST_SP_800-53_R5_AC-7 | NIST SP 800-53 Rev. 5 AC-7 | Access Control | Unsuccessful Logon Attempts | Shared | n/a | a. Enforce a limit of [Assignment: organization-defined number] consecutive invalid logon attempts by a user during a [Assignment: organization-defined time period]; and b. Automatically [Selection (OneOrMore): lock the account or node for an [Assignment: organization-defined time period] ;lock the account or node until released by an administrator;delay next logon prompt per [Assignment: organization-defined delay algorithm] ;notify system administrator;take other [Assignment: organization-defined action] ] when the maximum number of unsuccessful attempts is exceeded. | link | count: 001 Enforce a limit of consecutive failed login attempts (b4409bff-2287-8407-05fd-c73175a68302) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AT-1 | NIST_SP_800-53_R5_AT-1 | NIST SP 800-53 Rev. 5 AT-1 | Awareness and Training | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] awareness and training policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the awareness and training policy and the associated awareness and training controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the awareness and training policy and procedures; and c. Review and update the current awareness and training: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 002 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AT-2 | NIST_SP_800-53_R5_AT-2 | NIST SP 800-53 Rev. 5 AT-2 | Awareness and Training | Literacy Training and Awareness | Shared | n/a | a. Provide security and privacy literacy training to system users (including managers, senior executives, and contractors): 1. As part of initial training for new users and [Assignment: organization-defined frequency] thereafter; and 2. When required by system changes or following [Assignment: organization-defined events]; b. Employ the following techniques to increase the security and privacy awareness of system users [Assignment: organization-defined awareness techniques]; c. Update literacy training and awareness content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and d. Incorporate lessons learned from internal or external security incidents or breaches into literacy training and awareness techniques. | link | count: 003 Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AT-2(2) | NIST_SP_800-53_R5_AT-2(2) | NIST SP 800-53 Rev. 5 AT-2 (2) | Awareness and Training | Insider Threat | Shared | n/a | Provide literacy training on recognizing and reporting potential indicators of insider threat. | link | count: 001 Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AT-3 | NIST_SP_800-53_R5_AT-3 | NIST SP 800-53 Rev. 5 AT-3 | Awareness and Training | Role-based Training | Shared | n/a | a. Provide role-based security and privacy training to personnel with the following roles and responsibilities: [Assignment: organization-defined roles and responsibilities]: 1. Before authorizing access to the system, information, or performing assigned duties, and [Assignment: organization-defined frequency] thereafter; and 2. When required by system changes; b. Update role-based training content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and c. Incorporate lessons learned from internal or external security incidents or breaches into role-based training. | link | count: 003 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AT-3(3) | NIST_SP_800-53_R5_AT-3(3) | NIST SP 800-53 Rev. 5 AT-3 (3) | Awareness and Training | Practical Exercises | Shared | n/a | Provide practical exercises in security and privacy training that reinforce training objectives. | link | count: 001 Provide role-based practical exercises (d041726f-00e0-41ca-368c-b1a122066482) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AT-4 | NIST_SP_800-53_R5_AT-4 | NIST SP 800-53 Rev. 5 AT-4 | Awareness and Training | Training Records | Shared | n/a | a. Document and monitor information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training; and b. Retain individual training records for [Assignment: organization-defined time period]. | link | count: 003 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Monitor security and privacy training completion (82bd024a-5c99-05d6-96ff-01f539676a1a), Retain training records (3153d9c0-2584-14d3-362d-578b01358aeb) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-1 | NIST_SP_800-53_R5_AU-1 | NIST SP 800-53 Rev. 5 AU-1 | Audit and Accountability | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] audit and accountability policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the audit and accountability policy and the associated audit and accountability controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the audit and accountability policy and procedures; and c. Review and update the current audit and accountability: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 004 Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-10 | NIST_SP_800-53_R5_AU-10 | NIST SP 800-53 Rev. 5 AU-10 | Audit and Accountability | Non-repudiation | Shared | n/a | Provide irrefutable evidence that an individual (or process acting on behalf of an individual) has performed [Assignment: organization-defined actions to be covered by non-repudiation]. | link | count: 001 Establish electronic signature and certificate requirements (6f3866e8-6e12-69cf-788c-809d426094a1) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-11 | NIST_SP_800-53_R5_AU-11 | NIST SP 800-53 Rev. 5 AU-11 | Audit and Accountability | Audit Record Retention | Shared | n/a | Retain audit records for [Assignment: organization-defined time period consistent with records retention policy] to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements. | link | count: 004 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
Regulatory Compliance, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-12 | NIST_SP_800-53_R5_AU-12 | NIST SP 800-53 Rev. 5 AU-12 | Audit and Accountability | Audit Record Generation | Shared | n/a | a. Provide audit record generation capability for the event types the system is capable of auditing as defined in [AU-2a](#au-2_smt.a) on [Assignment: organization-defined system components]; b. Allow [Assignment: organization-defined personnel or roles] to select the event types that are to be logged by specific components of the system; and c. Generate audit records for the event types defined in [AU-2c](#au-2_smt.c) that include the audit record content defined in [AU-3](#au-3). | link | count: 037 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-12(1) | NIST_SP_800-53_R5_AU-12(1) | NIST SP 800-53 Rev. 5 AU-12 (1) | Audit and Accountability | System-wide and Time-correlated Audit Trail | Shared | n/a | Compile audit records from [Assignment: organization-defined system components] into a system-wide (logical or physical) audit trail that is time-correlated to within [Assignment: organization-defined level of tolerance for the relationship between time stamps of individual records in the audit trail]. | link | count: 034 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Compile Audit records into system wide audit (214ea241-010d-8926-44cc-b90a96d52adc), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-12(3) | NIST_SP_800-53_R5_AU-12(3) | NIST SP 800-53 Rev. 5 AU-12 (3) | Audit and Accountability | Changes by Authorized Individuals | Shared | n/a | Provide and implement the capability for [Assignment: organization-defined individuals or roles] to change the logging to be performed on [Assignment: organization-defined system components] based on [Assignment: organization-defined selectable event criteria] within [Assignment: organization-defined time thresholds]. | link | count: 001 Provide the capability to extend or limit auditing on customer-deployed resources (d200f199-69f4-95a6-90b0-37ff0cf1040c) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-2 | NIST_SP_800-53_R5_AU-2 | NIST SP 800-53 Rev. 5 AU-2 | Audit and Accountability | Event Logging | Shared | n/a | a. Identify the types of events that the system is capable of logging in support of the audit function: [Assignment: organization-defined event types that the system is capable of logging]; b. Coordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged; c. Specify the following event types for logging within the system: [Assignment: organization-defined event types (subset of the event types defined in [AU-2a.](#au-2_smt.a)) along with the frequency of (or situation requiring) logging for each identified event type]; d. Provide a rationale for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; and e. Review and update the event types selected for logging [Assignment: organization-defined frequency]. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-3 | NIST_SP_800-53_R5_AU-3 | NIST SP 800-53 Rev. 5 AU-3 | Audit and Accountability | Content of Audit Records | Shared | n/a | Ensure that audit records contain information that establishes the following: a. What type of event occurred; b. When the event occurred; c. Where the event occurred; d. Source of the event; e. Outcome of the event; and f. Identity of any individuals, subjects, or objects/entities associated with the event. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-3(1) | NIST_SP_800-53_R5_AU-3(1) | NIST SP 800-53 Rev. 5 AU-3 (1) | Audit and Accountability | Additional Audit Information | Shared | n/a | Generate audit records containing the following additional information: [Assignment: organization-defined additional information]. | link | count: 001 Configure Azure Audit capabilities (a3e98638-51d4-4e28-910a-60e98c1a756f) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-4 | NIST_SP_800-53_R5_AU-4 | NIST SP 800-53 Rev. 5 AU-4 | Audit and Accountability | Audit Log Storage Capacity | Shared | n/a | Allocate audit log storage capacity to accommodate [Assignment: organization-defined audit log retention requirements]. | link | count: 001 Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-5 | NIST_SP_800-53_R5_AU-5 | NIST SP 800-53 Rev. 5 AU-5 | Audit and Accountability | Response to Audit Logging Process Failures | Shared | n/a | a. Alert [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period] in the event of an audit logging process failure; and b. Take the following additional actions: [Assignment: organization-defined additional actions]. | link | count: 001 Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-5(2) | NIST_SP_800-53_R5_AU-5(2) | NIST SP 800-53 Rev. 5 AU-5 (2) | Audit and Accountability | Real-time Alerts | Shared | n/a | Provide an alert within [Assignment: organization-defined real-time period] to [Assignment: organization-defined personnel, roles, and/or locations] when the following audit failure events occur: [Assignment: organization-defined audit logging failure events requiring real-time alerts]. | link | count: 001 Provide real-time alerts for audit event failures (0f4fa857-079d-9d3d-5c49-21f616189e03) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-6 | NIST_SP_800-53_R5_AU-6 | NIST SP 800-53 Rev. 5 AU-6 | Audit and Accountability | Audit Record Review, Analysis, and Reporting | Shared | n/a | a. Review and analyze system audit records [Assignment: organization-defined frequency] for indications of [Assignment: organization-defined inappropriate or unusual activity] and the potential impact of the inappropriate or unusual activity; b. Report findings to [Assignment: organization-defined personnel or roles]; and c. Adjust the level of audit record review, analysis, and reporting within the system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information. | link | count: 025 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-6(1) | NIST_SP_800-53_R5_AU-6(1) | NIST SP 800-53 Rev. 5 AU-6 (1) | Audit and Accountability | Automated Process Integration | Shared | n/a | Integrate audit record review, analysis, and reporting processes using [Assignment: organization-defined automated mechanisms]. | link | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-6(3) | NIST_SP_800-53_R5_AU-6(3) | NIST SP 800-53 Rev. 5 AU-6 (3) | Audit and Accountability | Correlate Audit Record Repositories | Shared | n/a | Analyze and correlate audit records across different repositories to gain organization-wide situational awareness. | link | count: 002 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-6(4) | NIST_SP_800-53_R5_AU-6(4) | NIST SP 800-53 Rev. 5 AU-6 (4) | Audit and Accountability | Central Review and Analysis | Shared | n/a | Provide and implement the capability to centrally review and analyze audit records from multiple components within the system. | link | count: 033 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-6(5) | NIST_SP_800-53_R5_AU-6(5) | NIST SP 800-53 Rev. 5 AU-6 (5) | Audit and Accountability | Integrated Analysis of Audit Records | Shared | n/a | Integrate analysis of audit records with analysis of [Selection (OneOrMore): vulnerability scanning information;performance data;system monitoring information; [Assignment: organization-defined data/information collected from other sources] ] to further enhance the ability to identify inappropriate or unusual activity. | link | count: 034 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Integrate Audit record analysis (85335602-93f5-7730-830b-d43426fd51fa), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus, SQL, Stream Analytics | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-6(7) | NIST_SP_800-53_R5_AU-6(7) | NIST SP 800-53 Rev. 5 AU-6 (7) | Audit and Accountability | Permitted Actions | Shared | n/a | Specify the permitted actions for each [Selection (OneOrMore): system process;role;user] associated with the review, analysis, and reporting of audit record information. | link | count: 001 Specify permitted actions associated with customer audit information (3eecf628-a1c8-1b48-1b5c-7ca781e97970) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-7 | NIST_SP_800-53_R5_AU-7 | NIST SP 800-53 Rev. 5 AU-7 | Audit and Accountability | Audit Record Reduction and Report Generation | Shared | n/a | Provide and implement an audit record reduction and report generation capability that: a. Supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents; and b. Does not alter the original content or time ordering of audit records. | link | count: 002 Ensure audit records are not altered (27ce30dd-3d56-8b54-6144-e26d9a37a541), Provide audit review, analysis, and reporting capability (44f8a42d-739f-8030-89a8-4c2d5b3f6af3) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-7(1) | NIST_SP_800-53_R5_AU-7(1) | NIST SP 800-53 Rev. 5 AU-7 (1) | Audit and Accountability | Automatic Processing | Shared | n/a | Provide and implement the capability to process, sort, and search audit records for events of interest based on the following content: [Assignment: organization-defined fields within audit records]. | link | count: 001 Provide capability to process customer-controlled audit records (21633c09-804e-7fcd-78e3-635c6bfe2be7) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-8 | NIST_SP_800-53_R5_AU-8 | NIST SP 800-53 Rev. 5 AU-8 | Audit and Accountability | Time Stamps | Shared | n/a | a. Use internal system clocks to generate time stamps for audit records; and b. Record time stamps for audit records that meet [Assignment: organization-defined granularity of time measurement] and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or that include the local time offset as part of the time stamp. | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-9 | NIST_SP_800-53_R5_AU-9 | NIST SP 800-53 Rev. 5 AU-9 | Audit and Accountability | Protection of Audit Information | Shared | n/a | a. Protect audit information and audit logging tools from unauthorized access, modification, and deletion; and b. Alert [Assignment: organization-defined personnel or roles] upon detection of unauthorized access, modification, or deletion of audit information. | link | count: 002 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-9(2) | NIST_SP_800-53_R5_AU-9(2) | NIST SP 800-53 Rev. 5 AU-9 (2) | Audit and Accountability | Store on Separate Physical Systems or Components | Shared | n/a | Store audit records [Assignment: organization-defined frequency] in a repository that is part of a physically different system or system component than the system or component being audited. | link | count: 001 Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-9(3) | NIST_SP_800-53_R5_AU-9(3) | NIST SP 800-53 Rev. 5 AU-9 (3) | Audit and Accountability | Cryptographic Protection | Shared | n/a | Implement cryptographic mechanisms to protect the integrity of audit information and audit tools. | link | count: 001 Maintain integrity of audit system (c0559109-6a27-a217-6821-5a6d44f92897) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | AU-9(4) | NIST_SP_800-53_R5_AU-9(4) | NIST SP 800-53 Rev. 5 AU-9 (4) | Audit and Accountability | Access by Subset of Privileged Users | Shared | n/a | Authorize access to management of audit logging functionality to only [Assignment: organization-defined subset of privileged users or roles]. | link | count: 001 Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-1 | NIST_SP_800-53_R5_CA-1 | NIST SP 800-53 Rev. 5 CA-1 | Assessment, Authorization, and Monitoring | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] assessment, authorization, and monitoring policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and the associated assessment, authorization, and monitoring controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures; and c. Review and update the current assessment, authorization, and monitoring: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-2 | NIST_SP_800-53_R5_CA-2 | NIST SP 800-53 Rev. 5 CA-2 | Assessment, Authorization, and Monitoring | Control Assessments | Shared | n/a | a. Select the appropriate assessor or assessment team for the type of assessment to be conducted; b. Develop a control assessment plan that describes the scope of the assessment including: 1. Controls and control enhancements under assessment; 2. Assessment procedures to be used to determine control effectiveness; and 3. Assessment environment, assessment team, and assessment roles and responsibilities; c. Ensure the control assessment plan is reviewed and approved by the authorizing official or designated representative prior to conducting the assessment; d. Assess the controls in the system and its environment of operation [Assignment: organization-defined frequency] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security and privacy requirements; e. Produce a control assessment report that document the results of the assessment; and f. Provide the results of the control assessment to [Assignment: organization-defined individuals or roles]. | link | count: 004 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-2(1) | NIST_SP_800-53_R5_CA-2(1) | NIST SP 800-53 Rev. 5 CA-2 (1) | Assessment, Authorization, and Monitoring | Independent Assessors | Shared | n/a | Employ independent assessors or assessment teams to conduct control assessments. | link | count: 001 Employ independent assessors to conduct security control assessments (b65c5d8e-9043-9612-2c17-65f231d763bb) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-2(2) | NIST_SP_800-53_R5_CA-2(2) | NIST SP 800-53 Rev. 5 CA-2 (2) | Assessment, Authorization, and Monitoring | Specialized Assessments | Shared | n/a | Include as part of control assessments, [Assignment: organization-defined frequency], [Selection: announced;unannounced] , [Selection (OneOrMore): in-depth monitoring;security instrumentation;automated security test cases;vulnerability scanning;malicious user testing;insider threat assessment;performance and load testing;data leakage or data loss assessment; [Assignment: organization-defined other forms of assessment] ] . | link | count: 001 Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-2(3) | NIST_SP_800-53_R5_CA-2(3) | NIST SP 800-53 Rev. 5 CA-2 (3) | Assessment, Authorization, and Monitoring | Leveraging Results from External Organizations | Shared | n/a | Leverage the results of control assessments performed by [Assignment: organization-defined external organization] on [Assignment: organization-defined system] when the assessment meets [Assignment: organization-defined requirements]. | link | count: 001 Accept assessment results (3054c74b-9b45-2581-56cf-053a1a716c39) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-3 | NIST_SP_800-53_R5_CA-3 | NIST SP 800-53 Rev. 5 CA-3 | Assessment, Authorization, and Monitoring | Information Exchange | Shared | n/a | a. Approve and manage the exchange of information between the system and other systems using [Selection (OneOrMore): interconnection security agreements;information exchange security agreements;memoranda of understanding or agreement;service level agreements;user agreements;nondisclosure agreements; [Assignment: organization-defined type of agreement] ] ; b. Document, as part of each exchange agreement, the interface characteristics, security and privacy requirements, controls, and responsibilities for each system, and the impact level of the information communicated; and c. Review and update the agreements [Assignment: organization-defined frequency]. | link | count: 002 Require interconnection security agreements (096a7055-30cb-2db4-3fda-41b20ac72667), Update interconnection security agreements (d48a6f19-a284-6fc6-0623-3367a74d3f50) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-5 | NIST_SP_800-53_R5_CA-5 | NIST SP 800-53 Rev. 5 CA-5 | Assessment, Authorization, and Monitoring | Plan of Action and Milestones | Shared | n/a | a. Develop a plan of action and milestones for the system to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system; and b. Update existing plan of action and milestones [Assignment: organization-defined frequency] based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities. | link | count: 002 Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-6 | NIST_SP_800-53_R5_CA-6 | NIST SP 800-53 Rev. 5 CA-6 | Assessment, Authorization, and Monitoring | Authorization | Shared | n/a | a. Assign a senior official as the authorizing official for the system; b. Assign a senior official as the authorizing official for common controls available for inheritance by organizational systems; c. Ensure that the authorizing official for the system, before commencing operations: 1. Accepts the use of common controls inherited by the system; and 2. Authorizes the system to operate; d. Ensure that the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems; e. Update the authorizations [Assignment: organization-defined frequency]. | link | count: 003 Assign an authorizing official (AO) (e29a8f1b-149b-2fa3-969d-ebee1baa9472), Ensure resources are authorized (0716f0f5-4955-2ccb-8d5e-c6be14d57c0f), Update the security authorization (449ebb52-945b-36e5-3446-af6f33770f8f) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-7 | NIST_SP_800-53_R5_CA-7 | NIST SP 800-53 Rev. 5 CA-7 | Assessment, Authorization, and Monitoring | Continuous Monitoring | Shared | n/a | Develop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitoring strategy that includes: a. Establishing the following system-level metrics to be monitored: [Assignment: organization-defined system-level metrics]; b. Establishing [Assignment: organization-defined frequencies] for monitoring and [Assignment: organization-defined frequencies] for assessment of control effectiveness; c. Ongoing control assessments in accordance with the continuous monitoring strategy; d. Ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy; e. Correlation and analysis of information generated by control assessments and monitoring; f. Response actions to address results of the analysis of control assessment and monitoring information; and g. Reporting the security and privacy status of the system to [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency]. | link | count: 003 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-7(1) | NIST_SP_800-53_R5_CA-7(1) | NIST SP 800-53 Rev. 5 CA-7 (1) | Assessment, Authorization, and Monitoring | Independent Assessment | Shared | n/a | Employ independent assessors or assessment teams to monitor the controls in the system on an ongoing basis. | link | count: 001 Employ independent assessors for continuous monitoring (3baee3fd-30f5-882c-018c-cc78703a0106) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-7(3) | NIST_SP_800-53_R5_CA-7(3) | NIST SP 800-53 Rev. 5 CA-7 (3) | Assessment, Authorization, and Monitoring | Trend Analyses | Shared | n/a | Employ trend analyses to determine if control implementations, the frequency of continuous monitoring activities, and the types of activities used in the continuous monitoring process need to be modified based on empirical data. | link | count: 001 Analyse data obtained from continuous monitoring (6a379d74-903b-244a-4c44-838728bea6b0) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-8(1) | NIST_SP_800-53_R5_CA-8(1) | NIST SP 800-53 Rev. 5 CA-8 (1) | Assessment, Authorization, and Monitoring | Independent Penetration Testing Agent or Team | Shared | n/a | Employ an independent penetration testing agent or team to perform penetration testing on the system or system components. | link | count: 001 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CA-9 | NIST_SP_800-53_R5_CA-9 | NIST SP 800-53 Rev. 5 CA-9 | Assessment, Authorization, and Monitoring | Internal System Connections | Shared | n/a | a. Authorize internal connections of [Assignment: organization-defined system components or classes of components] to the system; b. Document, for each internal connection, the interface characteristics, security and privacy requirements, and the nature of the information communicated; c. Terminate internal system connections after [Assignment: organization-defined conditions]; and d. Review [Assignment: organization-defined frequency] the continued need for each internal connection. | link | count: 001 Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-1 | NIST_SP_800-53_R5_CM-1 | NIST SP 800-53 Rev. 5 CM-1 | Configuration Management | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] configuration management policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the configuration management policy and the associated configuration management controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the configuration management policy and procedures; and c. Review and update the current configuration management: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-10 | NIST_SP_800-53_R5_CM-10 | NIST SP 800-53 Rev. 5 CM-10 | Configuration Management | Software Usage Restrictions | Shared | n/a | a. Use software and associated documentation in accordance with contract agreements and copyright laws; b. Track the use of software and associated documentation protected by quantity licenses to control copying and distribution; and c. Control and document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work. | link | count: 004 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Require compliance with intellectual property rights (725164e5-3b21-1ec2-7e42-14f077862841), Track software license usage (77cc89bb-774f-48d7-8a84-fb8c322c3000) |
Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-10(1) | NIST_SP_800-53_R5_CM-10(1) | NIST SP 800-53 Rev. 5 CM-10 (1) | Configuration Management | Open-source Software | Shared | n/a | Establish the following restrictions on the use of open-source software: [Assignment: organization-defined restrictions]. | link | count: 001 Restrict use of open source software (08c11b48-8745-034d-1c1b-a144feec73b9) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-11 | NIST_SP_800-53_R5_CM-11 | NIST SP 800-53 Rev. 5 CM-11 | Configuration Management | User-installed Software | Shared | n/a | a. Establish [Assignment: organization-defined policies] governing the installation of software by users; b. Enforce software installation policies through the following methods: [Assignment: organization-defined methods]; and c. Monitor policy compliance [Assignment: organization-defined frequency]. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-2 | NIST_SP_800-53_R5_CM-2 | NIST SP 800-53 Rev. 5 CM-2 | Configuration Management | Baseline Configuration | Shared | n/a | a. Develop, document, and maintain under configuration control, a current baseline configuration of the system; and b. Review and update the baseline configuration of the system: 1. [Assignment: organization-defined frequency]; 2. When required due to [Assignment: organization-defined circumstances]; and 3. When system components are installed or upgraded. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-2(2) | NIST_SP_800-53_R5_CM-2(2) | NIST SP 800-53 Rev. 5 CM-2 (2) | Configuration Management | Automation Support for Accuracy and Currency | Shared | n/a | Maintain the currency, completeness, accuracy, and availability of the baseline configuration of the system using [Assignment: organization-defined automated mechanisms]. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-2(3) | NIST_SP_800-53_R5_CM-2(3) | NIST SP 800-53 Rev. 5 CM-2 (3) | Configuration Management | Retention of Previous Configurations | Shared | n/a | Retain [Assignment: organization-defined number] of previous versions of baseline configurations of the system to support rollback. | link | count: 001 Retain previous versions of baseline configs (5e4e9685-3818-5934-0071-2620c4fa2ca5) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-2(7) | NIST_SP_800-53_R5_CM-2(7) | NIST SP 800-53 Rev. 5 CM-2 (7) | Configuration Management | Configure Systems and Components for High-risk Areas | Shared | n/a | (a) Issue [Assignment: organization-defined systems or system components] with [Assignment: organization-defined configurations] to individuals traveling to locations that the organization deems to be of significant risk; and (b) Apply the following controls to the systems or components when the individuals return from travel: [Assignment: organization-defined controls]. | link | count: 002 Ensure security safeguards not needed when the individuals return (1fdf0b24-4043-3c55-357e-036985d50b52), Not allow for information systems to accompany with individuals (41172402-8d73-64c7-0921-909083c086b0) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-3 | NIST_SP_800-53_R5_CM-3 | NIST SP 800-53 Rev. 5 CM-3 | Configuration Management | Configuration Change Control | Shared | n/a | a. Determine and document the types of changes to the system that are configuration-controlled; b. Review proposed configuration-controlled changes to the system and approve or disapprove such changes with explicit consideration for security and privacy impact analyses; c. Document configuration change decisions associated with the system; d. Implement approved configuration-controlled changes to the system; e. Retain records of configuration-controlled changes to the system for [Assignment: organization-defined time period]; f. Monitor and review activities associated with configuration-controlled changes to the system; and g. Coordinate and provide oversight for configuration change control activities through [Assignment: organization-defined configuration change control element] that convenes [Selection (OneOrMore): [Assignment: organization-defined frequency] ;when [Assignment: organization-defined configuration change conditions] ] . | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-3(1) | NIST_SP_800-53_R5_CM-3(1) | NIST SP 800-53 Rev. 5 CM-3 (1) | Configuration Management | Automated Documentation, Notification, and Prohibition of Changes | Shared | n/a | Use [Assignment: organization-defined automated mechanisms] to: (a) Document proposed changes to the system; (b) Notify [Assignment: organization-defined approval authorities] of proposed changes to the system and request change approval; (c) Highlight proposed changes to the system that have not been approved or disapproved within [Assignment: organization-defined time period]; (d) Prohibit changes to the system until designated approvals are received; (e) Document all changes to the system; and (f) Notify [Assignment: organization-defined personnel] when approved changes to the system are completed. | link | count: 006 Automate approval request for proposed changes (575ed5e8-4c29-99d0-0e4d-689fb1d29827), Automate implementation of approved change notifications (c72fc0c8-2df8-7506-30be-6ba1971747e1), Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Automate process to prohibit implementation of unapproved changes (7d10debd-4775-85a7-1a41-7e128e0e8c50), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-3(2) | NIST_SP_800-53_R5_CM-3(2) | NIST SP 800-53 Rev. 5 CM-3 (2) | Configuration Management | Testing, Validation, and Documentation of Changes | Shared | n/a | Test, validate, and document changes to the system before finalizing the implementation of the changes. | link | count: 003 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-3(4) | NIST_SP_800-53_R5_CM-3(4) | NIST SP 800-53 Rev. 5 CM-3 (4) | Configuration Management | Security and Privacy Representatives | Shared | n/a | Require [Assignment: organization-defined security and privacy representatives] to be members of the [Assignment: organization-defined configuration change control element]. | link | count: 001 Assign information security representative to change control (6abdf7c7-362b-3f35-099e-533ed50988f9) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-3(6) | NIST_SP_800-53_R5_CM-3(6) | NIST SP 800-53 Rev. 5 CM-3 (6) | Configuration Management | Cryptography Management | Shared | n/a | Ensure that cryptographic mechanisms used to provide the following controls are under configuration management: [Assignment: organization-defined controls]. | link | count: 001 Ensure cryptographic mechanisms are under configuration management (b8dad106-6444-5f55-307e-1e1cc9723e39) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-4 | NIST_SP_800-53_R5_CM-4 | NIST SP 800-53 Rev. 5 CM-4 | Configuration Management | Impact Analyses | Shared | n/a | Analyze changes to the system to determine potential security and privacy impacts prior to change implementation. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-4(1) | NIST_SP_800-53_R5_CM-4(1) | NIST SP 800-53 Rev. 5 CM-4 (1) | Configuration Management | Separate Test Environments | Shared | n/a | Analyze changes to the system in a separate test environment before implementation in an operational environment, looking for security and privacy impacts due to flaws, weaknesses, incompatibility, or intentional malice. | link | count: 005 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-5 | NIST_SP_800-53_R5_CM-5 | NIST SP 800-53 Rev. 5 CM-5 | Configuration Management | Access Restrictions for Change | Shared | n/a | Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system. | link | count: 001 Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-5(1) | NIST_SP_800-53_R5_CM-5(1) | NIST SP 800-53 Rev. 5 CM-5 (1) | Configuration Management | Automated Access Enforcement and Audit Records | Shared | n/a | (a) Enforce access restrictions using [Assignment: organization-defined automated mechanisms]; and (b) Automatically generate audit records of the enforcement actions. | link | count: 001 Enforce and audit access restrictions (8cd815bf-97e1-5144-0735-11f6ddb50a59) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-5(5) | NIST_SP_800-53_R5_CM-5(5) | NIST SP 800-53 Rev. 5 CM-5 (5) | Configuration Management | Privilege Limitation for Production and Operation | Shared | n/a | (a) Limit privileges to change system components and system-related information within a production or operational environment; and (b) Review and reevaluate privileges [Assignment: organization-defined frequency]. | link | count: 002 Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Review and reevaluate privileges (585af6e9-90c0-4575-67a7-2f9548972e32) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-6 | NIST_SP_800-53_R5_CM-6 | NIST SP 800-53 Rev. 5 CM-6 | Configuration Management | Configuration Settings | Shared | n/a | a. Establish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with operational requirements using [Assignment: organization-defined common secure configurations]; b. Implement the configuration settings; c. Identify, document, and approve any deviations from established configuration settings for [Assignment: organization-defined system components] based on [Assignment: organization-defined operational requirements]; and d. Monitor and control changes to the configuration settings in accordance with organizational policies and procedures. | link | count: 023 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Guest Configuration, Kubernetes, Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-6(1) | NIST_SP_800-53_R5_CM-6(1) | NIST SP 800-53 Rev. 5 CM-6 (1) | Configuration Management | Automated Management, Application, and Verification | Shared | n/a | Manage, apply, and verify configuration settings for [Assignment: organization-defined system components] using [Assignment: organization-defined automated mechanisms]. | link | count: 003 Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Govern compliance of cloud service providers (5c33538e-02f8-0a7f-998b-a4c1e22076d3), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-7 | NIST_SP_800-53_R5_CM-7 | NIST SP 800-53 Rev. 5 CM-7 | Configuration Management | Least Functionality | Shared | n/a | a. Configure the system to provide only [Assignment: organization-defined mission essential capabilities]; and b. Prohibit or restrict the use of the following functions, ports, protocols, software, and/or services: [Assignment: organization-defined prohibited or restricted functions, system ports, protocols, software, and/or services]. | link | count: 003 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-7(2) | NIST_SP_800-53_R5_CM-7(2) | NIST SP 800-53 Rev. 5 CM-7 (2) | Configuration Management | Prevent Program Execution | Shared | n/a | Prevent program execution in accordance with [Selection (OneOrMore): [Assignment: organization-defined policies, rules of behavior, and/or access agreements regarding software program usage and restrictions] ;rules authorizing the terms and conditions of software program usage] . | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-7(5) | NIST_SP_800-53_R5_CM-7(5) | NIST SP 800-53 Rev. 5 CM-7 (5) | Configuration Management | Authorized Software ??? Allow-by-exception | Shared | n/a | (a) Identify [Assignment: organization-defined software programs authorized to execute on the system]; (b) Employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system; and (c) Review and update the list of authorized software programs [Assignment: organization-defined frequency]. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-8 | NIST_SP_800-53_R5_CM-8 | NIST SP 800-53 Rev. 5 CM-8 | Configuration Management | System Component Inventory | Shared | n/a | a. Develop and document an inventory of system components that: 1. Accurately reflects the system; 2. Includes all components within the system; 3. Does not include duplicate accounting of components or components assigned to any other system; 4. Is at the level of granularity deemed necessary for tracking and reporting; and 5. Includes the following information to achieve system component accountability: [Assignment: organization-defined information deemed necessary to achieve effective system component accountability]; and b. Review and update the system component inventory [Assignment: organization-defined frequency]. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-8(1) | NIST_SP_800-53_R5_CM-8(1) | NIST SP 800-53 Rev. 5 CM-8 (1) | Configuration Management | Updates During Installation and Removal | Shared | n/a | Update the inventory of system components as part of component installations, removals, and system updates. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-8(3) | NIST_SP_800-53_R5_CM-8(3) | NIST SP 800-53 Rev. 5 CM-8 (3) | Configuration Management | Automated Unauthorized Component Detection | Shared | n/a | (a) Detect the presence of unauthorized hardware, software, and firmware components within the system using [Assignment: organization-defined automated mechanisms] [Assignment: organization-defined frequency]; and (b) Take the following actions when unauthorized components are detected: [Selection (OneOrMore): disable network access by such components;isolate the components;notify [Assignment: organization-defined personnel or roles] ] . | link | count: 002 Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-8(4) | NIST_SP_800-53_R5_CM-8(4) | NIST SP 800-53 Rev. 5 CM-8 (4) | Configuration Management | Accountability Information | Shared | n/a | Include in the system component inventory information, a means for identifying by [Selection (OneOrMore): name;position;role] , individuals responsible and accountable for administering those components. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CM-9 | NIST_SP_800-53_R5_CM-9 | NIST SP 800-53 Rev. 5 CM-9 | Configuration Management | Configuration Management Plan | Shared | n/a | Develop, document, and implement a configuration management plan for the system that: a. Addresses roles, responsibilities, and configuration management processes and procedures; b. Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items; c. Defines the configuration items for the system and places the configuration items under configuration management; d. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; and e. Protects the configuration management plan from unauthorized disclosure and modification. | link | count: 006 Create configuration plan protection (874a6f2e-2098-53bc-3a16-20dcdc425a7e), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Develop configuration item identification plan (836f8406-3b8a-11bb-12cb-6c7fa0765668), Develop configuration management plan (04837a26-2601-1982-3da7-bf463e6408f4), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-1 | NIST_SP_800-53_R5_CP-1 | NIST SP 800-53 Rev. 5 CP-1 | Contingency Planning | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] contingency planning policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the contingency planning policy and the associated contingency planning controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the contingency planning policy and procedures; and c. Review and update the current contingency planning: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update contingency planning policies and procedures (e9c60c37-65b0-2d72-6c3c-af66036203ae) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-10 | NIST_SP_800-53_R5_CP-10 | NIST SP 800-53 Rev. 5 CP-10 | Contingency Planning | System Recovery and Reconstitution | Shared | n/a | Provide for the recovery and reconstitution of the system to a known state within [Assignment: organization-defined time period consistent with recovery time and recovery point objectives] after a disruption, compromise, or failure. | link | count: 001 Recover and reconstitute resources after any disruption (f33c3238-11d2-508c-877c-4262ec1132e1) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-10(2) | NIST_SP_800-53_R5_CP-10(2) | NIST SP 800-53 Rev. 5 CP-10 (2) | Contingency Planning | Transaction Recovery | Shared | n/a | Implement transaction recovery for systems that are transaction-based. | link | count: 001 Implement transaction based recovery (ba02d0a0-566a-25dc-73f1-101c726a19c5) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-10(4) | NIST_SP_800-53_R5_CP-10(4) | NIST SP 800-53 Rev. 5 CP-10 (4) | Contingency Planning | Restore Within Time Period | Shared | n/a | Provide the capability to restore system components within [Assignment: organization-defined restoration time periods] from configuration-controlled and integrity-protected information representing a known, operational state for the components. | link | count: 001 Restore resources to operational state (f801d58e-5659-9a4a-6e8d-02c9334732e5) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-2 | NIST_SP_800-53_R5_CP-2 | NIST SP 800-53 Rev. 5 CP-2 | Contingency Planning | Contingency Plan | Shared | n/a | a. Develop a contingency plan for the system that: 1. Identifies essential mission and business functions and associated contingency requirements; 2. Provides recovery objectives, restoration priorities, and metrics; 3. Addresses contingency roles, responsibilities, assigned individuals with contact information; 4. Addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure; 5. Addresses eventual, full system restoration without deterioration of the controls originally planned and implemented; 6. Addresses the sharing of contingency information; and 7. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; b. Distribute copies of the contingency plan to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements]; c. Coordinate contingency planning activities with incident handling activities; d. Review the contingency plan for the system [Assignment: organization-defined frequency]; e. Update the contingency plan to address changes to the organization, system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing; f. Communicate contingency plan changes to [Assignment: organization-defined key contingency personnel (identified by name and/or by role) and organizational elements]; g. Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and h. Protect the contingency plan from unauthorized disclosure and modification. | link | count: 008 Communicate contingency plan changes (a1334a65-2622-28ee-5067-9d7f5b915cc5), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82), Review contingency plan (53fc1282-0ee3-2764-1319-e20143bb0ea5), Update contingency plan (14a4fd0a-9100-1e12-1362-792014a28155) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-2(1) | NIST_SP_800-53_R5_CP-2(1) | NIST SP 800-53 Rev. 5 CP-2 (1) | Contingency Planning | Coordinate with Related Plans | Shared | n/a | Coordinate contingency plan development with organizational elements responsible for related plans. | link | count: 001 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-2(2) | NIST_SP_800-53_R5_CP-2(2) | NIST SP 800-53 Rev. 5 CP-2 (2) | Contingency Planning | Capacity Planning | Shared | n/a | Conduct capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations. | link | count: 001 Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-2(3) | NIST_SP_800-53_R5_CP-2(3) | NIST SP 800-53 Rev. 5 CP-2 (3) | Contingency Planning | Resume Mission and Business Functions | Shared | n/a | Plan for the resumption of [Selection: all;essential] mission and business functions within [Assignment: organization-defined time period] of contingency plan activation. | link | count: 001 Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-2(5) | NIST_SP_800-53_R5_CP-2(5) | NIST SP 800-53 Rev. 5 CP-2 (5) | Contingency Planning | Continue Mission and Business Functions | Shared | n/a | Plan for the continuance of [Selection: all;essential] mission and business functions with minimal or no loss of operational continuity and sustains that continuity until full system restoration at primary processing and/or storage sites. | link | count: 001 Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-2(8) | NIST_SP_800-53_R5_CP-2(8) | NIST SP 800-53 Rev. 5 CP-2 (8) | Contingency Planning | Identify Critical Assets | Shared | n/a | Identify critical system assets supporting [Selection: all;essential] mission and business functions. | link | count: 001 Perform a business impact assessment and application criticality assessment (cb8841d4-9d13-7292-1d06-ba4d68384681) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-3 | NIST_SP_800-53_R5_CP-3 | NIST SP 800-53 Rev. 5 CP-3 | Contingency Planning | Contingency Training | Shared | n/a | a. Provide contingency training to system users consistent with assigned roles and responsibilities: 1. Within [Assignment: organization-defined time period] of assuming a contingency role or responsibility; 2. When required by system changes; and 3. [Assignment: organization-defined frequency] thereafter; and b. Review and update contingency training content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Provide contingency training (de936662-13dc-204c-75ec-1af80f994088) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-3(1) | NIST_SP_800-53_R5_CP-3(1) | NIST SP 800-53 Rev. 5 CP-3 (1) | Contingency Planning | Simulated Events | Shared | n/a | Incorporate simulated events into contingency training to facilitate effective response by personnel in crisis situations. | link | count: 001 Incorporate simulated contingency training (9c954fcf-6dd8-81f1-41b5-832ae5c62caf) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-4 | NIST_SP_800-53_R5_CP-4 | NIST SP 800-53 Rev. 5 CP-4 | Contingency Planning | Contingency Plan Testing | Shared | n/a | a. Test the contingency plan for the system [Assignment: organization-defined frequency] using the following tests to determine the effectiveness of the plan and the readiness to execute the plan: [Assignment: organization-defined tests]. b. Review the contingency plan test results; and c. Initiate corrective actions, if needed. | link | count: 003 Initiate contingency plan testing corrective actions (8bfdbaa6-6824-3fec-9b06-7961bf7389a6), Review the results of contingency plan testing (5d3abfea-a130-1208-29c0-e57de80aa6b0), Test the business continuity and disaster recovery plan (58a51cde-008b-1a5d-61b5-d95849770677) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-4(1) | NIST_SP_800-53_R5_CP-4(1) | NIST SP 800-53 Rev. 5 CP-4 (1) | Contingency Planning | Coordinate with Related Plans | Shared | n/a | Coordinate contingency plan testing with organizational elements responsible for related plans. | link | count: 001 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-4(2) | NIST_SP_800-53_R5_CP-4(2) | NIST SP 800-53 Rev. 5 CP-4 (2) | Contingency Planning | Alternate Processing Site | Shared | n/a | Test the contingency plan at the alternate processing site: (a) To familiarize contingency personnel with the facility and available resources; and (b) To evaluate the capabilities of the alternate processing site to support contingency operations. | link | count: 002 Evaluate alternate processing site capabilities (60442979-6333-85f0-84c5-b887bac67448), Test contingency plan at an alternate processing location (ba99d512-3baa-1c38-8b0b-ae16bbd34274) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-6 | NIST_SP_800-53_R5_CP-6 | NIST SP 800-53 Rev. 5 CP-6 | Contingency Planning | Alternate Storage Site | Shared | n/a | a. Establish an alternate storage site, including necessary agreements to permit the storage and retrieval of system backup information; and b. Ensure that the alternate storage site provides controls equivalent to that of the primary site. | link | count: 007 Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Regulatory Compliance, SQL, Storage | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-6(1) | NIST_SP_800-53_R5_CP-6(1) | NIST SP 800-53 Rev. 5 CP-6 (1) | Contingency Planning | Separation from Primary Site | Shared | n/a | Identify an alternate storage site that is sufficiently separated from the primary storage site to reduce susceptibility to the same threats. | link | count: 006 Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Regulatory Compliance, SQL, Storage | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-6(2) | NIST_SP_800-53_R5_CP-6(2) | NIST SP 800-53 Rev. 5 CP-6 (2) | Contingency Planning | Recovery Time and Recovery Point Objectives | Shared | n/a | Configure the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives. | link | count: 001 Establish alternate storage site that facilitates recovery operations (245fe58b-96f8-9f1e-48c5-7f49903f66fd) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-6(3) | NIST_SP_800-53_R5_CP-6(3) | NIST SP 800-53 Rev. 5 CP-6 (3) | Contingency Planning | Accessibility | Shared | n/a | Identify potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outline explicit mitigation actions. | link | count: 001 Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-7 | NIST_SP_800-53_R5_CP-7 | NIST SP 800-53 Rev. 5 CP-7 | Contingency Planning | Alternate Processing Site | Shared | n/a | a. Establish an alternate processing site, including necessary agreements to permit the transfer and resumption of [Assignment: organization-defined system operations] for essential mission and business functions within [Assignment: organization-defined time period consistent with recovery time and recovery point objectives] when the primary processing capabilities are unavailable; b. Make available at the alternate processing site, the equipment and supplies required to transfer and resume operations or put contracts in place to support delivery to the site within the organization-defined time period for transfer and resumption; and c. Provide controls at the alternate processing site that are equivalent to those at the primary site. | link | count: 002 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Compute, Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-7(1) | NIST_SP_800-53_R5_CP-7(1) | NIST SP 800-53 Rev. 5 CP-7 (1) | Contingency Planning | Separation from Primary Site | Shared | n/a | Identify an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats. | link | count: 001 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-7(2) | NIST_SP_800-53_R5_CP-7(2) | NIST SP 800-53 Rev. 5 CP-7 (2) | Contingency Planning | Accessibility | Shared | n/a | Identify potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster and outlines explicit mitigation actions. | link | count: 001 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-7(3) | NIST_SP_800-53_R5_CP-7(3) | NIST SP 800-53 Rev. 5 CP-7 (3) | Contingency Planning | Priority of Service | Shared | n/a | Develop alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives). | link | count: 002 Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-7(4) | NIST_SP_800-53_R5_CP-7(4) | NIST SP 800-53 Rev. 5 CP-7 (4) | Contingency Planning | Preparation for Use | Shared | n/a | Prepare the alternate processing site so that the site can serve as the operational site supporting essential mission and business functions. | link | count: 001 Prepare alternate processing site for use as operational site (0f31d98d-5ce2-705b-4aa5-b4f6705110dd) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-8(1) | NIST_SP_800-53_R5_CP-8(1) | NIST SP 800-53 Rev. 5 CP-8 (1) | Contingency Planning | Priority of Service Provisions | Shared | n/a | (a) Develop primary and alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives); and (b) Request Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness if the primary and/or alternate telecommunications services are provided by a common carrier. | link | count: 001 Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-9 | NIST_SP_800-53_R5_CP-9 | NIST SP 800-53 Rev. 5 CP-9 | Contingency Planning | System Backup | Shared | n/a | a. Conduct backups of user-level information contained in [Assignment: organization-defined system components] [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; b. Conduct backups of system-level information contained in the system [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; c. Conduct backups of system documentation, including security- and privacy-related documentation [Assignment: organization-defined frequency consistent with recovery time and recovery point objectives]; and d. Protect the confidentiality, integrity, and availability of backup information. | link | count: 009 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Backup, Key Vault, Regulatory Compliance, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-9(3) | NIST_SP_800-53_R5_CP-9(3) | NIST SP 800-53 Rev. 5 CP-9 (3) | Contingency Planning | Separate Storage for Critical Information | Shared | n/a | Store backup copies of [Assignment: organization-defined critical system software and other security-related information] in a separate facility or in a fire rated container that is not collocated with the operational system. | link | count: 001 Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | CP-9(5) | NIST_SP_800-53_R5_CP-9(5) | NIST SP 800-53 Rev. 5 CP-9 (5) | Contingency Planning | Transfer to Alternate Storage Site | Shared | n/a | Transfer system backup information to the alternate storage site [Assignment: organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives]. | link | count: 001 Transfer backup information to an alternate storage site (7bdb79ea-16b8-453e-4ca4-ad5b16012414) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-1 | NIST_SP_800-53_R5_IA-1 | NIST SP 800-53 Rev. 5 IA-1 | Identification and Authentication | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] identification and authentication policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the identification and authentication policy and the associated identification and authentication controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the identification and authentication policy and procedures; and c. Review and update the current identification and authentication: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-2 | NIST_SP_800-53_R5_IA-2 | NIST SP 800-53 Rev. 5 IA-2 | Identification and Authentication | Identification and Authentication (organizational Users) | Shared | n/a | Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users. | link | count: 010 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
App Service, Azure Ai Services, Regulatory Compliance, Security Center, Service Fabric, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-2(1) | NIST_SP_800-53_R5_IA-2(1) | NIST SP 800-53 Rev. 5 IA-2 (1) | Identification and Authentication | Multi-factor Authentication to Privileged Accounts | Shared | n/a | Implement multi-factor authentication for access to privileged accounts. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-2(12) | NIST_SP_800-53_R5_IA-2(12) | NIST SP 800-53 Rev. 5 IA-2 (12) | Identification and Authentication | Acceptance of PIV Credentials | Shared | n/a | Accept and electronically verify Personal Identity Verification-compliant credentials. | link | count: 001 Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-2(2) | NIST_SP_800-53_R5_IA-2(2) | NIST SP 800-53 Rev. 5 IA-2 (2) | Identification and Authentication | Multi-factor Authentication to Non-privileged Accounts | Shared | n/a | Implement multi-factor authentication for access to non-privileged accounts. | link | count: 002 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a) |
Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-2(5) | NIST_SP_800-53_R5_IA-2(5) | NIST SP 800-53 Rev. 5 IA-2 (5) | Identification and Authentication | Individual Authentication with Group Authentication | Shared | n/a | When shared accounts or authenticators are employed, require users to be individually authenticated before granting access to the shared accounts or resources. | link | count: 001 Require use of individual authenticators (08ad71d0-52be-6503-4908-e015460a16ae) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-4 | NIST_SP_800-53_R5_IA-4 | NIST SP 800-53 Rev. 5 IA-4 | Identification and Authentication | Identifier Management | Shared | n/a | Manage system identifiers by: a. Receiving authorization from [Assignment: organization-defined personnel or roles] to assign an individual, group, role, service, or device identifier; b. Selecting an identifier that identifies an individual, group, role, service, or device; c. Assigning the identifier to the intended individual, group, role, service, or device; and d. Preventing reuse of identifiers for [Assignment: organization-defined time period]. | link | count: 007 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Prevent identifier reuse for the defined time period (4781e5fd-76b8-7d34-6df3-a0a7fca47665), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Azure Ai Services, Regulatory Compliance, Service Fabric, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-4(4) | NIST_SP_800-53_R5_IA-4(4) | NIST SP 800-53 Rev. 5 IA-4 (4) | Identification and Authentication | Identify User Status | Shared | n/a | Manage individual identifiers by uniquely identifying each individual as [Assignment: organization-defined characteristic identifying individual status]. | link | count: 001 Identify status of individual users (ca748dfe-3e28-1d18-4221-89aea30aa0a5) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-5 | NIST_SP_800-53_R5_IA-5 | NIST SP 800-53 Rev. 5 IA-5 | Identification and Authentication | Authenticator Management | Shared | n/a | Manage system authenticators by: a. Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, service, or device receiving the authenticator; b. Establishing initial authenticator content for any authenticators issued by the organization; c. Ensuring that authenticators have sufficient strength of mechanism for their intended use; d. Establishing and implementing administrative procedures for initial authenticator distribution, for lost or compromised or damaged authenticators, and for revoking authenticators; e. Changing default authenticators prior to first use; f. Changing or refreshing authenticators [Assignment: organization-defined time period by authenticator type] or when [Assignment: organization-defined events] occur; g. Protecting authenticator content from unauthorized disclosure and modification; h. Requiring individuals to take, and having devices implement, specific controls to protect authenticators; and i. Changing authenticators for group or role accounts when membership to those accounts changes. | link | count: 018 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Guest Configuration, Key Vault, Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-5(1) | NIST_SP_800-53_R5_IA-5(1) | NIST SP 800-53 Rev. 5 IA-5 (1) | Identification and Authentication | Password-based Authentication | Shared | n/a | For password-based authentication: (a) Maintain a list of commonly-used, expected, or compromised passwords and update the list [Assignment: organization-defined frequency] and when organizational passwords are suspected to have been compromised directly or indirectly; (b) Verify, when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5(1)(a); (c) Transmit passwords only over cryptographically-protected channels; (d) Store passwords using an approved salted key derivation function, preferably using a keyed hash; (e) Require immediate selection of a new password upon account recovery; (f) Allow user selection of long passwords and passphrases, including spaces and all printable characters; (g) Employ automated tools to assist the user in selecting strong password authenticators; and (h) Enforce the following composition and complexity rules: [Assignment: organization-defined composition and complexity rules]. | link | count: 015 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Guest Configuration, Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-5(13) | NIST_SP_800-53_R5_IA-5(13) | NIST SP 800-53 Rev. 5 IA-5 (13) | Identification and Authentication | Expiration of Cached Authenticators | Shared | n/a | Prohibit the use of cached authenticators after [Assignment: organization-defined time period]. | link | count: 001 Enforce expiration of cached authenticators (c7e8ddc1-14aa-1814-7fe1-aad1742b27da) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-5(2) | NIST_SP_800-53_R5_IA-5(2) | NIST SP 800-53 Rev. 5 IA-5 (2) | Identification and Authentication | Public Key-based Authentication | Shared | n/a | (a) For public key-based authentication: (1) Enforce authorized access to the corresponding private key; and (2) Map the authenticated identity to the account of the individual or group; and (b) When public key infrastructure (PKI) is used: (1) Validate certificates by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information; and (2) Implement a local cache of revocation data to support path discovery and validation. | link | count: 007 Bind authenticators and identities dynamically (6f311b49-9b0d-8c67-3d6e-db80ae528173), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish parameters for searching secret authenticators and verifiers (0065241c-72e9-3b2c-556f-75de66332a94), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Map authenticated identities to individuals (4012c2b7-4e0e-a7ab-1688-4aab43f14420), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-5(6) | NIST_SP_800-53_R5_IA-5(6) | NIST SP 800-53 Rev. 5 IA-5 (6) | Identification and Authentication | Protection of Authenticators | Shared | n/a | Protect authenticators commensurate with the security category of the information to which use of the authenticator permits access. | link | count: 001 Ensure authorized users protect provided authenticators (37dbe3dc-0e9c-24fa-36f2-11197cbfa207) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-5(7) | NIST_SP_800-53_R5_IA-5(7) | NIST SP 800-53 Rev. 5 IA-5 (7) | Identification and Authentication | No Embedded Unencrypted Static Authenticators | Shared | n/a | Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage. | link | count: 001 Ensure there are no unencrypted static authenticators (eda0cbb7-6043-05bf-645b-67411f1a59b3) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-6 | NIST_SP_800-53_R5_IA-6 | NIST SP 800-53 Rev. 5 IA-6 | Identification and Authentication | Authentication Feedback | Shared | n/a | Obscure feedback of authentication information during the authentication process to protect the information from possible exploitation and use by unauthorized individuals. | link | count: 001 Obscure feedback information during authentication process (1ff03f2a-974b-3272-34f2-f6cd51420b30) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-7 | NIST_SP_800-53_R5_IA-7 | NIST SP 800-53 Rev. 5 IA-7 | Identification and Authentication | Cryptographic Module Authentication | Shared | n/a | Implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and guidelines for such authentication. | link | count: 001 Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-8 | NIST_SP_800-53_R5_IA-8 | NIST SP 800-53 Rev. 5 IA-8 | Identification and Authentication | Identification and Authentication (non-organizational Users) | Shared | n/a | Uniquely identify and authenticate non-organizational users or processes acting on behalf of non-organizational users. | link | count: 001 Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-8(1) | NIST_SP_800-53_R5_IA-8(1) | NIST SP 800-53 Rev. 5 IA-8 (1) | Identification and Authentication | Acceptance of PIV Credentials from Other Agencies | Shared | n/a | Accept and electronically verify Personal Identity Verification-compliant credentials from other federal agencies. | link | count: 001 Accept PIV credentials (55be3260-a7a2-3c06-7fe6-072d07525ab7) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-8(2) | NIST_SP_800-53_R5_IA-8(2) | NIST SP 800-53 Rev. 5 IA-8 (2) | Identification and Authentication | Acceptance of External Authenticators | Shared | n/a | (a) Accept only external authenticators that are NIST-compliant; and (b) Document and maintain a list of accepted external authenticators. | link | count: 001 Accept only FICAM-approved third-party credentials (2d2ca910-7957-23ee-2945-33f401606efc) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IA-8(4) | NIST_SP_800-53_R5_IA-8(4) | NIST SP 800-53 Rev. 5 IA-8 (4) | Identification and Authentication | Use of Defined Profiles | Shared | n/a | Conform to the following profiles for identity management [Assignment: organization-defined identity management profiles]. | link | count: 001 Conform to FICAM-issued profiles (a8df9c78-4044-98be-2c05-31a315ac8957) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-1 | NIST_SP_800-53_R5_IR-1 | NIST SP 800-53 Rev. 5 IR-1 | Incident Response | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] incident response policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the incident response policy and the associated incident response controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the incident response policy and procedures; and c. Review and update the current incident response: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-2 | NIST_SP_800-53_R5_IR-2 | NIST SP 800-53 Rev. 5 IR-2 | Incident Response | Incident Response Training | Shared | n/a | a. Provide incident response training to system users consistent with assigned roles and responsibilities: 1. Within [Assignment: organization-defined time period] of assuming an incident response role or responsibility or acquiring system access; 2. When required by system changes; and 3. [Assignment: organization-defined frequency] thereafter; and b. Review and update incident response training content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-2(1) | NIST_SP_800-53_R5_IR-2(1) | NIST SP 800-53 Rev. 5 IR-2 (1) | Incident Response | Simulated Events | Shared | n/a | Incorporate simulated events into incident response training to facilitate the required response by personnel in crisis situations. | link | count: 001 Incorporate simulated events into incident response training (1fdeb7c4-4c93-8271-a135-17ebe85f1cc7) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-2(2) | NIST_SP_800-53_R5_IR-2(2) | NIST SP 800-53 Rev. 5 IR-2 (2) | Incident Response | Automated Training Environments | Shared | n/a | Provide an incident response training environment using [Assignment: organization-defined automated mechanisms]. | link | count: 001 Employ automated training environment (c8aa992d-76b7-7ca0-07b3-31a58d773fa9) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-3 | NIST_SP_800-53_R5_IR-3 | NIST SP 800-53 Rev. 5 IR-3 | Incident Response | Incident Response Testing | Shared | n/a | Test the effectiveness of the incident response capability for the system [Assignment: organization-defined frequency] using the following tests: [Assignment: organization-defined tests]. | link | count: 003 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-3(2) | NIST_SP_800-53_R5_IR-3(2) | NIST SP 800-53 Rev. 5 IR-3 (2) | Incident Response | Coordination with Related Plans | Shared | n/a | Coordinate incident response testing with organizational elements responsible for related plans. | link | count: 003 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-4 | NIST_SP_800-53_R5_IR-4 | NIST SP 800-53 Rev. 5 IR-4 | Incident Response | Incident Handling | Shared | n/a | a. Implement an incident handling capability for incidents that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradication, and recovery; b. Coordinate incident handling activities with contingency planning activities; c. Incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly; and d. Ensure the rigor, intensity, scope, and results of incident handling activities are comparable and predictable across the organization. | link | count: 024 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance, Security Center, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-4(1) | NIST_SP_800-53_R5_IR-4(1) | NIST SP 800-53 Rev. 5 IR-4 (1) | Incident Response | Automated Incident Handling Processes | Shared | n/a | Support the incident handling process using [Assignment: organization-defined automated mechanisms]. | link | count: 003 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-4(2) | NIST_SP_800-53_R5_IR-4(2) | NIST SP 800-53 Rev. 5 IR-4 (2) | Incident Response | Dynamic Reconfiguration | Shared | n/a | Include the following types of dynamic reconfiguration for [Assignment: organization-defined system components] as part of the incident response capability: [Assignment: organization-defined types of dynamic reconfiguration]. | link | count: 001 Include dynamic reconfig of customer deployed resources (1e0d5ba8-a433-01aa-829c-86b06c9631ec) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-4(3) | NIST_SP_800-53_R5_IR-4(3) | NIST SP 800-53 Rev. 5 IR-4 (3) | Incident Response | Continuity of Operations | Shared | n/a | Identify [Assignment: organization-defined classes of incidents] and take the following actions in response to those incidents to ensure continuation of organizational mission and business functions: [Assignment: organization-defined actions to take in response to classes of incidents]. | link | count: 001 Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-4(4) | NIST_SP_800-53_R5_IR-4(4) | NIST SP 800-53 Rev. 5 IR-4 (4) | Incident Response | Information Correlation | Shared | n/a | Correlate incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response. | link | count: 001 Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-4(6) | NIST_SP_800-53_R5_IR-4(6) | NIST SP 800-53 Rev. 5 IR-4 (6) | Incident Response | Insider Threats | Shared | n/a | Implement an incident handling capability for incidents involving insider threats. | link | count: 001 Implement Incident handling capability (98e33927-8d7f-6d5f-44f5-2469b40b7215) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-4(8) | NIST_SP_800-53_R5_IR-4(8) | NIST SP 800-53 Rev. 5 IR-4 (8) | Incident Response | Correlation with External Organizations | Shared | n/a | Coordinate with [Assignment: organization-defined external organizations] to correlate and share [Assignment: organization-defined incident information] to achieve a cross-organization perspective on incident awareness and more effective incident responses. | link | count: 001 Coordinate with external organizations to achieve cross org perspective (d4e6a629-28eb-79a9-000b-88030e4823ca) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-5 | NIST_SP_800-53_R5_IR-5 | NIST SP 800-53 Rev. 5 IR-5 | Incident Response | Incident Monitoring | Shared | n/a | Track and document incidents. | link | count: 013 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-6(1) | NIST_SP_800-53_R5_IR-6(1) | NIST SP 800-53 Rev. 5 IR-6 (1) | Incident Response | Automated Reporting | Shared | n/a | Report incidents using [Assignment: organization-defined automated mechanisms]. | link | count: 001 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-6(2) | NIST_SP_800-53_R5_IR-6(2) | NIST SP 800-53 Rev. 5 IR-6 (2) | Incident Response | Vulnerabilities Related to Incidents | Customer | n/a | Report system vulnerabilities associated with reported incidents to [Assignment: organization-defined personnel or roles]. | link | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-7 | NIST_SP_800-53_R5_IR-7 | NIST SP 800-53 Rev. 5 IR-7 | Incident Response | Incident Response Assistance | Shared | n/a | Provide an incident response support resource, integral to the organizational incident response capability, that offers advice and assistance to users of the system for the handling and reporting of incidents. | link | count: 001 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-7(1) | NIST_SP_800-53_R5_IR-7(1) | NIST SP 800-53 Rev. 5 IR-7 (1) | Incident Response | Automation Support for Availability of Information and Support | Shared | n/a | Increase the availability of incident response information and support using [Assignment: organization-defined automated mechanisms]. | link | count: 007 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-7(2) | NIST_SP_800-53_R5_IR-7(2) | NIST SP 800-53 Rev. 5 IR-7 (2) | Incident Response | Coordination with External Providers | Shared | n/a | (a) Establish a direct, cooperative relationship between its incident response capability and external providers of system protection capability; and (b) Identify organizational incident response team members to the external providers. | link | count: 002 Establish relationship between incident response capability and external providers (b470a37a-7a47-3792-34dd-7a793140702e), Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-8 | NIST_SP_800-53_R5_IR-8 | NIST SP 800-53 Rev. 5 IR-8 | Incident Response | Incident Response Plan | Shared | n/a | a. Develop an incident response plan that: 1. Provides the organization with a roadmap for implementing its incident response capability; 2. Describes the structure and organization of the incident response capability; 3. Provides a high-level approach for how the incident response capability fits into the overall organization; 4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions; 5. Defines reportable incidents; 6. Provides metrics for measuring the incident response capability within the organization; 7. Defines the resources and management support needed to effectively maintain and mature an incident response capability; 8. Addresses the sharing of incident information; 9. Is reviewed and approved by [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency]; and 10. Explicitly designates responsibility for incident response to [Assignment: organization-defined entities, personnel, or roles]. b. Distribute copies of the incident response plan to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; c. Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing; d. Communicate incident response plan changes to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and e. Protect the incident response plan from unauthorized disclosure and modification. | link | count: 006 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-9 | NIST_SP_800-53_R5_IR-9 | NIST SP 800-53 Rev. 5 IR-9 | Incident Response | Information Spillage Response | Shared | n/a | Respond to information spills by: a. Assigning [Assignment: organization-defined personnel or roles] with responsibility for responding to information spills; b. Identifying the specific information involved in the system contamination; c. Alerting [Assignment: organization-defined personnel or roles] of the information spill using a method of communication not associated with the spill; d. Isolating the contaminated system or system component; e. Eradicating the information from the contaminated system or component; f. Identifying other systems or system components that may have been subsequently contaminated; and g. Performing the following additional actions: [Assignment: organization-defined actions]. | link | count: 007 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify contaminated systems and components (279052a0-8238-694d-9661-bf649f951747), Identify spilled information (69d90ee6-9f9f-262a-2038-d909fb4e5723), Isolate information spills (22457e81-3ec6-5271-a786-c3ca284601dd) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-9(2) | NIST_SP_800-53_R5_IR-9(2) | NIST SP 800-53 Rev. 5 IR-9 (2) | Incident Response | Training | Shared | n/a | Provide information spillage response training [Assignment: organization-defined frequency]. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-9(3) | NIST_SP_800-53_R5_IR-9(3) | NIST SP 800-53 Rev. 5 IR-9 (3) | Incident Response | Post-spill Operations | Shared | n/a | Implement the following procedures to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions: [Assignment: organization-defined procedures]. | link | count: 001 Develop spillage response procedures (bb048641-6017-7272-7772-a008f285a520) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | IR-9(4) | NIST_SP_800-53_R5_IR-9(4) | NIST SP 800-53 Rev. 5 IR-9 (4) | Incident Response | Exposure to Unauthorized Personnel | Shared | n/a | Employ the following controls for personnel exposed to information not within assigned access authorizations: [Assignment: organization-defined controls]. | link | count: 001 Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-1 | NIST_SP_800-53_R5_MA-1 | NIST SP 800-53 Rev. 5 MA-1 | Maintenance | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] maintenance policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the maintenance policy and the associated maintenance controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the maintenance policy and procedures; and c. Review and update the current maintenance: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update system maintenance policies and procedures (2067b904-9552-3259-0cdd-84468e284b7c) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-2 | NIST_SP_800-53_R5_MA-2 | NIST SP 800-53 Rev. 5 MA-2 | Maintenance | Controlled Maintenance | Shared | n/a | a. Schedule, document, and review records of maintenance, repair, and replacement on system components in accordance with manufacturer or vendor specifications and/or organizational requirements; b. Approve and monitor all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location; c. Require that [Assignment: organization-defined personnel or roles] explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or replacement; d. Sanitize equipment to remove the following information from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement: [Assignment: organization-defined information]; e. Check all potentially impacted controls to verify that the controls are still functioning properly following maintenance, repair, or replacement actions; and f. Include the following information in organizational maintenance records: [Assignment: organization-defined information]. | link | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-2(2) | NIST_SP_800-53_R5_MA-2(2) | NIST SP 800-53 Rev. 5 MA-2 (2) | Maintenance | Automated Maintenance Activities | Shared | n/a | (a) Schedule, conduct, and document maintenance, repair, and replacement actions for the system using [Assignment: organization-defined automated mechanisms]; and (b) Produce up-to date, accurate, and complete records of all maintenance, repair, and replacement actions requested, scheduled, in process, and completed. | link | count: 002 Automate remote maintenance activities (b8587fce-138f-86e8-33a3-c60768bf1da6), Produce complete records of remote maintenance activities (74041cfe-3f87-1d17-79ec-34ca5f895542) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-3 | NIST_SP_800-53_R5_MA-3 | NIST SP 800-53 Rev. 5 MA-3 | Maintenance | Maintenance Tools | Shared | n/a | a. Approve, control, and monitor the use of system maintenance tools; and b. Review previously approved system maintenance tools [Assignment: organization-defined frequency]. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-3(1) | NIST_SP_800-53_R5_MA-3(1) | NIST SP 800-53 Rev. 5 MA-3 (1) | Maintenance | Inspect Tools | Shared | n/a | Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-3(2) | NIST_SP_800-53_R5_MA-3(2) | NIST SP 800-53 Rev. 5 MA-3 (2) | Maintenance | Inspect Media | Shared | n/a | Check media containing diagnostic and test programs for malicious code before the media are used in the system. | link | count: 002 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-3(3) | NIST_SP_800-53_R5_MA-3(3) | NIST SP 800-53 Rev. 5 MA-3 (3) | Maintenance | Prevent Unauthorized Removal | Shared | n/a | Prevent the removal of maintenance equipment containing organizational information by: (a) Verifying that there is no organizational information contained on the equipment; (b) Sanitizing or destroying the equipment; (c) Retaining the equipment within the facility; or (d) Obtaining an exemption from [Assignment: organization-defined personnel or roles] explicitly authorizing removal of the equipment from the facility. | link | count: 004 Control maintenance and repair activities (b6ad009f-5c24-1dc0-a25e-74b60e4da45f), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-4 | NIST_SP_800-53_R5_MA-4 | NIST SP 800-53 Rev. 5 MA-4 | Maintenance | Nonlocal Maintenance | Shared | n/a | a. Approve and monitor nonlocal maintenance and diagnostic activities; b. Allow the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the system; c. Employ strong authentication in the establishment of nonlocal maintenance and diagnostic sessions; d. Maintain records for nonlocal maintenance and diagnostic activities; and e. Terminate session and network connections when nonlocal maintenance is completed. | link | count: 001 Manage nonlocal maintenance and diagnostic activities (1fb1cb0e-1936-6f32-42fd-89970b535855) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-4(3) | NIST_SP_800-53_R5_MA-4(3) | NIST SP 800-53 Rev. 5 MA-4 (3) | Maintenance | Comparable Security and Sanitization | Shared | n/a | (a) Require that nonlocal maintenance and diagnostic services be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced; or (b) Remove the component to be serviced from the system prior to nonlocal maintenance or diagnostic services; sanitize the component (for organizational information); and after the service is performed, inspect and sanitize the component (for potentially malicious software) before reconnecting the component to the system. | link | count: 001 Perform all non-local maintenance (5bac5fb7-7735-357b-767d-02264bfe5c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-4(6) | NIST_SP_800-53_R5_MA-4(6) | NIST SP 800-53 Rev. 5 MA-4 (6) | Maintenance | Cryptographic Protection | Shared | n/a | Implement the following cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications: [Assignment: organization-defined cryptographic mechanisms]. | link | count: 001 Implement cryptographic mechanisms (10c3a1b1-29b0-a2d5-8f4c-a284b0f07830) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-5 | NIST_SP_800-53_R5_MA-5 | NIST SP 800-53 Rev. 5 MA-5 | Maintenance | Maintenance Personnel | Shared | n/a | a. Establish a process for maintenance personnel authorization and maintain a list of authorized maintenance organizations or personnel; b. Verify that non-escorted personnel performing maintenance on the system possess the required access authorizations; and c. Designate organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations. | link | count: 003 Designate personnel to supervise unauthorized maintenance activities (7a489c62-242c-5db9-74df-c073056d6fa3), Maintain list of authorized remote maintenance personnel (4ce91e4e-6dab-3c46-011a-aa14ae1561bf), Manage maintenance personnel (b273f1e3-79e7-13ee-5b5d-dca6c66c3d5d) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-5(1) | NIST_SP_800-53_R5_MA-5(1) | NIST SP 800-53 Rev. 5 MA-5 (1) | Maintenance | Individuals Without Appropriate Access | Shared | n/a | (a) Implement procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements: (1) Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified; and (2) Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the system are sanitized and all nonvolatile storage media are removed or physically disconnected from the system and secured; and (b) Develop and implement [Assignment: organization-defined alternate controls] in the event a system component cannot be sanitized, removed, or disconnected from the system. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MA-6 | NIST_SP_800-53_R5_MA-6 | NIST SP 800-53 Rev. 5 MA-6 | Maintenance | Timely Maintenance | Shared | n/a | Obtain maintenance support and/or spare parts for [Assignment: organization-defined system components] within [Assignment: organization-defined time period] of failure. | link | count: 001 Provide timely maintenance support (eb598832-4bcc-658d-4381-3ecbe17b9866) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MP-1 | NIST_SP_800-53_R5_MP-1 | NIST SP 800-53 Rev. 5 MP-1 | Media Protection | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] media protection policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the media protection policy and the associated media protection controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the media protection policy and procedures; and c. Review and update the current media protection: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MP-2 | NIST_SP_800-53_R5_MP-2 | NIST SP 800-53 Rev. 5 MP-2 | Media Protection | Media Access | Shared | n/a | Restrict access to [Assignment: organization-defined types of digital and/or non-digital media] to [Assignment: organization-defined personnel or roles]. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MP-3 | NIST_SP_800-53_R5_MP-3 | NIST SP 800-53 Rev. 5 MP-3 | Media Protection | Media Marking | Shared | n/a | a. Mark system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and b. Exempt [Assignment: organization-defined types of system media] from marking if the media remain within [Assignment: organization-defined controlled areas]. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MP-4 | NIST_SP_800-53_R5_MP-4 | NIST SP 800-53 Rev. 5 MP-4 | Media Protection | Media Storage | Shared | n/a | a. Physically control and securely store [Assignment: organization-defined types of digital and/or non-digital media] within [Assignment: organization-defined controlled areas]; and b. Protect system media types defined in MP-4a until the media are destroyed or sanitized using approved equipment, techniques, and procedures. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MP-5 | NIST_SP_800-53_R5_MP-5 | NIST SP 800-53 Rev. 5 MP-5 | Media Protection | Media Transport | Shared | n/a | a. Protect and control [Assignment: organization-defined types of system media] during transport outside of controlled areas using [Assignment: organization-defined controls]; b. Maintain accountability for system media during transport outside of controlled areas; c. Document activities associated with the transport of system media; and d. Restrict the activities associated with the transport of system media to authorized personnel. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MP-6 | NIST_SP_800-53_R5_MP-6 | NIST SP 800-53 Rev. 5 MP-6 | Media Protection | Media Sanitization | Shared | n/a | a. Sanitize [Assignment: organization-defined system media] prior to disposal, release out of organizational control, or release for reuse using [Assignment: organization-defined sanitization techniques and procedures]; and b. Employ sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MP-6(1) | NIST_SP_800-53_R5_MP-6(1) | NIST SP 800-53 Rev. 5 MP-6 (1) | Media Protection | Review, Approve, Track, Document, and Verify | Shared | n/a | Review, approve, track, document, and verify media sanitization and disposal actions. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MP-6(2) | NIST_SP_800-53_R5_MP-6(2) | NIST SP 800-53 Rev. 5 MP-6 (2) | Media Protection | Equipment Testing | Shared | n/a | Test sanitization equipment and procedures [Assignment: organization-defined frequency] to ensure that the intended sanitization is being achieved. | link | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | MP-7 | NIST_SP_800-53_R5_MP-7 | NIST SP 800-53 Rev. 5 MP-7 | Media Protection | Media Use | Shared | n/a | a. [Selection: Restrict;Prohibit] the use of [Assignment: organization-defined types of system media] on [Assignment: organization-defined systems or system components] using [Assignment: organization-defined controls]; and b. Prohibit the use of portable storage devices in organizational systems when such devices have no identifiable owner. | link | count: 004 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Control use of portable storage devices (36b74844-4a99-4c80-1800-b18a516d1585), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Restrict media use (6122970b-8d4a-7811-0278-4c6c68f61e4f) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-1 | NIST_SP_800-53_R5_PE-1 | NIST SP 800-53 Rev. 5 PE-1 | Physical and Environmental Protection | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] physical and environmental protection policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the physical and environmental protection policy and the associated physical and environmental protection controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures; and c. Review and update the current physical and environmental protection: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-12 | NIST_SP_800-53_R5_PE-12 | NIST SP 800-53 Rev. 5 PE-12 | Physical and Environmental Protection | Emergency Lighting | Shared | n/a | Employ and maintain automatic emergency lighting for the system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility. | link | count: 001 Employ automatic emergency lighting (aa892c0d-2c40-200c-0dd8-eac8c4748ede) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-13 | NIST_SP_800-53_R5_PE-13 | NIST SP 800-53 Rev. 5 PE-13 | Physical and Environmental Protection | Fire Protection | Shared | n/a | Employ and maintain fire detection and suppression systems that are supported by an independent energy source. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-13(1) | NIST_SP_800-53_R5_PE-13(1) | NIST SP 800-53 Rev. 5 PE-13 (1) | Physical and Environmental Protection | Detection Systems ??? Automatic Activation and Notification | Shared | n/a | Employ fire detection systems that activate automatically and notify [Assignment: organization-defined personnel or roles] and [Assignment: organization-defined emergency responders] in the event of a fire. | link | count: 003 Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-13(2) | NIST_SP_800-53_R5_PE-13(2) | NIST SP 800-53 Rev. 5 PE-13 (2) | Physical and Environmental Protection | Suppression Systems ??? Automatic Activation and Notification | Shared | n/a | (a) Employ fire suppression systems that activate automatically and notify [Assignment: organization-defined personnel or roles] and [Assignment: organization-defined emergency responders]; and (b) Employ an automatic fire suppression capability when the facility is not staffed on a continuous basis. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-14 | NIST_SP_800-53_R5_PE-14 | NIST SP 800-53 Rev. 5 PE-14 | Physical and Environmental Protection | Environmental Controls | Shared | n/a | a. Maintain [Selection (OneOrMore): temperature;humidity;pressure;radiation; [Assignment: organization-defined environmental control] ] levels within the facility where the system resides at [Assignment: organization-defined acceptable levels]; and b. Monitor environmental control levels [Assignment: organization-defined frequency]. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-14(2) | NIST_SP_800-53_R5_PE-14(2) | NIST SP 800-53 Rev. 5 PE-14 (2) | Physical and Environmental Protection | Monitoring with Alarms and Notifications | Shared | n/a | Employ environmental control monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment to [Assignment: organization-defined personnel or roles]. | link | count: 002 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-15 | NIST_SP_800-53_R5_PE-15 | NIST SP 800-53 Rev. 5 PE-15 | Physical and Environmental Protection | Water Damage Protection | Shared | n/a | Protect the system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible, working properly, and known to key personnel. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-16 | NIST_SP_800-53_R5_PE-16 | NIST SP 800-53 Rev. 5 PE-16 | Physical and Environmental Protection | Delivery and Removal | Shared | n/a | a. Authorize and control [Assignment: organization-defined types of system components] entering and exiting the facility; and b. Maintain records of the system components. | link | count: 002 Define requirements for managing assets (25a1f840-65d0-900a-43e4-bee253de04de), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-17 | NIST_SP_800-53_R5_PE-17 | NIST SP 800-53 Rev. 5 PE-17 | Physical and Environmental Protection | Alternate Work Site | Shared | n/a | a. Determine and document the [Assignment: organization-defined alternate work sites] allowed for use by employees; b. Employ the following controls at alternate work sites: [Assignment: organization-defined controls]; c. Assess the effectiveness of controls at alternate work sites; and d. Provide a means for employees to communicate with information security and privacy personnel in case of incidents. | link | count: 001 Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-18 | NIST_SP_800-53_R5_PE-18 | NIST SP 800-53 Rev. 5 PE-18 | Physical and Environmental Protection | Location of System Components | Shared | n/a | Position system components within the facility to minimize potential damage from [Assignment: organization-defined physical and environmental hazards] and to minimize the opportunity for unauthorized access. | link | count: 001 Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-2 | NIST_SP_800-53_R5_PE-2 | NIST SP 800-53 Rev. 5 PE-2 | Physical and Environmental Protection | Physical Access Authorizations | Shared | n/a | a. Develop, approve, and maintain a list of individuals with authorized access to the facility where the system resides; b. Issue authorization credentials for facility access; c. Review the access list detailing authorized facility access by individuals [Assignment: organization-defined frequency]; and d. Remove individuals from the facility access list when access is no longer required. | link | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-3 | NIST_SP_800-53_R5_PE-3 | NIST SP 800-53 Rev. 5 PE-3 | Physical and Environmental Protection | Physical Access Control | Shared | n/a | a. Enforce physical access authorizations at [Assignment: organization-defined entry and exit points to the facility where the system resides] by: 1. Verifying individual access authorizations before granting access to the facility; and 2. Controlling ingress and egress to the facility using [Selection (OneOrMore): [Assignment: organization-defined physical access control systems or devices] ;guards] ; b. Maintain physical access audit logs for [Assignment: organization-defined entry or exit points]; c. Control access to areas within the facility designated as publicly accessible by implementing the following controls: [Assignment: organization-defined physical access controls]; d. Escort visitors and control visitor activity [Assignment: organization-defined circumstances requiring visitor escorts and control of visitor activity]; e. Secure keys, combinations, and other physical access devices; f. Inventory [Assignment: organization-defined physical access devices] every [Assignment: organization-defined frequency]; and g. Change combinations and keys [Assignment: organization-defined frequency] and/or when keys are lost, combinations are compromised, or when individuals possessing the keys or combinations are transferred or terminated. | link | count: 004 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-4 | NIST_SP_800-53_R5_PE-4 | NIST SP 800-53 Rev. 5 PE-4 | Physical and Environmental Protection | Access Control for Transmission | Shared | n/a | Control physical access to [Assignment: organization-defined system distribution and transmission lines] within organizational facilities using [Assignment: organization-defined security controls]. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-5 | NIST_SP_800-53_R5_PE-5 | NIST SP 800-53 Rev. 5 PE-5 | Physical and Environmental Protection | Access Control for Output Devices | Shared | n/a | Control physical access to output from [Assignment: organization-defined output devices] to prevent unauthorized individuals from obtaining the output. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-6(1) | NIST_SP_800-53_R5_PE-6(1) | NIST SP 800-53 Rev. 5 PE-6 (1) | Physical and Environmental Protection | Intrusion Alarms and Surveillance Equipment | Shared | n/a | Monitor physical access to the facility where the system resides using physical intrusion alarms and surveillance equipment. | link | count: 002 Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PE-8 | NIST_SP_800-53_R5_PE-8 | NIST SP 800-53 Rev. 5 PE-8 | Physical and Environmental Protection | Visitor Access Records | Shared | n/a | a. Maintain visitor access records to the facility where the system resides for [Assignment: organization-defined time period]; b. Review visitor access records [Assignment: organization-defined frequency]; and c. Report anomalies in visitor access records to [Assignment: organization-defined personnel]. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PL-1 | NIST_SP_800-53_R5_PL-1 | NIST SP 800-53 Rev. 5 PL-1 | Planning | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] planning policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the planning policy and the associated planning controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the planning policy and procedures; and c. Review and update the current planning: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update planning policies and procedures (28aa060e-25c7-6121-05d8-a846f11433df) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PL-2 | NIST_SP_800-53_R5_PL-2 | NIST SP 800-53 Rev. 5 PL-2 | Planning | System Security and Privacy Plans | Shared | n/a | a. Develop security and privacy plans for the system that: 1. Are consistent with the organization???s enterprise architecture; 2. Explicitly define the constituent system components; 3. Describe the operational context of the system in terms of mission and business processes; 4. Identify the individuals that fulfill system roles and responsibilities; 5. Identify the information types processed, stored, and transmitted by the system; 6. Provide the security categorization of the system, including supporting rationale; 7. Describe any specific threats to the system that are of concern to the organization; 8. Provide the results of a privacy risk assessment for systems processing personally identifiable information; 9. Describe the operational environment for the system and any dependencies on or connections to other systems or system components; 10. Provide an overview of the security and privacy requirements for the system; 11. Identify any relevant control baselines or overlays, if applicable; 12. Describe the controls in place or planned for meeting the security and privacy requirements, including a rationale for any tailoring decisions; 13. Include risk determinations for security and privacy architecture and design decisions; 14. Include security- and privacy-related activities affecting the system that require planning and coordination with [Assignment: organization-defined individuals or groups]; and 15. Are reviewed and approved by the authorizing official or designated representative prior to plan implementation. b. Distribute copies of the plans and communicate subsequent changes to the plans to [Assignment: organization-defined personnel or roles]; c. Review the plans [Assignment: organization-defined frequency]; d. Update the plans to address changes to the system and environment of operation or problems identified during plan implementation or control assessments; and e. Protect the plans from unauthorized disclosure and modification. | link | count: 006 Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PL-4 | NIST_SP_800-53_R5_PL-4 | NIST SP 800-53 Rev. 5 PL-4 | Planning | Rules of Behavior | Shared | n/a | a. Establish and provide to individuals requiring access to the system, the rules that describe their responsibilities and expected behavior for information and system usage, security, and privacy; b. Receive a documented acknowledgment from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the system; c. Review and update the rules of behavior [Assignment: organization-defined frequency]; and d. Require individuals who have acknowledged a previous version of the rules of behavior to read and re-acknowledge [Selection (OneOrMore): [Assignment: organization-defined frequency] ;when the rules are revised or updated] . | link | count: 009 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PL-4(1) | NIST_SP_800-53_R5_PL-4(1) | NIST SP 800-53 Rev. 5 PL-4 (1) | Planning | Social Media and External Site/application Usage Restrictions | Shared | n/a | Include in the rules of behavior, restrictions on: (a) Use of social media, social networking sites, and external sites/applications; (b) Posting organizational information on public websites; and (c) Use of organization-provided identifiers (e.g., email addresses) and authentication secrets (e.g., passwords) for creating accounts on external sites/applications. | link | count: 001 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PL-8 | NIST_SP_800-53_R5_PL-8 | NIST SP 800-53 Rev. 5 PL-8 | Planning | Security and Privacy Architectures | Shared | n/a | a. Develop security and privacy architectures for the system that: 1. Describe the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information; 2. Describe the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals; 3. Describe how the architectures are integrated into and support the enterprise architecture; and 4. Describe any assumptions about, and dependencies on, external systems and services; b. Review and update the architectures [Assignment: organization-defined frequency] to reflect changes in the enterprise architecture; and c. Reflect planned architecture changes in security and privacy plans, Concept of Operations (CONOPS), criticality analysis, organizational procedures, and procurements and acquisitions. | link | count: 002 Develop a concept of operations (CONOPS) (e7422f08-65b4-50e4-3779-d793156e0079), Review and update the information security architecture (ced291b8-1d3d-7e27-40cf-829e9dd523c8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-1 | NIST_SP_800-53_R5_PS-1 | NIST SP 800-53 Rev. 5 PS-1 | Personnel Security | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] personnel security policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the personnel security policy and the associated personnel security controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the personnel security policy and procedures; and c. Review and update the current personnel security: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update personnel security policies and procedures (e5c5fc78-4aa5-3d6b-81bc-5fcc88b318e9) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-2 | NIST_SP_800-53_R5_PS-2 | NIST SP 800-53 Rev. 5 PS-2 | Personnel Security | Position Risk Designation | Shared | n/a | a. Assign a risk designation to all organizational positions; b. Establish screening criteria for individuals filling those positions; and c. Review and update position risk designations [Assignment: organization-defined frequency]. | link | count: 001 Assign risk designations (b7897ddc-9716-2460-96f7-7757ad038cc4) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-3 | NIST_SP_800-53_R5_PS-3 | NIST SP 800-53 Rev. 5 PS-3 | Personnel Security | Personnel Screening | Shared | n/a | a. Screen individuals prior to authorizing access to the system; and b. Rescreen individuals in accordance with [Assignment: organization-defined conditions requiring rescreening and, where rescreening is so indicated, the frequency of rescreening]. | link | count: 003 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Rescreen individuals at a defined frequency (c6aeb800-0b19-944d-92dc-59b893722329) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-3(3) | NIST_SP_800-53_R5_PS-3(3) | NIST SP 800-53 Rev. 5 PS-3 (3) | Personnel Security | Information Requiring Special Protective Measures | Shared | n/a | Verify that individuals accessing a system processing, storing, or transmitting information requiring special protection: (a) Have valid access authorizations that are demonstrated by assigned official government duties; and (b) Satisfy [Assignment: organization-defined additional personnel screening criteria]. | link | count: 001 Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-4 | NIST_SP_800-53_R5_PS-4 | NIST SP 800-53 Rev. 5 PS-4 | Personnel Security | Personnel Termination | Shared | n/a | Upon termination of individual employment: a. Disable system access within [Assignment: organization-defined time period]; b. Terminate or revoke any authenticators and credentials associated with the individual; c. Conduct exit interviews that include a discussion of [Assignment: organization-defined information security topics]; d. Retrieve all security-related organizational system-related property; and e. Retain access to organizational information and systems formerly controlled by terminated individual. | link | count: 005 Conduct exit interview upon termination (496b407d-9b9e-81e8-4ba4-44bc686b016a), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Protect against and prevent data theft from departing employees (80a97208-264e-79da-0cc7-4fca179a0c9c), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-4(2) | NIST_SP_800-53_R5_PS-4(2) | NIST SP 800-53 Rev. 5 PS-4 (2) | Personnel Security | Automated Actions | Shared | n/a | Use [Assignment: organization-defined automated mechanisms] to [Selection (OneOrMore): notify [Assignment: organization-defined personnel or roles] of individual termination actions;disable access to system resources] . | link | count: 001 Automate notification of employee termination (729c8708-2bec-093c-8427-2e87d2cd426d) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-5 | NIST_SP_800-53_R5_PS-5 | NIST SP 800-53 Rev. 5 PS-5 | Personnel Security | Personnel Transfer | Shared | n/a | a. Review and confirm ongoing operational need for current logical and physical access authorizations to systems and facilities when individuals are reassigned or transferred to other positions within the organization; b. Initiate [Assignment: organization-defined transfer or reassignment actions] within [Assignment: organization-defined time period following the formal transfer action]; c. Modify access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and d. Notify [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period]. | link | count: 004 Initiate transfer or reassignment actions (b8a9bb2f-7290-3259-85ce-dca7d521302d), Modify access authorizations upon personnel transfer (979ed3b6-83f9-26bc-4b86-5b05464700bf), Notify upon termination or transfer (c79d378a-2521-822a-0407-57454f8d2c74), Reevaluate access upon personnel transfer (e89436d8-6a93-3b62-4444-1d2a42ad56b2) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-6 | NIST_SP_800-53_R5_PS-6 | NIST SP 800-53 Rev. 5 PS-6 | Personnel Security | Access Agreements | Shared | n/a | a. Develop and document access agreements for organizational systems; b. Review and update the access agreements [Assignment: organization-defined frequency]; and c. Verify that individuals requiring access to organizational information and systems: 1. Sign appropriate access agreements prior to being granted access; and 2. Re-sign access agreements to maintain access to organizational systems when access agreements have been updated or [Assignment: organization-defined frequency]. | link | count: 005 Document organizational access agreements (c981fa70-2e58-8141-1457-e7f62ebc2ade), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Ensure access agreements are signed or resigned timely (e7589f4e-1e8b-72c2-3692-1e14d7f3699f), Require users to sign access agreement (3af53f59-979f-24a8-540f-d7cdbc366607), Update organizational access agreements (e21f91d1-2803-0282-5f2d-26ebc4b170ef) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-7 | NIST_SP_800-53_R5_PS-7 | NIST SP 800-53 Rev. 5 PS-7 | Personnel Security | External Personnel Security | Shared | n/a | a. Establish personnel security requirements, including security roles and responsibilities for external providers; b. Require external providers to comply with personnel security policies and procedures established by the organization; c. Document personnel security requirements; d. Require external providers to notify [Assignment: organization-defined personnel or roles] of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges, or who have system privileges within [Assignment: organization-defined time period]; and e. Monitor provider compliance with personnel security requirements. | link | count: 005 Document third-party personnel security requirements (b320aa42-33b4-53af-87ce-100091d48918), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Require notification of third-party personnel transfer or termination (afd5d60a-48d2-8073-1ec2-6687e22f2ddd), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | PS-8 | NIST_SP_800-53_R5_PS-8 | NIST SP 800-53 Rev. 5 PS-8 | Personnel Security | Personnel Sanctions | Shared | n/a | a. Employ a formal sanctions process for individuals failing to comply with established information security and privacy policies and procedures; and b. Notify [Assignment: organization-defined personnel or roles] within [Assignment: organization-defined time period] when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction. | link | count: 002 Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-1 | NIST_SP_800-53_R5_RA-1 | NIST SP 800-53 Rev. 5 RA-1 | Risk Assessment | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] risk assessment policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the risk assessment policy and the associated risk assessment controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the risk assessment policy and procedures; and c. Review and update the current risk assessment: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-2 | NIST_SP_800-53_R5_RA-2 | NIST SP 800-53 Rev. 5 RA-2 | Risk Assessment | Security Categorization | Shared | n/a | a. Categorize the system and information it processes, stores, and transmits; b. Document the security categorization results, including supporting rationale, in the security plan for the system; and c. Verify that the authorizing official or authorizing official designated representative reviews and approves the security categorization decision. | link | count: 004 Categorize information (93fa357f-2e38-22a9-5138-8cc5124e1923), Develop business classification schemes (11ba0508-58a8-44de-5f3a-9e05d80571da), Ensure security categorization is approved (6c79c3e5-5f7b-a48a-5c7b-8c158bc01115), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-3 | NIST_SP_800-53_R5_RA-3 | NIST SP 800-53 Rev. 5 RA-3 | Risk Assessment | Risk Assessment | Shared | n/a | a. Conduct a risk assessment, including: 1. Identifying threats to and vulnerabilities in the system; 2. Determining the likelihood and magnitude of harm from unauthorized access, use, disclosure, disruption, modification, or destruction of the system, the information it processes, stores, or transmits, and any related information; and 3. Determining the likelihood and impact of adverse effects on individuals arising from the processing of personally identifiable information; b. Integrate risk assessment results and risk management decisions from the organization and mission or business process perspectives with system-level risk assessments; c. Document risk assessment results in [Selection: security and privacy plans;risk assessment report; [Assignment: organization-defined document] ] ; d. Review risk assessment results [Assignment: organization-defined frequency]; e. Disseminate risk assessment results to [Assignment: organization-defined personnel or roles]; and f. Update the risk assessment [Assignment: organization-defined frequency] or when there are significant changes to the system, its environment of operation, or other conditions that may impact the security or privacy state of the system. | link | count: 004 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-5 | NIST_SP_800-53_R5_RA-5 | NIST SP 800-53 Rev. 5 RA-5 | Risk Assessment | Vulnerability Monitoring and Scanning | Shared | n/a | a. Monitor and scan for vulnerabilities in the system and hosted applications [Assignment: organization-defined frequency and/or randomly in accordance with organization-defined process] and when new vulnerabilities potentially affecting the system are identified and reported; b. Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: 1. Enumerating platforms, software flaws, and improper configurations; 2. Formatting checklists and test procedures; and 3. Measuring vulnerability impact; c. Analyze vulnerability scan reports and results from vulnerability monitoring; d. Remediate legitimate vulnerabilities [Assignment: organization-defined response times] in accordance with an organizational assessment of risk; e. Share information obtained from the vulnerability monitoring process and control assessments with [Assignment: organization-defined personnel or roles] to help eliminate similar vulnerabilities in other systems; and f. Employ vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned. | link | count: 021 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Regulatory Compliance, Security Center, SQL, Synapse | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-5(10) | NIST_SP_800-53_R5_RA-5(10) | NIST SP 800-53 Rev. 5 RA-5 (10) | Risk Assessment | Correlate Scanning Information | Shared | n/a | Correlate the output from vulnerability scanning tools to determine the presence of multi-vulnerability and multi-hop attack vectors. | link | count: 001 Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-5(2) | NIST_SP_800-53_R5_RA-5(2) | NIST SP 800-53 Rev. 5 RA-5 (2) | Risk Assessment | Update Vulnerabilities to Be Scanned | Shared | n/a | Update the system vulnerabilities to be scanned [Selection (OneOrMore): [Assignment: organization-defined frequency] ;prior to a new scan;when new vulnerabilities are identified and reported] . | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-5(3) | NIST_SP_800-53_R5_RA-5(3) | NIST SP 800-53 Rev. 5 RA-5 (3) | Risk Assessment | Breadth and Depth of Coverage | Shared | n/a | Define the breadth and depth of vulnerability scanning coverage. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-5(4) | NIST_SP_800-53_R5_RA-5(4) | NIST SP 800-53 Rev. 5 RA-5 (4) | Risk Assessment | Discoverable Information | Shared | n/a | Determine information about the system that is discoverable and take [Assignment: organization-defined corrective actions]. | link | count: 001 Take action in response to customer information (d25cbded-121e-0ed6-1857-dc698c9095b1) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-5(5) | NIST_SP_800-53_R5_RA-5(5) | NIST SP 800-53 Rev. 5 RA-5 (5) | Risk Assessment | Privileged Access | Shared | n/a | Implement privileged access authorization to [Assignment: organization-defined system components] for [Assignment: organization-defined vulnerability scanning activities]. | link | count: 001 Implement privileged access for executing vulnerability scanning activities (5b802722-71dd-a13d-2e7e-231e09589efb) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-5(6) | NIST_SP_800-53_R5_RA-5(6) | NIST SP 800-53 Rev. 5 RA-5 (6) | Risk Assessment | Automated Trend Analyses | Shared | n/a | Compare the results of multiple vulnerability scans using [Assignment: organization-defined automated mechanisms]. | link | count: 005 Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | RA-5(8) | NIST_SP_800-53_R5_RA-5(8) | NIST SP 800-53 Rev. 5 RA-5 (8) | Risk Assessment | Review Historic Audit Logs | Shared | n/a | Review historic audit logs to determine if a vulnerability identified in a [Assignment: organization-defined system] has been previously exploited within an [Assignment: organization-defined time period]. | link | count: 015 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review exploit protection events (a30bd8e9-7064-312a-0e1f-e1b485d59f6e), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-1 | NIST_SP_800-53_R5_SA-1 | NIST SP 800-53 Rev. 5 SA-1 | System and Services Acquisition | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] system and services acquisition policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the system and services acquisition policy and the associated system and services acquisition controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures; and c. Review and update the current system and services acquisition: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-10 | NIST_SP_800-53_R5_SA-10 | NIST SP 800-53 Rev. 5 SA-10 | System and Services Acquisition | Developer Configuration Management | Shared | n/a | Require the developer of the system, system component, or system service to: a. Perform configuration management during system, component, or service [Selection (OneOrMore): design;development;implementation;operation;disposal] ; b. Document, manage, and control the integrity of changes to [Assignment: organization-defined configuration items under configuration management]; c. Implement only organization-approved changes to the system, component, or service; d. Document approved changes to the system, component, or service and the potential security and privacy impacts of such changes; and e. Track security flaws and flaw resolution within the system, component, or service and report findings to [Assignment: organization-defined personnel]. | link | count: 009 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-10(1) | NIST_SP_800-53_R5_SA-10(1) | NIST SP 800-53 Rev. 5 SA-10 (1) | System and Services Acquisition | Software and Firmware Integrity Verification | Shared | n/a | Require the developer of the system, system component, or system service to enable integrity verification of software and firmware components. | link | count: 001 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-11 | NIST_SP_800-53_R5_SA-11 | NIST SP 800-53 Rev. 5 SA-11 | System and Services Acquisition | Developer Testing and Evaluation | Shared | n/a | Require the developer of the system, system component, or system service, at all post-design stages of the system development life cycle, to: a. Develop and implement a plan for ongoing security and privacy control assessments; b. Perform [Selection (OneOrMore): unit;integration;system;regression] testing/evaluation [Assignment: organization-defined frequency] at [Assignment: organization-defined depth and coverage]; c. Produce evidence of the execution of the assessment plan and the results of the testing and evaluation; d. Implement a verifiable flaw remediation process; and e. Correct flaws identified during testing and evaluation. | link | count: 003 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-15 | NIST_SP_800-53_R5_SA-15 | NIST SP 800-53 Rev. 5 SA-15 | System and Services Acquisition | Development Process, Standards, and Tools | Shared | n/a | a. Require the developer of the system, system component, or system service to follow a documented development process that: 1. Explicitly addresses security and privacy requirements; 2. Identifies the standards and tools used in the development process; 3. Documents the specific tool options and tool configurations used in the development process; and 4. Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and b. Review the development process, standards, tools, tool options, and tool configurations [Assignment: organization-defined frequency] to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: [Assignment: organization-defined security and privacy requirements]. | link | count: 001 Review development process, standards and tools (1e876c5c-0f2a-8eb6-69f7-5f91e7918ed6) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-16 | NIST_SP_800-53_R5_SA-16 | NIST SP 800-53 Rev. 5 SA-16 | System and Services Acquisition | Developer-provided Training | Shared | n/a | Require the developer of the system, system component, or system service to provide the following training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms: [Assignment: organization-defined training]. | link | count: 001 Require developers to provide training (676c3c35-3c36-612c-9523-36d266a65000) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-17 | NIST_SP_800-53_R5_SA-17 | NIST SP 800-53 Rev. 5 SA-17 | System and Services Acquisition | Developer Security and Privacy Architecture and Design | Shared | n/a | Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that: a. Is consistent with the organization???s security and privacy architecture that is an integral part the organization???s enterprise architecture; b. Accurately and completely describes the required security and privacy functionality, and the allocation of controls among physical and logical components; and c. Expresses how individual security and privacy functions, mechanisms, and services work together to provide required security and privacy capabilities and a unified approach to protection. | link | count: 003 Require developers to build security architecture (f131c8c5-a54a-4888-1efc-158928924bc1), Require developers to describe accurate security functionality (3e37c891-840c-3eb4-78d2-e2e0bb5063e0), Require developers to provide unified security protection approach (7a114735-a420-057d-a651-9a73cd0416ef) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-2 | NIST_SP_800-53_R5_SA-2 | NIST SP 800-53 Rev. 5 SA-2 | System and Services Acquisition | Allocation of Resources | Shared | n/a | a. Determine the high-level information security and privacy requirements for the system or system service in mission and business process planning; b. Determine, document, and allocate the resources required to protect the system or system service as part of the organizational capital planning and investment control process; and c. Establish a discrete line item for information security and privacy in organizational programming and budgeting documentation. | link | count: 006 Align business objectives and IT goals (ab02bb73-4ce1-89dd-3905-d93042809ba0), Allocate resources in determining information system requirements (90a156a6-49ed-18d1-1052-69aac27c05cd), Establish a discrete line item in budgeting documentation (06af77de-02ca-0f3e-838a-a9420fe466f5), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-3 | NIST_SP_800-53_R5_SA-3 | NIST SP 800-53 Rev. 5 SA-3 | System and Services Acquisition | System Development Life Cycle | Shared | n/a | a. Acquire, develop, and manage the system using [Assignment: organization-defined system development life cycle] that incorporates information security and privacy considerations; b. Define and document information security and privacy roles and responsibilities throughout the system development life cycle; c. Identify individuals having information security and privacy roles and responsibilities; and d. Integrate the organizational information security and privacy risk management process into system development life cycle activities. | link | count: 003 Define information security roles and responsibilities (ef5a7059-6651-73b1-18b3-75b1b79c1565), Identify individuals with security roles and responsibilities (0dcbaf2f-075e-947b-8f4c-74ecc5cd302c), Integrate risk management process into SDLC (00f12b6f-10d7-8117-9577-0f2b76488385) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-4 | NIST_SP_800-53_R5_SA-4 | NIST SP 800-53 Rev. 5 SA-4 | System and Services Acquisition | Acquisition Process | Shared | n/a | Include the following requirements, descriptions, and criteria, explicitly or by reference, using [Selection (OneOrMore): standardized contract language; [Assignment: organization-defined contract language] ] in the acquisition contract for the system, system component, or system service: a. Security and privacy functional requirements; b. Strength of mechanism requirements; c. Security and privacy assurance requirements; d. Controls needed to satisfy the security and privacy requirements. e. Security and privacy documentation requirements; f. Requirements for protecting security and privacy documentation; g. Description of the system development environment and environment in which the system is intended to operate; h. Allocation of responsibility or identification of parties responsible for information security, privacy, and supply chain risk management; and i. Acceptance criteria. | link | count: 011 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-4(1) | NIST_SP_800-53_R5_SA-4(1) | NIST SP 800-53 Rev. 5 SA-4 (1) | System and Services Acquisition | Functional Properties of Controls | Shared | n/a | Require the developer of the system, system component, or system service to provide a description of the functional properties of the controls to be implemented. | link | count: 001 Obtain functional properties of security controls (44b71aa8-099d-8b97-1557-0e853ec38e0d) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-4(10) | NIST_SP_800-53_R5_SA-4(10) | NIST SP 800-53 Rev. 5 SA-4 (10) | System and Services Acquisition | Use of Approved PIV Products | Shared | n/a | Employ only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational systems. | link | count: 001 Employ FIPS 201-approved technology for PIV (8b333332-6efd-7c0d-5a9f-d1eb95105214) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-4(2) | NIST_SP_800-53_R5_SA-4(2) | NIST SP 800-53 Rev. 5 SA-4 (2) | System and Services Acquisition | Design and Implementation Information for Controls | Shared | n/a | Require the developer of the system, system component, or system service to provide design and implementation information for the controls that includes: [Selection (OneOrMore): security-relevant external system interfaces;high-level design;low-level design;source code or hardware schematics; [Assignment: organization-defined design and implementation information] ] at [Assignment: organization-defined level of detail]. | link | count: 001 Obtain design and implementation information for the security controls (22a02c9a-49e4-5dc9-0d14-eb35ad717154) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-4(8) | NIST_SP_800-53_R5_SA-4(8) | NIST SP 800-53 Rev. 5 SA-4 (8) | System and Services Acquisition | Continuous Monitoring Plan for Controls | Shared | n/a | Require the developer of the system, system component, or system service to produce a plan for continuous monitoring of control effectiveness that is consistent with the continuous monitoring program of the organization. | link | count: 001 Obtain continuous monitoring plan for security controls (ca6d7878-3189-1833-4620-6c7254ed1607) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-4(9) | NIST_SP_800-53_R5_SA-4(9) | NIST SP 800-53 Rev. 5 SA-4 (9) | System and Services Acquisition | Functions, Ports, Protocols, and Services in Use | Shared | n/a | Require the developer of the system, system component, or system service to identify the functions, ports, protocols, and services intended for organizational use. | link | count: 001 Require developer to identify SDLC ports, protocols, and services (f6da5cca-5795-60ff-49e1-4972567815fe) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-5 | NIST_SP_800-53_R5_SA-5 | NIST SP 800-53 Rev. 5 SA-5 | System and Services Acquisition | System Documentation | Shared | n/a | a. Obtain or develop administrator documentation for the system, system component, or system service that describes: 1. Secure configuration, installation, and operation of the system, component, or service; 2. Effective use and maintenance of security and privacy functions and mechanisms; and 3. Known vulnerabilities regarding configuration and use of administrative or privileged functions; b. Obtain or develop user documentation for the system, system component, or system service that describes: 1. User-accessible security and privacy functions and mechanisms and how to effectively use those functions and mechanisms; 2. Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner and protect individual privacy; and 3. User responsibilities in maintaining the security of the system, component, or service and privacy of individuals; c. Document attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent and take [Assignment: organization-defined actions] in response; and d. Distribute documentation to [Assignment: organization-defined personnel or roles]. | link | count: 005 Distribute information system documentation (84a01872-5318-049e-061e-d56734183e84), Document customer-defined actions (8c44a0ea-9b09-4d9c-0e91-f9bee3d05bfb), Obtain Admin documentation (3f1216b0-30ee-1ac9-3899-63eb744e85f5), Obtain user security function documentation (be1c34ab-295a-07a6-785c-36f63c1d223e), Protect administrator and user documentation (09960521-759e-5d12-086f-4192a72a5e92) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-9 | NIST_SP_800-53_R5_SA-9 | NIST SP 800-53 Rev. 5 SA-9 | System and Services Acquisition | External System Services | Shared | n/a | a. Require that providers of external system services comply with organizational security and privacy requirements and employ the following controls: [Assignment: organization-defined controls]; b. Define and document organizational oversight and user roles and responsibilities with regard to external system services; and c. Employ the following processes, methods, and techniques to monitor control compliance by external service providers on an ongoing basis: [Assignment: organization-defined processes, methods, and techniques]. | link | count: 004 Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-9(1) | NIST_SP_800-53_R5_SA-9(1) | NIST SP 800-53 Rev. 5 SA-9 (1) | System and Services Acquisition | Risk Assessments and Organizational Approvals | Shared | n/a | (a) Conduct an organizational assessment of risk prior to the acquisition or outsourcing of information security services; and (b) Verify that the acquisition or outsourcing of dedicated information security services is approved by [Assignment: organization-defined personnel or roles]. | link | count: 002 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Obtain approvals for acquisitions and outsourcing (92b94485-1c49-3350-9ada-dffe94f08e87) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-9(2) | NIST_SP_800-53_R5_SA-9(2) | NIST SP 800-53 Rev. 5 SA-9 (2) | System and Services Acquisition | Identification of Functions, Ports, Protocols, and Services | Shared | n/a | Require providers of the following external system services to identify the functions, ports, protocols, and other services required for the use of such services: [Assignment: organization-defined external system services]. | link | count: 001 Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-9(4) | NIST_SP_800-53_R5_SA-9(4) | NIST SP 800-53 Rev. 5 SA-9 (4) | System and Services Acquisition | Consistent Interests of Consumers and Providers | Shared | n/a | Take the following actions to verify that the interests of [Assignment: organization-defined external service providers] are consistent with and reflect organizational interests: [Assignment: organization-defined actions]. | link | count: 001 Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SA-9(5) | NIST_SP_800-53_R5_SA-9(5) | NIST SP 800-53 Rev. 5 SA-9 (5) | System and Services Acquisition | Processing, Storage, and Service Location | Shared | n/a | Restrict the location of [Selection (OneOrMore): information processing;information or data;system services] to [Assignment: organization-defined locations] based on [Assignment: organization-defined requirements or conditions]. | link | count: 001 Restrict location of information processing, storage and services (0040d2e5-2779-170d-6a2c-1f5fca353335) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-1 | NIST_SP_800-53_R5_SC-1 | NIST SP 800-53 Rev. 5 SC-1 | System and Communications Protection | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] system and communications protection policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the system and communications protection policy and the associated system and communications protection controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the system and communications protection policy and procedures; and c. Review and update the current system and communications protection: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-10 | NIST_SP_800-53_R5_SC-10 | NIST SP 800-53 Rev. 5 SC-10 | System and Communications Protection | Network Disconnect | Shared | n/a | Terminate the network connection associated with a communications session at the end of the session or after [Assignment: organization-defined time period] of inactivity. | link | count: 001 Reauthenticate or terminate a user session (d6653f89-7cb5-24a4-9d71-51581038231b) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-12 | NIST_SP_800-53_R5_SC-12 | NIST SP 800-53 Rev. 5 SC-12 | System and Communications Protection | Cryptographic Key Establishment and Management | Shared | n/a | Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: [Assignment: organization-defined requirements for key generation, distribution, storage, access, and destruction]. | link | count: 040 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) (47031206-ce96-41f8-861b-6a915f3de284), Azure API for FHIR should use a customer-managed key to encrypt data at rest (051cba44-2429-45b9-9649-46cec11c7119), Azure Automation accounts should use customer-managed keys to encrypt data at rest (56a5ee18-2ae6-4810-86f7-18e39ce5629b), Azure Batch account should use customer-managed keys to encrypt data (99e9ccd8-3db9-4592-b0d1-14b1715a4d8a), Azure Container Instance container group should use customer-managed key for encryption (0aa61e00-0a01-4a3c-9945-e93cffedf0e6), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password (86efb160-8de7-451d-bc08-5d475b0aadae), Azure Data Explorer encryption at rest should use a customer-managed key (81e74cea-30fd-40d5-802f-d72103c2aaaa), Azure data factories should be encrypted with a customer-managed key (4ec52d6d-beb7-40c4-9a9e-fe753254690e), Azure HDInsight clusters should use customer-managed keys to encrypt data at rest (64d314f6-6062-4780-a861-c23e8951bee5), Azure HDInsight clusters should use encryption at host to encrypt data at rest (1fd32ebd-e4c3-4e13-a54a-d7422d4d95f6), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Stream Analytics jobs should use customer-managed keys to encrypt data (87ba29ef-1ab3-4d82-b763-87fcd4f531f7), Azure Synapse workspaces should use customer-managed keys to encrypt data at rest (f7d52b2d-e161-4dfa-a82b-55e564167385), Bot Service should be encrypted with a customer-managed key (51522a96-0869-4791-82f3-981000c2c67f), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Event Hub namespaces should use a customer-managed key for encryption (a1ad735a-e96f-45d2-a7b2-9a4932cab7ec), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Logic Apps Integration Service Environment should be encrypted with customer-managed keys (1fafeaf6-7927-4059-a50a-8eb2a7a6f2b5), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), OS and data disks should be encrypted with a customer-managed key (702dd420-7fcc-42c5-afe8-4026edd20fe0), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Service Bus Premium namespaces should use a customer-managed key for encryption (295fc8b1-dc9f-4f53-9c61-3f313ceab40a), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
API for FHIR, Automation, Azure Data Explorer, Backup, Batch, Bot Service, Cognitive Services, Compute, Container Instance, Container Registry, Cosmos DB, Data Box, Data Factory, Event Hub, HDInsight, Internet of Things, Kubernetes, Logic Apps, Machine Learning, Monitoring, Regulatory Compliance, Service Bus, SQL, Storage, Stream Analytics, Synapse | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-12(1) | NIST_SP_800-53_R5_SC-12(1) | NIST SP 800-53 Rev. 5 SC-12 (1) | System and Communications Protection | Availability | Shared | n/a | Maintain availability of information in the event of the loss of cryptographic keys by users. | link | count: 001 Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-12(2) | NIST_SP_800-53_R5_SC-12(2) | NIST SP 800-53 Rev. 5 SC-12 (2) | System and Communications Protection | Symmetric Keys | Shared | n/a | Produce, control, and distribute symmetric cryptographic keys using [Selection: NIST FIPS-validated;NSA-approved] key management technology and processes. | link | count: 001 Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-12(3) | NIST_SP_800-53_R5_SC-12(3) | NIST SP 800-53 Rev. 5 SC-12 (3) | System and Communications Protection | Asymmetric Keys | Shared | n/a | Produce, control, and distribute asymmetric cryptographic keys using [Selection: NSA-approved key management technology and processes;prepositioned keying material;DoD-approved or DoD-issued Medium Assurance PKI certificates;DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user???s private key;certificates issued in accordance with organization-defined requirements] . | link | count: 001 Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-13 | NIST_SP_800-53_R5_SC-13 | NIST SP 800-53 Rev. 5 SC-13 | System and Communications Protection | Cryptographic Protection | Shared | n/a | a. Determine the [Assignment: organization-defined cryptographic uses]; and b. Implement the following types of cryptography required for each specified cryptographic use: [Assignment: organization-defined types of cryptography for each specified cryptographic use]. | link | count: 001 Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-15 | NIST_SP_800-53_R5_SC-15 | NIST SP 800-53 Rev. 5 SC-15 | System and Communications Protection | Collaborative Computing Devices and Applications | Shared | n/a | a. Prohibit remote activation of collaborative computing devices and applications with the following exceptions: [Assignment: organization-defined exceptions where remote activation is to be allowed]; and b. Provide an explicit indication of use to users physically present at the devices. | link | count: 002 Explicitly notify use of collaborative computing devices (62fa14f0-4cbe-762d-5469-0899a99b98aa), Prohibit remote activation of collaborative computing devices (678ca228-042d-6d8e-a598-c58d5670437d) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-17 | NIST_SP_800-53_R5_SC-17 | NIST SP 800-53 Rev. 5 SC-17 | System and Communications Protection | Public Key Infrastructure Certificates | Shared | n/a | a. Issue public key certificates under an [Assignment: organization-defined certificate policy] or obtain public key certificates from an approved service provider; and b. Include only approved trust anchors in trust stores or certificate stores managed by the organization. | link | count: 001 Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-18 | NIST_SP_800-53_R5_SC-18 | NIST SP 800-53 Rev. 5 SC-18 | System and Communications Protection | Mobile Code | Shared | n/a | a. Define acceptable and unacceptable mobile code and mobile code technologies; and b. Authorize, monitor, and control the use of mobile code within the system. | link | count: 003 Authorize, monitor, and control usage of mobile code technologies (291f20d4-8d93-1d73-89f3-6ce28b825563), Define acceptable and unacceptable mobile code technologies (1afada58-8b34-7ac2-a38a-983218635201), Establish usage restrictions for mobile code technologies (ffdaa742-0d6f-726f-3eac-6e6c34e36c93) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-2 | NIST_SP_800-53_R5_SC-2 | NIST SP 800-53 Rev. 5 SC-2 | System and Communications Protection | Separation of System and User Functionality | Shared | n/a | Separate user functionality, including user interface services, from system management functionality. | link | count: 003 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Separate user and information system management functionality (8a703eb5-4e53-701b-67e4-05ba2f7930c8), Use dedicated machines for administrative tasks (b8972f60-8d77-1cb8-686f-9c9f4cdd8a59) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-20 | NIST_SP_800-53_R5_SC-20 | NIST SP 800-53 Rev. 5 SC-20 | System and Communications Protection | Secure Name/address Resolution Service (authoritative Source) | Shared | n/a | a. Provide additional data origin authentication and integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries; and b. Provide the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace. | link | count: 002 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Provide secure name and address resolution services (bbb2e6d6-085f-5a35-a55d-e45daad38933) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-21 | NIST_SP_800-53_R5_SC-21 | NIST SP 800-53 Rev. 5 SC-21 | System and Communications Protection | Secure Name/address Resolution Service (recursive or Caching Resolver) | Shared | n/a | Request and perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources. | link | count: 002 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-22 | NIST_SP_800-53_R5_SC-22 | NIST SP 800-53 Rev. 5 SC-22 | System and Communications Protection | Architecture and Provisioning for Name/address Resolution Service | Shared | n/a | Ensure the systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal and external role separation. | link | count: 001 Implement a fault tolerant name/address service (ced727b3-005e-3c5b-5cd5-230b79d56ee8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-23 | NIST_SP_800-53_R5_SC-23 | NIST SP 800-53 Rev. 5 SC-23 | System and Communications Protection | Session Authenticity | Shared | n/a | Protect the authenticity of communications sessions. | link | count: 002 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce random unique session identifiers (c7d57a6a-7cc2-66c0-299f-83bf90558f5d) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-23(1) | NIST_SP_800-53_R5_SC-23(1) | NIST SP 800-53 Rev. 5 SC-23 (1) | System and Communications Protection | Invalidate Session Identifiers at Logout | Shared | n/a | Invalidate session identifiers upon user logout or other session termination. | link | count: 001 Invalidate session identifiers at logout (396f465d-375e-57de-58ba-021adb008191) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-24 | NIST_SP_800-53_R5_SC-24 | NIST SP 800-53 Rev. 5 SC-24 | System and Communications Protection | Fail in Known State | Shared | n/a | Fail to a [Assignment: organization-defined known system state] for the following failures on the indicated components while preserving [Assignment: organization-defined system state information] in failure: [Assignment: list of organization-defined types of system failures on organization-defined system components]. | link | count: 001 Ensure information system fails in known state (12af7c7a-92af-9e96-0d0c-5e732d1a3751) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-28 | NIST_SP_800-53_R5_SC-28 | NIST SP 800-53 Rev. 5 SC-28 | System and Communications Protection | Protection of Information at Rest | Shared | n/a | Protect the [Selection (OneOrMore): confidentiality;integrity] of the following information at rest: [Assignment: organization-defined information at rest]. | link | count: 017 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-28(1) | NIST_SP_800-53_R5_SC-28(1) | NIST SP 800-53 Rev. 5 SC-28 (1) | System and Communications Protection | Cryptographic Protection | Shared | n/a | Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on [Assignment: organization-defined system components or media]: [Assignment: organization-defined information]. | link | count: 017 App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Stack Edge devices should use double-encryption (b4ac1030-89c5-4697-8e00-28b5ba6a8811), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Azure Data Explorer, Azure Stack Edge, Compute, Data Box, Kubernetes, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-3 | NIST_SP_800-53_R5_SC-3 | NIST SP 800-53 Rev. 5 SC-3 | System and Communications Protection | Security Function Isolation | Shared | n/a | Isolate security functions from nonsecurity functions. | link | count: 004 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-39 | NIST_SP_800-53_R5_SC-39 | NIST SP 800-53 Rev. 5 SC-39 | System and Communications Protection | Process Isolation | Shared | n/a | Maintain a separate execution domain for each executing system process. | link | count: 001 Maintain separate execution domains for running processes (bfc540fe-376c-2eef-4355-121312fa4437) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-5 | NIST_SP_800-53_R5_SC-5 | NIST SP 800-53 Rev. 5 SC-5 | System and Communications Protection | Denial-of-service Protection | Shared | n/a | a. [Selection: Protect against;Limit] the effects of the following types of denial-of-service events: [Assignment: organization-defined types of denial-of-service events]; and b. Employ the following controls to achieve the denial-of-service objective: [Assignment: organization-defined controls by type of denial-of-service event]. | link | count: 005 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Develop and document a DDoS response plan (b7306e73-0494-83a2-31f5-280e934a8f70), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Network, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-6 | NIST_SP_800-53_R5_SC-6 | NIST SP 800-53 Rev. 5 SC-6 | System and Communications Protection | Resource Availability | Shared | n/a | Protect the availability of resources by allocating [Assignment: organization-defined resources] by [Selection (OneOrMore): priority;quota; [Assignment: organization-defined controls] ] . | link | count: 003 Govern the allocation of resources (33d34fac-56a8-1c0f-0636-3ed94892a709), Manage availability and capacity (edcc36f1-511b-81e0-7125-abee29752fe7), Secure commitment from leadership (70057208-70cc-7b31-3c3a-121af6bc1966) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7 | NIST_SP_800-53_R5_SC-7 | NIST SP 800-53 Rev. 5 SC-7 | System and Communications Protection | Boundary Protection | Shared | n/a | a. Monitor and control communications at the external managed interfaces to the system and at key internal managed interfaces within the system; b. Implement subnetworks for publicly accessible system components that are [Selection: physically;logically] separated from internal organizational networks; and c. Connect to external networks or systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture. | link | count: 053 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Regulatory Compliance, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7(12) | NIST_SP_800-53_R5_SC-7(12) | NIST SP 800-53 Rev. 5 SC-7 (12) | System and Communications Protection | Host-based Protection | Shared | n/a | Implement [Assignment: organization-defined host-based boundary protection mechanisms] at [Assignment: organization-defined system components]. | link | count: 001 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7(13) | NIST_SP_800-53_R5_SC-7(13) | NIST SP 800-53 Rev. 5 SC-7 (13) | System and Communications Protection | Isolation of Security Tools, Mechanisms, and Support Components | Shared | n/a | Isolate [Assignment: organization-defined information security tools, mechanisms, and support components] from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system. | link | count: 001 Isolate SecurID systems, Security Incident Management systems (dd6d00a8-701a-5935-a22b-c7b9c0c698b2) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7(18) | NIST_SP_800-53_R5_SC-7(18) | NIST SP 800-53 Rev. 5 SC-7 (18) | System and Communications Protection | Fail Secure | Shared | n/a | Prevent systems from entering unsecure states in the event of an operational failure of a boundary protection device. | link | count: 002 Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage transfers between standby and active system components (df54d34f-65f3-39f1-103c-a0464b8615df) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7(20) | NIST_SP_800-53_R5_SC-7(20) | NIST SP 800-53 Rev. 5 SC-7 (20) | System and Communications Protection | Dynamic Isolation and Segregation | Shared | n/a | Provide the capability to dynamically isolate [Assignment: organization-defined system components] from other system components. | link | count: 001 Ensure system capable of dynamic isolation of resources (83eea3d3-0d2c-9ccd-1021-2111b29b2a62) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7(21) | NIST_SP_800-53_R5_SC-7(21) | NIST SP 800-53 Rev. 5 SC-7 (21) | System and Communications Protection | Isolation of System Components | Shared | n/a | Employ boundary protection mechanisms to isolate [Assignment: organization-defined system components] supporting [Assignment: organization-defined missions and/or business functions]. | link | count: 001 Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7(3) | NIST_SP_800-53_R5_SC-7(3) | NIST SP 800-53 Rev. 5 SC-7 (3) | System and Communications Protection | Access Points | Shared | n/a | Limit the number of external network connections to the system. | link | count: 052 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Cache, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7(4) | NIST_SP_800-53_R5_SC-7(4) | NIST SP 800-53 Rev. 5 SC-7 (4) | System and Communications Protection | External Telecommunications Services | Shared | n/a | (a) Implement a managed interface for each external telecommunication service; (b) Establish a traffic flow policy for each managed interface; (c) Protect the confidentiality and integrity of the information being transmitted across each interface; (d) Document each exception to the traffic flow policy with a supporting mission or business need and duration of that need; (e) Review exceptions to the traffic flow policy [Assignment: organization-defined frequency] and remove exceptions that are no longer supported by an explicit mission or business need; (f) Prevent unauthorized exchange of control plane traffic with external networks; (g) Publish information to enable remote networks to detect unauthorized control plane traffic from internal networks; and (h) Filter unauthorized control plane traffic from external networks. | link | count: 003 Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7(7) | NIST_SP_800-53_R5_SC-7(7) | NIST SP 800-53 Rev. 5 SC-7 (7) | System and Communications Protection | Split Tunneling for Remote Devices | Shared | n/a | Prevent split tunneling for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using [Assignment: organization-defined safeguards]. | link | count: 001 Prevent split tunneling for remote devices (66e5cb69-9f1c-8b8d-8fbd-b832466d5aa8) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-7(8) | NIST_SP_800-53_R5_SC-7(8) | NIST SP 800-53 Rev. 5 SC-7 (8) | System and Communications Protection | Route Traffic to Authenticated Proxy Servers | Shared | n/a | Route [Assignment: organization-defined internal communications traffic] to [Assignment: organization-defined external networks] through authenticated proxy servers at managed interfaces. | link | count: 001 Route traffic through authenticated proxy network (d91558ce-5a5c-551b-8fbb-83f793255e09) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-8 | NIST_SP_800-53_R5_SC-8 | NIST SP 800-53 Rev. 5 SC-8 | System and Communications Protection | Transmission Confidentiality and Integrity | Shared | n/a | Protect the [Selection (OneOrMore): confidentiality;integrity] of transmitted information. | link | count: 015 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, Regulatory Compliance, SQL, Storage | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SC-8(1) | NIST_SP_800-53_R5_SC-8(1) | NIST SP 800-53 Rev. 5 SC-8 (1) | System and Communications Protection | Cryptographic Protection | Shared | n/a | Implement cryptographic mechanisms to [Selection (OneOrMore): prevent unauthorized disclosure of information;detect changes to information] during transmission. | link | count: 014 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, HDInsight, Kubernetes, Regulatory Compliance, SQL, Storage | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-1 | NIST_SP_800-53_R5_SI-1 | NIST SP 800-53 Rev. 5 SI-1 | System and Information Integrity | Policy and Procedures | Shared | n/a | a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (OneOrMore): Organization-level;Mission/business process-level;System-level] system and information integrity policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the system and information integrity policy and the associated system and information integrity controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the system and information integrity policy and procedures; and c. Review and update the current system and information integrity: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | link | count: 001 Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-10 | NIST_SP_800-53_R5_SI-10 | NIST SP 800-53 Rev. 5 SI-10 | System and Information Integrity | Information Input Validation | Shared | n/a | Check the validity of the following information inputs: [Assignment: organization-defined information inputs to the system]. | link | count: 001 Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-11 | NIST_SP_800-53_R5_SI-11 | NIST SP 800-53 Rev. 5 SI-11 | System and Information Integrity | Error Handling | Shared | n/a | a. Generate error messages that provide information necessary for corrective actions without revealing information that could be exploited; and b. Reveal error messages only to [Assignment: organization-defined personnel or roles]. | link | count: 002 Generate error messages (c2cb4658-44dc-9d11-3dad-7c6802dd5ba3), Reveal error messages (20762f1e-85fb-31b0-a600-e833633f10fe) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-12 | NIST_SP_800-53_R5_SI-12 | NIST SP 800-53 Rev. 5 SI-12 | System and Information Integrity | Information Management and Retention | Shared | n/a | Manage and retain information within the system and information output from the system in accordance with applicable laws, executive orders, directives, regulations, policies, standards, guidelines and operational requirements. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-16 | NIST_SP_800-53_R5_SI-16 | NIST SP 800-53 Rev. 5 SI-16 | System and Information Integrity | Memory Protection | Shared | n/a | Implement the following controls to protect the system memory from unauthorized code execution: [Assignment: organization-defined controls]. | link | count: 002 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-2 | NIST_SP_800-53_R5_SI-2 | NIST SP 800-53 Rev. 5 SI-2 | System and Information Integrity | Flaw Remediation | Shared | n/a | a. Identify, report, and correct system flaws; b. Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation; c. Install security-relevant software and firmware updates within [Assignment: organization-defined time period] of the release of the updates; and d. Incorporate flaw remediation into the organizational configuration management process. | link | count: 019 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
App Service, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-2(2) | NIST_SP_800-53_R5_SI-2(2) | NIST SP 800-53 Rev. 5 SI-2 (2) | System and Information Integrity | Automated Flaw Remediation Status | Shared | n/a | Determine if system components have applicable security-relevant software and firmware updates installed using [Assignment: organization-defined automated mechanisms] [Assignment: organization-defined frequency]. | link | count: 002 Automate flaw remediation (a90c4d44-7fac-8e02-6d5b-0d92046b20e6), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-2(3) | NIST_SP_800-53_R5_SI-2(3) | NIST SP 800-53 Rev. 5 SI-2 (3) | System and Information Integrity | Time to Remediate Flaws and Benchmarks for Corrective Actions | Shared | n/a | (a) Measure the time between flaw identification and flaw remediation; and (b) Establish the following benchmarks for taking corrective actions: [Assignment: organization-defined benchmarks]. | link | count: 002 Establish benchmarks for flaw remediation (dd2523d5-2db3-642b-a1cf-83ac973b32c2), Measure the time between flaw identification and flaw remediation (dad1887d-161b-7b61-2e4d-5124a7b5724e) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-2(6) | NIST_SP_800-53_R5_SI-2(6) | NIST SP 800-53 Rev. 5 SI-2 (6) | System and Information Integrity | Removal of Previous Versions of Software and Firmware | Customer | n/a | Remove previous versions of [Assignment: organization-defined software and firmware components] after updated versions have been installed. | link | count: 003 App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c) |
App Service, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-3 | NIST_SP_800-53_R5_SI-3 | NIST SP 800-53 Rev. 5 SI-3 | System and Information Integrity | Malicious Code Protection | Shared | n/a | a. Implement [Selection (OneOrMore): signature based;non-signature based] malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code; b. Automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy and procedures; c. Configure malicious code protection mechanisms to: 1. Perform periodic scans of the system [Assignment: organization-defined frequency] and real-time scans of files from external sources at [Selection (OneOrMore): endpoint;network entry and exit points] as the files are downloaded, opened, or executed in accordance with organizational policy; and 2. [Selection (OneOrMore): block malicious code;quarantine malicious code;take [Assignment: organization-defined action] ] ; and send alert to [Assignment: organization-defined personnel or roles] in response to malicious code detection; and d. Address the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system. | link | count: 011 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Regulatory Compliance, Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-4 | NIST_SP_800-53_R5_SI-4 | NIST SP 800-53 Rev. 5 SI-4 | System and Information Integrity | System Monitoring | Shared | n/a | a. Monitor the system to detect: 1. Attacks and indicators of potential attacks in accordance with the following monitoring objectives: [Assignment: organization-defined monitoring objectives]; and 2. Unauthorized local, network, and remote connections; b. Identify unauthorized use of the system through the following techniques and methods: [Assignment: organization-defined techniques and methods]; c. Invoke internal monitoring capabilities or deploy monitoring devices: 1. Strategically within the system to collect organization-determined essential information; and 2. At ad hoc locations within the system to track specific types of transactions of interest to the organization; d. Analyze detected events and anomalies; e. Adjust the level of system monitoring activity when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation; f. Obtain legal opinion regarding system monitoring activities; and g. Provide [Assignment: organization-defined system monitoring information] to [Assignment: organization-defined personnel or roles] [Selection (OneOrMore): as needed; [Assignment: organization-defined frequency] ] . | link | count: 025 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
Kubernetes, Monitoring, Network, Regulatory Compliance, Security Center, SQL | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-4(12) | NIST_SP_800-53_R5_SI-4(12) | NIST SP 800-53 Rev. 5 SI-4 (12) | System and Information Integrity | Automated Organization-generated Alerts | Customer | n/a | Alert [Assignment: organization-defined personnel or roles] using [Assignment: organization-defined automated mechanisms] when the following indications of inappropriate or unusual activities with security or privacy implications occur: [Assignment: organization-defined activities that trigger alerts]. | link | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-4(14) | NIST_SP_800-53_R5_SI-4(14) | NIST SP 800-53 Rev. 5 SI-4 (14) | System and Information Integrity | Wireless Intrusion Detection | Shared | n/a | Employ a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises or breaches to the system. | link | count: 001 Document wireless access security controls (8f835d6a-4d13-9a9c-37dc-176cebd37fda) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-4(2) | NIST_SP_800-53_R5_SI-4(2) | NIST SP 800-53 Rev. 5 SI-4 (2) | System and Information Integrity | Automated Tools and Mechanisms for Real-time Analysis | Shared | n/a | Employ automated tools and mechanisms to support near real-time analysis of events. | link | count: 002 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-4(22) | NIST_SP_800-53_R5_SI-4(22) | NIST SP 800-53 Rev. 5 SI-4 (22) | System and Information Integrity | Unauthorized Network Services | Shared | n/a | (a) Detect network services that have not been authorized or approved by [Assignment: organization-defined authorization or approval processes]; and (b) [Selection (OneOrMore): Audit;Alert [Assignment: organization-defined personnel or roles] ] when detected. | link | count: 001 Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-4(24) | NIST_SP_800-53_R5_SI-4(24) | NIST SP 800-53 Rev. 5 SI-4 (24) | System and Information Integrity | Indicators of Compromise | Shared | n/a | Discover, collect, and distribute to [Assignment: organization-defined personnel or roles], indicators of compromise provided by [Assignment: organization-defined sources]. | link | count: 001 Discover any indicators of compromise (07b42fb5-027e-5a3c-4915-9d9ef3020ec7) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-4(4) | NIST_SP_800-53_R5_SI-4(4) | NIST SP 800-53 Rev. 5 SI-4 (4) | System and Information Integrity | Inbound and Outbound Communications Traffic | Shared | n/a | (a) Determine criteria for unusual or unauthorized activities or conditions for inbound and outbound communications traffic; (b) Monitor inbound and outbound communications traffic [Assignment: organization-defined frequency] for [Assignment: organization-defined unusual or unauthorized activities or conditions]. | link | count: 004 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-4(5) | NIST_SP_800-53_R5_SI-4(5) | NIST SP 800-53 Rev. 5 SI-4 (5) | System and Information Integrity | System-generated Alerts | Shared | n/a | Alert [Assignment: organization-defined personnel or roles] when the following system-generated indications of compromise or potential compromise occur: [Assignment: organization-defined compromise indicators]. | link | count: 003 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-5 | NIST_SP_800-53_R5_SI-5 | NIST SP 800-53 Rev. 5 SI-5 | System and Information Integrity | Security Alerts, Advisories, and Directives | Shared | n/a | a. Receive system security alerts, advisories, and directives from [Assignment: organization-defined external organizations] on an ongoing basis; b. Generate internal security alerts, advisories, and directives as deemed necessary; c. Disseminate security alerts, advisories, and directives to: [Selection (OneOrMore): [Assignment: organization-defined personnel or roles] ; [Assignment: organization-defined elements within the organization] ; [Assignment: organization-defined external organizations] ] ; and d. Implement security directives in accordance with established time frames, or notify the issuing organization of the degree of noncompliance. | link | count: 004 Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Generate internal security alerts (171e377b-5224-4a97-1eaa-62a3b5231dac), Implement security directives (26d178a4-9261-6f04-a100-47ed85314c6e) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-5(1) | NIST_SP_800-53_R5_SI-5(1) | NIST SP 800-53 Rev. 5 SI-5 (1) | System and Information Integrity | Automated Alerts and Advisories | Shared | n/a | Broadcast security alert and advisory information throughout the organization using [Assignment: organization-defined automated mechanisms]. | link | count: 001 Use automated mechanisms for security alerts (b8689b2e-4308-a58b-a0b4-6f3343a000df) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-6 | NIST_SP_800-53_R5_SI-6 | NIST SP 800-53 Rev. 5 SI-6 | System and Information Integrity | Security and Privacy Function Verification | Shared | n/a | a. Verify the correct operation of [Assignment: organization-defined security and privacy functions]; b. Perform the verification of the functions specified in SI-6a [Selection (OneOrMore): [Assignment: organization-defined system transitional states] ;upon command by user with appropriate privilege; [Assignment: organization-defined frequency] ] ; c. Alert [Assignment: organization-defined personnel or roles] to failed security and privacy verification tests; and d. [Selection (OneOrMore): Shut the system down;Restart the system; [Assignment: organization-defined alternative action(s)] ] when anomalies are discovered. | link | count: 004 Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Notify personnel of any failed security verification tests (18e9d748-73d4-0c96-55ab-b108bfbd5bc3), Perform security function verification at a defined frequency (f30edfad-4e1d-1eef-27ee-9292d6d89842), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-7 | NIST_SP_800-53_R5_SI-7 | NIST SP 800-53 Rev. 5 SI-7 | System and Information Integrity | Software, Firmware, and Information Integrity | Shared | n/a | a. Employ integrity verification tools to detect unauthorized changes to the following software, firmware, and information: [Assignment: organization-defined software, firmware, and information]; and b. Take the following actions when unauthorized changes to the software, firmware, and information are detected: [Assignment: organization-defined actions]. | link | count: 001 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-7(1) | NIST_SP_800-53_R5_SI-7(1) | NIST SP 800-53 Rev. 5 SI-7 (1) | System and Information Integrity | Integrity Checks | Shared | n/a | Perform an integrity check of [Assignment: organization-defined software, firmware, and information] [Selection (OneOrMore): at startup;at [Assignment: organization-defined transitional states or security-relevant events] ; [Assignment: organization-defined frequency] ] . | link | count: 002 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NIST_SP_800-53_R5 | SI-7(5) | NIST_SP_800-53_R5_SI-7(5) | NIST SP 800-53 Rev. 5 SI-7 (5) | System and Information Integrity | Automated Response to Integrity Violations | Shared | n/a | Automatically [Selection (OneOrMore): shut the system down;restart the system;implement [Assignment: organization-defined controls] ] when integrity violations are discovered. | link | count: 001 Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4) |
Regulatory Compliance | NIST SP 800-53 Rev. 5 (179d1daa-458f-4e47-8086-2a68d0d6c38f) |
| NZ_ISM_v3.5 | AC-11 | NZ_ISM_v3.5_AC-11 | NZISM Security Benchmark AC-11 | Access Control and Passwords | 16.4.30 Privileged Access Management | Customer | n/a | A fundamental part of any security policy is the inclusion of requirements for the treatment of Privileged Accounts. This is most conveniently contained in a Privileged Access Management (PAM) section within the agency???s security policy. A PAM policy is a fundamental component of an agency???s IT Governance. | link | count: 007 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center, SQL | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | AC-13 | NZ_ISM_v3.5_AC-13 | NZISM Security Benchmark AC-13 | Access Control and Passwords | 16.5.10 Authentication | Customer | n/a | Authenticating remote system users and devices ensures that only authorised system users and devices are allowed to connect to agency systems. | link | count: 001 Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023) |
Guest Configuration | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | AC-17 | NZ_ISM_v3.5_AC-17 | NZISM Security Benchmark AC-17 | Access Control and Passwords | 16.6.8 Logging Requirements | Customer | n/a | Event logging can help raise the security posture of a system by increasing the accountability for all system user actions. | link | count: 001 Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17) |
Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | AC-18 | NZ_ISM_v3.5_AC-18 | NZISM Security Benchmark AC-18 | Access Control and Passwords | 16.6.9 Events to be logged | Customer | n/a | The events to be logged are key elements in the monitoring of the security posture of systems and contributing to reviews, audits, investigations and incident management. | link | count: 019 App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Disconnections should be logged for PostgreSQL database servers. (eb6f77b9-bd53-4e35-a23d-7f65d5f0e446), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Log connections should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e442), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Kubernetes Service should be enabled (245fc9df-fa96-4414-9a0b-3738c2f7341c), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743) |
App Service, Batch, Data Lake, Event Hub, General, Internet of Things, Key Vault, Kubernetes, Logic Apps, Search, Security Center, Service Bus, SQL, Stream Analytics | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | AC-19 | NZ_ISM_v3.5_AC-19 | NZISM Security Benchmark AC-19 | Access Control and Passwords | 16.6.12 Event log protection | Customer | n/a | Effective log protection and storage (possibly involving the use of a dedicated event logging server) will help ensure the integrity and availability of the collected logs when they are audited. | link | count: 001 Storage account containing the container with activity logs must be encrypted with BYOK (fbb99e8e-e444-4da0-9ff1-75c92f5a85b2) |
Monitoring | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | AC-2 | NZ_ISM_v3.5_AC-2 | NZISM Security Benchmark AC-2 | Access Control and Passwords | 16.1.32 System User Identitfication | Customer | n/a | Having uniquely identifiable system users ensures accountability. | link | count: 003 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Service Fabric | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | AC-3 | NZ_ISM_v3.5_AC-3 | NZISM Security Benchmark AC-3 | Access Control and Passwords | 16.1.35 Methods for system user identification and authentication | Customer | n/a | A personal identification number is typically short in length and employs a small character set, making it susceptible to brute force attacks. | link | count: 001 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4) |
Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | AC-5 | NZ_ISM_v3.5_AC-5 | NZISM Security Benchmark AC-5 | Access Control and Passwords | 16.1.46 Suspension of access | Customer | n/a | Locking a system user account after a specified number of failed logon attempts will reduce the risk of brute force attacks. Removing a system user account when it is no longer required will prevent personnel from accessing their old account and reduce the number of accounts that an attacker can target. Suspending inactive accounts after a specified number of days will reduce the number of accounts that an attacker can target. Investigating repeated account lockouts will reduce the security risk of any ongoing brute force logon attempts and allow security management to act accordingly. | link | count: 002 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be) |
Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | AC-9 | NZ_ISM_v3.5_AC-9 | NZISM Security Benchmark AC-9 | Access Control and Passwords | 16.3.5 Use of Privileged Accounts | Customer | n/a | Inappropriate use of any feature or facility of a system that enables a privileged user to override system or application controls can be a major contributory factor to failures, information security incidents, or system breaches. | link | count: 001 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c) |
Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | CR-10 | NZ_ISM_v3.5_CR-10 | NZISM Security Benchmark CR-10 | Cryptography | 17.5.7 Authentication mechanisms | Customer | n/a | Public key-based systems have greater potential for strong authentication, put simply, people are not able to remember particularly strong passwords. Password-based authentication schemes are also more susceptible to interception than public key-based authentication schemes. | link | count: 001 Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6) |
Guest Configuration | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | CR-15 | NZ_ISM_v3.5_CR-15 | NZISM Security Benchmark CR-15 | Cryptography | 17.9.25 Contents of KMPs | Customer | n/a | When agencies implement the recommended contents for Key Management Plans (KMPs) they will have a good starting point for the protection of cryptographic systems and their material within their agencies. | link | count: 004 IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274) |
Key Vault, Security Center, SQL | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | CR-2 | NZ_ISM_v3.5_CR-2 | NZISM Security Benchmark CR-2 | Cryptography | 17.1.52 Data Recovery | Customer | n/a | It is important for continuity and operational stability that cryptographic products provide a means of data recovery to allow for the recovery of data in circumstances such as where the encryption key is unavailable due to loss, damage or failure. This includes production, storage, backup and virtual systems. This is sometimes described as ???key escrow???. | link | count: 002 Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Key Vault | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | CR-3 | NZ_ISM_v3.5_CR-3 | NZISM Security Benchmark CR-3 | Cryptography | 17.1.53 Reducing storage and physical transfer requirements | Customer | n/a | When encryption is applied to media or media residing within IT equipment it provides an additional layer of defence. Whilst such measures do not reduce or alter the classification of the information itself, physical storage, handling and transfer requirements may be reduced to those of a lesser classification for the media or equipment (but not the data itself). | link | count: 012 Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Automation, Cognitive Services, Container Registry, Cosmos DB, Machine Learning, Security Center, Service Fabric, SQL, Storage | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | CR-5 | NZ_ISM_v3.5_CR-5 | NZISM Security Benchmark CR-5 | Cryptography | 17.2.24 Using RSA | Customer | n/a | A modulus of at least 3072 bits for RSA is considered good practice by the cryptographic community. | link | count: 001 Certificates using RSA cryptography should have the specified minimum key size (cee51871-e572-4576-855c-047c820360f0) |
Key Vault | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | CR-8 | NZ_ISM_v3.5_CR-8 | NZISM Security Benchmark CR-8 | Cryptography | 17.4.16 Using TLS | Customer | n/a | Whilst version 1.0 of SSL was never released, version 2.0 had significant security flaws leading to the development of SSL 3.0. SSL has since been superseded by TLS with the latest version being TLS 1.3 which was released in August 2018. SSL is no longer an approved cryptographic protocol | link | count: 003 App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Guest Configuration | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | GS-2 | NZ_ISM_v3.5_GS-2 | NZISM Security Benchmark GS-2 | Gateway security | 19.1.11 Using Gateways | Customer | n/a | Physically locating all gateway components inside a secure server room will reduce the risk of unauthorised access to the device(s). The system owner of the higher security domain of connected security domains would be most familiar with the controls required to protect the more sensitive information and as such is best placed to manage any shared components of gateways. In some cases where multiple security domains from different agencies are connected to a gateway, it may be more appropriate to have a qualified third party manage the gateway on behalf of all connected agencies. Gateway components may also reside in a virtual environment ??? refer to Section 22.2 ??? Virtualisation and Section 22.3 ??? Virtual Local Area Networks | link | count: 010 All authorization rules except RootManageSharedAccessKey should be removed from Service Bus namespace (a1817ec0-a368-432a-8057-8371e17ac6ee), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure Key Vault Managed HSM should have purge protection enabled (c39ba22d-4428-4149-b981-70acb31fc383), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage account keys should not be expired (044985bb-afe1-42cd-8a36-9d5d42424537) |
Key Vault, Security Center, Service Bus, SQL, Storage | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | GS-3 | NZ_ISM_v3.5_GS-3 | NZISM Security Benchmark GS-3 | Gateway security | 19.1.12 Configuration of Gateways | Customer | n/a | Gateways are essential in controlling the flow of information between security domains. Any failure, particularly at the higher classifications, may have serious consequences. Hence mechanisms for alerting personnel to situations that may give rise to information security incidents are especially important for gateways. | link | count: 006 All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517) |
Azure Ai Services, Container Registry, Cosmos DB, Security Center, Storage | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | GS-5 | NZ_ISM_v3.5_GS-5 | NZISM Security Benchmark GS-5 | Gateway security | 19.1.23 Testing of Gateways | Customer | n/a | The testing of security measures on gateways will assist in ensuring that the integrity of the gateway is being maintained. An attacker who is aware of the regular testing schedule may cease malicious activities during such periods to avoid detection. Any test should, therefore, be unannounced and conducted at irregular intervals. | link | count: 001 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6) |
Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | INF-9 | NZ_ISM_v3.5_INF-9 | NZISM Security Benchmark INF-9 | Infrastructure | 10.8.35 Security Architecture | Customer | n/a | It is important that the principles of separation and segregation as well as the system classification are incorporated into the overall security architecture to maximise design and operational efficiency and to provide and support essential security to the network design. | link | count: 017 API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint connections on Batch accounts should be enabled (009a0c92-f5b4-4776-9b66-4ed2b4775563), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API Management, App Configuration, App Platform, Batch, Container Registry, Event Grid, Kubernetes, Machine Learning, Security Center, SQL, Storage, VM Image Builder | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | ISI-2 | NZ_ISM_v3.5_ISI-2 | NZISM Security Benchmark ISI-2 | Information Security Incidents | 7.1.7 Preventing and detecting information security incidents | Customer | n/a | Processes and procedures for the detection of information security incidents will assist in mitigating attacks using the most common vectors in systems exploits. Automated tools are only as good as their implementation and the level of analysis they perform. If tools are not configured to assess all areas of potential security risk then some vulnerabilities or attacks will not be detected. In addition, if tools are not regularly updated, including updates for new vulnerabilities and attack methods, their effectiveness will be reduced. | link | count: 011 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4) |
Security Center, SQL | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | ISM-3 | NZ_ISM_v3.5_ISM-3 | NZISM Security Benchmark ISM-3 | Information security monitoring | 6.2.5 Conducting vulnerability assessments | Customer | n/a | A baseline or known point of origin is the basis of any comparison and allows measurement of changes and improvements when further information security monitoring activities are conducted. | link | count: 003 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | ISM-4 | NZ_ISM_v3.5_ISM-4 | NZISM Security Benchmark ISM-4 | Information security monitoring | 6.2.6 Resolving vulnerabilities | Customer | n/a | Vulnerabilities may occur as a result of poorly designed or implemented information security practices, accidental activities or malicious activities, and not just as the result of a technical issue. | link | count: 010 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center, SQL | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | ISM-7 | NZ_ISM_v3.5_ISM-7 | NZISM Security Benchmark ISM-7 | Information security monitoring | 6.4.5 Availability requirements | Customer | n/a | Availability and recovery requirements will vary based on each agency???s business needs and are likely to be widely variable across government. Agencies will determine their own availability and recovery requirements and implement measures consistent with the agency's SRMP to achieve them as part of their risk management and governance processes. | link | count: 001 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56) |
Compute | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | NS-5 | NZ_ISM_v3.5_NS-5 | NZISM Security Benchmark NS-5 | Network security | 18.3.19 Content of a Denial of Service (DoS) response plan | Customer | n/a | An VTC or IPT DoS response plan will need to address the following: how to identify the source of the DoS, either internal or external (location and content of logs); how to diagnose the incident or attack type and attack method; how to minimise the effect on VTC or IPT, of a DoS of the data network (e.g. Internet or internal DoS), including separate links to other office locations for VTC and IPT and/or quality of service prioritisation; strategies that can mitigate the DOS (banning certain devices/Ips at the call controller and firewalls, implementing quality of service, changing VoIP authentication, changing dial-in authentication; and alternative communication options (such as designated devices or personal mobile phones) that have been identified for use in case of an emergency. | link | count: 001 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd) |
Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | NS-7 | NZ_ISM_v3.5_NS-7 | NZISM Security Benchmark NS-7 | Network security | 18.4.7 Intrusion Detection and Prevention strategy (IDS/IPS) | Customer | n/a | An IDS/IPS when configured correctly, kept up to date and supported by appropriate processes, can be an effective way of identifying, responding to and containing known attack types, specific attack profiles or anomalous or suspicious network activities. | link | count: 001 Connection throttling should be enabled for PostgreSQL database servers (5345bb39-67dc-4960-a1bf-427e16b9a0bd) |
SQL | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | NS-8 | NZ_ISM_v3.5_NS-8 | NZISM Security Benchmark NS-8 | Network security | 18.4.8 IDS/IPSs on gateways | Customer | n/a | If the firewall is configured to block all traffic on a particular range of port numbers, then the IDS should inspect traffic for these port numbers and alert if they are detected. | link | count: 004 Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8) |
Network | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | PRS-5 | NZ_ISM_v3.5_PRS-5 | NZISM Security Benchmark PRS-5 | Product Security | 12.4.4 Patching vulnerabilities in products | Customer | n/a | The assurance provided by an evaluation is related to the date at which the results were issued. Over the course of a normal product lifecycle, patches are released to address known security vulnerabilities. Applying these patches should be considered as part of an agency???s overall risk management strategy. Given the potential threat vectors and the value of the classified information being protected, high assurance products MUST NOT be patched by an agency without specific direction from the GCSB. If a patch is released for a high assurance product, the GCSB will conduct an assessment of the patch and might revise the product???s usage guidance. Likewise, for patches released for HGCE, the GCSB will subsequently conduct an assessment of the cryptographic vulnerability and might revise usage guidance in the consumer guide for the product. | link | count: 002 System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | PS-4 | NZ_ISM_v3.5_PS-4 | NZISM Security Benchmark PS-4 | Physical Security | 8.3.5 Network infrastructure in unsecure areas | Customer | n/a | As agencies lose control over classified information when it is communicated over unsecure public network infrastructure or over infrastructure in unsecure areas they MUST ensure that it is encrypted to a sufficient level that if it was captured that it would be sufficiently difficult to determine the original information from the encrypted information. | link | count: 002 Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
Cache, Storage | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | SS-2 | NZ_ISM_v3.5_SS-2 | NZISM Security Benchmark SS-2 | Software security | 14.1.8 Developing hardened SOEs | Customer | n/a | Antivirus and anti-malware software, while an important defensive measure, can be defeated by malicious code that has yet to be identified by antivirus vendors. This can include targeted attacks, where a new virus is engineered or an existing one modified to defeat the signature-based detection schemes. The use of antivirus and anti-malware software, while adding value to the defence of workstations, cannot be relied solely upon to protect the workstation. As such agencies still need to deploy appropriately hardened SOEs to assist with the protection of workstations against a broader range of security risks. | link | count: 003 App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917) |
App Service, Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | SS-3 | NZ_ISM_v3.5_SS-3 | NZISM Security Benchmark SS-3 | Software security | 14.1.9 Maintaining hardened SOEs | Customer | n/a | Whilst a SOE can be sufficiently hardened when it is deployed, its security will progressively degrade over time. Agencies can address the degradation of the security of a SOE by ensuring that patches are continually applied, system users are not able to disable or bypass security functionality and antivirus and other security software is appropriately maintained with the latest signatures and updates. End Point Agents monitor traffic and apply security policies on applications, storage interfaces and data in real-time. Administrators actively block or monitor and log policy breaches. The End Point Agent can also create forensic monitoring to facilitate incident investigation. End Point Agents can monitor user activity, such as the cut, copy, paste, print, print screen operations and copying data to external drives and other devices. The Agent can then apply policies to limit such activity. | link | count: 017 Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Endpoint protection health issues should be resolved on your machines (8e42c1f2-a2ab-49bc-994a-12bcd0dc4ac2), Endpoint protection should be installed on your machines (1f7c564c-0a90-4d44-b7e1-9d456cffaee8), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Kubernetes clusters should disable automounting API credentials (423dd1ba-798e-40e4-9c4d-b6902674b423), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Kubernetes clusters should not grant CAP_SYS_ADMIN security capabilities (d2e7ea85-6b44-4317-a0be-1b951587f626), Kubernetes clusters should not use the default namespace (9f061a12-e40d-4183-a00e-171812443373), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
API for FHIR, Guest Configuration, Kubernetes, Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | SS-5 | NZ_ISM_v3.5_SS-5 | NZISM Security Benchmark SS-5 | Software security | 14.2.4 Application Whitelisting | Customer | n/a | Application whitelisting can be an effective mechanism to prevent the successful compromise of an agency system resulting from the exploitation of a vulnerability in an application or the execution of malicious code. Defining a list of trusted executables, a whitelist, is a practical and secure method of securing a system rather than relying on a list of bad executables (black list) to be prevented from running. Application whitelisting is considered only one part of a defence-in-depth strategy in order to prevent a successful attack, or to help mitigate consequences arising from an attack. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZ_ISM_v3.5 | SS-9 | NZ_ISM_v3.5_SS-9 | NZISM Security Benchmark SS-9 | Software security | 14.5.8 Web applications | Customer | n/a | The Open Web Application Security Project guide provides a comprehensive resource to consult when developing Web applications. | link | count: 012 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have authentication enabled (95bccee9-a7f8-4bec-9ee9-62c3473701fc), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Function apps should have authentication enabled (c75248c1-ea1d-4a9c-8fc9-29a6aabd5da8), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c) |
App Service | [Deprecated]: New Zealand ISM Restricted v3.5 (93d2179e-3068-c82f-2428-d614ae836a04) |
| NZISM_Security_Benchmark_v1.1 | AC-11 | NZISM_Security_Benchmark_v1.1_AC-11 | NZISM Security Benchmark AC-11 | Access Control and Passwords | 16.4.30 Privileged Access Management | Customer | Agencies MUST establish a Privileged Access Management (PAM) policy. Within the context of agency operations, the agency’s PAM policy MUST define: a privileged account; and privileged access. Agencies MUST manage Privileged Accounts in accordance with the Agency’s PAM Policy. | A fundamental part of any security policy is the inclusion of requirements for the treatment of Privileged Accounts. This is most conveniently contained in a Privileged Access Management (PAM) section within the agency’s security policy. A PAM policy is a fundamental component of an agency’s IT Governance. | link | count: 009 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit Windows machines missing any of specified members in the Administrators group (30f71ea1-ac77-4f26-9fc5-2d926bbd4ba7), Audit Windows machines that have extra accounts in the Administrators group (3d2a3320-2a72-4c67-ac5f-caa40fbee2b2), Audit Windows machines that have the specified members in the Administrators group (69bf4abd-ca1e-4cf6-8b5a-762d42e61d4f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Security Center, SQL | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | AC-13 | NZISM_Security_Benchmark_v1.1_AC-13 | NZISM Security Benchmark AC-13 | Access Control and Passwords | 16.5.10 Authentication | Customer | Agencies MUST authenticate each remote connection and user prior to permitting access to an agency system. | Authenticating remote system users and devices ensures that only authorised system users and devices are allowed to connect to agency systems. | link | count: 001 Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023) |
Guest Configuration | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | AC-17 | NZISM_Security_Benchmark_v1.1_AC-17 | NZISM Security Benchmark AC-17 | Access Control and Passwords | 16.6.9 Events to be logged | Customer | Agencies MUST log, at minimum, the following events for all software components: logons; failed logon attempts; logoffs; date and time; all privileged operations; failed attempts to elevate privileges; security related system alerts and failures; system user and group additions, deletions and modification to permissions; and unauthorised or failed access attempts to systems and files identified as critical to the agency. | The events to be logged are key elements in the monitoring of the security posture of systems and contributing to reviews, audits, investigations and incident management. | link | count: 014 App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45) |
App Service, Batch, Data Lake, Event Hub, General, Internet of Things, Key Vault, Logic Apps, Monitoring, Search, Service Bus, SQL, Stream Analytics | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | AC-2 | NZISM_Security_Benchmark_v1.1_AC-2 | NZISM Security Benchmark AC-2 | Access Control and Passwords | 16.1.32 System User Identitfication | Customer | Agencies must ensure that all users are: - uniquely identifiable - authenticated on each occasion that access is granted to a system. | Having uniquely identifiable system users ensures accountability. | link | count: 003 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
App Service, Service Fabric | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | AC-3 | NZISM_Security_Benchmark_v1.1_AC-3 | NZISM Security Benchmark AC-3 | Access Control and Passwords | 16.1.35 Methods for system user identification and authentication | Customer | Agencies SHOULD ensure that they combine the use of multiple methods when identifying and authenticating system users. | A personal identification number is typically short in length and employs a small character set, making it susceptible to brute force attacks. | link | count: 001 Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4) |
Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | AC-4 | NZISM_Security_Benchmark_v1.1_AC-4 | NZISM Security Benchmark AC-4 | Access Control and Passwords | 16.1.40 Password selection policy | Customer | Agencies SHOULD implement a password policy enforcing either: a minimum password length of 16 characters with no complexity requirement; or -a minimum password length of ten characters, consisting of atleast three of the following character sets: - lowercase characters (a-z); - uppercase characters (A-Z); - digits (0-9); and - punctuation and special characters. | Passwords are the primary authentication mechanism for almost all information systems and are fundamental part of access and authentication processes and mechanisms. While there are some limitations in the use of passwords, they remain the most cost effective means available with current technology. Passwords are subject to three principal groups of risks: Intentional password sharing; Password theft, loss or compromise; and Password guessing and cracking. Associated with these risk groups are four principal methods of attacking passwords: Interactive attempts including password guessing, brute force attacks or some knowledge of the user or agency. Obtaining the password through social engineering or phishing. Compromising the password through oversight, observation, use of keyloggers, cameras etc. Cracking through network traffic interception, misconfiguration, malware, data capture etc. For example a simple eight-letter password can today be brute-forced in minutes by software freely available on the Internet. Password controls are designed to manage these risks and attack methods using the controls specified in this section. For example, passwords with at least ten characters utilising upper and lower case, numbers and special characters have a much greater resistance to brute force attacks. When use in combination with controls such as password history and regular password change, passwords can present high resistance to known attack methods. | link | count: 002 Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Windows machines should meet requirements for 'Security Settings - Account Policies' (f2143251-70de-4e81-87a8-36cee5a2f29d) |
Guest Configuration | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | AC-5 | NZISM_Security_Benchmark_v1.1_AC-5 | NZISM Security Benchmark AC-5 | Access Control and Passwords | 16.1.46 Suspension of access | Customer | Agencies SHOULD: lock system user accounts after three failed logon attempts; have a system administrator reset locked accounts; remove or suspend system user accounts as soon as possible when personnel no longer need access due to changing roles or leaving the agency; and remove or suspend inactive accounts after a specified number of days. | Locking a system user account after a specified number of failed logon attempts will reduce the risk of brute force attacks. Removing a system user account when it is no longer required will prevent personnel from accessing their old account and reduce the number of accounts that an attacker can target. Suspending inactive accounts after a specified number of days will reduce the number of accounts that an attacker can target. Investigating repeated account lockouts will reduce the security risk of any ongoing brute force logon attempts and allow security management to act accordingly. | link | count: 002 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be) |
Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | AC-9 | NZISM_Security_Benchmark_v1.1_AC-9 | NZISM Security Benchmark AC-9 | Access Control and Passwords | 16.3.5 Use of Privileged Accounts | Customer | Agencies SHOULD: - ensure strong change management practices are implemented; - ensure that the use of privileged accounts is controlled and accountable; - ensure that system administrators are assigned an individual account for the performance of their administration tasks; -keep privileged accounts to a minimum; and allow the use of privileged accounts for administrative work only. | Inappropriate use of any feature or facility of a system that enables a privileged user to override system or application controls can be a major contributory factor to failures, information security incidents, or system breaches. | link | count: 001 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c) |
Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | CR-14 | NZISM_Security_Benchmark_v1.1_CR-14 | NZISM Security Benchmark CR-14 | Cryptography | 17.9.25 Contents of KMPs | Customer | The list below describes the minimum contents which SHOULD be documented in the KMP: Objectives of the KMP System Description Roles and Administrative responsibilities Accounting Classification Information Security Incidents Key Management Maintenance References | When agencies implement the recommended contents for Key Management Plans (KMPs) they will have a good starting point for the protection of cryptographic systems and their material within their agencies. | link | count: 002 IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274) |
Security Center, SQL | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | CR-2 | NZISM_Security_Benchmark_v1.1_CR-2 | NZISM Security Benchmark CR-2 | Cryptography | 17.1.45 Data Recovery | Customer | Cryptographic products SHOULD provide a means of data recovery to allow for recovery of data in circumstances where the encryption key is unavailable due to loss, damage or failure. | It is important for continuity and operational stability that cryptographic products provide a means of data recovery to allow for the recovery of data in circumstances such as where the encryption key is unavailable due to loss, damage or failure. This includes production, storage, backup and virtual systems. This is sometimes described as “key escrow”. | link | count: 002 Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Key Vault | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | CR-3 | NZISM_Security_Benchmark_v1.1_CR-3 | NZISM Security Benchmark CR-3 | Cryptography | 17.1.46 Reducing storage and physical transfer requirements | Customer | If an agency wishes to use encryption to reduce the storage or physical transfer requirements for IT equipment or media that contains classified information, they SHOULD use: full disk encryption; or partial disk encryption where the access control will only allow writing to the encrypted partition holding the classified information. | When encryption is applied to media or media residing within IT equipment it provides an additional layer of defence. Whilst such measures do not reduce or alter the classification of the information itself, physical storage, handling and transfer requirements may be reduced to those of a lesser classification for the media or equipment (but not the data itself). | link | count: 011 Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Cognitive Services, Container Registry, Cosmos DB, Machine Learning, Security Center, SQL, Storage | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | CR-7 | NZISM_Security_Benchmark_v1.1_CR-7 | NZISM Security Benchmark CR-7 | Cryptography | 17.4.16 Using TLS | Customer | Agencies SHOULD use the current version of TLS. | Whilst version 1.0 of SSL was never released, version 2.0 had significant security flaws leading to the development of SSL 3.0. SSL has since been superseded by TLS with the latest version being TLS 1.3 which was released in August 2018. SSL is no longer an approved cryptographic protocol | link | count: 005 App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Guest Configuration | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | CR-9 | NZISM_Security_Benchmark_v1.1_CR-9 | NZISM Security Benchmark CR-9 | Cryptography | 17.5.7 Authentication mechanisms | Customer | Agencies SHOULD use public key-based authentication before using password-based authentication. | Public key-based systems have greater potential for strong authentication, put simply, people are not able to remember particularly strong passwords. Password-based authentication schemes are also more susceptible to interception than public key-based authentication schemes. | link | count: 001 Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6) |
Guest Configuration | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | DM-6 | NZISM_Security_Benchmark_v1.1_DM-6 | NZISM Security Benchmark DM-6 | Data management | 20.4.4 Database files | Customer | Agencies SHOULD protect database files from access that bypass normal access controls. | Even though a database may provide access controls to stored data, the database files themselves MUST also be protected. | link | count: 002 Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9) |
SQL | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | GS-2 | NZISM_Security_Benchmark_v1.1_GS-2 | NZISM Security Benchmark GS-2 | Gateway security | 19.1.11 Using Gateways | Customer | Agencies MUST ensure that: all agency networks are protected from networks in other security domains by one or more gateways; all gateways contain mechanisms to filter or limit data flow at the network and content level to only the information necessary for business purposes; and all gateway components, discrete and virtual, are physically located within an appropriately secured server room. | Physically locating all gateway components inside a secure server room will reduce the risk of unauthorised access to the device(s). The system owner of the higher security domain of connected security domains would be most familiar with the controls required to protect the more sensitive information and as such is best placed to manage any shared components of gateways. In some cases where multiple security domains from different agencies are connected to a gateway, it may be more appropriate to have a qualified third party manage the gateway on behalf of all connected agencies. Gateway components may also reside in a virtual environment – refer to Section 22.2 – Virtualisation and Section 22.3 – Virtual Local Area Networks | link | count: 008 All authorization rules except RootManageSharedAccessKey should be removed from Service Bus namespace (a1817ec0-a368-432a-8057-8371e17ac6ee), Azure Key Vault Managed HSM should have purge protection enabled (c39ba22d-4428-4149-b981-70acb31fc383), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage account keys should not be expired (044985bb-afe1-42cd-8a36-9d5d42424537) |
Key Vault, Security Center, Service Bus, SQL, Storage | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | GS-3 | NZISM_Security_Benchmark_v1.1_GS-3 | NZISM Security Benchmark GS-3 | Gateway security | 19.1.12 Configuration of Gateways | Customer | Agencies MUST ensure that gateways: are the only communications paths into and out of internal networks; by default, deny all connections into and out of the network; allow only explicitly authorised connections; are managed via a secure path isolated from all connected networks (i.e. physically at the gateway or on a dedicated administration network); provide sufficient logging and audit capabilities to detect information security incidents, attempted intrusions or anomalous usage patterns; and provide real-time alerts. | Gateways are essential in controlling the flow of information between security domains. Any failure, particularly at the higher classifications, may have serious consequences. Hence mechanisms for alerting personnel to situations that may give rise to information security incidents are especially important for gateways. | link | count: 006 All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517) |
Azure Ai Services, Container Registry, Cosmos DB, Security Center, Storage | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | GS-5 | NZISM_Security_Benchmark_v1.1_GS-5 | NZISM Security Benchmark GS-5 | Gateway security | 19.1.23 Testing of Gateways | Customer | Agencies SHOULD ensure that testing of security measures is performed at random intervals no more than six months apart. | The testing of security measures on gateways will assist in ensuring that the integrity of the gateway is being maintained. An attacker who is aware of the regular testing schedule may cease malicious activities during such periods to avoid detection. Any test should, therefore, be unannounced and conducted at irregular intervals. | link | count: 001 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6) |
Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | INF-9 | NZISM_Security_Benchmark_v1.1_INF-9 | NZISM Security Benchmark INF-9 | Infrastructure | 10.8.35 Security Architecture | Customer | Security architectures MUST apply the principles of separation and segregation. | It is important that the principles of separation and segregation as well as the system classification are incorporated into the overall security architecture to maximise design and operational efficiency and to provide and support essential security to the network design. | link | count: 016 API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint connections on Batch accounts should be enabled (009a0c92-f5b4-4776-9b66-4ed2b4775563), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API Management, App Configuration, App Platform, Batch, Container Registry, Event Grid, Machine Learning, SignalR, SQL, Storage, VM Image Builder | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | ISM-3 | NZISM_Security_Benchmark_v1.1_ISM-3 | NZISM Security Benchmark ISM-3 | Information security monitoring | 6.2.5 Conducting vulnerability assessments | Customer | Agencies should conduct vulnerability assessments on systems: - before the system is deployed, including conducting assessments during the system design and development stages - after a significant change to the system - after significant changes to the threats or risks faced by a system; for example, a software vendor announces a critical vulnerability in a product used by the agency at least annually, or as specified by an ITSM or the system owner. | A baseline or known point of origin is the basis of any comparison and allows measurement of changes and improvements when further information security monitoring activities are conducted. | link | count: 003 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | ISM-4 | NZISM_Security_Benchmark_v1.1_ISM-4 | NZISM Security Benchmark ISM-4 | Information security monitoring | 6.2.6 Resolving vulnerabilities | Customer | Agencies SHOULD analyse and treat all vulnerabilities and subsequent security risks to their systems identified during a vulnerability assessment. | Vulnerabilities may occur as a result of poorly designed or implemented information security practices, accidental activities or malicious activities, and not just as the result of a technical issue. | link | count: 005 SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | ISM-7 | NZISM_Security_Benchmark_v1.1_ISM-7 | NZISM Security Benchmark ISM-7 | Information security monitoring | 6.4.5 Availability requirements | Customer | Agencies MUST determine availability and recovery requirements for their systems and implement measures consistent with the agency's SRMP to support them. | Availability and recovery requirements will vary based on each agency’s business needs and are likely to be widely variable across government. Agencies will determine their own availability and recovery requirements and implement measures consistent with the agency's SRMP to achieve them as part of their risk management and governance processes. | link | count: 001 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56) |
Compute | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | NS-5 | NZISM_Security_Benchmark_v1.1_NS-5 | NZISM Security Benchmark NS-5 | Network security | 18.3.19 Content of a Denial of Service (DoS) response plan | Customer | A Denial of Service response plan SHOULD include monitoring and use of: . router and switch logging and flow data; . packet captures; . proxy and call manager logs and access control lists; . VTC and IPT aware firewalls and voice gateways; . network redundancy; . load balancing; . PSTN failover; and . alternative communication paths. | An VTC or IPT DoS response plan will need to address the following: how to identify the source of the DoS, either internal or external (location and content of logs); how to diagnose the incident or attack type and attack method; how to minimise the effect on VTC or IPT, of a DoS of the data network (e.g. Internet or internal DoS), including separate links to other office locations for VTC and IPT and/or quality of service prioritisation; strategies that can mitigate the DOS (banning certain devices/Ips at the call controller and firewalls, implementing quality of service, changing VoIP authentication, changing dial-in authentication; and alternative communication options (such as designated devices or personal mobile phones) that have been identified for use in case of an emergency. | link | count: 001 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd) |
Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | NS-7 | NZISM_Security_Benchmark_v1.1_NS-7 | NZISM Security Benchmark NS-7 | Network security | 18.4.8 IDS/IPSs on gateways | Customer | Agencies SHOULD deploy IDS/IPSs in all gateways between the agency’s networks and unsecure public networks or BYOD wireless networks. Agencies SHOULD deploy IDS/IPSs at all gateways between the agency’s networks and any network not managed by the agency. Agencies SHOULD locate IDS/IPSs within the gateway environment, immediately inside the outermost firewall. | If the firewall is configured to block all traffic on a particular range of port numbers, then the IDS should inspect traffic for these port numbers and alert if they are detected. | link | count: 003 Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8) |
Network | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | PRS-5 | NZISM_Security_Benchmark_v1.1_PRS-5 | NZISM Security Benchmark PRS-5 | Product Security | 12.4.4 Patching vulnerabilities in products | Customer | Agencies SHOULD ensure that security patches are applied through a vendor recommended patch or upgrade process. | The assurance provided by an evaluation is related to the date at which the results were issued. Over the course of a normal product lifecycle, patches are released to address known security vulnerabilities. Applying these patches should be considered as part of an agency’s overall risk management strategy. Given the potential threat vectors and the value of the classified information being protected, high assurance products MUST NOT be patched by an agency without specific direction from the GCSB. If a patch is released for a high assurance product, the GCSB will conduct an assessment of the patch and might revise the product’s usage guidance. Likewise, for patches released for HGCE, the GCSB will subsequently conduct an assessment of the cryptographic vulnerability and might revise usage guidance in the consumer guide for the product. | link | count: 002 System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | PS-4 | NZISM_Security_Benchmark_v1.1_PS-4 | NZISM Security Benchmark PS-4 | Physical Security | 8.3.5 Network infrastructure in unsecure areas | Customer | Agencies communicating classified information over public network infrastructure or over infrastructure in unsecure areas MUST use encryption to lower the handling instructions to be equivalent to those for unclassified networks. | As agencies lose control over classified information when it is communicated over unsecure public network infrastructure or over infrastructure in unsecure areas they MUST ensure that it is encrypted to a sufficient level that if it was captured that it would be sufficiently difficult to determine the original information from the encrypted information. | link | count: 002 Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9) |
Cache, Storage | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | SS-2 | NZISM_Security_Benchmark_v1.1_SS-2 | NZISM Security Benchmark SS-2 | Software security | 14.1.8 Developing hardened SOEs | Customer | Agencies SHOULD develop a hardened SOE for workstations and servers, covering: removal of unneeded software and operating system components; removal or disabling of unneeded services, ports and BIOS settings; disabling of unused or undesired functionality in software and operating systems; implementation of access controls on relevant objects to limit system users and programs to the minimum access required; installation of antivirus and anti-malware software; installation of software-based firewalls limiting inbound and outbound network connections; configuration of either remote logging or the transfer of local event logs to a central server; and protection of audit and other logs through the use of a one way pipe to reduce likelihood of compromise key transaction records. | Antivirus and anti-malware software, while an important defensive measure, can be defeated by malicious code that has yet to be identified by antivirus vendors. This can include targeted attacks, where a new virus is engineered or an existing one modified to defeat the signature-based detection schemes. The use of antivirus and anti-malware software, while adding value to the defence of workstations, cannot be relied solely upon to protect the workstation. As such agencies still need to deploy appropriately hardened SOEs to assist with the protection of workstations against a broader range of security risks. | 7 | count: 003 App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917) |
App Service, Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | SS-3 | NZISM_Security_Benchmark_v1.1_SS-3 | NZISM Security Benchmark SS-3 | Software security | 14.1.9 Maintaining hardened SOEs | Customer | Agencies SHOULD ensure that for all servers and workstations: malware detection heuristics are set to a high level; malware pattern signatures are checked for updates on at least a daily basis; malware pattern signatures are updated as soon as possible after vendors make them available; all disks and systems are regularly scanned for malicious code; and the use of End Point Agents is considered. | Whilst a SOE can be sufficiently hardened when it is deployed, its security will progressively degrade over time. Agencies can address the degradation of the security of a SOE by ensuring that patches are continually applied, system users are not able to disable or bypass security functionality and antivirus and other security software is appropriately maintained with the latest signatures and updates. End Point Agents monitor traffic and apply security policies on applications, storage interfaces and data in real-time. Administrators actively block or monitor and log policy breaches. The End Point Agent can also create forensic monitoring to facilitate incident investigation. End Point Agents can monitor user activity, such as the cut, copy, paste, print, print screen operations and copying data to external drives and other devices. The Agent can then apply policies to limit such activity. | link | count: 013 Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
API for FHIR, Guest Configuration, Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | SS-5 | NZISM_Security_Benchmark_v1.1_SS-5 | NZISM Security Benchmark SS-5 | Software security | 14.2.4 Application Whitelisting | Customer | Agencies SHOULD implement application whitelisting as part of the SOE for workstations, servers and any other network device. | Application whitelisting can be an effective mechanism to prevent the successful compromise of an agency system resulting from the exploitation of a vulnerability in an application or the execution of malicious code. Defining a list of trusted executables, a whitelist, is a practical and secure method of securing a system rather than relying on a list of bad executables (black list) to be prevented from running. Application whitelisting is considered only one part of a defence-in-depth strategy in order to prevent a successful attack, or to help mitigate consequences arising from an attack. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| NZISM_Security_Benchmark_v1.1 | SS-9 | NZISM_Security_Benchmark_v1.1_SS-9 | NZISM Security Benchmark SS-9 | Software security | 14.5.8 Web applications | Customer | Agencies SHOULD follow the documentation provided in the Open Web Application Security Project guide to building secure Web applications and Web services. | The Open Web Application Security Project guide provides a comprehensive resource to consult when developing Web applications. | link | count: 004 App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab) |
App Service | [Deprecated]: New Zealand ISM Restricted (d1a462af-7e6d-4901-98ac-61570b4ed22a) |
| PCI_DSS_V3.2.1 | 1.3.2 | PCI_DSS_v3.2.1_1.3.2 | PCI DSS v3.2.1 1.3.2 | Requirement 1 | PCI DSS requirement 1.3.2 | customer | n/a | n/a | link | count: 002 All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Security Center, Storage | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 1.3.4 | PCI_DSS_v3.2.1_1.3.4 | PCI DSS v3.2.1 1.3.4 | Requirement 1 | PCI DSS requirement 1.3.4 | customer | n/a | n/a | link | count: 002 All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Security Center, Storage | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 10.3 | PCI_DSS_V3.2.1_10.3 | 404 not found | n/a | n/a | count: 004 Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Monitoring, SQL, Storage | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) | ||||
| PCI_DSS_V3.2.1 | 10.5.4 | PCI_DSS_v3.2.1_10.5.4 | PCI DSS v3.2.1 10.5.4 | Requirement 10 | PCI DSS requirement 10.5.4 | shared | n/a | n/a | link | count: 004 Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Monitoring, SQL, Storage | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 11.2.1 | PCI_DSS_v3.2.1_11.2.1 | PCI DSS v3.2.1 11.2.1 | Requirement 11 | PCI DSS requirement 11.2.1 | shared | n/a | n/a | link | count: 005 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 3.2 | PCI_DSS_v3.2.1_3.2 | PCI DSS v3.2.1 3.2 | Requirement 3 | PCI DSS requirement 3.2 | customer | n/a | n/a | link | count: 007 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
General, Security Center, SQL | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 3.4 | PCI_DSS_v3.2.1_3.4 | PCI DSS v3.2.1 3.4 | Requirement 3 | PCI DSS requirement 3.4 | customer | n/a | n/a | link | count: 008 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Cache, Security Center, Service Fabric, SQL, Storage | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 4.1 | PCI_DSS_v3.2.1_4.1 | PCI DSS v3.2.1 4.1 | Requirement 4 | PCI DSS requirement 4.1 | customer | n/a | n/a | link | count: 008 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Cache, Security Center, Service Fabric, SQL, Storage | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 5.1 | PCI_DSS_v3.2.1_5.1 | PCI DSS v3.2.1 5.1 | Requirement 5 | PCI DSS requirement 5.1 | shared | n/a | n/a | link | count: 005 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 6.2 | PCI_DSS_v3.2.1_6.2 | PCI DSS v3.2.1 6.2 | Requirement 6 | PCI DSS requirement 6.2 | shared | n/a | n/a | link | count: 005 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 6.5.3 | PCI_DSS_v3.2.1_6.5.3 | PCI DSS v3.2.1 6.5.3 | Requirement 6 | PCI DSS requirement 6.5.3 | shared | n/a | n/a | link | count: 008 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Cache, Security Center, Service Fabric, SQL, Storage | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 6.6 | PCI_DSS_v3.2.1_6.6 | PCI DSS v3.2.1 6.6 | Requirement 6 | PCI DSS requirement 6.6 | shared | n/a | n/a | link | count: 005 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 7.1.1 | PCI_DSS_v3.2.1_7.1.1 | PCI DSS v3.2.1 7.1.1 | Requirement 7 | PCI DSS requirement 7.1.1 | customer | n/a | n/a | link | count: 002 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 7.1.2 | PCI_DSS_v3.2.1_7.1.2 | PCI DSS v3.2.1 7.1.2 | Requirement 7 | PCI DSS requirement 7.1.2 | shared | n/a | n/a | link | count: 002 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 7.1.3 | PCI_DSS_v3.2.1_7.1.3 | PCI DSS v3.2.1 7.1.3 | Requirement 7 | PCI DSS requirement 7.1.3 | customer | n/a | n/a | link | count: 002 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 7.2.1 | PCI_DSS_v3.2.1_7.2.1 | PCI DSS v3.2.1 7.2.1 | Requirement 7 | PCI DSS requirement 7.2.1 | customer | n/a | n/a | link | count: 007 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
General, Security Center, SQL | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 8.1.2 | PCI_DSS_v3.2.1_8.1.2 | PCI DSS v3.2.1 8.1.2 | Requirement 8 | PCI DSS requirement 8.1.2 | customer | n/a | n/a | link | count: 005 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 8.1.3 | PCI_DSS_v3.2.1_8.1.3 | PCI DSS v3.2.1 8.1.3 | Requirement 8 | PCI DSS requirement 8.1.3 | customer | n/a | n/a | link | count: 002 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 8.1.5 | PCI_DSS_v3.2.1_8.1.5 | PCI DSS v3.2.1 8.1.5 | Requirement 8 | PCI DSS requirement 8.1.5 | shared | n/a | n/a | link | count: 005 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
Security Center | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 8.2.3 | PCI_DSS_v3.2.1_8.2.3 | PCI DSS v3.2.1 8.2.3 | Requirement 8 | PCI DSS requirement 8.2.3 | customer | n/a | n/a | link | count: 006 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 8.2.5 | PCI_DSS_v3.2.1_8.2.5 | PCI DSS v3.2.1 8.2.5 | Requirement 8 | PCI DSS requirement 8.2.5 | customer | n/a | n/a | link | count: 006 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6) |
Guest Configuration | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_V3.2.1 | 8.3.1 | PCI_DSS_v3.2.1_8.3.1 | PCI DSS v3.2.1 8.3.1 | Requirement 8 | PCI DSS requirement 8.3.1 | shared | n/a | n/a | link | count: 007 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
General, Security Center, SQL | PCI v3.2.1:2018 (496eeda9-8f2f-4d5e-8dfd-204f0a92ed41) |
| PCI_DSS_v4.0 | 1.1.1 | PCI_DSS_v4.0_1.1.1 | PCI DSS v4.0 1.1.1 | Requirement 01: Install and Maintain Network Security Controls | Processes and mechanisms for installing and maintaining network security controls are defined and understood | Shared | n/a | All security policies and operational procedures that are identified in Requirement 1 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 002 Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.2.1 | PCI_DSS_v4.0_1.2.1 | PCI DSS v4.0 1.2.1 | Requirement 01: Install and Maintain Network Security Controls | Network security controls (NSCs) are configured and maintained | Shared | n/a | Configuration standards for NSC rulesets are: • Defined. • Implemented. • Maintained. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.2.2 | PCI_DSS_v4.0_1.2.2 | PCI DSS v4.0 1.2.2 | Requirement 01: Install and Maintain Network Security Controls | Network security controls (NSCs) are configured and maintained | Shared | n/a | All changes to network connections and to configurations of NSCs are approved and managed in accordance with the change control process defined at Requirement 6.5.1. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.2.3 | PCI_DSS_v4.0_1.2.3 | PCI DSS v4.0 1.2.3 | Requirement 01: Install and Maintain Network Security Controls | Network security controls (NSCs) are configured and maintained | Shared | n/a | An accurate network diagram(s) is maintained that shows all connections between the CDE and other networks, including any wireless networks. | link | count: 001 Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.2.4 | PCI_DSS_v4.0_1.2.4 | PCI DSS v4.0 1.2.4 | Requirement 01: Install and Maintain Network Security Controls | Network security controls (NSCs) are configured and maintained | Shared | n/a | An accurate data-flow diagram(s) is maintained that meets the following: • Shows all account data flows across systems and networks. • Updated as needed upon changes to the environment. | link | count: 001 Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.2.5 | PCI_DSS_v4.0_1.2.5 | PCI DSS v4.0 1.2.5 | Requirement 01: Install and Maintain Network Security Controls | Network security controls (NSCs) are configured and maintained | Shared | n/a | All services, protocols, and ports allowed are identified, approved, and have a defined business need. | link | count: 002 Identify external service providers (46ab2c5e-6654-1f58-8c83-e97a44f39308), Require developer to identify SDLC ports, protocols, and services (f6da5cca-5795-60ff-49e1-4972567815fe) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.2.8 | PCI_DSS_v4.0_1.2.8 | PCI DSS v4.0 1.2.8 | Requirement 01: Install and Maintain Network Security Controls | Network security controls (NSCs) are configured and maintained | Shared | n/a | Configuration files for NSCs are: • Secured from unauthorized access. • Kept consistent with active network configurations. | link | count: 003 Enforce and audit access restrictions (8cd815bf-97e1-5144-0735-11f6ddb50a59), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Review changes for any unauthorized changes (c246d146-82b0-301f-32e7-1065dcd248b7) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.3.2 | PCI_DSS_v4.0_1.3.2 | PCI DSS v4.0 1.3.2 | Requirement 01: Install and Maintain Network Security Controls | Network access to and from the cardholder data environment is restricted | Shared | n/a | Outbound traffic from the CDE is restricted as follows: • To only traffic that is necessary. • All other traffic is specifically denied. | link | count: 002 All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Security Center, Storage | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.3.3 | PCI_DSS_v4.0_1.3.3 | PCI DSS v4.0 1.3.3 | Requirement 01: Install and Maintain Network Security Controls | Network access to and from the cardholder data environment is restricted | Shared | n/a | NSCs are installed between all wireless networks and the CDE, regardless of whether the wireless network is a CDE, such that: • All wireless traffic from wireless networks into the CDE is denied by default. • Only wireless traffic with an authorized business purpose is allowed into the CDE. | link | count: 002 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.4.1 | PCI_DSS_v4.0_1.4.1 | PCI DSS v4.0 1.4.1 | Requirement 01: Install and Maintain Network Security Controls | Network connections between trusted and untrusted networks are controlled | Shared | n/a | NSCs are implemented between trusted and untrusted networks. | link | count: 005 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.4.2 | PCI_DSS_v4.0_1.4.2 | PCI DSS v4.0 1.4.2 | Requirement 01: Install and Maintain Network Security Controls | Network connections between trusted and untrusted networks are controlled | Shared | n/a | Inbound traffic from untrusted networks to trusted networks is restricted to: • Communications with system components that are authorized to provide publicly accessible services, protocols, and ports. • Stateful responses to communications initiated by system components in a trusted network. • All other traffic is denied. | link | count: 007 All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Regulatory Compliance, Security Center, Storage | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.4.3 | PCI_DSS_v4.0_1.4.3 | PCI DSS v4.0 1.4.3 | Requirement 01: Install and Maintain Network Security Controls | Network connections between trusted and untrusted networks are controlled | Shared | n/a | Anti-spoofing measures are implemented to detect and block forged source IP addresses from entering the trusted network. | link | count: 002 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.4.4 | PCI_DSS_v4.0_1.4.4 | PCI DSS v4.0 1.4.4 | Requirement 01: Install and Maintain Network Security Controls | Network connections between trusted and untrusted networks are controlled | Shared | n/a | System components that store cardholder data are not directly accessible from untrusted networks. | link | count: 002 Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 1.5.1 | PCI_DSS_v4.0_1.5.1 | PCI DSS v4.0 1.5.1 | Requirement 01: Install and Maintain Network Security Controls | Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated | Shared | n/a | Security controls are implemented on any computing devices, including company- and employee-owned devices, that connect to both untrusted networks (including the Internet) and the CDE as follows: • Specific configuration settings are defined to prevent threats being introduced into the entity’s network. • Security controls are actively running. • Security controls are not alterable by users of the computing devices unless specifically documented and authorized by management on a case-by-case basis for a limited period. | link | count: 005 Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.1.1 | PCI_DSS_v4.0_10.1.1 | PCI DSS v4.0 10.1.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Processes and mechanisms for logging and monitoring all access to system components and cardholder data are defined and documented | Shared | n/a | All security policies and operational procedures that are identified in Requirement 10 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 004 Develop audit and accountability policies and procedures (a28323fe-276d-3787-32d2-cef6395764c4), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.2.1 | PCI_DSS_v4.0_10.2.1 | PCI DSS v4.0 10.2.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Shared | n/a | Audit logs are enabled and active for all system components and cardholder data. | link | count: 004 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.2.1.1 | PCI_DSS_v4.0_10.2.1.1 | PCI DSS v4.0 10.2.1.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Shared | n/a | Audit logs capture all individual user access to cardholder data. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.2.1.2 | PCI_DSS_v4.0_10.2.1.2 | PCI DSS v4.0 10.2.1.2 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Shared | n/a | Audit logs capture all actions taken by any individual with administrative access, including any interactive use of application or system accounts. | link | count: 007 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.2.1.3 | PCI_DSS_v4.0_10.2.1.3 | PCI DSS v4.0 10.2.1.3 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Shared | n/a | Audit logs capture all access to audit logs. | link | count: 008 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.2.1.4 | PCI_DSS_v4.0_10.2.1.4 | PCI DSS v4.0 10.2.1.4 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Shared | n/a | Audit logs capture all invalid logical access attempts. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.2.1.5 | PCI_DSS_v4.0_10.2.1.5 | PCI DSS v4.0 10.2.1.5 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Shared | n/a | Audit logs capture all changes to identification and authentication credentials including, but not limited to: • Creation of new accounts. • Elevation of privileges. • All changes, additions, or deletions to accounts with administrative access. | link | count: 013 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.2.1.6 | PCI_DSS_v4.0_10.2.1.6 | PCI DSS v4.0 10.2.1.6 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Shared | n/a | Audit logs capture the following: • All initialization of new audit logs, and • All starting, stopping, or pausing of the existing audit logs. | link | count: 008 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.2.1.7 | PCI_DSS_v4.0_10.2.1.7 | PCI DSS v4.0 10.2.1.7 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Shared | n/a | Audit logs capture all creation and deletion of system-level objects. | link | count: 001 Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.2.2 | PCI_DSS_v4.0_10.2.2 | PCI DSS v4.0 10.2.2 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Shared | n/a | Audit logs record the following details for each auditable event: • User identification. • Type of event. • Date and time. • Success and failure indication. • Origination of event. • Identity or name of affected data, system component, resource, or service (for example, name and protocol). | link | count: 005 Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Monitoring, Regulatory Compliance, SQL, Storage | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.3.1 | PCI_DSS_v4.0_10.3.1 | PCI DSS v4.0 10.3.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are protected from destruction and unauthorized modifications | Shared | n/a | Read access to audit logs files is limited to those with a job-related need. | link | count: 002 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.3.2 | PCI_DSS_v4.0_10.3.2 | PCI DSS v4.0 10.3.2 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are protected from destruction and unauthorized modifications | Shared | n/a | Audit log files are protected to prevent modifications by individuals. | link | count: 002 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.3.3 | PCI_DSS_v4.0_10.3.3 | PCI DSS v4.0 10.3.3 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are protected from destruction and unauthorized modifications | Shared | n/a | Audit log files, including those for externalfacing technologies, are promptly backed up to a secure, central, internal log server(s) or other media that is difficult to modify. | link | count: 005 Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Monitoring, Regulatory Compliance, SQL, Storage | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.3.4 | PCI_DSS_v4.0_10.3.4 | PCI DSS v4.0 10.3.4 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are protected from destruction and unauthorized modifications | Shared | n/a | File integrity monitoring or change-detection mechanisms is used on audit logs to ensure that existing log data cannot be changed without generating alerts. | link | count: 002 Enable dual or joint authorization (2c843d78-8f64-92b5-6a9b-e8186c0e7eb6), Protect audit information (0e696f5a-451f-5c15-5532-044136538491) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.4.1 | PCI_DSS_v4.0_10.4.1 | PCI DSS v4.0 10.4.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are reviewed to identify anomalies or suspicious activity | Shared | n/a | The following audit logs are reviewed at least once daily: • All security events. • Logs of all system components that store, process, or transmit CHD and/or SAD. • Logs of all critical system components. • Logs of all servers and system components that perform security functions (for example, network security controls, intrusion-detection systems/intrusion-prevention systems (IDS/IPS), authentication servers). | link | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.4.1.1 | PCI_DSS_v4.0_10.4.1.1 | PCI DSS v4.0 10.4.1.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are reviewed to identify anomalies or suspicious activity | Shared | n/a | Automated mechanisms are used to perform audit log reviews. | link | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.4.2 | PCI_DSS_v4.0_10.4.2 | PCI DSS v4.0 10.4.2 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are reviewed to identify anomalies or suspicious activity | Shared | n/a | Logs of all other system components (those not specified in Requirement 10.4.1) are reviewed periodically. | link | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.4.2.1 | PCI_DSS_v4.0_10.4.2.1 | PCI DSS v4.0 10.4.2.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are reviewed to identify anomalies or suspicious activity | Shared | n/a | The frequency of periodic log reviews for all other system components (not defined in Requirement 10.4.1) is defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requirement12.3.1 | link | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.4.3 | PCI_DSS_v4.0_10.4.3 | PCI DSS v4.0 10.4.3 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit logs are reviewed to identify anomalies or suspicious activity | Shared | n/a | Exceptions and anomalies identified during the review process are addressed. | link | count: 011 Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.5.1 | PCI_DSS_v4.0_10.5.1 | PCI DSS v4.0 10.5.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Audit log history is retained and available for analysis | Shared | n/a | Retain audit log history for at least 12 months, with at least the most recent three months immediately available for analysis. | link | count: 003 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.6.1 | PCI_DSS_v4.0_10.6.1 | PCI DSS v4.0 10.6.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Time-synchronization mechanisms support consistent time settings across all systems | Shared | n/a | System clocks and time are synchronized using time-synchronization technology. | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.6.2 | PCI_DSS_v4.0_10.6.2 | PCI DSS v4.0 10.6.2 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Time-synchronization mechanisms support consistent time settings across all systems | Shared | n/a | Systems are configured to the correct and consistent time as follows: • One or more designated time servers are in use. • Only the designated central time server(s) receives time from external sources. • Time received from external sources is based on International Atomic Time or Coordinated Universal Time (UTC). • The designated time server(s) accept time updates only from specific industry-accepted external sources. • Where there is more than one designated time server, the time servers peer with one another to keep accurate time. • Internal systems receive time information only from designated central time server(s). | link | count: 001 Use system clocks for audit records (1ee4c7eb-480a-0007-77ff-4ba370776266) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.6.3 | PCI_DSS_v4.0_10.6.3 | PCI DSS v4.0 10.6.3 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Time-synchronization mechanisms support consistent time settings across all systems | Shared | n/a | Time synchronization settings and data are protected as follows: • Access to time data is restricted to only personnel with a business need. • Any changes to time settings on critical systems are logged, monitored, and reviewed. | link | count: 010 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Conduct a full text analysis of logged privileged commands (8eea8c14-4d93-63a3-0c82-000343ee5204), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.7.1 | PCI_DSS_v4.0_10.7.1 | PCI DSS v4.0 10.7.1 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Failures of critical security control systems are detected, reported, and responded to promptly | Shared | n/a | Failures of critical security control systems are detected, alerted, and addressed promptly, including but not limited to failure of the following critical security control systems: • Network security controls • IDS/IPS • FIM • Anti-malware solutions • Physical access controls • Logical access controls • Audit logging mechanisms • Segmentation controls (if used) | link | count: 005 Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Notify personnel of any failed security verification tests (18e9d748-73d4-0c96-55ab-b108bfbd5bc3), Perform security function verification at a defined frequency (f30edfad-4e1d-1eef-27ee-9292d6d89842), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.7.2 | PCI_DSS_v4.0_10.7.2 | PCI DSS v4.0 10.7.2 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Failures of critical security control systems are detected, reported, and responded to promptly | Shared | n/a | Failures of critical security control systems are detected, alerted, and addressed promptly, including but not limited to failure of the following critical security control systems: • Network security controls • IDS/IPS • Change-detection mechanisms • Anti-malware solutions • Physical access controls • Logical access controls • Audit logging mechanisms • Segmentation controls (if used) • Audit log review mechanisms • Automated security testing tools (if used) | link | count: 005 Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Notify personnel of any failed security verification tests (18e9d748-73d4-0c96-55ab-b108bfbd5bc3), Perform security function verification at a defined frequency (f30edfad-4e1d-1eef-27ee-9292d6d89842), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 10.7.3 | PCI_DSS_v4.0_10.7.3 | PCI DSS v4.0 10.7.3 | Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | Failures of critical security control systems are detected, reported, and responded to promptly | Shared | n/a | Failures of any critical security controls systems are responded to promptly, including but not limited to: • Restoring security functions. • Identifying and documenting the duration (date and time from start to end) of the security failure. • Identifying and documenting the cause(s) of failure and documenting required remediation. • Identifying and addressing any security issues that arose during the failure. • Determining whether further actions are required as a result of the security failure. • Implementing controls to prevent the cause of failure from reoccurring. • Resuming monitoring of security controls. | link | count: 004 Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Notify personnel of any failed security verification tests (18e9d748-73d4-0c96-55ab-b108bfbd5bc3), Perform security function verification at a defined frequency (f30edfad-4e1d-1eef-27ee-9292d6d89842), Verify security functions (ece8bb17-4080-5127-915f-dc7267ee8549) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.1.1 | PCI_DSS_v4.0_11.1.1 | PCI DSS v4.0 11.1.1 | Requirement 11: Test Security of Systems and Networks Regularly | Processes and mechanisms for regularly testing security of systems and networks are defined and understood | Shared | n/a | All security policies and operational procedures that are identified in Requirement 11 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 003 Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Review security assessment and authorization policies and procedures (a4493012-908c-5f48-a468-1e243be884ce) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.2.2 | PCI_DSS_v4.0_11.2.2 | PCI DSS v4.0 11.2.2 | Requirement 11: Test Security of Systems and Networks Regularly | Wireless access points are identified and monitored, and unauthorized wireless access points are addressed | Shared | n/a | An inventory of authorized wireless access points is maintained, including a documented business justification. | link | count: 002 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.3.1 | PCI_DSS_v4.0_11.3.1 | PCI DSS v4.0 11.3.1 | Requirement 11: Test Security of Systems and Networks Regularly | External and internal vulnerabilities are regularly identified, prioritized, and addressed | Shared | n/a | Internal vulnerability scans are performed as follows: • At least once every three months. • High-risk and critical vulnerabilities (per the entity’s vulnerability risk rankings defined at Requirement 6.3.1) are resolved. • Rescans are performed that confirm all high-risk and critical vulnerabilities as noted above) have been resolved. • Scan tool is kept up to date with latest vulnerability information. • Scans are performed by qualified personnel and organizational independence of the tester exists. | link | count: 007 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Regulatory Compliance, Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.3.1.1 | PCI_DSS_v4.0_11.3.1.1 | PCI DSS v4.0 11.3.1.1 | Requirement 11: Test Security of Systems and Networks Regularly | External and internal vulnerabilities are regularly identified, prioritized, and addressed | Shared | n/a | All other applicable vulnerabilities (those not ranked as high-risk or critical (per the entity’s vulnerability risk rankings defined at Requirement 6.3.1) are managed as follows: • Addressed based on the risk defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requirement 12.3.1. • Rescans are conducted as needed. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.3.1.3 | PCI_DSS_v4.0_11.3.1.3 | PCI DSS v4.0 11.3.1.3 | Requirement 11: Test Security of Systems and Networks Regularly | External and internal vulnerabilities are regularly identified, prioritized, and addressed | Shared | n/a | Internal scans are performed after any significant change as follows: • High-risk and critical vulnerabilities (per the entity’s vulnerability risk rankings defined at Requirement 6.3.1) are resolved. • Rescans are conducted as needed. • Scans are performed by qualified personnel and organizational independence of the tester exists (not required to be a QSA or ASV). | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.3.2 | PCI_DSS_v4.0_11.3.2 | PCI DSS v4.0 11.3.2 | Requirement 11: Test Security of Systems and Networks Regularly | External and internal vulnerabilities are regularly identified, prioritized, and addressed | Shared | n/a | External vulnerability scans are performed as follows: • At least once every three months. • By PCI SSC Approved Scanning Vendor (ASV). • Vulnerabilities are resolved and ASV Program Guide requirements for a passing scan are met. • Rescans are performed as needed to confirm that vulnerabilities are resolved per the ASV Program Guide requirements for a passing scan. | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.3.2.1 | PCI_DSS_v4.0_11.3.2.1 | PCI DSS v4.0 11.3.2.1 | Requirement 11: Test Security of Systems and Networks Regularly | External and internal vulnerabilities are regularly identified, prioritized, and addressed | Shared | n/a | External scans are performed after any significant change as follows: • Vulnerabilities that are scored 4.0 or higher by the CVSS are resolved. • Rescans are conducted as needed. • Scans are performed by qualified personnel and organizational independence of the tester exists (not required to be a QSA or ASV). | link | count: 002 Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.4.1 | PCI_DSS_v4.0_11.4.1 | PCI DSS v4.0 11.4.1 | Requirement 11: Test Security of Systems and Networks Regularly | External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected | Shared | n/a | A penetration testing methodology is defined, documented, and implemented by the entity, and includes: • Industry-accepted penetration testing approaches. • Coverage for the entire CDE perimeter and critical systems. • Testing from both inside and outside the network. • Testing to validate any segmentation and scopereduction controls. • Application-layer penetration testing to identify, at a minimum, the vulnerabilities listed in Requirement 6.2.4. • Network-layer penetration tests that encompass all components that support network functions as well as operating systems. • Review and consideration of threats and vulnerabilities experienced in the last 12 months. • Documented approach to assessing and addressing the risk posed by exploitable vulnerabilities and security weaknesses found during penetration testing. • Retention of penetration testing results and remediation activities results for at least 12 months. | link | count: 001 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.4.3 | PCI_DSS_v4.0_11.4.3 | PCI DSS v4.0 11.4.3 | Requirement 11: Test Security of Systems and Networks Regularly | External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected | Shared | n/a | External penetration testing is performed: • Per the entity’s defined methodology • At least once every 12 months • After any significant infrastructure or application upgrade or change • By a qualified internal resource or qualified external third party • Organizational independence of the tester exists (not required to be a QSA or ASV). | link | count: 001 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.5.1 | PCI_DSS_v4.0_11.5.1 | PCI DSS v4.0 11.5.1 | Requirement 11: Test Security of Systems and Networks Regularly | Network intrusions and unexpected file changes are detected and responded to | Shared | n/a | Intrusion-detection and/or intrusionprevention techniques are used to detect and/or prevent intrusions into the network as follows: • All traffic is monitored at the perimeter of the CDE. • All traffic is monitored at critical points in the CDE. • Personnel are alerted to suspected compromises. • All intrusion-detection and prevention engines, baselines, and signatures are kept up to date. | link | count: 004 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.5.1.1 | PCI_DSS_v4.0_11.5.1.1 | PCI DSS v4.0 11.5.1.1 | Requirement 11: Test Security of Systems and Networks Regularly | Network intrusions and unexpected file changes are detected and responded to | Shared | n/a | Intrusion-detection and/or intrusion-prevention techniques detect, alert on/prevent, and address covert malware communication channels. | link | count: 003 Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.5.2 | PCI_DSS_v4.0_11.5.2 | PCI DSS v4.0 11.5.2 | Requirement 11: Test Security of Systems and Networks Regularly | Network intrusions and unexpected file changes are detected and responded to | Shared | n/a | A change-detection mechanism (for example, file integrity monitoring tools) is deployed as follows: • To alert personnel to unauthorized modification (including changes, additions, and deletions) of critical files • To perform critical file comparisons at least once weekly. | link | count: 003 Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 11.6.1 | PCI_DSS_v4.0_11.6.1 | PCI DSS v4.0 11.6.1 | Requirement 11: Test Security of Systems and Networks Regularly | Unauthorized changes on payment pages are detected and responded to | Shared | n/a | A change- and tamper-detection mechanism is deployed as follows: • To alert personnel to unauthorized modification (including indicators of compromise, changes, additions, and deletions) to the HTTP headers and the contents of payment pages as received by the consumer browser. • The mechanism is configured to evaluate the received HTTP header and payment page. • The mechanism functions are performed as follows: – At least once every seven days OR – Periodically (at the frequency defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requirement 12.3.1). | link | count: 003 Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.1.2 | PCI_DSS_v4.0_12.1.2 | PCI DSS v4.0 12.1.2 | Requirement 12: Support Information Security with Organizational Policies and Programs | A comprehensive information security policy that governs and provides direction for protection of the entity’s information assets is known and current | Shared | n/a | The information security policy is: • Reviewed at least once every 12 months. • Updated as needed to reflect changes to business objectives or risks to the environment. | link | count: 002 Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.1.4 | PCI_DSS_v4.0_12.1.4 | PCI DSS v4.0 12.1.4 | Requirement 12: Support Information Security with Organizational Policies and Programs | A comprehensive information security policy that governs and provides direction for protection of the entity’s information assets is known and current | Shared | n/a | Responsibility for information security is formally assigned to a Chief Information Security Officer or other information security knowledgeable member of executive management. | link | count: 001 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.10.2 | PCI_DSS_v4.0_12.10.2 | PCI DSS v4.0 12.10.2 | Requirement 12: Support Information Security with Organizational Policies and Programs | Suspected and confirmed security incidents that could impact the CDE are responded to immediately | Shared | n/a | At least once every 12 months, the security incident response plan is: • Reviewed and the content is updated as needed. • Tested, including all elements listed in Requirement 12.10.1. | link | count: 006 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.10.4 | PCI_DSS_v4.0_12.10.4 | PCI DSS v4.0 12.10.4 | Requirement 12: Support Information Security with Organizational Policies and Programs | Suspected and confirmed security incidents that could impact the CDE are responded to immediately | Shared | n/a | Personnel responsible for responding to suspected and confirmed security incidents are appropriately and periodically trained on their incident response responsibilities. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.10.4.1 | PCI_DSS_v4.0_12.10.4.1 | PCI DSS v4.0 12.10.4.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | Suspected and confirmed security incidents that could impact the CDE are responded to immediately | Shared | n/a | The frequency of periodic training for incident response personnel is defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requirement 12.3.1. | link | count: 001 Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.10.5 | PCI_DSS_v4.0_12.10.5 | PCI DSS v4.0 12.10.5 | Requirement 12: Support Information Security with Organizational Policies and Programs | Suspected and confirmed security incidents that could impact the CDE are responded to immediately | Shared | n/a | The security incident response plan includes monitoring and responding to alerts from security monitoring systems, including but not limited to: • Intrusion-detection and intrusion-prevention systems. • Network security controls. • Change-detection mechanisms for critical files. • The change-and tamper-detection mechanism for payment pages. This bullet is a best practice until its effective date; refer to Applicability Notes below for details. • Detection of unauthorized wireless access points. | link | count: 003 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.10.6 | PCI_DSS_v4.0_12.10.6 | PCI DSS v4.0 12.10.6 | Requirement 12: Support Information Security with Organizational Policies and Programs | Suspected and confirmed security incidents that could impact the CDE are responded to immediately | Shared | n/a | The security incident response plan is modified and evolved according to lessons learned and to incorporate industry developments. | link | count: 002 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.10.7 | PCI_DSS_v4.0_12.10.7 | PCI DSS v4.0 12.10.7 | Requirement 12: Support Information Security with Organizational Policies and Programs | Suspected and confirmed security incidents that could impact the CDE are responded to immediately | Shared | n/a | Incident response procedures are in place, to be initiated upon the detection of stored PAN anywhere it is not expected, and include: • Determining what to do if PAN is discovered outside the CDE, including its retrieval, secure deletion, and/or migration into the currently defined CDE, as applicable. • Identifying whether sensitive authentication data is stored with PAN. • Determining where the account data came from and how it ended up where it was not expected. • Remediating data leaks or process gaps that resulted in the account data being where it was not expected. | link | count: 008 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.2.1 | PCI_DSS_v4.0_12.2.1 | PCI DSS v4.0 12.2.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | Acceptable use policies for end-user technologies are defined and implemented | Shared | n/a | Acceptable use policies for end-user technologies are documented and implemented, including: • Explicit approval by authorized parties. • Acceptable uses of the technology. • List of products approved by the company for employee use, including hardware and software. | link | count: 004 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Require compliance with intellectual property rights (725164e5-3b21-1ec2-7e42-14f077862841), Track software license usage (77cc89bb-774f-48d7-8a84-fb8c322c3000) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.3.1 | PCI_DSS_v4.0_12.3.1 | PCI DSS v4.0 12.3.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | Risks to the cardholder data environment are formally identified, evaluated, and managed | Shared | n/a | Each PCI DSS requirement that provides flexibility for how frequently it is performed (for example, requirements to be performed periodically) is supported by a targeted risk analysis that is documented and includes: • Identification of the assets being protected. • Identification of the threat(s) that the requirement is protecting against. • Identification of factors that contribute to the likelihood and/or impact of a threat being realized. • Resulting analysis that determines, and includes justification for, how frequently the requirement must be performed to minimize the likelihood of the threat being realized. • Review of each targeted risk analysis at least once every 12 months to determine whether the results are still valid or if an updated risk analysis is needed. • Performance of updated risk analyses when needed, as determined by the annual review. | link | count: 004 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.3.2 | PCI_DSS_v4.0_12.3.2 | PCI DSS v4.0 12.3.2 | Requirement 12: Support Information Security with Organizational Policies and Programs | Risks to the cardholder data environment are formally identified, evaluated, and managed | Shared | n/a | A targeted risk analysis is performed for each PCI DSS requirement that the entity meets with the customized approach, to include: • Documented evidence detailing each element specified in Appendix D: Customized Approach (including, at a minimum, a controls matrix and risk analysis). • Approval of documented evidence by senior management. • Performance of the targeted analysis of risk at least once every 12 months. | link | count: 004 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.3.4 | PCI_DSS_v4.0_12.3.4 | PCI DSS v4.0 12.3.4 | Requirement 12: Support Information Security with Organizational Policies and Programs | Risks to the cardholder data environment are formally identified, evaluated, and managed | Shared | n/a | Hardware and software technologies in use are reviewed at least once every 12 months, including at least the following: • Analysis that the technologies continue to receive security fixes from vendors promptly. • Analysis that the technologies continue to support (and do not preclude) the entity’s PCI DSS compliance. • Documentation of any industry announcements or trends related to a technology, such as when a vendor has announced “end of life” plans for a technology. • Documentation of a plan, approved by senior management, to remediate outdated technologies, including those for which vendors have announced “end of life” plans. | link | count: 003 Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.4.1 | PCI_DSS_v4.0_12.4.1 | PCI DSS v4.0 12.4.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | PCI DSS compliance is managed | Shared | n/a | Responsibility is established by executive management for the protection of cardholder data and a PCI DSS compliance program to include: • Overall accountability for maintaining PCI DSS compliance. • Defining a charter for a PCI DSS compliance program and communication to executive management. | link | count: 005 Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Manage compliance activities (4e400494-53a5-5147-6f4d-718b539c7394), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.4.2 | PCI_DSS_v4.0_12.4.2 | PCI DSS v4.0 12.4.2 | Requirement 12: Support Information Security with Organizational Policies and Programs | PCI DSS compliance is managed | Shared | n/a | Reviews are performed at least once every three months, by personnel other than those responsible for performing the given task to confirm personnel are performing their tasks, in accordance with all security policies and all operational procedures, including but not limited to the following tasks: • Daily log reviews. • Configuration reviews for network security controls. • Applying configuration standards to new systems. • Responding to security alerts. • Change-management processes. | link | count: 006 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.4.2.1 | PCI_DSS_v4.0_12.4.2.1 | PCI DSS v4.0 12.4.2.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | PCI DSS compliance is managed | Shared | n/a | Reviews conducted in accordance with Requirement 12.4.2 are documented to include: • Results of the reviews. • Documented remediation actions taken for any tasks that were found to not be performed at Requirement 12.4.2. • Review and sign-off of results by personnel assigned responsibility for the PCI DSS compliance program. | link | count: 007 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop POA&M (477bd136-7dd9-55f8-48ac-bae096b86a07), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), Update POA&M items (cc057769-01d9-95ad-a36f-1e62a7f9540b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.5.2 | PCI_DSS_v4.0_12.5.2 | PCI DSS v4.0 12.5.2 | Requirement 12: Support Information Security with Organizational Policies and Programs | PCI DSS scope is documented and validated | Shared | n/a | PCI DSS scope is documented and confirmed by the entity at least once every 12 months and upon significant change to the in-scope environment. At a minimum, the scoping validation includes: • Identifying all data flows for the various payment stages (for example, authorization, capture settlement, chargebacks, and refunds) and acceptance channels (for example, card-present, card-not-present, and e-commerce). • Updating all data-flow diagrams per Requirement 1.2.4. • Identifying all locations where account data is stored, processed, and transmitted, including but not limited to: 1) any locations outside of the currently defined CDE, 2) applications that process CHD, 3) transmissions between systems and networks, and 4) file backups. • Identifying all system components in the CDE, connected to the CDE, or that could impact security of the CDE. • Identifying all segmentation controls in use and the environment(s) from which the CDE is segmented, including justification for environments being out of scope. • Identifying all connections from third-party entities with access to the CDE. • Confirming that all identified data flows, account data, system components, segmentation controls, and connections from third parties with access to the CDE are included in scope. | link | count: 001 Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.5.2.1 | PCI_DSS_v4.0_12.5.2.1 | PCI DSS v4.0 12.5.2.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | PCI DSS scope is documented and validated | Shared | n/a | PCI DSS scope is documented and confirmed by the entity at least once every six months and upon significant change to the in-scope environment. At a minimum, the scoping validation includes all the elements specified in Requirement 12.5.2. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.5.3 | PCI_DSS_v4.0_12.5.3 | PCI DSS v4.0 12.5.3 | Requirement 12: Support Information Security with Organizational Policies and Programs | PCI DSS scope is documented and validated | Shared | n/a | Significant changes to organizational structure result in a documented (internal) review of the impact to PCI DSS scope and applicability of controls, with results communicated to executive management. | link | count: 002 Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Update information security policies (5226dee6-3420-711b-4709-8e675ebd828f) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.6.1 | PCI_DSS_v4.0_12.6.1 | PCI DSS v4.0 12.6.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | Security awareness education is an ongoing activity | Shared | n/a | A formal security awareness program is implemented to make all personnel aware of the entity’s information security policy and procedures, and their role in protecting the cardholder data. | link | count: 002 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Establish information security workforce development and improvement program (b544f797-a73b-1be3-6d01-6b1a085376bc) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.6.2 | PCI_DSS_v4.0_12.6.2 | PCI DSS v4.0 12.6.2 | Requirement 12: Support Information Security with Organizational Policies and Programs | Security awareness education is an ongoing activity | Shared | n/a | The security awareness program is: • Reviewed at least once every 12 months, and • Updated as needed to address any new threats and vulnerabilities that may impact the security of the entity’s CDE, or the information provided to personnel about their role in protecting cardholder data. | link | count: 001 Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.6.3 | PCI_DSS_v4.0_12.6.3 | PCI DSS v4.0 12.6.3 | Requirement 12: Support Information Security with Organizational Policies and Programs | Security awareness education is an ongoing activity | Shared | n/a | Personnel receive security awareness training as follows: • Upon hire and at least once every 12 months. • Multiple methods of communication are used. • Personnel acknowledge at least once every 12 months that they have read and understood the information security policy and procedures. | link | count: 008 Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.6.3.1 | PCI_DSS_v4.0_12.6.3.1 | PCI DSS v4.0 12.6.3.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | Security awareness education is an ongoing activity | Shared | n/a | Security awareness training includes awareness of threats and vulnerabilities that could impact the security of the CDE, including but not limited to: • Phishing and related attacks. • Social engineering. | link | count: 003 Implement a threat awareness program (015b4935-448a-8684-27c0-d13086356c33), Implement an insider threat program (35de8462-03ff-45b3-5746-9d4603c74c56), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.6.3.2 | PCI_DSS_v4.0_12.6.3.2 | PCI DSS v4.0 12.6.3.2 | Requirement 12: Support Information Security with Organizational Policies and Programs | Security awareness education is an ongoing activity | Shared | n/a | Security awareness training includes awareness about the acceptable use of end-user technologies in accordance with Requirement 12.2.1. | link | count: 002 Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.7.1 | PCI_DSS_v4.0_12.7.1 | PCI DSS v4.0 12.7.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | Personnel are screened to reduce risks from insider threats | Shared | n/a | Potential personnel who will have access to the CDE are screened, within the constraints of local laws, prior to hire to minimize the risk of attacks from internal sources. | link | count: 003 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Rescreen individuals at a defined frequency (c6aeb800-0b19-944d-92dc-59b893722329) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.8.1 | PCI_DSS_v4.0_12.8.1 | PCI DSS v4.0 12.8.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | Risk to information assets associated with third-party service provider (TPSP) relationships is managed | Shared | n/a | A list of all third-party service providers (TPSPs) with which account data is shared or that could affect the security of account data is maintained, including a description for each of the services provided. | link | count: 001 Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.8.2 | PCI_DSS_v4.0_12.8.2 | PCI DSS v4.0 12.8.2 | Requirement 12: Support Information Security with Organizational Policies and Programs | Risk to information assets associated with third-party service provider (TPSP) relationships is managed | Shared | n/a | Written agreements with TPSPs are maintained as follows: • Written agreements are maintained with all TPSPs with which account data is shared or that could affect the security of the CDE. • Written agreements include acknowledgments from TPSPs that they are responsible for the security of account data the TPSPs possess or otherwise store, process, or transmit on behalf of the entity, or to the extent that they could impact the security of the entity’s CDE. | link | count: 015 Define the duties of processors (52375c01-4d4c-7acc-3aa4-5b3d53a047ec), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Obtain design and implementation information for the security controls (22a02c9a-49e4-5dc9-0d14-eb35ad717154), Obtain functional properties of security controls (44b71aa8-099d-8b97-1557-0e853ec38e0d), Record disclosures of PII to third parties (8b1da407-5e60-5037-612e-2caa1b590719) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.8.3 | PCI_DSS_v4.0_12.8.3 | PCI DSS v4.0 12.8.3 | Requirement 12: Support Information Security with Organizational Policies and Programs | Risk to information assets associated with third-party service provider (TPSP) relationships is managed | Shared | n/a | An established process is implemented for engaging TPSPs, including proper due diligence prior to engagement. | link | count: 005 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.8.4 | PCI_DSS_v4.0_12.8.4 | PCI DSS v4.0 12.8.4 | Requirement 12: Support Information Security with Organizational Policies and Programs | Risk to information assets associated with third-party service provider (TPSP) relationships is managed | Shared | n/a | A program is implemented to monitor TPSPs’ PCI DSS compliance status at least once every 12 months. | link | count: 008 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Obtain continuous monitoring plan for security controls (ca6d7878-3189-1833-4620-6c7254ed1607), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.8.5 | PCI_DSS_v4.0_12.8.5 | PCI DSS v4.0 12.8.5 | Requirement 12: Support Information Security with Organizational Policies and Programs | Risk to information assets associated with third-party service provider (TPSP) relationships is managed | Shared | n/a | Information is maintained about which PCI DSS requirements are managed by each TPSP, which are managed by the entity, and any that are shared between the TPSP and the entity. | link | count: 013 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Obtain design and implementation information for the security controls (22a02c9a-49e4-5dc9-0d14-eb35ad717154), Obtain functional properties of security controls (44b71aa8-099d-8b97-1557-0e853ec38e0d) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.9.1 | PCI_DSS_v4.0_12.9.1 | PCI DSS v4.0 12.9.1 | Requirement 12: Support Information Security with Organizational Policies and Programs | Third-party service providers (TPSPs) support their customers’ PCI DSS compliance | Shared | n/a | TPSPs acknowledge in writing to customers that they are responsible for the security of account data the TPSP possesses or otherwise stores, processes, or transmits on behalf of the customer, or to the extent that they could impact the security of the customer’s CDE. | link | count: 003 Define the duties of processors (52375c01-4d4c-7acc-3aa4-5b3d53a047ec), Record disclosures of PII to third parties (8b1da407-5e60-5037-612e-2caa1b590719), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 12.9.2 | PCI_DSS_v4.0_12.9.2 | PCI DSS v4.0 12.9.2 | Requirement 12: Support Information Security with Organizational Policies and Programs | Third-party service providers (TPSPs) support their customers’ PCI DSS compliance | Shared | n/a | TPSPs support their customers’ requests for information to meet Requirements 12.8.4 and 12.8.5 by providing the following upon customer request: • PCI DSS compliance status information for any service the TPSP performs on behalf of customers (Requirement 12.8.4). • Information about which PCI DSS requirements are the responsibility of the TPSP and which are the responsibility of the customer, including any shared responsibilities (Requirement 12.8.5). | link | count: 003 Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 2.1.1 | PCI_DSS_v4.0_2.1.1 | PCI DSS v4.0 2.1.1 | Requirement 02: Apply Secure Configurations to All System Components | Processes and mechanisms for applying secure configurations to all system components are defined and understood | Shared | n/a | All security policies and operational procedures that are identified in Requirement 2 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 001 Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 2.2.1 | PCI_DSS_v4.0_2.2.1 | PCI DSS v4.0 2.2.1 | Requirement 02: Apply Secure Configurations to All System Components | System components are configured and managed securely | Shared | n/a | Configuration standards are developed, implemented, and maintained to: • Cover all system components. • Address all known security vulnerabilities. • Be consistent with industry-accepted system hardening standards or vendor hardening recommendations. • Be updated as new vulnerability issues are identified, as defined in Requirement 6.3.1. • Be applied when new systems are configured and verified as in place before or immediately after a system component is connected to a production environment. | link | count: 006 Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 2.2.2 | PCI_DSS_v4.0_2.2.2 | PCI DSS v4.0 2.2.2 | Requirement 02: Apply Secure Configurations to All System Components | System components are configured and managed securely | Shared | n/a | Vendor default accounts are managed as follows: • If the vendor default account(s) will be used, the default password is changed per Requirement 8.3.6. • If the vendor default account(s) will not be used, the account is removed or disabled. | link | count: 001 Manage Authenticators (4aacaec9-0628-272c-3e83-0d68446694e0) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 2.2.5 | PCI_DSS_v4.0_2.2.5 | PCI DSS v4.0 2.2.5 | Requirement 02: Apply Secure Configurations to All System Components | System components are configured and managed securely | Shared | n/a | If any insecure services, protocols, or daemons are present: • Business justification is documented. • Additional security features are documented and implemented that reduce the risk of using insecure services, protocols, or daemons. | link | count: 002 Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 2.2.7 | PCI_DSS_v4.0_2.2.7 | PCI DSS v4.0 2.2.7 | Requirement 02: Apply Secure Configurations to All System Components | System components are configured and managed securely | Shared | n/a | All non-console administrative access is encrypted using strong cryptography. | link | count: 001 Implement cryptographic mechanisms (10c3a1b1-29b0-a2d5-8f4c-a284b0f07830) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 2.3.1 | PCI_DSS_v4.0_2.3.1 | PCI DSS v4.0 2.3.1 | Requirement 02: Apply Secure Configurations to All System Components | Wireless environments are configured and managed securely | Shared | n/a | For wireless environments connected to the CDE or transmitting account data, all wireless vendor defaults are changed at installation or are confirmed to be secure, including but not limited to: • Default wireless encryption keys. • Passwords or wireless access points. • SNMP defaults. • Any other security-related wireless vendor defaults. | link | count: 003 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 2.3.2 | PCI_DSS_v4.0_2.3.2 | PCI DSS v4.0 2.3.2 | Requirement 02: Apply Secure Configurations to All System Components | Wireless environments are configured and managed securely | Shared | n/a | For wireless environments connected to the CDE or transmitting account data, wireless encryption keys are changed as follows: • Whenever personnel with knowledge of the key leave the company or the role for which the knowledge was necessary. • Whenever a key is suspected of or known to be compromised. | link | count: 003 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.1.1 | PCI_DSS_v4.0_3.1.1 | PCI DSS v4.0 3.1.1 | Requirement 03: Protect Stored Account Data | Processes and mechanisms for protecting stored account data are defined and understood | Shared | n/a | All security policies and operational procedures that are identified in Requirement 3 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 003 Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e), Update privacy plan, policies, and procedures (96333008-988d-4add-549b-92b3a8c42063) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.2.1 | PCI_DSS_v4.0_3.2.1 | PCI DSS v4.0 3.2.1 | Requirement 03: Protect Stored Account Data | Storage of account data is kept to a minimum | Shared | n/a | Account data storage is kept to a minimum through implementation of data retention and disposal policies, procedures, and processes that include at least the following: • Coverage for all locations of stored account data. • Coverage for any sensitive authentication data (SAD) stored prior to completion of authorization. This bullet is a best practice until its effective date; refer to Applicability Notes below for details. • Limiting data storage amount and retention time to that which is required for legal or regulatory, and/or business requirements. • Specific retention requirements for stored account data that defines length of retention period and includes a documented business justification. • Processes for secure deletion or rendering account data unrecoverable when no longer needed per the retention policy. • A process for verifying, at least once every three months, that stored account data exceeding the defined retention period has been securely deleted or rendered unrecoverable. | link | count: 008 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.3.1 | PCI_DSS_v4.0_3.3.1 | PCI DSS v4.0 3.3.1 | Requirement 03: Protect Stored Account Data | Sensitive authentication data (SAD) is not stored after authorization | Shared | n/a | SAD is not retained after authorization, even if encrypted. All sensitive authentication data received is rendered unrecoverable upon completion of the authorization process. | link | count: 008 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.3.1.1 | PCI_DSS_v4.0_3.3.1.1 | PCI DSS v4.0 3.3.1.1 | Requirement 03: Protect Stored Account Data | Sensitive authentication data (SAD) is not stored after authorization | Shared | n/a | The full contents of any track are not retained upon completion of the authorization process. | link | count: 008 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.3.1.2 | PCI_DSS_v4.0_3.3.1.2 | PCI DSS v4.0 3.3.1.2 | Requirement 03: Protect Stored Account Data | Sensitive authentication data (SAD) is not stored after authorization | Shared | n/a | The card verification code is not retained upon completion of the authorization process. | link | count: 005 Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.3.1.3 | PCI_DSS_v4.0_3.3.1.3 | PCI DSS v4.0 3.3.1.3 | Requirement 03: Protect Stored Account Data | Sensitive authentication data (SAD) is not stored after authorization | Shared | n/a | The personal identification number (PIN) and the PIN block are not retained upon completion of the authorization process. | link | count: 008 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.3.2 | PCI_DSS_v4.0_3.3.2 | PCI DSS v4.0 3.3.2 | Requirement 03: Protect Stored Account Data | Sensitive authentication data (SAD) is not stored after authorization | Shared | n/a | SAD that is stored electronically prior to completion of authorization is encrypted using strong cryptography. | link | count: 001 Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.3.3 | PCI_DSS_v4.0_3.3.3 | PCI DSS v4.0 3.3.3 | Requirement 03: Protect Stored Account Data | Sensitive authentication data (SAD) is not stored after authorization | Shared | n/a | Additional requirement for issuers and companies that support issuing services and store sensitive authentication data: Any storage of sensitive authentication data is: • Limited to that which is needed for a legitimate issuing business need and is secured. • Encrypted using strong cryptography. This bullet is a best practice until its effective date; refer to Applicability Notes below for details. | link | count: 013 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Authenticate to cryptographic module (6f1de470-79f3-1572-866e-db0771352fc8), Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9) |
General, Regulatory Compliance, Security Center, SQL | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.4.1 | PCI_DSS_v4.0_3.4.1 | PCI DSS v4.0 3.4.1 | Requirement 03: Protect Stored Account Data | Access to displays of full PAN and ability to copy cardholder data are restricted | Shared | n/a | PAN is masked when displayed (the BIN and last four digits are the maximum number of digits to be displayed), such that only personnel with a legitimate business need can see more than the BIN and last four digits of the PAN. | link | count: 003 Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.4.2 | PCI_DSS_v4.0_3.4.2 | PCI DSS v4.0 3.4.2 | Requirement 03: Protect Stored Account Data | Access to displays of full PAN and ability to copy cardholder data are restricted | Shared | n/a | When using remote-access technologies, technical controls prevent copy and/or relocation of PAN for all personnel, except for those with documented, explicit authorization and a legitimate, defined business need. | link | count: 003 Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.5.1 | PCI_DSS_v4.0_3.5.1 | PCI DSS v4.0 3.5.1 | Requirement 03: Protect Stored Account Data | Primary account number (PAN) is secured wherever it is stored | Shared | n/a | PAN is rendered unreadable anywhere it is stored by using any of the following approaches: • One-way hashes based on strong cryptography of the entire PAN. • Truncation (hashing cannot be used to replace the truncated segment of PAN). – If hashed and truncated versions of the same PAN, or different truncation formats of the same PAN, are present in an environment, additional controls are in place such that the different versions cannot be correlated to reconstruct the original PAN. • Index tokens. • Strong cryptography with associated keymanagement processes and procedures. | link | count: 012 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Cache, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.5.1.1 | PCI_DSS_v4.0_3.5.1.1 | PCI DSS v4.0 3.5.1.1 | Requirement 03: Protect Stored Account Data | Primary account number (PAN) is secured wherever it is stored | Shared | n/a | Hashes used to render PAN unreadable (per the first bullet of Requirement 3.5.1) are keyed cryptographic hashes of the entire PAN, with associated key-management processes and procedures in accordance with Requirements 3.6 and 3.7. | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.5.1.2 | PCI_DSS_v4.0_3.5.1.2 | PCI DSS v4.0 3.5.1.2 | Requirement 03: Protect Stored Account Data | Primary account number (PAN) is secured wherever it is stored | Shared | n/a | If disk-level or partition-level encryption (rather than file-, column-, or field-level database encryption) is used to render PAN unreadable, it is implemented only as follows: • On removable electronic media, OR • If used for non-removable electronic media, PAN is also rendered unreadable via another mechanism that meets Requirement 3.5.1. | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.5.1.3 | PCI_DSS_v4.0_3.5.1.3 | PCI DSS v4.0 3.5.1.3 | Requirement 03: Protect Stored Account Data | Primary account number (PAN) is secured wherever it is stored | Shared | n/a | If disk-level or partition-level encryption is used (rather than file-, column-, or field--level database encryption) to render PAN unreadable, it is managed as follows: • Logical access is managed separately and independently of native operating system authentication and access control mechanisms. • Decryption keys are not associated with user accounts. | link | count: 004 Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.6.1 | PCI_DSS_v4.0_3.6.1 | PCI DSS v4.0 3.6.1 | Requirement 03: Protect Stored Account Data | Cryptographic keys used to protect stored account data are secured | Shared | n/a | Procedures are defined and implemented to protect cryptographic keys used to Protect Stored Account Data against disclosure and misuse that include: • Access to keys is restricted to the fewest number of custodians necessary. • Key-encrypting keys are at least as strong as the data-encrypting keys they protect. • Key-encrypting keys are stored separately from data-encrypting keys. • Keys are stored securely in the fewest possible locations and forms. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.6.1.1 | PCI_DSS_v4.0_3.6.1.1 | PCI DSS v4.0 3.6.1.1 | Requirement 03: Protect Stored Account Data | Cryptographic keys used to protect stored account data are secured | Shared | n/a | A documented description of the cryptographic architecture is maintained that includes: • Details of all algorithms, protocols, and keys used for the protection of stored account data, including key strength and expiry date. • Preventing the use of the same cryptographic keys in production and test environments. This bullet is a best practice until its effective date; refer to Applicability Notes below for details. • Description of the key usage for each key. • Inventory of any hardware security modules (HSMs), key management systems (KMS), and other secure cryptographic devices (SCDs) used for key management, including type and location of devices, as outlined in Requirement 12.3.4. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.6.1.2 | PCI_DSS_v4.0_3.6.1.2 | PCI DSS v4.0 3.6.1.2 | Requirement 03: Protect Stored Account Data | Cryptographic keys used to protect stored account data are secured | Shared | n/a | Secret and private keys used to encrypt/decrypt stored account data are stored in one (or more) of the following forms at all times: • Encrypted with a key-encrypting key that is at least as strong as the data-encrypting key, and that is stored separately from the dataencrypting key. • Within a secure cryptographic device (SCD), such as a hardware security module (HSM) or PTS-approved point-of-interaction device. • As at least two full-length key components or key shares, in accordance with an industry-accepted method. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.6.1.3 | PCI_DSS_v4.0_3.6.1.3 | PCI DSS v4.0 3.6.1.3 | Requirement 03: Protect Stored Account Data | Cryptographic keys used to protect stored account data are secured | Shared | n/a | Access to cleartext cryptographic key components is restricted to the fewest number of custodians necessary. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.6.1.4 | PCI_DSS_v4.0_3.6.1.4 | PCI DSS v4.0 3.6.1.4 | Requirement 03: Protect Stored Account Data | Cryptographic keys used to protect stored account data are secured | Shared | n/a | Cryptographic keys are stored in the fewest possible locations. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.7.1 | PCI_DSS_v4.0_3.7.1 | PCI DSS v4.0 3.7.1 | Requirement 03: Protect Stored Account Data | Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented | Shared | n/a | Key-management policies and procedures are implemented to include generation of strong cryptographic keys used to Protect Stored Account Data. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.7.2 | PCI_DSS_v4.0_3.7.2 | PCI DSS v4.0 3.7.2 | Requirement 03: Protect Stored Account Data | Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented | Shared | n/a | Key-management policies and procedures are implemented to include secure distribution of cryptographic keys used to Protect Stored Account Data. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.7.3 | PCI_DSS_v4.0_3.7.3 | PCI DSS v4.0 3.7.3 | Requirement 03: Protect Stored Account Data | Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented | Shared | n/a | Key-management policies and procedures are implemented to include secure storage of cryptographic keys used to Protect Stored Account Data. | link | count: 009 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.7.4 | PCI_DSS_v4.0_3.7.4 | PCI DSS v4.0 3.7.4 | Requirement 03: Protect Stored Account Data | Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented | Shared | n/a | Key management policies and procedures are implemented for cryptographic key changes for keys that have reached the end of their cryptoperiod, as defined by the associated application vendor or key owner, and based on industry best practices and guidelines, including the following: • A defined cryptoperiod for each key type in use. • A process for key changes at the end of the defined cryptoperiod. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.7.5 | PCI_DSS_v4.0_3.7.5 | PCI DSS v4.0 3.7.5 | Requirement 03: Protect Stored Account Data | Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented | Shared | n/a | Key management policies procedures are implemented to include the retirement, replacement, or destruction of keys used to Protect Stored Account Data, as deemed necessary when: • The key has reached the end of its defined cryptoperiod. • The integrity of the key has been weakened, including when personnel with knowledge of a cleartext key component leaves the company, or the role for which the key component was known. • When keys are suspected of or known to be compromised. • Retired or replaced keys are not used for encryption operations. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.7.6 | PCI_DSS_v4.0_3.7.6 | PCI DSS v4.0 3.7.6 | Requirement 03: Protect Stored Account Data | Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented | Shared | n/a | Where manual cleartext cryptographic keymanagement operations are performed by personnel, key-management policies and procedures are implemented include managing these operations using split knowledge and dual control. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.7.7 | PCI_DSS_v4.0_3.7.7 | PCI DSS v4.0 3.7.7 | Requirement 03: Protect Stored Account Data | Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented | Shared | n/a | Key management policies and procedures are implemented to include the prevention of unauthorized substitution of cryptographic keys. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.7.8 | PCI_DSS_v4.0_3.7.8 | PCI DSS v4.0 3.7.8 | Requirement 03: Protect Stored Account Data | Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented | Shared | n/a | Key management policies and procedures are implemented to include that cryptographic key custodians formally acknowledge (in writing or electronically) that they understand and accept their key-custodian responsibilities. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 3.7.9 | PCI_DSS_v4.0_3.7.9 | PCI DSS v4.0 3.7.9 | Requirement 03: Protect Stored Account Data | Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented | Shared | n/a | Where a service provider shares cryptographic keys with its customers for transmission or storage of account data, guidance on secure transmission, storage and updating of such keys is documented and distributed to the service providers' customers. | link | count: 007 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 4.1.1 | PCI_DSS_v4.0_4.1.1 | PCI DSS v4.0 4.1.1 | Requirement 04: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks | Processes and mechanisms for protecting cardholder data with strong cryptography during transmission over open, public networks are defined and documented | Shared | n/a | All security policies and operational procedures that are identified in Requirement 4 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 001 Review and update system and communications protection policies and procedures (adf517f3-6dcd-3546-9928-34777d0c277e) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 4.2.1 | PCI_DSS_v4.0_4.2.1 | PCI DSS v4.0 4.2.1 | Requirement 04: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks | PAN is protected with strong cryptography during transmission | Shared | n/a | Strong cryptography and security protocols are implemented as follows to safeguard PAN during transmission over open, public networks: • Only trusted keys and certificates are accepted. • Certificates used to safeguard PAN during transmission over open, public networks are confirmed as valid and are not expired or revoked. This bullet is a best practice until its effective date; refer to applicability notes below for details. • The protocol in use supports only secure versions or configurations and does not support fallback to, or use of insecure versions, algorithms, key sizes, or implementations. • The encryption strength is appropriate for the encryption methodology in use. | link | count: 012 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 4.2.1.1 | PCI_DSS_v4.0_4.2.1.1 | PCI DSS v4.0 4.2.1.1 | Requirement 04: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks | PAN is protected with strong cryptography during transmission | Shared | n/a | An inventory of the entity’s trusted keys and certificates used to protect PAN during transmission is maintained. | link | count: 008 Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 4.2.1.2 | PCI_DSS_v4.0_4.2.1.2 | PCI DSS v4.0 4.2.1.2 | Requirement 04: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks | PAN is protected with strong cryptography during transmission | Shared | n/a | Wireless networks transmitting PAN or connected to the CDE use industry best practices to implement strong cryptography for authentication and transmission. | link | count: 003 Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 4.2.2 | PCI_DSS_v4.0_4.2.2 | PCI DSS v4.0 4.2.2 | Requirement 04: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks | PAN is protected with strong cryptography during transmission | Shared | n/a | PAN is secured with strong cryptography whenever it is sent via end-user messaging technologies. | link | count: 003 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.1.1 | PCI_DSS_v4.0_5.1.1 | PCI DSS v4.0 5.1.1 | Requirement 05: Protect All Systems and Networks from Malicious Software | Processes and mechanisms for protecting all systems and networks from malicious software are defined and understood | Shared | n/a | All security policies and operational procedures that are identified in Requirement 5 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 001 Review and update information integrity policies and procedures (6bededc0-2985-54d5-4158-eb8bad8070a0) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.2.1 | PCI_DSS_v4.0_5.2.1 | PCI DSS v4.0 5.2.1 | Requirement 05: Protect All Systems and Networks from Malicious Software | Malicious software (malware) is prevented, or detected and addressed | Shared | n/a | An anti-malware solution(s) is deployed on all system components, except for those system components identified in periodic evaluations per Requirement 5.2.3 that concludes the system components are not at risk from malware. | link | count: 012 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Regulatory Compliance, Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.2.2 | PCI_DSS_v4.0_5.2.2 | PCI DSS v4.0 5.2.2 | Requirement 05: Protect All Systems and Networks from Malicious Software | Malicious software (malware) is prevented, or detected and addressed | Shared | n/a | The deployed anti-malware solution(s): • Detects all known types of malware. • Removes, blocks, or contains all known types of malware. | link | count: 012 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Regulatory Compliance, Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.2.3 | PCI_DSS_v4.0_5.2.3 | PCI DSS v4.0 5.2.3 | Requirement 05: Protect All Systems and Networks from Malicious Software | Malicious software (malware) is prevented, or detected and addressed | Shared | n/a | Any system components that are not at risk for malware are evaluated periodically to include the following: • A documented list of all system components not at risk for malware. • Identification and evaluation of evolving malware threats for those system components. • Confirmation whether such system components continue to not require anti-malware protection. | link | count: 012 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Regulatory Compliance, Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.2.3.1 | PCI_DSS_v4.0_5.2.3.1 | PCI DSS v4.0 5.2.3.1 | Requirement 05: Protect All Systems and Networks from Malicious Software | Malicious software (malware) is prevented, or detected and addressed | Shared | n/a | The frequency of periodic evaluations of system components identified as not at risk for malware is defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requirement 12.3.1. | link | count: 003 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.3.1 | PCI_DSS_v4.0_5.3.1 | PCI DSS v4.0 5.3.1 | Requirement 05: Protect All Systems and Networks from Malicious Software | Anti-malware mechanisms and processes are active, maintained, and monitored | Shared | n/a | The anti-malware solution(s) is kept current via automatic updates. | link | count: 006 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.3.3 | PCI_DSS_v4.0_5.3.3 | PCI DSS v4.0 5.3.3 | Requirement 05: Protect All Systems and Networks from Malicious Software | Anti-malware mechanisms and processes are active, maintained, and monitored | Shared | n/a | For removable electronic media, the antimalware solution: • Performs automatic scans of when the media is inserted, connected, or logically mounted, OR • Performs continuous behavioral analysis of systems or processes when the media is inserted, connected, or logically mounted. | link | count: 007 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.3.4 | PCI_DSS_v4.0_5.3.4 | PCI DSS v4.0 5.3.4 | Requirement 05: Protect All Systems and Networks from Malicious Software | Anti-malware mechanisms and processes are active, maintained, and monitored | Shared | n/a | Audit logs for the anti-malware solution are enabled and retained in accordance with Requirement 10.5.1. | link | count: 004 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Retain security policies and procedures (efef28d0-3226-966a-a1e8-70e89c1b30bc), Retain terminated user data (7c7032fe-9ce6-9092-5890-87a1a3755db1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.3.5 | PCI_DSS_v4.0_5.3.5 | PCI DSS v4.0 5.3.5 | Requirement 05: Protect All Systems and Networks from Malicious Software | Anti-malware mechanisms and processes are active, maintained, and monitored | Shared | n/a | Anti-malware mechanisms cannot be disabled or altered by users, unless specifically documented, and authorized by management on a case-by-case basis for a limited time period. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 5.4.1 | PCI_DSS_v4.0_5.4.1 | PCI DSS v4.0 5.4.1 | Requirement 05: Protect All Systems and Networks from Malicious Software | Anti-phishing mechanisms protect users against phishing attacks | Shared | n/a | Processes and automated mechanisms are in place to detect and protect personnel against phishing attacks. | link | count: 007 Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.1.1 | PCI_DSS_v4.0_6.1.1 | PCI DSS v4.0 6.1.1 | Requirement 06: Develop and Maintain Secure Systems and Software | Processes and mechanisms for developing and maintaining secure systems and software are defined and understood | Shared | n/a | All security policies and operational procedures that are identified in Requirement 6 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 002 Review and update configuration management policies and procedures (eb8a8df9-521f-3ccd-7e2c-3d1fcc812340), Review and update system and services acquisition policies and procedures (f49925aa-9b11-76ae-10e2-6e973cc60f37) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.2.2 | PCI_DSS_v4.0_6.2.2 | PCI DSS v4.0 6.2.2 | Requirement 06: Develop and Maintain Secure Systems and Software | Bespoke and custom software are developed securely | Shared | n/a | Software development personnel working on bespoke and custom software are trained at least once every 12 months as follows: • On software security relevant to their job function and development languages. • Including secure software design and secure coding techniques. • Including, if security testing tools are used, how to use the tools for detecting vulnerabilities in software. | link | count: 002 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.2.3.1 | PCI_DSS_v4.0_6.2.3.1 | PCI DSS v4.0 6.2.3.1 | Requirement 06: Develop and Maintain Secure Systems and Software | Bespoke and custom software are developed securely | Shared | n/a | If manual code reviews are performed for bespoke and custom software prior to release to production, code changes are: • Reviewed by individuals other than the originating code author, and who are knowledgeable about code-review techniques and secure coding practices. • Reviewed and approved by management prior to release. | link | count: 001 Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.2.4 | PCI_DSS_v4.0_6.2.4 | PCI DSS v4.0 6.2.4 | Requirement 06: Develop and Maintain Secure Systems and Software | Bespoke and custom software are developed securely | Shared | n/a | Software engineering techniques or other methods are defined and in use for bespoke and custom software by software development personnel to prevent or mitigate common software attacks and related vulnerabilities, including but not limited to the following: • Injection attacks, including SQL, LDAP, XPath, or other command, parameter, object, fault, or injection-type flaws. • Attacks on data and data structures, including attempts to manipulate buffers, pointers, input data, or shared data. • Attacks on cryptography usage, including attempts to exploit weak, insecure, or inappropriate cryptographic implementations, algorithms, cipher suites, or modes of operation. • Attacks on business logic, including attempts to abuse or bypass application features and functionalities through the manipulation of APIs, communication protocols and channels, clientside functionality, or other system/application functions and resources. This includes cross-site scripting (XSS) and cross-site request forgery (CSRF). • Attacks on access control mechanisms, including attempts to bypass or abuse identification, authentication, or authorization mechanisms, or attempts to exploit weaknesses in the implementation of such mechanisms. • Attacks via any “high-risk” vulnerabilities identified in the vulnerability identification process, as defined in Requirement 6.3.1. | link | count: 008 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Cache, Security Center, Service Fabric, SQL, Storage | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.3.1 | PCI_DSS_v4.0_6.3.1 | PCI DSS v4.0 6.3.1 | Requirement 06: Develop and Maintain Secure Systems and Software | Security vulnerabilities are identified and addressed | Shared | n/a | Security vulnerabilities are identified and managed as follows: • New security vulnerabilities are identified using industry-recognized sources for security vulnerability information, including alerts from international and national computer emergency response teams (CERTs). • Vulnerabilities are assigned a risk ranking based on industry best practices and consideration of potential impact. • Risk rankings identify, at a minimum, all vulnerabilities considered to be a high-risk or critical to the environment. • Vulnerabilities for bespoke and custom, and third-party software (for example operating systems and databases) are covered. | link | count: 004 Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Establish a threat intelligence program (b0e3035d-6366-2e37-796e-8bcab9c649e6), Implement security directives (26d178a4-9261-6f04-a100-47ed85314c6e), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.3.2 | PCI_DSS_v4.0_6.3.2 | PCI DSS v4.0 6.3.2 | Requirement 06: Develop and Maintain Secure Systems and Software | Security vulnerabilities are identified and addressed | Shared | n/a | An inventory of bespoke and custom software, and third-party software components incorporated into bespoke and custom software is maintained to facilitate vulnerability and patch management. | link | count: 001 Obtain Admin documentation (3f1216b0-30ee-1ac9-3899-63eb744e85f5) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.3.3 | PCI_DSS_v4.0_6.3.3 | PCI DSS v4.0 6.3.3 | Requirement 06: Develop and Maintain Secure Systems and Software | Security vulnerabilities are identified and addressed | Shared | n/a | All system components are protected from known vulnerabilities by installing applicable security patches/updates as follows: • Critical or high-security patches/updates are identified according to the risk ranking process at Requirement 6.3.1. • Critical or high-security patches/updates are installed within one month of release. • All other applicable security patches/updates are installed within an appropriate time frame as determined by the entity (for example, within three months of release). | link | count: 005 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.4.1 | PCI_DSS_v4.0_6.4.1 | PCI DSS v4.0 6.4.1 | Requirement 06: Develop and Maintain Secure Systems and Software | Public-facing web applications are protected against attacks | Shared | n/a | For public-facing web applications, new threats and vulnerabilities are addressed on an ongoing basis and these applications are protected against known attacks as follows: • Reviewing public-facing web applications via manual or automated application vulnerability security assessment tools or methods as follows: – At least once every 12 months and after significant changes. – By an entity that specializes in application security. – Including, at a minimum, all common software attacks in Requirement 6.3.6. – All vulnerabilities are ranked in accordance with requirement 6.2.1. – All vulnerabilities are corrected. – The application is re-evaluated after the corrections OR • Installing an automated technical solution(s) that continually detects and prevents web-based attacks as follows: – Installed in front of public-facing web applications to detect and prevent webbased attacks. – Actively running and up to date as applicable. – Generating audit logs. – Configured to either block web-based attacks or generate an alert that is immediately investigated. | link | count: 007 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Regulatory Compliance, Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.4.3 | PCI_DSS_v4.0_6.4.3 | PCI DSS v4.0 6.4.3 | Requirement 06: Develop and Maintain Secure Systems and Software | Public-facing web applications are protected against attacks | Shared | n/a | All payment page scripts that are loaded and executed in the consumer’s browser are managed as follows: • A method is implemented to confirm that each script is authorized. • A method is implemented to assure the integrity of each script. • An inventory of all scripts is maintained with written justification as to why each is necessary. | link | count: 002 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.5.1 | PCI_DSS_v4.0_6.5.1 | PCI DSS v4.0 6.5.1 | Requirement 06: Develop and Maintain Secure Systems and Software | Changes to all system components are managed securely | Shared | n/a | Changes to all system components in the production environment are made according to established procedures that include: • Reason for, and description of, the change. • Documentation of security impact. • Documented change approval by authorized parties. • Testing to verify that the change does not adversely impact system security. • For bespoke and custom software changes, all updates are tested for compliance with Requirement 6.2.4 before being deployed into production. • Procedures to address failures and return to a secure state. | link | count: 008 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.5.2 | PCI_DSS_v4.0_6.5.2 | PCI DSS v4.0 6.5.2 | Requirement 06: Develop and Maintain Secure Systems and Software | Changes to all system components are managed securely | Shared | n/a | Upon completion of a significant change, all applicable PCI DSS requirements are confirmed to be in place on all new or changed systems and networks, and documentation is updated as applicable. | link | count: 001 Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.5.3 | PCI_DSS_v4.0_6.5.3 | PCI DSS v4.0 6.5.3 | Requirement 06: Develop and Maintain Secure Systems and Software | Changes to all system components are managed securely | Shared | n/a | Pre-production environments are separated from production environments and the separation is enforced with access controls. | link | count: 006 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.5.4 | PCI_DSS_v4.0_6.5.4 | PCI DSS v4.0 6.5.4 | Requirement 06: Develop and Maintain Secure Systems and Software | Changes to all system components are managed securely | Shared | n/a | Roles and functions are separated between production and pre-production environments to provide accountability such that only reviewed and approved changes are deployed. | link | count: 006 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Limit privileges to make changes in production environment (2af551d5-1775-326a-0589-590bfb7e9eb2), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.5.5 | PCI_DSS_v4.0_6.5.5 | PCI DSS v4.0 6.5.5 | Requirement 06: Develop and Maintain Secure Systems and Software | Changes to all system components are managed securely | Shared | n/a | Live PANs are not used in pre-production environments, except where those environments are included in the CDE and protected in accordance with all applicable PCI DSS requirements. | link | count: 001 Incorporate security and data privacy practices in research processing (834b7a4a-83ab-2188-1a26-9c5033d8173b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 6.5.6 | PCI_DSS_v4.0_6.5.6 | PCI DSS v4.0 6.5.6 | Requirement 06: Develop and Maintain Secure Systems and Software | Changes to all system components are managed securely | Shared | n/a | Test data and test accounts are removed from system components before the system goes into production. | link | count: 005 Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.1.1 | PCI_DSS_v4.0_7.1.1 | PCI DSS v4.0 7.1.1 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Processes and mechanisms for restricting access to system components and cardholder data by business need to know are defined and understood | Shared | n/a | All security policies and operational procedures that are identified in Requirement 7 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 004 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de), Review access control policies and procedures (03d550b4-34ee-03f4-515f-f2e2faf7a413) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.1.2 | PCI_DSS_v4.0_7.1.2 | PCI DSS v4.0 7.1.2 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Processes and mechanisms for restricting access to system components and cardholder data by business need to know are defined and understood | Shared | n/a | Roles and responsibilities for performing activities in Requirement 7 are documented, assigned, and understood. | link | count: 003 Develop access control policies and procedures (59f7feff-02aa-6539-2cf7-bea75b762140), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Govern policies and procedures (1a2a03a4-9992-5788-5953-d8f6615306de) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.2.1 | PCI_DSS_v4.0_7.2.1 | PCI DSS v4.0 7.2.1 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is appropriately defined and assigned | Shared | n/a | An access control model is defined and includes granting access as follows: • Appropriate access depending on the entity’s business and access needs. • Access to system components and data resources that is based on users’ job classification and functions. • The least privileges required (for example, user, administrator) to perform a job function. | link | count: 010 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Regulatory Compliance, Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.2.2 | PCI_DSS_v4.0_7.2.2 | PCI DSS v4.0 7.2.2 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is appropriately defined and assigned | Shared | n/a | Access is assigned to users, including privileged users, based on: • Job classification and function. • Least privileges necessary to perform job responsibilities. | link | count: 007 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Regulatory Compliance, Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.2.3 | PCI_DSS_v4.0_7.2.3 | PCI DSS v4.0 7.2.3 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is appropriately defined and assigned | Shared | n/a | Required privileges are approved by authorized personnel. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.2.4 | PCI_DSS_v4.0_7.2.4 | PCI DSS v4.0 7.2.4 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is appropriately defined and assigned | Shared | n/a | All user accounts and related access privileges, including third-party/vendor accounts, are reviewed as follows: • At least once every six months. • To ensure user accounts and access remain appropriate based on job function. • Any inappropriate access is addressed. • Management acknowledges that access remains appropriate. | link | count: 004 Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.2.5 | PCI_DSS_v4.0_7.2.5 | PCI DSS v4.0 7.2.5 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is appropriately defined and assigned | Shared | n/a | All application and system accounts and related access privileges are assigned and managed as follows: • Based on the least privileges necessary for the operability of the system or application. • Access is limited to the systems, applications, or processes that specifically require their use. | link | count: 001 Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.2.5.1 | PCI_DSS_v4.0_7.2.5.1 | PCI DSS v4.0 7.2.5.1 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is appropriately defined and assigned | Shared | n/a | All access by application and system accounts and related access privileges are reviewed as follows: • Periodically (at the frequency defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requirement 12.3.1). • The application/system access remains appropriate for the function being performed. • Any inappropriate access is addressed. • Management acknowledges that that access remains appropriate. | link | count: 001 Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.2.6 | PCI_DSS_v4.0_7.2.6 | PCI DSS v4.0 7.2.6 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is appropriately defined and assigned | Shared | n/a | All user access to query repositories of stored cardholder data is restricted as follows: • Via applications or other programmatic methods, with access and allowed actions based on user roles and least privileges. • Only the responsible administrator(s) can directly access or query repositories of stored CHD. | link | count: 008 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.3.1 | PCI_DSS_v4.0_7.3.1 | PCI DSS v4.0 7.3.1 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is managed via an access control system(s) | Shared | n/a | An access control system(s) is in place that restricts access based on a user’s need to know and covers all system components. | link | count: 017 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
General, Regulatory Compliance, Security Center, SQL | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.3.2 | PCI_DSS_v4.0_7.3.2 | PCI DSS v4.0 7.3.2 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is managed via an access control system(s) | Shared | n/a | The access control system(s) is configured to enforce permissions assigned to individuals, applications, and systems based on job classification and function. | link | count: 010 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 7.3.3 | PCI_DSS_v4.0_7.3.3 | PCI DSS v4.0 7.3.3 | Requirement 07: Restrict Access to System Components and Cardholder Data by Business Need to Know | Access to system components and data is managed via an access control system(s) | Shared | n/a | The access control system(s) is set to “deny all” by default. | link | count: 006 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.1.1 | PCI_DSS_v4.0_8.1.1 | PCI DSS v4.0 8.1.1 | Requirement 08: Identify Users and Authenticate Access to System Components | Processes and mechanisms for identifying users and authenticating access to system components are defined and understood | Shared | n/a | All security policies and operational procedures that are identified in Requirement 8 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 001 Review and update identification and authentication policies and procedures (29acfac0-4bb4-121b-8283-8943198b1549) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.2.1 | PCI_DSS_v4.0_8.2.1 | PCI DSS v4.0 8.2.1 | Requirement 08: Identify Users and Authenticate Access to System Components | User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle | Shared | n/a | All users are assigned a unique ID before access to system components or cardholder data is allowed. | link | count: 003 Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Enforce user uniqueness (e336d5f4-4d8f-0059-759c-ae10f63d1747), Support personal verification credentials issued by legal authorities (1d39b5d9-0392-8954-8359-575ce1957d1a) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.2.2 | PCI_DSS_v4.0_8.2.2 | PCI DSS v4.0 8.2.2 | Requirement 08: Identify Users and Authenticate Access to System Components | User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle | Shared | n/a | Group, shared, or generic accounts, or other shared authentication credentials are only used when necessary on an exception basis, and are managed as follows: • Account use is prevented unless needed for an exceptional circumstance. • Use is limited to the time needed for the exceptional circumstance. • Business justification for use is documented. • Use is explicitly approved by management. • Individual user identity is confirmed before access to an account is granted. • Every action taken is attributable to an individual user. | link | count: 004 Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Reissue authenticators for changed groups and accounts (2f204e72-1896-3bf8-75c9-9128b8683a36), Require use of individual authenticators (08ad71d0-52be-6503-4908-e015460a16ae), Terminate customer controlled account credentials (76d66b5c-85e4-93f5-96a5-ebb2fad61dc6) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.2.3 | PCI_DSS_v4.0_8.2.3 | PCI DSS v4.0 8.2.3 | Requirement 08: Identify Users and Authenticate Access to System Components | User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle | Shared | n/a | Service providers with remote access to customer premises use unique authentication factors for each customer premises. | link | count: 003 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.2.4 | PCI_DSS_v4.0_8.2.4 | PCI DSS v4.0 8.2.4 | Requirement 08: Identify Users and Authenticate Access to System Components | User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle | Shared | n/a | Addition, deletion, and modification of user IDs, authentication factors, and other identifier objects are managed as follows: • Authorized with the appropriate approval. • Implemented with only the privileges specified on the documented approval. | link | count: 007 Assign system identifiers (f29b17a4-0df2-8a50-058a-8570f9979d28), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734) |
Regulatory Compliance, Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.2.5 | PCI_DSS_v4.0_8.2.5 | PCI DSS v4.0 8.2.5 | Requirement 08: Identify Users and Authenticate Access to System Components | User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle | Shared | n/a | Access for terminated users is immediately revoked. | link | count: 002 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be) |
Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.2.6 | PCI_DSS_v4.0_8.2.6 | PCI DSS v4.0 8.2.6 | Requirement 08: Identify Users and Authenticate Access to System Components | User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle | Shared | n/a | Inactive user accounts are removed or disabled within 90 days of inactivity. | link | count: 002 Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.2.7 | PCI_DSS_v4.0_8.2.7 | PCI DSS v4.0 8.2.7 | Requirement 08: Identify Users and Authenticate Access to System Components | User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle | Shared | n/a | Accounts used by third parties to access, support, or maintain system components via remote access are managed as follows: • Enabled only during the time period needed and disabled when not in use. • Use is monitored for unexpected activity. | link | count: 006 Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Identify and authenticate non-organizational users (e1379836-3492-6395-451d-2f5062e14136) |
Regulatory Compliance, Security Center | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.2.8 | PCI_DSS_v4.0_8.2.8 | PCI DSS v4.0 8.2.8 | Requirement 08: Identify Users and Authenticate Access to System Components | User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle | Shared | n/a | If a user session has been idle for more than 15 minutes, the user is required to re-authenticate to re-activate the terminal or session. | link | count: 002 Define and enforce inactivity log policy (2af4640d-11a6-a64b-5ceb-a468f4341c0c), Terminate user session automatically (4502e506-5f35-0df4-684f-b326e3cc7093) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.1 | PCI_DSS_v4.0_8.3.1 | PCI DSS v4.0 8.3.1 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | All user access to system components for users and administrators is authenticated via at least one of the following authentication factors: • Something you know, such as a password or passphrase. • Something you have, such as a token device or smart card. • Something you are, such as a biometric element. | link | count: 004 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.10 | PCI_DSS_v4.0_8.3.10 | PCI DSS v4.0 8.3.10 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | If passwords/passphrases are used as the only authentication factor for customer user access to cardholder data (i.e., in any singlefactor authentication implementation), then guidance is provided to customer users including: • Guidance for customers to change their user passwords/passphrases periodically. • Guidance as to when, and under what circumstances, passwords/passphrases are changed. | link | count: 002 Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.10.1 | PCI_DSS_v4.0_8.3.10.1 | PCI DSS v4.0 8.3.10.1 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | If passwords/passphrases are used as the only authentication factor for customer user access (i.e., in any single-factor authentication implementation) then either: • Passwords/passphrases are changed at least once every 90 days, OR • The security posture of accounts is dynamically analyzed, and real-time access to resources is automatically determined accordingly. | link | count: 002 Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.11 | PCI_DSS_v4.0_8.3.11 | PCI DSS v4.0 8.3.11 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | Where authentication factors such as physical or logical security tokens, smart cards, or certificates are used: • Factors are assigned to an individual user and not shared among multiple users. • Physical and/or logical controls ensure only the intended user can use that factor to gain access. | link | count: 006 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Distribute authenticators (098dcde7-016a-06c3-0985-0daaf3301d3a), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.2 | PCI_DSS_v4.0_8.3.2 | PCI DSS v4.0 8.3.2 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components. | link | count: 002 Ensure authorized users protect provided authenticators (37dbe3dc-0e9c-24fa-36f2-11197cbfa207), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.4 | PCI_DSS_v4.0_8.3.4 | PCI DSS v4.0 8.3.4 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | Invalid authentication attempts are limited by: • Locking out the user ID after not more than 10 attempts. • Setting the lockout duration to a minimum of 30 minutes or until the user’s identity is confirmed. | link | count: 001 Enforce a limit of consecutive failed login attempts (b4409bff-2287-8407-05fd-c73175a68302) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.5 | PCI_DSS_v4.0_8.3.5 | PCI DSS v4.0 8.3.5 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | If passwords/passphrases are used as authentication factors to meet Requirement 8.3.1, they are set and reset for each user as follows: • Set to a unique value for first-time use and upon reset. • Forced to be changed immediately after the first use. | link | count: 001 Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.6 | PCI_DSS_v4.0_8.3.6 | PCI DSS v4.0 8.3.6 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | If passwords/passphrases are used as authentication factors to meet Requirement 8.3.1, they meet the following minimum level of complexity: • A minimum length of 12 characters (or IF the system does not support 12 characters, a minimum length of eight characters). • Contain both numeric and alphabetic characters. | link | count: 009 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d) |
Guest Configuration, Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.8 | PCI_DSS_v4.0_8.3.8 | PCI DSS v4.0 8.3.8 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | Authentication policies and procedures are documented and communicated to all users including: • Guidance on selecting strong authentication factors. • Guidance for how users should protect their authentication factors. • Instructions not to reuse previously used passwords/passphrases. • Instructions to change passwords/passphrases if there is any suspicion or knowledge that the password/passphrases have been compromised and how to report the incident. | link | count: 001 Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.3.9 | PCI_DSS_v4.0_8.3.9 | PCI DSS v4.0 8.3.9 | Requirement 08: Identify Users and Authenticate Access to System Components | Strong authentication for users and administrators is established and managed | Shared | n/a | If passwords/passphrases are used as the only authentication factor for user access (i.e., in any single-factor authentication implementation) then either: • Passwords/passphrases are changed at least once every 90 days, OR • The security posture of accounts is dynamically analyzed, and real-time access to resources is automatically determined accordingly. | link | count: 002 Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.4.1 | PCI_DSS_v4.0_8.4.1 | PCI DSS v4.0 8.4.1 | Requirement 08: Identify Users and Authenticate Access to System Components | Multi-factor authentication (MFA) is implemented to secure access into the CDE | Shared | n/a | MFA is implemented for all non-console access into the CDE for personnel with administrative access. | link | count: 008 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
General, Regulatory Compliance, Security Center, SQL | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.4.2 | PCI_DSS_v4.0_8.4.2 | PCI DSS v4.0 8.4.2 | Requirement 08: Identify Users and Authenticate Access to System Components | Multi-factor authentication (MFA) is implemented to secure access into the CDE | Shared | n/a | MFA is implemented for all access into the CDE. | link | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.4.3 | PCI_DSS_v4.0_8.4.3 | PCI DSS v4.0 8.4.3 | Requirement 08: Identify Users and Authenticate Access to System Components | Multi-factor authentication (MFA) is implemented to secure access into the CDE | Shared | n/a | MFA is implemented for all remote network access originating from outside the entity’s network that could access or impact the CDE as follows: • All remote access by all personnel, both users and administrators, originating from outside the entity’s network. • All remote access by third parties and vendors. | link | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.5.1 | PCI_DSS_v4.0_8.5.1 | PCI DSS v4.0 8.5.1 | Requirement 08: Identify Users and Authenticate Access to System Components | Multi-factor authentication (MFA) systems are configured to prevent misuse | Shared | n/a | MFA systems are implemented as follows: • The MFA system is not susceptible to replay attacks. • MFA systems cannot be bypassed by any users, including administrative users unless specifically documented, and authorized by management on an exception basis, for a limited time period. • At least two different types of authentication factors are used. • Success of all authentication factors is required before access is granted. | link | count: 008 Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Satisfy token quality requirements (056a723b-4946-9d2a-5243-3aa27c4d31a1) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.6.1 | PCI_DSS_v4.0_8.6.1 | PCI DSS v4.0 8.6.1 | Requirement 08: Identify Users and Authenticate Access to System Components | Use of application and system accounts and associated authentication factors is strictly managed | Shared | n/a | If accounts used by systems or a can be used for interactive login, they are managed as follows: • Interactive use is prevented unless needed for an exceptional circumstance. • Interactive use is limited to the time needed for the exceptional circumstance. • Business justification for interactive use is documented. • Interactive use is explicitly approved by management. • Individual user identity is confirmed before access to account is granted. • Every action taken is attributable to an individual user. | link | count: 002 Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.6.2 | PCI_DSS_v4.0_8.6.2 | PCI DSS v4.0 8.6.2 | Requirement 08: Identify Users and Authenticate Access to System Components | Use of application and system accounts and associated authentication factors is strictly managed | Shared | n/a | Passwords/passphrases for any application and system accounts that can be used for interactive login are not hard coded in scripts, configuration/property files, or bespoke and custom source code. | link | count: 001 Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 8.6.3 | PCI_DSS_v4.0_8.6.3 | PCI DSS v4.0 8.6.3 | Requirement 08: Identify Users and Authenticate Access to System Components | Use of application and system accounts and associated authentication factors is strictly managed | Shared | n/a | Passwords/passphrases for any application and system accounts are protected against misuse as follows: • Passwords/passphrases are changed periodically (at the frequency defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requirement 12.3.1) and upon suspicion or confirmation of compromise. • Passwords/passphrases are constructed with sufficient complexity appropriate for how frequently the entity changes the passwords/passphrases. | link | count: 006 Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Implement training for protecting authenticators (e4b00788-7e1c-33ec-0418-d048508e095b), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Refresh authenticators (3ae68d9a-5696-8c32-62d3-c6f9c52e437c) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.1.1 | PCI_DSS_v4.0_9.1.1 | PCI DSS v4.0 9.1.1 | Requirement 09: Restrict Physical Access to Cardholder Data | Processes and mechanisms for restricting physical access to cardholder data are defined and understood | Shared | n/a | All security policies and operational procedures that are identified in Requirement 9 are: • Documented. • Kept up to date. • In use. • Known to all affected parties. | link | count: 002 Review and update media protection policies and procedures (b4e19d22-8c0e-7cad-3219-c84c62dc250f), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.2.2 | PCI_DSS_v4.0_9.2.2 | PCI DSS v4.0 9.2.2 | Requirement 09: Restrict Physical Access to Cardholder Data | Physical access controls manage entry into facilities and systems containing cardholder data | Shared | n/a | Physical and/or logical controls are implemented to restrict use of publicly accessible network jacks within the facility. | link | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.2.3 | PCI_DSS_v4.0_9.2.3 | PCI DSS v4.0 9.2.3 | Requirement 09: Restrict Physical Access to Cardholder Data | Physical access controls manage entry into facilities and systems containing cardholder data | Shared | n/a | Physical access to wireless access points, gateways, networking/communications hardware, and telecommunication lines within the facility is restricted. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.2.4 | PCI_DSS_v4.0_9.2.4 | PCI DSS v4.0 9.2.4 | Requirement 09: Restrict Physical Access to Cardholder Data | Physical access controls manage entry into facilities and systems containing cardholder data | Shared | n/a | Access to consoles in sensitive areas is restricted via locking when not in use. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.3.1 | PCI_DSS_v4.0_9.3.1 | PCI DSS v4.0 9.3.1 | Requirement 09: Restrict Physical Access to Cardholder Data | Physical access for personnel and visitors is authorized and managed | Shared | n/a | Procedures are implemented for authorizing and managing physical access of personnel to the CDE, including: • Identifying personnel. • Managing changes to an individual’s physical access requirements. • Revoking or terminating personnel identification. • Limiting access to the identification process or system to authorized personnel. | link | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.3.1.1 | PCI_DSS_v4.0_9.3.1.1 | PCI DSS v4.0 9.3.1.1 | Requirement 09: Restrict Physical Access to Cardholder Data | Physical access for personnel and visitors is authorized and managed | Shared | n/a | Physical access to sensitive areas within the CDE for personnel is controlled as follows: • Access is authorized and based on individual job function. • Access is revoked immediately upon termination. • All physical access mechanisms, such as keys, access cards, etc., are returned or disabled upon termination. | link | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.3.2 | PCI_DSS_v4.0_9.3.2 | PCI DSS v4.0 9.3.2 | Requirement 09: Restrict Physical Access to Cardholder Data | Physical access for personnel and visitors is authorized and managed | Shared | n/a | Procedures are implemented for authorizing and managing visitor access to the CDE, including: • Visitors are authorized before entering. • Visitors are escorted at all times. • Visitors are clearly identified and given a badge or other identification that expires. • Visitor badges or other identification visibly distinguishes visitors from personnel. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.3.3 | PCI_DSS_v4.0_9.3.3 | PCI DSS v4.0 9.3.3 | Requirement 09: Restrict Physical Access to Cardholder Data | Physical access for personnel and visitors is authorized and managed | Shared | n/a | Visitor badges or identification are surrendered or deactivated before visitors leave the facility or at the date of expiration. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.3.4 | PCI_DSS_v4.0_9.3.4 | PCI DSS v4.0 9.3.4 | Requirement 09: Restrict Physical Access to Cardholder Data | Physical access for personnel and visitors is authorized and managed | Shared | n/a | A visitor log is used to maintain a physical record of visitor activity within the facility and within sensitive areas, including: • The visitor’s name and the organization represented. • The date and time of the visit. • The name of the personnel authorizing physical access. • Retaining the log for at least three months, unless otherwise restricted by law. | link | count: 002 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.4.1 | PCI_DSS_v4.0_9.4.1 | PCI DSS v4.0 9.4.1 | Requirement 09: Restrict Physical Access to Cardholder Data | Media with cardholder data is securely stored, accessed, distributed, and destroyed | Shared | n/a | Offline media backups with cardholder data are stored in a secure location. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.4.1.1 | PCI_DSS_v4.0_9.4.1.1 | PCI DSS v4.0 9.4.1.1 | Requirement 09: Restrict Physical Access to Cardholder Data | Media with cardholder data is securely stored, accessed, distributed, and destroyed | Shared | n/a | The security of the offline media backup location(s) with cardholder data is reviewed at least once every 12 months. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.4.2 | PCI_DSS_v4.0_9.4.2 | PCI DSS v4.0 9.4.2 | Requirement 09: Restrict Physical Access to Cardholder Data | Media with cardholder data is securely stored, accessed, distributed, and destroyed | Shared | n/a | All media with cardholder data is classified in accordance with the sensitivity of the data. | link | count: 001 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.4.3 | PCI_DSS_v4.0_9.4.3 | PCI DSS v4.0 9.4.3 | Requirement 09: Restrict Physical Access to Cardholder Data | Media with cardholder data is securely stored, accessed, distributed, and destroyed | Shared | n/a | Media with cardholder data sent outside the facility is secured as follows: • Media sent outside the facility is logged. • Media is sent by secured courier or other delivery method that can be accurately tracked. • Offsite tracking logs include details about media location. | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.4.4 | PCI_DSS_v4.0_9.4.4 | PCI DSS v4.0 9.4.4 | Requirement 09: Restrict Physical Access to Cardholder Data | Media with cardholder data is securely stored, accessed, distributed, and destroyed | Shared | n/a | Management approves all media with cardholder data that is moved outside the facility (including when media is distributed to individuals). | link | count: 002 Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.4.5.1 | PCI_DSS_v4.0_9.4.5.1 | PCI DSS v4.0 9.4.5.1 | Requirement 09: Restrict Physical Access to Cardholder Data | Media with cardholder data is securely stored, accessed, distributed, and destroyed | Shared | n/a | Inventories of electronic media with cardholder data are conducted at least once every 12 months. | link | count: 002 Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.4.6 | PCI_DSS_v4.0_9.4.6 | PCI DSS v4.0 9.4.6 | Requirement 09: Restrict Physical Access to Cardholder Data | Media with cardholder data is securely stored, accessed, distributed, and destroyed | Shared | n/a | Hard-copy materials with cardholder data are destroyed when no longer needed for business or legal reasons, as follows: • Materials are cross-cut shredded, incinerated, or pulped so that cardholder data cannot be reconstructed. • Materials are stored in secure storage containers prior to destruction. | link | count: 004 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.4.7 | PCI_DSS_v4.0_9.4.7 | PCI DSS v4.0 9.4.7 | Requirement 09: Restrict Physical Access to Cardholder Data | Media with cardholder data is securely stored, accessed, distributed, and destroyed | Shared | n/a | Electronic media with cardholder data is destroyed when no longer needed for business or legal reasons via one of the following: • The electronic media is destroyed. • The cardholder data is rendered unrecoverable so that it cannot be reconstructed. | link | count: 004 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.5.1 | PCI_DSS_v4.0_9.5.1 | PCI DSS v4.0 9.5.1 | Requirement 09: Restrict Physical Access to Cardholder Data | Point of interaction (POI) devices are protected from tampering and unauthorized substitution | Shared | n/a | POI devices that capture payment card data via direct physical interaction with the payment card form factor are protected from tampering and unauthorized substitution, including the following: • Maintaining a list of POI devices. • Periodically inspecting POI devices to look for tampering or unauthorized substitution. • Training personnel to be aware of suspicious behavior and to report tampering or unauthorized substitution of devices. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.5.1.2 | PCI_DSS_v4.0_9.5.1.2 | PCI DSS v4.0 9.5.1.2 | Requirement 09: Restrict Physical Access to Cardholder Data | Point of interaction (POI) devices are protected from tampering and unauthorized substitution | Shared | n/a | POI device surfaces are periodically inspected to detect tampering and unauthorized substitution. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.5.1.2.1 | PCI_DSS_v4.0_9.5.1.2.1 | PCI DSS v4.0 9.5.1.2.1 | Requirement 09: Restrict Physical Access to Cardholder Data | Point of interaction (POI) devices are protected from tampering and unauthorized substitution | Shared | n/a | The frequency of periodic POI device inspections and the type of inspections performed is defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requirement 12.3.1. | link | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| PCI_DSS_v4.0 | 9.5.1.3 | PCI_DSS_v4.0_9.5.1.3 | PCI DSS v4.0 9.5.1.3 | Requirement 09: Restrict Physical Access to Cardholder Data | Point of interaction (POI) devices are protected from tampering and unauthorized substitution | Shared | n/a | Training is provided for personnel in POI environments to be aware of attempted tampering or replacement of POI devices, and includes: • Verifying the identity of any third-party persons claiming to be repair or maintenance personnel, before granting them access to modify or troubleshoot devices. • Procedures to ensure devices are not installed, replaced, or returned without verification. • Being aware of suspicious behavior around devices. • Reporting suspicious behavior and indications of device tampering or substitution to appropriate personnel. | link | count: 001 Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082) |
Regulatory Compliance | PCI DSS v4 (c676748e-3af9-4e22-bc28-50feed564afb) |
| RBI_CSF_Banks_v2016 | 10.1 | RBI_CSF_Banks_v2016_10.1 | Secure Mail And Messaging Systems | Secure Mail And Messaging Systems-10.1 | n/a | Implement secure mail and messaging systems, including those used by bank???s partners & vendors, that include measures to prevent email spoofing, identical mail domains, protection of attachments, malicious links etc | count: 016 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, Security Center, SQL, Storage | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 10.2 | RBI_CSF_Banks_v2016_10.2 | Secure Mail And Messaging Systems | Secure Mail And Messaging Systems-10.2 | n/a | Document and implement emailserver specific controls | count: 016 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, Security Center, SQL, Storage | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 13.1 | RBI_CSF_Banks_v2016_13.1 | Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.1 | n/a | Build a robust defence against the installation, spread, and execution of malicious code at multiple points in the enterprise. | count: 027 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines (672fe5a1-2fcd-42d7-b85d-902b6e28c6ff), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines scale sets (a21f8c92-9e22-4f09-b759-50500d1d2dda), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines (1cb4d9c2-f88f-4069-bee0-dba239a57b09), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines scale sets (f655e522-adff-494d-95c2-52d4f6d56a42), [Preview]: Secure Boot should be enabled on supported Windows virtual machines (97566dd7-78ae-4997-8b36-1c7bfe0d8121), [Preview]: vTPM should be enabled on supported virtual machines (1c30f9cd-b84c-49cc-aa2c-9288447cc3b3), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Endpoint protection health issues should be resolved on your machines (8e42c1f2-a2ab-49bc-994a-12bcd0dc4ac2), Endpoint protection should be installed on your machines (1f7c564c-0a90-4d44-b7e1-9d456cffaee8), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Compute, Guest Configuration, Security Center, Storage | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 13.2 | RBI_CSF_Banks_v2016_13.2 | Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.2 | n/a | Implement Anti-malware, Antivirus protection including behavioural detection systems for all categories of devices ???(Endpoints such as PCs/laptops/ mobile devices etc.), servers (operating systems, databases, applications, etc.), Web/Internet gateways, email-gateways, Wireless networks, SMS servers etc. including tools and processes for centralised management and monitoring. | count: 021 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Kubernetes Service clusters should have Defender profile enabled (a1840de2-8088-4ea8-b153-b4c723e9cb01), Endpoint protection health issues should be resolved on your machines (8e42c1f2-a2ab-49bc-994a-12bcd0dc4ac2), Endpoint protection should be installed on your machines (1f7c564c-0a90-4d44-b7e1-9d456cffaee8), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Kubernetes, Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 13.3 | RBI_CSF_Banks_v2016_13.3 | Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.3 | n/a | Consider implementing whitelisting of internet websites/systems. | count: 015 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517) |
Backup, Network, Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 13.4 | RBI_CSF_Banks_v2016_13.4 | Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | n/a | Consider implementingsecure web gateways with capability to deep scan network packets including secure (HTTPS, etc.) traffic passing through the web/internet gateway | count: 043 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Automation, Cache, Cognitive Services, Container Registry, Cosmos DB, Guest Configuration, Machine Learning, Network, Security Center, SQL, Storage | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 14.1 | RBI_CSF_Banks_v2016_14.1 | Anti-Phishing | Anti-Phishing-14.1 | n/a | Subscribe to Anti-phishing/anti-rouge app services from external service providers for identifying and taking down phishing websites/rouge applications. | count: 030 [Preview]: Azure Recovery Services vaults should use private link for backup (deeddb44-9f94-4903-9fa0-081d524406e3), [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API Management, App Configuration, App Platform, Azure Ai Services, Backup, Container Registry, Event Grid, Key Vault, Machine Learning, Security Center, SQL, Storage, VM Image Builder | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 15.1 | RBI_CSF_Banks_v2016_15.1 | Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.1 | n/a | Develop a comprehensive data loss/leakage prevention strategy to safeguard sensitive (including confidential)business and customer data/information. | count: 008 All flow log resources should be in enabled state (27960feb-a23c-4577-8d36-ef8b5f35e0be), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Endpoint protection health issues should be resolved on your machines (8e42c1f2-a2ab-49bc-994a-12bcd0dc4ac2), Endpoint protection should be installed on your machines (1f7c564c-0a90-4d44-b7e1-9d456cffaee8), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Network, Security Center, Storage | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 15.2 | RBI_CSF_Banks_v2016_15.2 | Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.2 | n/a | This shall includeprotecting data processed in end point devices, data in transmission, as well as data stored in servers and other digital stores, whether online or offline. | count: 007 Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should disable public network access (b2982f36-99f2-4db5-8eff-283140c09693), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f) |
SQL, Storage | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 15.3 | RBI_CSF_Banks_v2016_15.3 | Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.3 | n/a | Similar arrangements need to be ensured at the vendor managed facilities as well. | count: 005 Endpoint protection health issues should be resolved on your machines (8e42c1f2-a2ab-49bc-994a-12bcd0dc4ac2), Endpoint protection should be installed on your machines (1f7c564c-0a90-4d44-b7e1-9d456cffaee8), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 16.1 | RBI_CSF_Banks_v2016_16.1 | Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | n/a | Consult all the stakeholders before finalising the scope, frequency and storage of log collection. | count: 005 All flow log resources should be in enabled state (27960feb-a23c-4577-8d36-ef8b5f35e0be), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Log duration should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e8f3), Network Watcher flow logs should have traffic analytics enabled (2f080164-9f4d-497e-9db6-416dc9f7b48a) |
Monitoring, Network, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 16.2 | RBI_CSF_Banks_v2016_16.2 | Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.2 | n/a | Manage and analyse audit logs in a systematic manner so as to detect, understand or recover from an attack. | count: 004 [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7) |
Monitoring | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 16.3 | RBI_CSF_Banks_v2016_16.3 | Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | n/a | Enough care is to be taken tocapture audit logs pertaining to user actions in a system. Such arrangements should facilitate forensic auditing, if need be. | count: 005 [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21) |
Key Vault, Monitoring, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 17.1 | RBI_CSF_Banks_v2016_17.1 | Audit Log Settings | Audit Log Settings-17.1 | n/a | Implement and periodically validate settings for capturing of appropriate logs/audit trails of each device, system software and application software , ensuring that logs include minimum information to uniquely identify the log for example by including a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or event and/or transaction. | count: 014 [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Data Lake, Event Hub, Guest Configuration, Key Vault, Logic Apps, Monitoring, Security Center, Service Bus, Stream Analytics | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 18.1 | RBI_CSF_Banks_v2016_18.1 | Vulnerability Assessment And Penetration Test And Red Team Exercises | Vulnerability Assessment And Penetration Test And Red Team Exercises-18.1 | n/a | Periodically conduct vulnerability assessment and penetration testing exercises for all the critical systems, particularly those facing the internet. | count: 003 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 18.2 | RBI_CSF_Banks_v2016_18.2 | Vulnerability Assessment And Penetration Test And Red Team Exercises | Vulnerability Assessment And Penetration Test And Red Team Exercises-18.2 | n/a | The vulnerabilities detected are to be remedied promptly in terms of the bank???s risk management/treatment framework so asto avoid exploitation of such vulnerabilities. | count: 004 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 18.4 | RBI_CSF_Banks_v2016_18.4 | Vulnerability Assessment And Penetration Test And Red Team Exercises | Vulnerability Assessment And Penetration Test And Red Team Exercises-18.4 | n/a | Findings of VA/PT and the follow up actions necessitated are to be monitored closely by the Information Security/Information Technology Audit team as well as Senior/Top Management. | count: 005 SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 19.2 | RBI_CSF_Banks_v2016_19.2 | Incident Response & Management | Responding To Cyber-Incidents:-19.2 | n/a | Have written incident response procedures including the roles of staff / outsourced staff handling such incidents; Response strategies shall consider readiness to meet various incident scenarios based on situational awareness and potential/post impact, consistent communication & co-ordination with stakeholders during response; | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 19.4 | RBI_CSF_Banks_v2016_19.4 | Incident Response & Management | Recovery From Cyber - Incidents-19.4 | n/a | Bank???s BCP/DR capabilities shall adequately and effectively support the Bank???s cyber resilience objectives and should be so designed to enable the bank to recover rapidly from cyber-attacks/other incidents and safely resume critical operations aligned with recovery time objectives while ensuring security of processes and data is protected. | count: 002 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Compute, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 19.5 | RBI_CSF_Banks_v2016_19.5 | Incident Response & Management | Recovery From Cyber - Incidents-19.5 | n/a | Banks shall ensure such capabilities in all interconnected systems and networks including those of vendors and partners and readiness demonstrated through collaborative & co-ordinated resilience testing that meet the bank???s recovery time objectives. | count: 005 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430) |
Backup, Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 19.6 | RBI_CSF_Banks_v2016_19.6 | Incident Response & Management | Recovery From Cyber - Incidents-19.6 | n/a | Such testing shall also include testing of crisis communication to customers and other internal and external stakeholders, reputation management. Adequate capacity shall be planned and maintained, in consideration thereof. The following may be considered: | count: 004 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 19.6b | RBI_CSF_Banks_v2016_19.6b | Incident Response & Management | Recovery From Cyber - Incidents-19.6b | n/a | Establish and implement a Security Operations Centre for centralised and coordinated monitoring and management of security related incidents. | count: 004 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 19.6c | RBI_CSF_Banks_v2016_19.6c | Incident Response & Management | Recovery From Cyber - Incidents-19.6c | n/a | Establish and implement systems to collect and share threat information from local/national/international sources following legally accepted/defined means/process | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 19.6e | RBI_CSF_Banks_v2016_19.6e | Incident Response & Management | Recovery From Cyber - Incidents-19.6e | n/a | Contain the level of cyber-attack by implementing shielding controls/quarantining the affected devices/systems. | count: 001 Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 2.1 | RBI_CSF_Banks_v2016_2.1 | Preventing Execution Of Unauthorised Software | Software Inventory-2.1 | n/a | Maintain an up-to-date and preferably centralised inventory of authorised/unauthorised software(s). Consider implementing whitelisting of authorised applications / software/libraries, etc. | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 2.2 | RBI_CSF_Banks_v2016_2.2 | Preventing Execution Of Unauthorised Software | Authorised Software Installation-2.2 | n/a | Have mechanism to centrally/otherwise control installation of software/applications on end-user PCs, laptops, workstations, servers, mobile devices, etc. and mechanism to block /prevent and identify installation and running of unauthorised software/applications on such devices/systems. | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 2.3 | RBI_CSF_Banks_v2016_2.3 | Preventing Execution Of Unauthorised Software | Security Update Management-2.3 | n/a | Continuously monitor the release of patches by various vendors / OEMs, advisories issued by CERT-in and other similar agencies and expeditiously apply the security patches as per the patch management policy of the bank. If a patch/series of patches is/are released by the OEM/manufacturer/vendor for protection against wellknown/well publicised/reported attacks exploiting the vulnerability patched, the banks must have a mechanism to apply them expeditiously following an emergency patch management process. | count: 007 SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 20.1 | RBI_CSF_Banks_v2016_20.1 | Risk Based Transaction Monitoring | Risk Based Transaction Monitoring-20.1 | n/a | Risk based transaction monitoring or surveillance process shall be implemented as part of fraud risk management system across all -delivery channels. | count: 006 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 21.1 | RBI_CSF_Banks_v2016_21.1 | Metrics | Metrics-21.1 | n/a | Develop a comprehensive set of metrics that provide for prospective and retrospective measures, like key performance indicators and key risk indicators | count: 015 Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
Cognitive Services, Container Registry, Cosmos DB, Key Vault, Machine Learning, Security Center, SQL, Storage | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 21.2 | RBI_CSF_Banks_v2016_21.2 | Metrics | Metrics-21.2 | n/a | Some illustrative metrics include coverage of anti-malware software and their updation percentage, patch latency, extent of user awareness training, vulnerability related metrics, etc | count: 001 Hotpatch should be enabled for Windows Server Azure Edition VMs (6d02d2f7-e38b-4bdc-96f3-adc0a8726abc) |
Automanage | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 22.1 | RBI_CSF_Banks_v2016_22.1 | Forensics | Forensics-22.1 | n/a | Have support/ arrangement for network forensics/forensic investigation/DDOS mitigation services on stand-by. | count: 001 Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 4.10 | RBI_CSF_Banks_v2016_4.10 | Network Management And Security | Perimeter Protection And Detection-4.10 | n/a | Boundary defences should be multi-layered with properly configured firewalls, proxies, DMZ perimeter networks, and network--???based IPS and IDS. Mechanism to filter both inbound and outbound traffic to be put in place. | count: 012 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Network, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 4.2 | RBI_CSF_Banks_v2016_4.2 | Network Management And Security | Network Inventory-4.2 | n/a | Maintain an up-to-date/centralised inventory of authorised devices connected to bank???s network (within/outside bank???s premises) and authorised devices enabling the bank???s network. The bank may consider implementing solutions to automate network discovery and management. | count: 006 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Network Watcher flow logs should have traffic analytics enabled (2f080164-9f4d-497e-9db6-416dc9f7b48a) |
Monitoring, Network, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 4.3 | RBI_CSF_Banks_v2016_4.3 | Network Management And Security | Network Device Configuration Management-4.3 | n/a | Ensure that all the network devices are configured appropriately and periodically assess whether the configurations are appropriate to the desired level of network security. | count: 017 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: vTPM should be enabled on supported virtual machines (1c30f9cd-b84c-49cc-aa2c-9288447cc3b3), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Azure firewall policy should enable TLS inspection within application rules (a58ac66d-92cb-409c-94b8-8e48d7a96596), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should enable all firewall rules for Application Gateway (632d3993-e2c0-44ea-a7db-2eca131f356d) |
App Service, Network, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 4.7 | RBI_CSF_Banks_v2016_4.7 | Network Management And Security | Anomaly Detection-4.7 | n/a | Put in place mechanism to detect and remedy any unusual activities in systems, servers, network devices and endpoints. | count: 014 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Network, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 4.9 | RBI_CSF_Banks_v2016_4.9 | Network Management And Security | Security Operation Centre-4.9 | n/a | Security Operation Centre to monitor the logs of various network activities and should have the capability to escalate any abnormal / undesirable activities. | count: 015 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Network, Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 5.1 | RBI_CSF_Banks_v2016_5.1 | Secure Configuration | Secure Configuration-5.1 | n/a | Document and apply baseline security requirements/configurations to all categories of devices (end-points/workstations, mobile devices, operating systems, databases, applications, network devices, security devices, security systems, etc.), throughout the lifecycle (from conception to deployment) and carry out reviews periodically. | count: 008 Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Azure Cosmos DB should be enabled (adbe85b5-83e6-4350-ab58-bf3a4f736e5e), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 5.2 | RBI_CSF_Banks_v2016_5.2 | Secure Configuration | Secure Configuration-5.2 | n/a | Periodically evaluate critical device (such as firewall, network switches, security devices, etc.) configurations and patch levels for all systems in the bank???s network including in Data Centres, in third party hosted sites, shared-infrastructure locations. | count: 002 Hotpatch should be enabled for Windows Server Azure Edition VMs (6d02d2f7-e38b-4bdc-96f3-adc0a8726abc), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Automanage, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 6.1 | RBI_CSF_Banks_v2016_6.1 | Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.1 | n/a | Incorporate/Ensure information security across all stages of application life cycle. | count: 001 Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 6.3 | RBI_CSF_Banks_v2016_6.3 | Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.3 | n/a | Secure coding practices may also be implemented for internally /collaboratively developed applications. | count: 001 Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 6.4 | RBI_CSF_Banks_v2016_6.4 | Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | n/a | Besides business functionalities, security requirements relating to system access control, authentication, transaction authorization, data integrity, system activity logging, audit trail, session management, security event tracking and exception handling are required to be clearly specified at the initial and ongoing stages of system development/acquisition/implementation. | count: 013 App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Application Insights components should block log ingestion and querying from public networks (1bc02227-0cb6-4e11-8f53-eb0b22eab7e8), Application Insights components should block non-Azure Active Directory based ingestion. (199d5677-e4d9-4264-9465-efe1839c06bd), Application Insights components with Private Link enabled should use Bring Your Own Storage accounts for profiler and debugger. (0c4bd2e8-8872-4f37-a654-03f6f38ddc76), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Monitor Logs for Application Insights should be linked to a Log Analytics workspace (d550e854-df1a-4de9-bf44-cd894b39a95e), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d) |
App Service, Key Vault, Logic Apps, Monitoring, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 6.6 | RBI_CSF_Banks_v2016_6.6 | Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.6 | n/a | Software/Application development approach should be based on threat modelling, incorporate secure coding principles and security testing based on global standards and secure rollout | count: 001 Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 6.7 | RBI_CSF_Banks_v2016_6.7 | Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.7 | n/a | Ensure that software/application development practices addresses the vulnerabilities based on best practices baselines such as Open Web Application Security Project (OWASP) proactively and adopt principle of defence-in-depth to provide layered security mechanism. | count: 004 Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should enable all firewall rules for Application Gateway (632d3993-e2c0-44ea-a7db-2eca131f356d), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096) |
Network, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 7.1 | RBI_CSF_Banks_v2016_7.1 | Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.1 | n/a | Follow a documented risk-based strategy for inventorying IT components that need to be patched, identification of patches and applying patches so as to minimize the number of vulnerable systems and the time window of vulnerability/exposure. | count: 010 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 7.2 | RBI_CSF_Banks_v2016_7.2 | Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.2 | n/a | Put in place systems and processes to identify, track, manage and monitor the status of patches to operating system and application software running at end-user devices directly connected to the internet and in respect of Server operating Systems/Databases/Applications/ Middleware, etc. | count: 010 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 7.6 | RBI_CSF_Banks_v2016_7.6 | Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.6 | n/a | As a threat mitigation strategy, identify the root cause of incident and apply necessary patches to plug the vulnerabilities. | count: 018 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 7.7 | RBI_CSF_Banks_v2016_7.7 | Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | n/a | Periodically evaluate the access device configurations and patch levels to ensure that all access points, nodes between (i) different VLANs in the Data Centre (ii) LAN/WAN interfaces (iii) bank???s network to external network and interconnections with partner, vendor and service provider networks are to be securely configured. | count: 025 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Spring Cloud should use network injection (af35e2a4-ef96-44e7-a9ae-853dd97032c4), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
API Management, App Configuration, App Platform, Container Registry, Event Grid, Guest Configuration, Key Vault, Machine Learning, Security Center, SQL, Storage, VM Image Builder | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 8.1 | RBI_CSF_Banks_v2016_8.1 | User Access Control / Management | User Access Control / Management-8.1 | n/a | Provide secure access to the bank???s assets/services from within/outside bank???s network by protecting data/information at rest (e.g. using encryption, if supported by the device) and in-transit (e.g. using technologies such as VPN or other secure web protocols, etc.) | count: 010 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
General, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 8.2 | RBI_CSF_Banks_v2016_8.2 | User Access Control / Management | User Access Control / Management-8.2 | n/a | Carefully protect customer access credentials such as logon userid, authentication information and tokens, access profiles, etc. against leakage/attacks | count: 007 An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0) |
Security Center, Service Fabric, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 8.3 | RBI_CSF_Banks_v2016_8.3 | User Access Control / Management | User Access Control / Management-8.3 | n/a | Disallow administrative rights on end-user workstations/PCs/laptops and provide access rights on a need to know basis and for specific duration when it is required following an established process. | count: 005 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 8.4 | RBI_CSF_Banks_v2016_8.4 | User Access Control / Management | User Access Control / Management-8.4 | n/a | Implement centralised authentication and authorisation system or accessing and administering applications, operating systems, databases, network and security devices/systems, point of connectivity (local/remote, etc.) including enforcement of strong password policy, two-factor/multi-factor authentication depending on risk assessment and following the principle of least privileges and separation of duties. | count: 003 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 8.5 | RBI_CSF_Banks_v2016_8.5 | User Access Control / Management | User Access Control / Management-8.5 | n/a | Implement appropriate (e.g. centralised) systems and controls to allow, manage, log and monitor privileged/superuser/administrative access to critical systems (Servers/OS/DB, applications, network devices etc.). | count: 012 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
General, Security Center, Service Fabric, SQL | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 8.8 | RBI_CSF_Banks_v2016_8.8 | User Access Control / Management | User Access Control / Management-8.8 | n/a | Implement measures to control installation of software on PCs/laptops, etc | count: 002 Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
General, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 9.1 | RBI_CSF_Banks_v2016_9.1 | Authentication Framework For Customers | Authentication Framework For Customers-9.1 | n/a | Implement authentication framework/mechanism to provide positive identify verification of bank to customers. | count: 004 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6) |
Guest Configuration, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_CSF_Banks_v2016 | 9.3 | RBI_CSF_Banks_v2016_9.3 | Authentication Framework For Customers | Authentication Framework For Customers-9.3 | n/a | Banks should act as the identity provider for identification and authentication of customers for access to partner systems using secure authentication technologies | count: 007 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
Guest Configuration, Security Center | [Preview]: Reserve Bank of India - IT Framework for Banks (d0d5578d-cc08-2b22-31e3-f525374f235a) | |||
| RBI_ITF_NBFC_v2017 | 1 | RBI_ITF_NBFC_v2017_1 | RBI IT Framework 1 | IT Governance | IT Governance-1 | n/a | IT Governance is an integral part of corporate governance. It involves leadership support, organizational structure and processes to ensure that the NBFC???s IT sustains and extends business strategies and objectives. Effective IT Governance is the responsibility of the Board of Directors and Executive Management. Well-defined roles and responsibilities of Board and Senior Management are critical, while implementing IT Governance. Clearly-defined roles enable effective project control. People, when they are aware of others' expectations from them, are able to complete work on time, within budget and to the expected level of quality. IT Governance Stakeholders include: Board of Directors, IT Strategy Committees, CEOs, Business Executives, Chief Information Officers (CIOs), Chief Technology Officers (CTOs), IT Steering Committees (operating at an executive level and focusing on priority setting, resource allocation and project tracking), Chief Risk Officer and Risk Committees. The basic principles of value delivery, IT Risk Management, IT resource management and performance management must form the basis of governance framework. IT Governance has a continuous life-cycle. It's a process in which IT strategy drives the processes, using resources necessary to execute responsibilities. Given the criticality of the IT, NBFCs may follow relevant aspects of such prudential governance standards that have found acceptability in the finance industry. | link | count: 014 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 1.1 | RBI_ITF_NBFC_v2017_1.1 | RBI IT Framework 1.1 | IT Governance | IT Governance-1.1 | n/a | NBFCs are required to form an IT Strategy Committee. The chairman of the committee shall be an independent director and CIO & CTO should be a part of the committee. The IT Strategy Committee should meet at an appropriate frequency but not more than six months should elapse between two meetings. The Committee shall work in partnership with other Board committees and Senior Management to provide input to them. It will also carry out review and amend the IT strategies in line with the corporate strategies, Board Policy reviews, cyber security arrangements and any other matter related to IT Governance. Its deliberations may be placed before the Board. | link | count: 004 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917) |
Network, Security Center | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 2 | RBI_ITF_NBFC_v2017_2 | RBI IT Framework 2 | IT Policy | IT Policy-2 | n/a | NBFCs may formulate a Board approved IT Policy, in line with the objectives of their organisation comprising the following: a. An IT organizational structure commensurate with the size, scale and nature of business activities carried out by the NBFC; b. NBFCs may designate a senior executive as the Chief Information Officer (CIO) or in-Charge of IT Operations whose responsibility is to ensure implementation of IT Policy to the operational level involving IT strategy, value delivery, risk management and IT resource management. c. To ensure technical competence at senior/middle level management of NBFC, periodic assessment of the IT training requirements should be formulated to ensure that sufficient, competent and capable human resources are available. d. The NBFCs which are currently not using IPv6 platform should migrate to the same as per National Telecom Policy issued by the Government of India in 2012. (As per Circular DNBS(Inf.).CC.No 309/24.01.022/2012-13 November 08, 2012) | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 3 | RBI_ITF_NBFC_v2017_3 | RBI IT Framework 3 | Information and Cyber Security | Information Security-3 | n/a | Information is an asset to all NBFCs and Information Security (IS) refers to the protection of these assets in order to achieve organizational goals. The purpose of IS is to control access to sensitive information, ensuring use only by legitimate users so that data cannot be read or compromised without proper authorization. NBFCs must have a board approved IS Policy with the following basic tenets: Confidentiality ??? Ensuring access to sensitive data to authorized users only. Integrity ??? Ensuring accuracy and reliability of information by ensuring that there is no modification without authorization. Availability ??? Ensuring that uninterrupted data is available to users when it is needed. Authenticity ??? For IS it is necessary to ensure that the data, transactions, communications or documents (electronic or physical) are genuine. | link | count: 001 Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 3.1.a | RBI_ITF_NBFC_v2017_3.1.a | RBI IT Framework 3.1.a | Information and Cyber Security | Identification and Classification of Information Assets-3.1 | n/a | The IS Policy must provide for a IS framework with the following basic tenets: Identification and Classification of Information Assets. NBFCs shall maintain detailed inventory of Information Asset with distinct and clear identification of the asset. | link | count: 007 Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
General, Security Center | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 3.1.b | RBI_ITF_NBFC_v2017_3.1.b | RBI IT Framework 3.1.b | Information and Cyber Security | Segregation of Functions-3.1 | n/a | The IS Policy must provide for a IS framework with the following basic tenets: Segregation of functions: There should be segregation of the duties of the Security Officer/Group (both physical security as well as cyber security) dealing exclusively with information systems security and the Information Technology division which actually implements the computer systems. The information security function should be adequately resourced in terms of the number of staff, level of skill and tools or techniques like risk assessment, security architecture, vulnerability assessment, forensic assessment, etc. Further, there should be a clear segregation of responsibilities relating to system administration, database administration and transaction processing. | link | count: 006 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), [Preview]: Secure Boot should be enabled on supported Windows virtual machines (97566dd7-78ae-4997-8b36-1c7bfe0d8121), [Preview]: vTPM should be enabled on supported virtual machines (1c30f9cd-b84c-49cc-aa2c-9288447cc3b3), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Security Center | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 3.1.c | RBI_ITF_NBFC_v2017_3.1.c | RBI IT Framework 3.1.c | Information and Cyber Security | Role based Access Control-3.1 | n/a | The IS Policy must provide for a IS framework with the following basic tenets: Role based Access Control ??? Access to information should be based on well-defined user roles (system administrator, user manager, application owner etc.), NBFCs shall avoid dependence on one or few persons for a particular job. There should be clear delegation of authority for right to upgrade/change user profiles and permissions and also key business parameters (eg. interest rates) which should be documented. | link | count: 015 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Monitoring, Security Center | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 3.1.f | RBI_ITF_NBFC_v2017_3.1.f | RBI IT Framework 3.1.f | Information and Cyber Security | Maker-checker-3.1 | n/a | The IS Policy must provide for a IS framework with the following basic tenets: Maker-checker is one of the important principles of authorization in the information systems of financial entities. For each transaction, there must be at least two individuals necessary for its completion as this will reduce the risk of error and will ensure reliability of information. | link | count: 023 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
General, Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 3.1.g | RBI_ITF_NBFC_v2017_3.1.g | RBI IT Framework 3.1.g | Information and Cyber Security | Trails-3.1 | n/a | The IS Policy must provide for a IS framework with the following basic tenets: Trails- NBFCs shall ensure that audit trails exist for IT assets satisfying its business requirements including regulatory and legal requirements, facilitating audit, serving as forensic evidence when required and assisting in dispute resolution. If an employee, for instance, attempts to access an unauthorized section, this improper activity should be recorded in the audit trail. | link | count: 039 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Activity log should be retained for at least one year (b02aacc0-b073-424e-8298-42b22829ee0a), All flow log resources should be in enabled state (27960feb-a23c-4577-8d36-ef8b5f35e0be), Application Insights components should block log ingestion and querying from public networks (1bc02227-0cb6-4e11-8f53-eb0b22eab7e8), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Kubernetes Service clusters should have Defender profile enabled (a1840de2-8088-4ea8-b153-b4c723e9cb01), Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Monitor Logs for Application Insights should be linked to a Log Analytics workspace (d550e854-df1a-4de9-bf44-cd894b39a95e), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7), Disconnections should be logged for PostgreSQL database servers. (eb6f77b9-bd53-4e35-a23d-7f65d5f0e446), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Log Analytics workspaces should block log ingestion and querying from public networks (6c53d030-cc64-46f0-906d-2bc061cd1334), Log Analytics Workspaces should block non-Azure Active Directory based ingestion. (e15effd4-2278-4c65-a0da-4d6f6d1890e2), Log checkpoints should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e43d), Log connections should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e442), Log duration should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e8f3), Logic Apps Integration Service Environment should be encrypted with customer-managed keys (1fafeaf6-7927-4059-a50a-8eb2a7a6f2b5), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher flow logs should have traffic analytics enabled (2f080164-9f4d-497e-9db6-416dc9f7b48a), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743), Storage account containing the container with activity logs must be encrypted with BYOK (fbb99e8e-e444-4da0-9ff1-75c92f5a85b2), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
Kubernetes, Logic Apps, Monitoring, Network, Security Center, SQL | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 3.1.h | RBI_ITF_NBFC_v2017_3.1.h | RBI IT Framework 3.1.h | Information and Cyber Security | Public Key Infrastructure (PKI)-3.1 | n/a | The IS Policy must provide for a IS framework with the following basic tenets: Public Key Infrastructure (PKI) - NBFCs may increase the usage of PKI to ensure confidentiality of data, access control, data integrity, authentication and nonrepudiation. | link | count: 032 App Configuration should use a customer-managed key (967a4b4b-2da9-43c1-b7d0-f98d0d74d0b1), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d), Managed disks should use a specific set of disk encryption sets for the customer-managed key encryption (d461a302-a187-421a-89ac-84acdb4edc04), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage account encryption scopes should use double encryption for data at rest (bfecdea6-31c4-4045-ad42-71b9dc87247d), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Configuration, App Service, Automation, Azure Data Explorer, Compute, Cosmos DB, Key Vault, Monitoring, Security Center, SQL, Storage | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 3.3 | RBI_ITF_NBFC_v2017_3.3 | RBI IT Framework 3.3 | Information and Cyber Security | Vulnerability Management-3.3 | n/a | A vulnerability can be defined as an inherent configuration flaw in an organization???s information technology base, whether hardware or software, which can be exploited by a third party to gather sensitive information regarding the organization. Vulnerability management is an ongoing process to determine the process of eliminating or mitigating vulnerabilities based upon the risk and cost associated with the vulnerabilities. NBFCs may devise a strategy for managing and eliminating vulnerabilities and such strategy may clearly be communicated in the Cyber Security policy | link | count: 012 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), SQL servers on machines should have vulnerability findings resolved (6ba6d016-e7c3-4842-b8f2-4992ebc0d72d), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Security Center, SQL, Synapse | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 3.8 | RBI_ITF_NBFC_v2017_3.8 | RBI IT Framework 3.8 | Information and Cyber Security | Digital Signatures-3.8 | n/a | A Digital Signature Certificate authenticates entity???s identity electronically. It also provides a high level of security for online transactions by ensuring absolute privacy of the information exchanged using a Digital Signature Certificate. NBFCs may consider use of Digital signatures to protect the authenticity and integrity of important electronic documents and also for high value fund transfer. | link | count: 007 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), Certificates should be issued by the specified integrated certificate authority (8e826246-c976-48f6-b03e-619bb92b3d82), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Certificates should use allowed key types (1151cede-290b-4ba0-8b38-0ad145ac888f), Certificates using elliptic curve cryptography should have allowed curve names (bd78111f-4953-4367-9fd5-7e08808b54bf), Certificates using RSA cryptography should have the specified minimum key size (cee51871-e572-4576-855c-047c820360f0) |
App Service, Key Vault | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 4.2 | RBI_ITF_NBFC_v2017_4.2 | RBI IT Framework 4.2 | IT Operations | IT Operations-4.2 | n/a | NBFCs are required to realign their IT systems on a regular basis in line with the changing needs of its customers and business. The changes need to be done in such a way that adverse incidents and disruption to services are minimized while maximizing value for the customers. For this purpose, NBFCs should develop, with the approval of their Board, a Change Management Policy that encompasses the following: prioritizing and responding to change proposals from business, cost benefit analysis of the changes proposed, assessing risks associated with the changes proposed, change implementation, monitoring and reporting. It should be the responsibility of the senior management to ensure that the Change Management policy is being followed on an ongoing basis. | link | count: 001 [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602) |
Monitoring | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 4.4a | RBI_ITF_NBFC_v2017_4.4a | RBI IT Framework 4.4.a | IT Operations | IT Operations-4.4 | n/a | NBFCs may put in place MIS that assist the Top Management as well as the business heads in decision making and also to maintain an oversight over operations of various business verticals. With robust IT systems in place, NBFCs may have the following as part of an effective system generated MIS (indicative list) A dashboard for the Top Management summarising financial position vis-??-vis targets. It may include information on trend on returns on assets across categories, major growth business segments, movement of net-worth etc. System enabled identification and classification of Special Mention Accounts and NPA as well as generation of MIS reports in this regard. The MIS should facilitate pricing of products, especially large ticket loans. The MIS should capture regulatory requirements and their compliance. Financial Reports including operating and non-operating revenues and expenses, cost benefit analysis of segments/verticals, cost of funds, etc. (also regulatory compliance at transaction level) Reports relating to treasury operations. Fraud analysis- Suspicious transaction analysis, embezzlement, theft or suspected money-laundering, misappropriation of assets, manipulation of financial records etc. The regulatory requirement of reporting fraud to RBI should be system driven. Capacity and performance analysis of IT security systems Incident reporting, their impact and steps taken for non -recurrence of such events in the future. | link | count: 003 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 4.4b | RBI_ITF_NBFC_v2017_4.4b | RBI IT Framework 4.4.b | IT Operations | MIS For Top Management-4.4 | n/a | NBFCs may put in place MIS that assist the Top Management as well as the business heads in decision making and also to maintain an oversight over operations of various business verticals. With robust IT systems in place, NBFCs may have the following as part of an effective system generated MIS (indicative list) A dashboard for the Top Management summarising financial position vis-??-vis targets. It may include information on trend on returns on assets across categories, major growth business segments, movement of net-worth etc. System enabled identification and classification of Special Mention Accounts and NPA as well as generation of MIS reports in this regard. The MIS should facilitate pricing of products, especially large ticket loans. The MIS should capture regulatory requirements and their compliance. Financial Reports including operating and non-operating revenues and expenses, cost benefit analysis of segments/verticals, cost of funds, etc. (also regulatory compliance at transaction level) Reports relating to treasury operations. Fraud analysis- Suspicious transaction analysis, embezzlement, theft or suspected money-laundering, misappropriation of assets, manipulation of financial records etc. The regulatory requirement of reporting fraud to RBI should be system driven. Capacity and performance analysis of IT security systems Incident reporting, their impact and steps taken for non -recurrence of such events in the future. | link | count: 003 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2) |
Security Center | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 5 | RBI_ITF_NBFC_v2017_5 | RBI IT Framework 5 | IS Audit | Policy for Information System Audit (IS Audit)-5 | n/a | The objective of the IS Audit is to provide an insight on the effectiveness of controls that are in place to ensure confidentiality, integrity and availability of the organization???s IT infrastructure. IS Audit shall identify risks and methods to mitigate risk arising out of IT infrastructure such as server architecture, local and wide area networks, physical and information security, telecommunications etc. | link | count: 014 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), All flow log resources should be in enabled state (27960feb-a23c-4577-8d36-ef8b5f35e0be), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP firewall rules on Azure Synapse workspaces should be removed (56fd377d-098c-4f02-8406-81eb055902b8), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8) |
Cosmos DB, Network, Security Center, Synapse | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 5.2 | RBI_ITF_NBFC_v2017_5.2 | RBI IT Framework 5.2 | IS Audit | Coverage-5.2 | n/a | IS Audit should cover effectiveness of policy and oversight of IT systems, evaluating adequacy of processes and internal controls, recommend corrective action to address deficiencies and follow-up. IS Audit should also evaluate the effectiveness of business continuity planning, disaster recovery set up and ensure that BCP is effectively implemented in the organization. During the process of IS Audit, due importance shall be given to compliance of all the applicable legal and statutory requirements. | link | count: 004 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430) |
Backup, SQL | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 6 | RBI_ITF_NBFC_v2017_6 | RBI IT Framework 6 | Business Continuity Planning | Business Continuity Planning (BCP) and Disaster Recovery-6 | n/a | BCP forms a significant part of an organisation's overall Business Continuity Management plan, which includes policies, standards and procedures to ensure continuity, resumption and recovery of critical business processes. BCP shall be designed to minimise the operational, financial, legal, reputational and other material consequences arising from a disaster. NBFC should adopt a Board approved BCP Policy. The functioning of BCP shall be monitored by the Board by way of periodic reports. The CIO shall be responsible for formulation, review and monitoring of BCP to ensure continued effectiveness. The BCP may have the following salient features | link | count: 009 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: Azure Recovery Services vaults should use private link for backup (deeddb44-9f94-4903-9fa0-081d524406e3), [Preview]: Recovery Services vaults should use private link (11e3da8c-1d68-4392-badd-0ff3c43ab5b0), Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Backup, Compute, Site Recovery, SQL | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 6.2 | RBI_ITF_NBFC_v2017_6.2 | RBI IT Framework 6.2 | Business Continuity Planning | Recovery strategy / Contingency Plan-6.2 | n/a | NBFCs shall try to fully understand the vulnerabilities associated with interrelationships between various systems, departments and business processes. The BCP should come up with the probabilities of various failure scenarios. Evaluation of various options should be done for recovery and the most cost-effective, practical strategy should be selected to minimize losses in case of a disaster. | link | count: 008 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: Azure Recovery Services vaults should use private link for backup (deeddb44-9f94-4903-9fa0-081d524406e3), Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Backup, Compute, SQL | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 6.3 | RBI_ITF_NBFC_v2017_6.3 | RBI IT Framework 6.3 | Business Continuity Planning | Recovery strategy / Contingency Plan-6.3 | n/a | NBFCs shall consider the need to put in place necessary backup sites for their critical business systems and Data centers. | link | count: 007 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: Azure Recovery Services vaults should use private link for backup (deeddb44-9f94-4903-9fa0-081d524406e3), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Backup, SQL | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RBI_ITF_NBFC_v2017 | 6.4 | RBI_ITF_NBFC_v2017_6.4 | RBI IT Framework 6.4 | Business Continuity Planning | Recovery strategy / Contingency Plan-6.4 | n/a | NBFCs shall test the BCP either annually or when significant IT or business changes take place to determine if the entity could be recovered to an acceptable level of business within the timeframe stated in the contingency plan. The test should be based on ???worst case scenarios???. The results along with the gap analysis may be placed before the CIO and the Board. The GAP Analysis along with Board???s insight should form the basis for construction of the updated BCP. | link | count: 004 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: Azure Recovery Services vaults should use private link for backup (deeddb44-9f94-4903-9fa0-081d524406e3), [Preview]: Recovery Services vaults should use private link (11e3da8c-1d68-4392-badd-0ff3c43ab5b0), Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56) |
Backup, Compute, Site Recovery | [Preview]: Reserve Bank of India - IT Framework for NBFC (7f89f09c-48c1-f28d-1bd5-84f3fb22f86c) | |
| RMiT_v1.0 | 10.16 | RMiT_v1.0_10.16 | RMiT 10.16 | Cryptography | Cryptography - 10.16 | Shared | n/a | A financial institution must establish a robust and resilient cryptography policy to promote the adoption of strong cryptographic controls for protection of important data and information. This policy, at a minimum, shall address requirements for: (a) the adoption of industry standards for encryption algorithms, message authentication, hash functions, digital signatures and random number generation; (b) the adoption of robust and secure processes in managing cryptographic key lifecycles which include generation, distribution, renewal, usage, storage, recovery, revocation and destruction; (c) the periodic review, at least every three years, of existing cryptographic standards and algorithms in critical systems, external linked or transactional customer-facing applications to prevent exploitation of weakened algorithms or protocols; and (d) the development and testing of compromise-recovery plans in the event of a cryptographic key compromise. This must set out the escalation process, procedures for keys regeneration, interim measures, changes to business-as-usual protocols and containment strategies or options to minimise the impact of a compromise. | link | count: 010 Azure Key Vault Managed HSM should have purge protection enabled (c39ba22d-4428-4149-b981-70acb31fc383), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12) |
Key Vault, SQL, Storage | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.19 | RMiT_v1.0_10.19 | RMiT 10.19 | Cryptography | Cryptography - 10.19 | Shared | n/a | A financial institution must ensure cryptographic controls are based on the effective implementation of suitable cryptographic protocols. The protocols shall include secret and public cryptographic key protocols, both of which shall reflect a high degree of protection to the applicable secret or private cryptographic keys. The selection of such protocols must be based on recognised international standards and tested accordingly. Commensurate with the level of risk, secret cryptographic key and private-cryptographic key storage and encryption/decryption computation must be undertaken in a protected environment, supported by a hardware security module (HSM) or trusted execution environment (TEE). | link | count: 006 Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Key Vault should use a virtual network service endpoint (ea4d6841-2173-4317-9747-ff522a45120f), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8) |
Kubernetes, Network, Security Center, SQL | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.20 | RMiT_v1.0_10.20 | RMiT 10.20 | Cryptography | Cryptography - 10.20 | Shared | n/a | A financial institution shall store public cryptographic keys in a certificate issued by a certificate authority as appropriate to the level of risk. Such certificates associated with customers shall be issued by recognised certificate authorities. The financial institution must ensure that the implementation of authentication and signature protocols using such certificates are subject to strong protection to ensure that the use of private cryptographic keys corresponding to the user certificates are legally binding and irrefutable. The initial issuance and subsequent renewal of such certificates must be consistent with industry best practices and applicable legal/regulatory specifications. | link | count: 002 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef) |
App Service | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.27 | RMiT_v1.0_10.27 | RMiT 10.27 | Datacenter Operations | Datacenter Operations - 10.27 | Shared | n/a | A financial institution must establish real-time monitoring mechanisms to track capacity utilisation and performance of key processes and services. These monitoring mechanisms shall be capable of providing timely and actionable alerts to administrators. | link | count: 002 Deploy - Configure Log Analytics extension to be enabled on Windows virtual machine scale sets (3c1b3629-c8f8-4bf6-862c-037cb9094038), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Monitoring | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.30 | RMiT_v1.0_10.30 | RMiT 10.30 | Datacenter Operations | Datacenter Operations - 10.30 | Shared | n/a | A financial institution is required to undertake an independent risk assessment of its end-to-end backup storage and delivery management to ensure that existing controls are adequate in protecting sensitive data at all times. A financial institution must also maintain a sufficient number of backup copies of critical data, the updated version of the operating system software, production programs, system utilities, all master and transaction files and event logs for recovery purposes. Backup media must be stored in an environmentally secure and access-controlled backup site. | link | count: 002 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7) |
Backup, Monitoring | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.33 | RMiT_v1.0_10.33 | RMiT 10.33 | Network Resilience | Network Resilience - 10.33 | Shared | n/a | A financial institution must design a reliable, scalable and secure enterprise network that is able to support its business activities, including future growth plans. | link | count: 028 All flow log resources should be in enabled state (27960feb-a23c-4577-8d36-ef8b5f35e0be), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), Azure Container Instance container group should deploy into a virtual network (8af8f826-edcb-4178-b35f-851ea6fea615), Azure VPN gateways should not use 'basic' SKU (e345b6c3-24bd-4c93-9bbb-7e5e49a17b78), Configure App Configuration to disable public network access (73290fa2-dfa7-4bbb-945d-a5e23b75df2c), Configure Azure SQL Server to disable public network access (28b0b1e5-17ba-4963-a7a4-5a1ab4400a0b), Configure Azure SQL Server to enable private endpoint connections (8e8ca470-d980-4831-99e6-dc70d9f6af87), Configure Container registries to disable public network access (a3701552-92ea-433e-9d17-33b7f1208fc9), Configure managed disks to disable public network access (8426280e-b5be-43d9-979e-653d12a08638), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Cosmos DB should use a virtual network service endpoint (e0a2b1a3-f7f9-4569-807f-2a9edebdf4d9), Event Hub should use a virtual network service endpoint (d63edb4a-c612-454d-b47d-191a724fcbf0), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Managed disks should disable public network access (8405fdab-1faf-48aa-b702-999c9c172094), Modify - Configure Azure File Sync to disable public network access (0e07b2e9-6cd9-4c40-9ccb-52817b95133b), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Public network access should be disabled for Container registries (0fdf0491-d080-4575-b627-ad0e843cba0f), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Virtual machines should be connected to an approved virtual network (d416745a-506c-48b6-8ab1-83cb814bcaa3), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d), Virtual networks should use specified virtual network gateway (f1776c76-f58c-4245-a8d0-2b207198dc8b) |
API Management, App Configuration, Compute, Container Instance, Container Registry, Network, Security Center, SQL, Storage | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.35 | RMiT_v1.0_10.35 | RMiT 10.35 | Network Resilience | Network Resilience - 10.35 | Shared | n/a | A financial institution must establish real-time network bandwidth monitoring processes and corresponding network service resilience metrics to flag any over utilisation of bandwidth and system disruptions due to bandwidth congestion and network faults. This includes traffic analysis to detect trends and anomalies. | link | count: 002 Deploy - Configure Log Analytics extension to be enabled on Windows virtual machine scale sets (3c1b3629-c8f8-4bf6-862c-037cb9094038), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6) |
Monitoring, Network | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.38 | RMiT_v1.0_10.38 | RMiT 10.38 | Network Resilience | Network Resilience - 10.38 | Shared | n/a | A financial institution must ensure sufficient and relevant network device logs are retained for investigations and forensic purposes for at least three years. | link | count: 002 Enable Security Center's auto provisioning of the Log Analytics agent on your subscriptions with custom workspace. (8e7da0a5-0a0e-4bbc-bfc0-7773c018b616), Enable Security Center's auto provisioning of the Log Analytics agent on your subscriptions with default workspace. (6df2fee6-a9ed-4fef-bced-e13be1b25f1c) |
Security Center | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.39 | RMiT_v1.0_10.39 | RMiT 10.39 | Network Resilience | Network Resilience - 10.39 | Shared | n/a | A financial institution must implement appropriate safeguards to minimise the risk of a system compromise in one entity affecting other entities within the group. Safeguards implemented may include establishing logical network segmentation for the financial institution from other entities within the group. | link | count: 003 A custom IPsec/IKE policy must be applied to all Azure virtual network gateway connections (50b83b09-03da-41c1-b656-c293c914862b), SQL Server should use a virtual network service endpoint (ae5d2f14-d830-42b6-9899-df6cfe9c71a3), Storage Accounts should use a virtual network service endpoint (60d21c4f-21a3-4d94-85f4-b924e6aeeda4) |
Network | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.49 | RMiT_v1.0_10.49 | RMiT 10.49 | Cloud Services | Cloud Services - 10.49 | Shared | n/a | A financial institution must fully understand the inherent risk of adopting cloud services. In this regard, a financial institution is required to conduct a comprehensive risk assessment prior to cloud adoption which considers the inherent architecture of cloud services that leverages on the sharing of resources and services across multiple tenants over the Internet. The assessment must specifically address risks associated with the following: (a) sophistication of the deployment model; (b) migration of existing systems to cloud infrastructure; (c) location of cloud infrastructure; (d) multi-tenancy or data co-mingling; (e) vendor lock-in and application portability or interoperability; (f) ability to customise security configurations of the cloud infrastructure to ensure a high level of data and technology system protection; (g) exposure to cyber-attacks via cloud service providers; (h) termination of a cloud service provider including the ability to secure the financial institution's data following the termination; (i) demarcation of responsibilities, limitations and liability of the service provider; and (j) ability to meet regulatory requirements and international standards on cloud computing on a continuing basis. | link | count: 006 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Audit resource location matches resource group location (0a914e76-4921-4c19-b460-a2d36003525a), Connection throttling should be enabled for PostgreSQL database servers (5345bb39-67dc-4960-a1bf-427e16b9a0bd), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), SQL Database should avoid using GRS backup redundancy (b219b9cf-f672-4f96-9ab0-f5a3ac5e1c13), SQL Managed Instances should avoid using GRS backup redundancy (a9934fd7-29f2-4e6d-ab3d-607ea38e9079) |
General, Security Center, SQL | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.51 | RMiT_v1.0_10.51 | RMiT 10.51 | Cloud Services | Cloud Services - 10.51 | Shared | n/a | A financial institution is required to consult the Bank prior to the use of public cloud for critical systems. The financial institution is expected to demonstrate that specific risks associated with the use of cloud services for critical systems have been adequately considered and addressed. The risk assessment shall address the risks outlined in paragraph 10.49 as well as the following areas: (a) the adequacy of the overarching cloud adoption strategy of the financial institution including: (i) board oversight over cloud strategy and cloud operational management; (ii) senior management roles and responsibilities on cloud management; (iii) conduct of day-to-day operational management functions; (iv) management and oversight by the financial institution of cloud service providers; (v) quality of risk management and internal control functions; and (vi) strength of in-house competency and experience; (b) the availability of independent, internationally recognised certifications of the cloud service providers, at a minimum, in the following areas: (i) information security management framework, including cryptographic modules such as used for encryption and decryption of user data; and (ii) cloud-specific security controls for protection of customer and counterparty or proprietary information including payment transaction data in use, in storage and in transit; and (c) the degree to which the selected cloud configuration adequately addresses the following attributes: (i) geographical redundancy; (ii) high availability; (iii) scalability; (iv) portability; (v) interoperability; and (vi) strong recovery and resumption capability including appropriate alternate Internet path to protect against potential Internet faults. | link | count: 007 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570) |
Compute, Security Center, SQL, Storage | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.53 | RMiT_v1.0_10.53 | RMiT 10.53 | Cloud Services | Cloud Services - 10.53 | Shared | n/a | A financial institution must implement appropriate safeguards on customer and counterparty information and proprietary data when using cloud services to protect against unauthorised disclosure and access. This shall include retaining ownership, control and management of all data pertaining to customer and counterparty information, proprietary data and services hosted on the cloud, including the relevant cryptographic keys management. | link | count: 014 App Configuration should use a customer-managed key (967a4b4b-2da9-43c1-b7d0-f98d0d74d0b1), Azure Container Instance container group should use customer-managed key for encryption (0aa61e00-0a01-4a3c-9945-e93cffedf0e6), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Event Hub namespaces should use a customer-managed key for encryption (a1ad735a-e96f-45d2-a7b2-9a4932cab7ec), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Managed disks should use a specific set of disk encryption sets for the customer-managed key encryption (d461a302-a187-421a-89ac-84acdb4edc04), OS and data disks should be encrypted with a customer-managed key (702dd420-7fcc-42c5-afe8-4026edd20fe0), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account containing the container with activity logs must be encrypted with BYOK (fbb99e8e-e444-4da0-9ff1-75c92f5a85b2), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25) |
App Configuration, Compute, Container Instance, Container Registry, Event Hub, Monitoring, SQL, Storage | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.54 | RMiT_v1.0_10.54 | RMiT 10.54 | Access Control | Access Control - 10.54 | Shared | n/a | A financial institution must implement an appropriate access controls policy for the identification, authentication and authorisation of users (internal and external users such as third party service providers). This must address both logical and physical technology access controls which are commensurate with the level of risk of unauthorised access to its technology systems. | link | count: 017 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Configuration should disable public network access (3d9f5e4c-9947-4579-9539-2a7695fbc187), App Service apps should have authentication enabled (95bccee9-a7f8-4bec-9ee9-62c3473701fc), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Function apps should have authentication enabled (c75248c1-ea1d-4a9c-8fc9-29a6aabd5da8), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Configuration, App Service, Security Center, SQL | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.55 | RMiT_v1.0_10.55 | RMiT 10.55 | Access Control | Access Control - 10.55 | Shared | n/a | In observing paragraph 10.54, a financial institution should consider the following principles in its access control policy: (a) adopt a 'deny all' access control policy for users by default unless explicitly authorised; (b) employ 'least privilege' access rights or on a 'need-to-have' basis where only the minimum sufficient permissions are granted to legitimate users to perform their roles; (c) employ time-bound access rights which restrict access to a specific period including access rights granted to service providers; (d) employ segregation of incompatible functions where no single person is responsible for an entire operation that may provide the ability to independently modify, circumvent, and disable system security features. This may include a combination of functions such as: (i) system development and technology operations; (ii) security administration and system administration; and (iii) network operation and network security;" (e) employ dual control functions which require two or more persons to execute an activity; (f) adopt stronger authentication for critical activities including for remote access; (g) limit and control the use of the same user ID for multiple concurrent sessions; (h) limit and control the sharing of user ID and passwords across multiple users; and (i) control the use of generic user ID naming conventions in favour of more personally identifiable IDs. | link | count: 008 Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Authorization rules on the Event Hub instance should be defined (f4826e5f-6a27-407c-ae3e-9582eb39891d), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd) |
Event Hub, General, Kubernetes, Storage | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.58 | RMiT_v1.0_10.58 | RMiT 10.58 | Access Control | Access Control - 10.58 | Shared | n/a | Authentication methods that depend on more than one factor typically are more difficult to compromise than a single factor system. In view of this, financial institutions are encouraged to properly design and implement (especially in high-risk or 'single sign-on' systems) multi-factor authentication (MFA) that are more reliable and provide stronger fraud deterrents. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.60 | RMiT_v1.0_10.60 | RMiT 10.60 | Access Control | Access Control - 10.60 | Shared | n/a | A financial institution must establish a user access matrix to outline access rights, user roles or profiles, and the authorising and approving authorities. The access matrix must be periodically reviewed and updated. | link | count: 002 Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
General, Security Center | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.61 | RMiT_v1.0_10.61 | RMiT 10.61 | Access Control | Access Control - 10.61 | Shared | n/a | A financial institution must ensure' (a) access controls to enterprise-wide systems are effectively managed and monitored; and (b) user activities in critical systems are logged for audit and investigations. Activity logs must be maintained for at least three years and regularly reviewed in a timely manner. | link | count: 008 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
Security Center | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.62 | RMiT_v1.0_10.62 | RMiT 10.62 | Access Control | Access Control - 10.62 | Shared | n/a | In fulfilling the requirement under paragraph 10.61, large financial institutions are required to' (a) deploy an identity access management system to effectively manage and monitor user access to enterprise-wide systems; and (b) deploy automated audit tools to flag any anomalies. | link | count: 002 Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |
General, Security Center | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.63 | RMiT_v1.0_10.63 | RMiT 10.63 | Patch and End-of-Life System Management | Patch and End-of-Life System Management - 10.63 | Shared | n/a | A financial institution must ensure that critical systems are not running on outdated systems with known security vulnerabilities or end-of-life (EOL) technology systems. In this regard, a financial institution must clearly assign responsibilities to identified functions: (a) to continuously monitor and implement latest patch releases in a timely manner; and (b) identify critical technology systems that are approaching EOL for further remedial action. | link | count: 002 Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe) |
Compute, Security Center | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.65 | RMiT_v1.0_10.65 | RMiT 10.65 | Patch and End-of-Life System Management | Patch and End-of-Life System Management - 10.65 | Shared | n/a | A financial institution must establish a patch and EOL management framework which addresses among others the following requirements: (a) identification and risk assessment of all technology assets for potential vulnerabilities arising from undeployed patches or EOL systems; (b) conduct of compatibility testing for critical patches; (c) specification of turnaround time for deploying patches according to the severity of the patches; and (d) adherence to the workflow for end-to-end patch deployment processes including approval, monitoring and tracking of activities. | link | count: 003 Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Security Center | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.66 | RMiT_v1.0_10.66 | RMiT 10.66 | Security of Digital Services | Security of Digital Services - 10.66 | Shared | n/a | A financial institution must implement robust technology security controls in providing digital services which assure the following: (a) confidentiality and integrity of customer and counterparty information and transactions; (b) reliability of services delivered via channels and devices with minimum disruption to services; (c) proper authentication of users or devices and authorisation of transactions; (d) sufficient audit trail and monitoring of anomalous transactions; (e) ability to identify and revert to the recovery point prior to incident or service disruption; and (f) strong physical control and logical control measures | link | count: 032 Activity log should be retained for at least one year (b02aacc0-b073-424e-8298-42b22829ee0a), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Azure Monitor Logs for Application Insights should be linked to a Log Analytics workspace (d550e854-df1a-4de9-bf44-cd894b39a95e), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Azure Monitor solution 'Security and Audit' must be deployed (3e596b57-105f-48a6-be97-03e9243bad6e), Azure subscriptions should have a log profile for Activity Log (7796937f-307b-4598-941c-67d3a05ebfe7), Deploy - Configure diagnostic settings for SQL Databases to Log Analytics workspace (b79fa14e-238a-4c2d-b376-442ce508fc84), Deploy - Configure Log Analytics extension to be enabled on Windows virtual machines (0868462e-646c-4fe3-9ced-a733534b6a2c), Deploy Diagnostic Settings for Batch Account to Event Hub (db51110f-0865-4a6e-b274-e2e07a5b2cd7), Deploy Diagnostic Settings for Batch Account to Log Analytics workspace (c84e5349-db6d-4769-805e-e14037dab9b5), Deploy Diagnostic Settings for Data Lake Analytics to Event Hub (4daddf25-4823-43d4-88eb-2419eb6dcc08), Deploy Diagnostic Settings for Data Lake Analytics to Log Analytics workspace (d56a5a7c-72d7-42bc-8ceb-3baf4c0eae03), Deploy Diagnostic Settings for Data Lake Storage Gen1 to Event Hub (e8d096bc-85de-4c5f-8cfb-857bd1b9d62d), Deploy Diagnostic Settings for Data Lake Storage Gen1 to Log Analytics workspace (25763a0a-5783-4f14-969e-79d4933eb74b), Deploy Diagnostic Settings for Event Hub to Event Hub (ef7b61ef-b8e4-4c91-8e78-6946c6b0023f), Deploy Diagnostic Settings for Event Hub to Log Analytics workspace (1f6e93e8-6b31-41b1-83f6-36e449a42579), Deploy Diagnostic Settings for Key Vault to Log Analytics workspace (bef3f64c-5290-43b7-85b0-9b254eef4c47), Deploy Diagnostic Settings for Logic Apps to Event Hub (a1dae6c7-13f3-48ea-a149-ff8442661f60), Deploy Diagnostic Settings for Logic Apps to Log Analytics workspace (b889a06c-ec72-4b03-910a-cb169ee18721), Deploy Diagnostic Settings for Search Services to Event Hub (3d5da587-71bd-41f5-ac95-dd3330c2d58d), Deploy Diagnostic Settings for Search Services to Log Analytics workspace (08ba64b8-738f-4918-9686-730d2ed79c7d), Deploy Diagnostic Settings for Service Bus to Event Hub (6b51af03-9277-49a9-a3f8-1c69c9ff7403), Deploy Diagnostic Settings for Service Bus to Log Analytics workspace (04d53d87-841c-4f23-8a5b-21564380b55e), Deploy Diagnostic Settings for Stream Analytics to Event Hub (edf3780c-3d70-40fe-b17e-ab72013dafca), Deploy Diagnostic Settings for Stream Analytics to Log Analytics workspace (237e0f7e-b0e8-4ec4-ad46-8c12cb66d673), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Resource logs in Azure Key Vault Managed HSM should be enabled (a2a5b911-5617-447e-a49e-59dbe0e0434b), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
App Service, Key Vault, Monitoring, SQL | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 10.68 | RMiT_v1.0_10.68 | RMiT 10.68 | Security of Digital Services | Security of Digital Services - 10.68 | Shared | n/a | A financial institution must implement additional controls to authenticate devices and users, authorise transactions and support non-repudiation and accountability for high-risk transactions or transactions above RM10,000. These measures must include, at a minimum, the following: (a) ensure transactions are performed over secured channels such as the latest version of Transport Layer Security (TLS); (b) both client and host application systems must encrypt all confidential information prior to transmission over the network; (c) adopt MFA for transactions; (d) if OTP is used as a second factor, it must be dynamic and time-bound; (e) request users to verify details of the transaction prior to execution; (f) ensure secure user and session handling management; (g) be able to capture the location of origin and destination of each transaction; (h) implement strong mutual authentication between the users' end-point devices and financial institutions' servers, such as the use of the latest version of Extended Validation SSL certificate (EV SSL); and (i) provide timely notification to customers that is sufficiently descriptive of the nature of the transaction. | link | count: 002 App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193) |
App Service | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 11.13 | RMiT_v1.0_11.13 | RMiT 11.13 | Distributed Denial of Service (DDoS) | Distributed Denial of Service (DDoS) - 11.13 | Shared | n/a | A financial institution must ensure its technology systems and infrastructure, including critical systems outsourced to or hosted by third party service providers, are adequately protected against all types of DDoS attacks (including volumetric, protocol and application layer attacks) through the following measures: (a) subscribing to DDoS mitigation services, which include automatic 'clean pipe' services to filter and divert any potential malicious traffic away from the network bandwidth; (b) regularly assessing the capability of the provider to expand network bandwidth on-demand including upstream provider capability, adequacy of the provider's incident response plan and its responsiveness to an attack; and (c) implementing mechanisms to mitigate against Domain Name Server (DNS) based layer attacks. | link | count: 001 Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c) |
Network | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 11.15 | RMiT_v1.0_11.15 | RMiT 11.15 | Data Loss Prevention (DLP) | Data Loss Prevention (DLP) - 11.15 | Shared | n/a | A financial institution must design internal control procedures and implement appropriate technology in all applications and access points to enforce DLP policies and trigger any policy violations. The technology deployed must cover the following: (a) data in-use - data being processed by IT resources; (b) data in-motion - data being transmitted on the network; and (c) data at-rest - data stored in storage mediums such as servers, backup media and databases. | link | count: 014 Azure Key Vault Managed HSM should have purge protection enabled (c39ba22d-4428-4149-b981-70acb31fc383), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Configure App Configuration to disable public network access (73290fa2-dfa7-4bbb-945d-a5e23b75df2c), Configure Azure SQL Server to disable public network access (28b0b1e5-17ba-4963-a7a4-5a1ab4400a0b), Configure Container registries to disable public network access (a3701552-92ea-433e-9d17-33b7f1208fc9), Configure managed disks to disable public network access (8426280e-b5be-43d9-979e-653d12a08638), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d), Managed disks should disable public network access (8405fdab-1faf-48aa-b702-999c9c172094), Managed disks should use a specific set of disk encryption sets for the customer-managed key encryption (d461a302-a187-421a-89ac-84acdb4edc04), Modify - Configure Azure File Sync to disable public network access (0e07b2e9-6cd9-4c40-9ccb-52817b95133b), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12) |
App Configuration, Compute, Container Registry, Key Vault, Monitoring, SQL, Storage | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 11.17 | RMiT_v1.0_11.17 | RMiT 11.17 | Security Operations Centre (SOC) | Security Operations Centre (SOC) - 11.17 | Shared | n/a | A financial institution must ensure its SOC, whether managed in-house or by third party service providers, has adequate capabilities for proactive monitoring of its technology security posture. This shall enable the financial institution to detect anomalous user or network activities, flag potential breaches and establish the appropriate response supported by skilled resources based on the level of complexity of the alerts. The outcome of the SOC activities shall also inform the financial institution's reviews of its cybersecurity posture and strategy. | link | count: 004 Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de) |
Security Center | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 11.18 | RMiT_v1.0_11.18 | RMiT 11.18 | Security Operations Centre (SOC) | Security Operations Centre (SOC) - 11.18 | Shared | n/a | The SOC must be able to perform the following functions: (a) log collection and the implementation of an event correlation engine with parameter-driven use cases such as Security Information and Event Management (SIEM); (b) incident coordination and response; (c) vulnerability management; (d) threat hunting; (e) remediation functions including the ability to perform forensic artifact handling, malware and implant analysis; and (f) provision of situational awareness to detect adversaries and threats including threat intelligence analysis and operations, and monitoring indicators of compromise (IOC). This includes advanced behavioural analysis to detect signature-less and file-less malware and to identify anomalies that may pose security threats including at endpoints and network layers. | link | count: 014 Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Disconnections should be logged for PostgreSQL database servers. (eb6f77b9-bd53-4e35-a23d-7f65d5f0e446), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Log checkpoints should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e43d), Log connections should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e442), Log duration should be enabled for PostgreSQL database servers (eb6f77b9-bd53-4e35-a23d-7f65d5f0e8f3), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), SQL Auditing settings should have Action-Groups configured to capture critical activities (7ff426e2-515f-405a-91c8-4f2333442eb5), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Event Hub, Security Center, SQL | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 11.2 | RMiT_v1.0_11.2 | RMiT 11.2 | Cyber Risk Management | Cyber Risk Management - 11.2 | Shared | n/a | A financial institution must develop a CRF which clearly articulates the institution's governance for managing cyber risks, its cyber resilience objectives and its risk tolerance, with due regard to the evolving cyber threat environment. Objectives of the CRF shall include ensuring operational resilience against extreme but plausible cyber-attacks. The framework must be able to support the effective identification, protection, detection, response, and recovery (IPDRR) of systems and data hosted on-premise or by third party service providers from internal and external cyber-attacks. | link | count: 001 Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87) |
Compute | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 11.20 | RMiT_v1.0_11.20 | RMiT 11.20 | Security Operations Centre (SOC) | Security Operations Centre (SOC) - 11.20 | Shared | n/a | A financial institution must subscribe to reputable threat intelligence services to identify emerging cyber threats, uncover new cyber-attack techniques and support the implementation of countermeasures. | link | count: 001 Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87) |
Compute | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 11.4 | RMiT_v1.0_11.4 | RMiT 11.4 | Cyber Risk Management | Cyber Risk Management - 11.4 | Shared | n/a | A large financial institution is required to' (a) implement a centralised automated tracking system to manage its technology asset inventory; and (b) establish a dedicated in-house cyber risk management function to manage cyber risks or emerging cyber threats. The cyber risk management function shall be responsible for the following: (i) perform detailed analysis on cyber threats, provide risk assessments on potential cyber-attacks and ensure timely review and escalation of all high-risk cyber threats to senior management and the board; and (ii) proactively identify potential vulnerabilities including those arising from infrastructure hosted with third party service providers through the simulation of sophisticated 'Red Team' attacks on its current security controls. | link | count: 003 Configure backup on virtual machines without a given tag to an existing recovery services vault in the same location (09ce66bc-1220-4153-8104-e3f51c936913), Not allowed resource types (6c112d4e-5bc7-47ae-a041-ea2d9dccd749), Only approved VM extensions should be installed (c0e996f8-39cf-4af9-9f45-83fbde810432) |
Backup, Compute, General | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 11.5 | RMiT_v1.0_11.5 | RMiT 11.5 | Cybersecurity Operations | Cybersecurity Operations - 11.5 | Shared | n/a | A financial institution must establish clear responsibilities for cybersecurity operations which shall include implementing appropriate mitigating measures in the financial institution's conduct of business that correspond to the following phases of the cyber-attack lifecycle: (a) reconnaisance; (b) weaponisation; (c) delivery; (d) exploitation; (e) installation; (f) command and control; and (g) exfiltration. (harvest data) | link | count: 006 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Deploy Defender for Storage (Classic) on storage accounts (361c2074-3595-4e5d-8cab-4f21dffc835c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4) |
Security Center, Storage | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | 11.8 | RMiT_v1.0_11.8 | RMiT 11.8 | Cybersecurity Operations | Cybersecurity Operations - 11.8 | Shared | n/a | A financial institution must ensure that its cybersecurity operations continuously prevent and detect any potential compromise of its security controls or weakening of its security posture. For large financial institutions, this must include performing a quarterly vulnerability assessment of external and internal network components that support all critical systems. | link | count: 003 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | Appendix_5.2 | RMiT_v1.0_Appendix_5.2 | RMiT Appendix 5.2 | Control Measures on Cybersecurity | Control Measures on Cybersecurity - Appendix 5.2 | Customer | n/a | Update checklists on the latest security hardening of operating systems. | link | count: 002 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15) |
Security Center | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | Appendix_5.3 | RMiT_v1.0_Appendix_5.3 | RMiT Appendix 5.3 | Control Measures on Cybersecurity | Control Measures on Cybersecurity - Appendix 5.3 | Customer | n/a | Update security standards and protocols for web services encryption regularly. Disable support of weak ciphers and protocol in web-facing applications. | link | count: 007 App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c) |
App Service | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | Appendix_5.5 | RMiT_v1.0_Appendix_5.5 | RMiT Appendix 5.5 | Control Measures on Cybersecurity | Control Measures on Cybersecurity - Appendix 5.5 | Customer | n/a | Ensure security controls for server-to-server external network connections include the following: (a) server-to-server authentication such as Public Key Infrastructure (PKI) certificate or user ID and password; (b) use of secure tunnels such as Transport Layer Security (TLS) and Virtual Private Network (VPN) IPSec; and (c) deploying staging servers with adequate perimeter defences and protection such as firewall, IPS and antivirus. | link | count: 002 A custom IPsec/IKE policy must be applied to all Azure virtual network gateway connections (50b83b09-03da-41c1-b656-c293c914862b), Kubernetes cluster services should only use allowed external IPs (d46c275d-1680-448d-b2ec-e495a3b6cc89) |
Kubernetes, Network | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | Appendix_5.6 | RMiT_v1.0_Appendix_5.6 | RMiT Appendix 5.6 | Control Measures on Cybersecurity | Control Measures on Cybersecurity - Appendix 5.6 | Customer | n/a | Ensure security controls for remote access to server include the following: (a) restrict access to only hardened and locked down end-point devices; (b) use secure tunnels such as TLS and VPN IPSec; (c) deploy ‘gateway’ server with adequate perimeter defences and protection such as firewall, IPS and antivirus; and (d) close relevant ports immediately upon expiry of remote access. | link | count: 019 Azure SQL Database should be running TLS version 1.2 or newer (32e6bbec-16b6-44c2-be37-c5b672d103cf), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), MariaDB server should use a virtual network service endpoint (dfbd9a64-6114-48de-a47d-90574dc2e489), MySQL server should use a virtual network service endpoint (3375856c-3824-4e0e-ae6a-79e011dd4c47), PostgreSQL server should use a virtual network service endpoint (3c14b034-bcb6-4905-94e7-5b8e98a47b65), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL flexible servers (c9299215-ae47-4f50-9c54-8a392f68a052), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL flexible servers (5e1de0e3-42cb-4ebc-a86d-61d0c619ca48), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), SQL Managed Instance should have the minimal TLS version of 1.2 (a8793640-60f7-487c-b5c3-1d37215905c4), Virtual network firewall rule on Azure SQL Database should be enabled to allow traffic from the specified subnet (77e8b146-0078-4fb2-b002-e112381199f0), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Web Application Firewall (WAF) should use the specified mode for Application Gateway (12430be1-6cc8-4527-a9a8-e3d38f250096), Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service (425bea59-a659-4cbb-8d31-34499bd030b8) |
Kubernetes, Network, SQL | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| RMiT_v1.0 | Appendix_5.7 | RMiT_v1.0_Appendix_5.7 | RMiT Appendix 5.7 | Control Measures on Cybersecurity | Control Measures on Cybersecurity - Appendix 5.7 | Customer | n/a | Ensure overall network security controls are implemented including the following: (a) dedicated firewalls at all segments. All external-facing firewalls must be deployed on High Availability (HA) configuration and “fail-close” mode activated. Deploy different brand name/model for two firewalls located in sequence within the same network path; (b) IPS at all critical network segments with the capability to inspect and monitor encrypted network traffic; (c) web and email filtering systems such as web-proxy, spam filter and anti-spoofing controls; (d) endpoint protection solution to detect and remove security threats including viruses and malicious software; (e) solution to mitigate advanced persistent threats including zero-day and signatureless malware; and (f) capture the full network packets to rebuild relevant network sessions to aid forensics in the event of incidents. | link | count: 027 All flow log resources should be in enabled state (27960feb-a23c-4577-8d36-ef8b5f35e0be), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Configure Azure SQL Server to enable private endpoint connections (8e8ca470-d980-4831-99e6-dc70d9f6af87), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933) |
App Service, Compute, Network, Security Center, SQL | RMIT Malaysia (97a6d4f1-3bed-4cf4-ac5b-0e444c0408d6) |
| SO.1 - Data Residency | SO.1 - Data Residency | 404 not found | n/a | n/a | count: 003 Allowed locations (e56962a6-4747-49cd-b67b-bf8b01975c4c), Allowed locations for resource groups (e765b5de-1225-4ba3-bd56-1ac6695af988), Azure Cosmos DB allowed locations (0473574d-2d43-4217-aefe-941fcdf7e684) |
Cosmos DB, General | [Preview]: Sovereignty Baseline - Confidential Policies (03de05a4-c324-4ccd-882f-a814ea8ab9ea), [Preview]: Sovereignty Baseline - Global Policies (c1cbff38-87c0-4b9f-9f70-035c7a3b5523) | |||||
| SO | .3 - Customer-Managed Keys | SO.3 - Customer-Managed Keys | 404 not found | n/a | n/a | count: 012 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Queue Storage should use customer-managed key for encryption (f0e5abd0-2554-4736-b7c0-4ffef23475ef), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Table Storage should use customer-managed key for encryption (7c322315-e26d-4174-a99e-f49d351b4688) |
Backup, Compute, Kubernetes, SQL, Storage | [Preview]: Sovereignty Baseline - Confidential Policies (03de05a4-c324-4ccd-882f-a814ea8ab9ea) | ||||
| SO | .4 - Azure Confidential Computing | SO.4 - Azure Confidential Computing | 404 not found | n/a | n/a | count: 002 Allowed resource types (a08ec900-254a-4555-9bf5-e42af04b5c5c), Allowed virtual machine size SKUs (cccc23c7-8427-4f53-ad12-b6a63eb452b3) |
Compute, General | [Preview]: Sovereignty Baseline - Confidential Policies (03de05a4-c324-4ccd-882f-a814ea8ab9ea) | ||||
| SOC_2 | A1.1 | SOC_2_A1.1 | SOC 2 Type 2 A1.1 | Additional Criteria For Availability | Capacity management | Shared | The customer is responsible for implementing this recommendation. | The entity maintains, monitors, and evaluates current processing capacity and use of system components (infrastructure, data, and software) to manage capacity demand and to enable the implementation of additional capacity to help meet its objectives. The following points of focus, which apply only to an engagement using the trust services criteria for availability, highlight important characteristics relating to this criterion: • Measures Current Usage — The use of the system components is measured to establish a baseline for capacity management and to use when evaluating the risk of impaired availability due to capacity constraints. • Forecasts Capacity — The expected average and peak use of system components is forecasted and compared to system capacity and associated tolerances. Forecasting considers capacity in the event of the failure of system components that constrain capacity. • Makes Changes Based on Forecasts — The system change management process is initiated when forecasted usage exceeds capacity tolerances | count: 001 Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | A1.2 | SOC_2_A1.2 | SOC 2 Type 2 A1.2 | Additional Criteria For Availability | Environmental protections, software, data back-up processes, and recovery infrastructure | Shared | The customer is responsible for implementing this recommendation. | Identifies Environmental Threats — As part of the risk assessment process, management identifies environmental threats that could impair the availability of the system, including threats resulting from adverse weather, failure of environmental control systems, electrical discharge, fire, and water. • Designs Detection Measures — Detection measures are implemented to identify anomalies that could result from environmental threat events. • Implements and Maintains Environmental Protection Mechanisms — Management implements and maintains environmental protection mechanisms to prevent and mitigate environmental events. • Implements Alerts to Analyze Anomalies — Management implements alerts that are communicated to personnel for analysis to identify environmental threat events. • Responds to Environmental Threat Events — Procedures are in place for responding to environmental threat events and for evaluating the effectiveness of those policies and procedures on a periodic basis. This includes automatic mitigation systems (for example, uninterruptable power system and generator backup subsystem). • Communicates and Reviews Detected Environmental Threat Events — Detected environmental threat events are communicated to and reviewed by the individuals responsible for the management of the system and actions are taken, if necessary. • Determines Data Requiring Backup — Data is evaluated to determine whether backup is required. • Performs Data Backup — Procedures are in place for backing up data, monitoring to detect backup failures, and initiating corrective action when such failures occur. • Addresses Offsite Storage — Backup data is stored in a location at a distance from its principal storage location sufficient that the likelihood of a security or environmental threat event affecting both sets of data is reduced to an appropriate level. • Implements Alternate Processing Infrastructure — Measures are implemented for migrating processing to alternate infrastructure in the event normal processing infrastructure becomes unavailable. | count: 013 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Employ automatic emergency lighting (aa892c0d-2c40-200c-0dd8-eac8c4748ede), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Recover and reconstitute resources after any disruption (f33c3238-11d2-508c-877c-4262ec1132e1), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7), Transfer backup information to an alternate storage site (7bdb79ea-16b8-453e-4ca4-ad5b16012414) |
Backup, Regulatory Compliance, SQL | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | A1.3 | SOC_2_A1.3 | SOC 2 Type 2 A1.3 | Additional Criteria For Availability | Recovery plan testing | Shared | The customer is responsible for implementing this recommendation. | • Implements Business Continuity Plan Testing — Business continuity plan testing is performed on a periodic basis. The testing includes (1) development of testing scenarios based on threat likelihood and magnitude; (2) consideration of system components from across the entity that can impair the availability; (3) scenarios that consider the potential for the lack of availability of key personnel; and (4) revision of continuity plans and systems based on test results. • Tests Integrity and Completeness of Backup Data — The integrity and completeness of backup information is tested on a periodic basis | count: 004 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Initiate contingency plan testing corrective actions (8bfdbaa6-6824-3fec-9b06-7961bf7389a6), Review the results of contingency plan testing (5d3abfea-a130-1208-29c0-e57de80aa6b0), Test the business continuity and disaster recovery plan (58a51cde-008b-1a5d-61b5-d95849770677) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | C1.1 | SOC_2_C1.1 | SOC 2 Type 2 C1.1 | Additional Criteria For Confidentiality | Protection of confidential information | Shared | The customer is responsible for implementing this recommendation. | Identifies Confidential information — Procedures are in place to identify and designate confidential information when it is received or created and to determine the period over which the confidential information is to be retained. • Protects Confidential Information From Destruction — Procedures are in place to protect confidential information from erasure or destruction during the specified retention period of the information. | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | C1.2 | SOC_2_C1.2 | SOC 2 Type 2 C1.2 | Additional Criteria For Confidentiality | Disposal of confidential information | Shared | The customer is responsible for implementing this recommendation. | Identifies Confidential Information for Destruction — Procedures are in place to identify confidential information requiring destruction when the end of the retention period is reached. • Destroys Confidential Information — Procedures are in place to erase or otherwise destroy confidential information that has been identified for destruction | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC1.1 | SOC_2_CC1.1 | SOC 2 Type 2 CC1.1 | Control Environment | COSO Principle 1 | Shared | The customer is responsible for implementing this recommendation. | Sets the Tone at the Top — The board of directors and management, at all levels, demonstrate through their directives, actions, and behavior the importance of integrity and ethical values to support the functioning of the system of internal control. • Establishes Standards of Conduct — The expectations of the board of directors and senior management concerning integrity and ethical values are defined in the entity’s standards of conduct and understood at all levels of the entity and by outsourced service providers and business partners. • Evaluates Adherence to Standards of Conduct — Processes are in place to evaluate the performance of individuals and teams against the entity’s expected standards of conduct. • Addresses Deviations in a Timely Manner — Deviations from the entity’s expected standards of conduct are identified and remedied in a timely and consistent manner | count: 008 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Develop organization code of conduct policy (d02498e0-8a6f-6b02-8332-19adf6711d1e), Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Prohibit unfair practices (5fe84a4c-1b0c-a738-2aba-ed49c9069d3b), Review and sign revised rules of behavior (6c0a312f-04c5-5c97-36a5-e56763a02b6b), Update rules of behavior and access agreements (6610f662-37e9-2f71-65be-502bdc2f554d), Update rules of behavior and access agreements every 3 years (7ad83b58-2042-085d-08f0-13e946f26f89) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC1.2 | SOC_2_CC1.2 | SOC 2 Type 2 CC1.2 | Control Environment | COSO Principle 2 | Shared | The customer is responsible for implementing this recommendation. | • Establishes Oversight Responsibilities — The board of directors identifies and accepts its oversight responsibilities in relation to established requirements and expectations. • Applies Relevant Expertise — The board of directors defines, maintains, and periodically evaluates the skills and expertise needed among its members to enable them to ask probing questions of senior management and take commensurate action. • Operates Independently — The board of directors has sufficient members who are independent from management and objective in evaluations and decision making. | count: 005 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC1.3 | SOC_2_CC1.3 | SOC 2 Type 2 CC1.3 | Control Environment | COSO Principle 3 | Shared | The customer is responsible for implementing this recommendation. | Considers All Structures of the Entity — Management and the board of directors consider the multiple structures used (including operating units, legal entities, geographic distribution, and outsourced service providers) to support the achievement of objectives. • Establishes Reporting Lines — Management designs and evaluates lines of reporting for each entity structure to enable execution of authorities and responsibilities and flow of information to manage the activities of the entity. • Defines, Assigns, and Limits Authorities and Responsibilities — Management and the board of directors delegate authority, define responsibilities, and use appropriate processes and technology to assign responsibility and segregate duties as necessary at the various levels of the organization • Addresses Specific Requirements When Defining Authorities and Responsibilities — Management and the board of directors consider requirements relevant to security, availability, processing integrity, confidentiality, and privacy when defining authorities and responsibilities. • Considers Interactions With External Parties When Establishing Structures, Reporting Lines, Authorities, and Responsibilities — Management and the board of directors consider the need for the entity to interact with and monitor the activities of external parties when establishing structures, reporting lines, authorities, and responsibilities | count: 005 Appoint a senior information security officer (c6cf9f2c-5fd8-3f16-a1f1-f0b69c904928), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC1.4 | SOC_2_CC1.4 | SOC 2 Type 2 CC1.4 | Control Environment | COSO Principle 4 | Shared | The customer is responsible for implementing this recommendation. | Establishes Policies and Practices — Policies and practices reflect expectations of competence necessary to support the achievement of objectives. • Evaluates Competence and Addresses Shortcomings — The board of directors and management evaluate competence across the entity and in outsourced service providers in relation to established policies and practices and act as necessary to address shortcomings. • Attracts, Develops, and Retains Individuals — The entity provides the mentoring and training needed to attract, develop, and retain sufficient and competent personnel and outsourced service providers to support the achievement of objectives. • Plans and Prepares for Succession — Senior management and the board of directors develop contingency plans for assignments of responsibility important for internal control. Additional point of focus specifically related to all engagements using the trust services criteria:Page 16 TSP Ref. # TRUST SERVICES CRITERIA AND POINTS OF FOCUS • Considers the Background of Individuals — The entity considers the background of potential and existing personnel, contractors, and vendor employees when determining whether to employ and retain the individuals. • Considers the Technical Competency of Individuals — The entity considers the technical competency of potential and existing personnel, contractors, and vendor employees when determining whether to employ and retain the individuals. • Provides Training to Maintain Technical Competencies — The entity provides training programs, including continuing education and training, to ensure skill sets and technical competency of existing personnel, contractors, and vendor employees are developed and maintained | count: 005 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide role-based practical exercises (d041726f-00e0-41ca-368c-b1a122066482), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC1.5 | SOC_2_CC1.5 | SOC 2 Type 2 CC1.5 | Control Environment | COSO Principle 5 | Shared | The customer is responsible for implementing this recommendation. | • Enforces Accountability Through Structures, Authorities, and Responsibilities — Management and the board of directors establish the mechanisms to communicate and hold individuals accountable for performance of internal control responsibilities across the entity and implement corrective action as necessary. • Establishes Performance Measures, Incentives, and Rewards — Management and the board of directors establish performance measures, incentives, and other rewards appropriate for responsibilities at all levels of the entity, reflecting appropriate dimensions of performance and expected standards of conduct, and considering the achievement of both short-term and longer-term objectives. • Evaluates Performance Measures, Incentives, and Rewards for Ongoing Relevance — Management and the board of directors align incentives and rewards with the fulfillment of internal control responsibilities in the achievement of objectives. • Considers Excessive Pressures — Management and the board of directors evaluate and adjust pressures associated with the achievement of objectives as they assign responsibilities, develop performance measures, and evaluate performance. • Evaluates Performance and Rewards or Disciplines Individuals — Management and the board of directors evaluate performance of internal control responsibilities, including adherence to standards of conduct and expected levels of competence, and Page 17 TSP Ref. # TRUST SERVICES CRITERIA AND POINTS OF FOCUS provide rewards or exercise disciplinary action, as appropriate | count: 004 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Implement formal sanctions process (5decc032-95bd-2163-9549-a41aba83228e), Notify personnel upon sanctions (6228396e-2ace-7ca5-3247-45767dbf52f4) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC2.1 | SOC_2_CC2.1 | SOC 2 Type 2 CC2.1 | Communication and Information | COSO Principle 13 | Shared | The customer is responsible for implementing this recommendation. | Identifies Information Requirements — A process is in place to identify the information required and expected to support the functioning of the other components of internal control and the achievement of the entity’s objectives. • Captures Internal and External Sources of Data — Information systems capture internal and external sources of data. • Processes Relevant Data Into Information — Information systems process and transform relevant data into information. • Maintains Quality Throughout Processing — Information systems produce information that is timely, current, accurate, complete, accessible, protected, verifiable, and retained. Information is reviewed to assess its relevance in supporting the internal control components. | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC2.2 | SOC_2_CC2.2 | SOC 2 Type 2 CC2.2 | Communication and Information | COSO Principle 14 | Shared | The customer is responsible for implementing this recommendation. | • Communicates Internal Control Information — A process is in place to communicate required information to enable all personnel to understand and carry out their internal control responsibilities. • Communicates With the Board of Directors — Communication exists between management and the board of directors so that both have information needed to fulfill their roles with respect to the entity’s objectives. • Provides Separate Communication Lines — Separate communication channels, such as whistle-blower hotlines, are in place and serve as fail-safe mechanisms to enable anonymous or confidential communication when normal channels are inoperative or ineffective. • Selects Relevant Method of Communication — The method of communication considers the timing, audience, and nature of • Communicates Responsibilities — Entity personnel with responsibility for designing, developing, implementing, operating, maintaining, or monitoring system controls receive communications about their responsibilities, including changes in their responsibilities, and have the information necessary to carry out those responsibilities. • Communicates Information on Reporting Failures, Incidents, Concerns, and Other Matters — Entity personnel are provided with information on how to report systems failures, incidents, concerns, and other complaints to personnel. • Communicates Objectives and Changes to Objectives — The entity communicates its objectives and changes to those objectives to personnel in a timely manner. • Communicates Information to Improve Security Knowledge and Awareness — The entity communicates information to improve security knowledge and awareness and to model appropriate security behaviors to personnel through a security awareness training program | count: 009 Develop acceptable use policies and procedures (42116f15-5665-a52a-87bb-b40e64c74b6c), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Enforce rules of behavior and access agreements (509552f5-6528-3540-7959-fbeae4832533), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Regulatory Compliance, Security Center | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC2.3 | SOC_2_CC2.3 | SOC 2 Type 2 CC2.3 | Communication and Information | COSO Principle 15 | Shared | The customer is responsible for implementing this recommendation. | Communicates to External Parties — Processes are in place to communicate relevant and timely information to external parties, including shareholders, partners, owners, regulators, customers, financial analysts, and other external parties. • Enables Inbound Communications — Open communication channels allow input from customers, consumers, suppliers, external auditors, regulators, financial analysts, and others, providing management and the board of directors with relevant information. • Communicates With the Board of Directors — Relevant information resulting from assessments conducted by external parties is communicated to the board of directors. • Provides Separate Communication Lines — Separate communication channels, such as whistle-blower hotlines, are in place and serve as fail-safe mechanisms to enable anonymous or confidential communication when normal channels are inoperative or ineffective. • Selects Relevant Method of Communication — The method of communication considers the timing, audience, and nature of the communication and legal, regulatory, and fiduciary requirements and expectations. Additional point of focus that applies only to an engagement using the trust services criteria for confidentiality: • Communicates Objectives Related to Confidentiality and Changes to Objectives — The entity communicates, to external users, vendors, business partners, and others whose products and services are part of the system, objectives and changes to objectives related to confidentiality.Page 20 TSP Ref. # TRUST SERVICES CRITERIA AND POINTS OF FOCUS Additional point of focus that applies only to an engagement using the trust services criteria for privacy: • Communicates Objectives Related to Privacy and Changes to Objectives — The entity communicates, to external users, vendors, business partners, and others whose products and services are part of the system, objectives related to privacy and changes to those objectives. Additional points of focus that apply only when an engagement using the trust services criteria is performed at the system level: • Communicates Information About System Operation and Boundaries — The entity prepares and communicates information about the design and operation of the system and its boundaries to authorized external users to permit users to understand their role in the system and the results of system operation. • Communicates System Objectives — The entity communicates its system objectives to appropriate external users. • Communicates System Responsibilities — External users with responsibility for designing, developing, implementing, operating, maintaining, and monitoring system controls receive communications about their responsibilities and have the information necessary to carry out those responsibilities. • Communicates Information on Reporting System Failures, Incidents, Concerns, and Other Matters — External users are provided with information on how to report systems failures, incidents, concerns, and other complaints to appropriate personnel. | count: 014 Define the duties of processors (52375c01-4d4c-7acc-3aa4-5b3d53a047ec), Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Regulatory Compliance, Security Center | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC3.1 | SOC_2_CC3.1 | SOC 2 Type 2 CC3.1 | Risk Assessment | COSO Principle 6 | Shared | The customer is responsible for implementing this recommendation. | • Reflects Management's Choices — Operations objectives reflect management's choices about structure, industry considerations, and performance of the entity. • Considers Tolerances for Risk — Management considers the acceptable levels of variation relative to the achievement of operations objectives. • Includes Operations and Financial Performance Goals — The organization reflects the desired level of operations and financial performance for the entity within operations objectives. • Forms a Basis for Committing of Resources — Management uses operations objectives as a basis for allocating resources needed to attain desired operations and financial performance. External Financial Reporting Objectives • Complies With Applicable Accounting Standards — Financial reporting objectives are consistent with accounting principles suitable and available for that entity. The accounting principles selected are appropriate in the circumstances. • Considers Materiality — Management considers materiality in financial statement presentation. • Reflects Entity Activities — External reporting reflects the underlying transactions and events to show qualitative characteristics and assertions. External Nonfinancial Reporting Objectives • Complies With Externally Established Frameworks — Management establishes objectives consistent with laws and regulations or standards and frameworks of recognized external organizations. • Considers the Required Level of Precision — Management reflects the required level of precision and accuracy suitable for user needs and based on criteria established by third parties in nonfinancial reporting. • Reflects Entity Activities — External reporting reflects the underlying transactions and events within a range of acceptable limits. Internal Reporting Objectives • Reflects Management's Choices — Internal reporting provides management with accurate and complete information regarding management's choices and information Page 22 TSP Ref. # TRUST SERVICES CRITERIA AND POINTS OF FOCUS needed in managing the entity. • Considers the Required Level of Precision — Management reflects the required level of precision and accuracy suitable for user needs in nonfinancial reporting objectives and materiality within financial reporting objectives. • Reflects Entity Activities — Internal reporting reflects the underlying transactions and events within a range of acceptable limits. Compliance Objectives • Reflects External Laws and Regulations — Laws and regulations establish minimum standards of conduct, which the entity integrates into compliance objectives. • Considers Tolerances for Risk — Management considers the acceptable levels of variation relative to the achievement of operations objectives | count: 007 Categorize information (93fa357f-2e38-22a9-5138-8cc5124e1923), Determine information protection needs (dbcef108-7a04-38f5-8609-99da110a2a57), Develop business classification schemes (11ba0508-58a8-44de-5f3a-9e05d80571da), Develop SSP that meets criteria (6b957f60-54cd-5752-44d5-ff5a64366c93), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC3.2 | SOC_2_CC3.2 | SOC 2 Type 2 CC3.2 | Risk Assessment | COSO Principle 7 | Shared | The customer is responsible for implementing this recommendation. | Points of focus specified in the COSO framework: • Includes Entity, Subsidiary, Division, Operating Unit, and Functional Levels — The entity identifies and assesses risk at the entity, subsidiary, division, operating unit, and functional levels relevant to the achievement of objectives. • Analyzes Internal and External Factors — Risk identification considers both internal and external factors and their impact on the achievement of objectives. • Involves Appropriate Levels of Management — The entity puts into place effective risk assessment mechanisms that involve appropriate levels of management. • Estimates Significance of Risks Identified — Identified risks are analyzed through a process that includes estimating the potential significance of the risk. • Determines How to Respond to Risks — Risk assessment includes considering how the risk should be managed and whether to accept, avoid, reduce, or share the risk. Additional points of focus specifically related to all engagements using the trust services criteria: • Identifies and Assesses Criticality of Information Assets and Identifies Threats and Vulnerabilities — The entity's risk identification and assessment process includes (1) identifying information assets, including physical devices and systems, virtual devices, software, data and data flows, external information systems, and organizational roles; (2) assessing the criticality of those information assets; (3) identifying the threats to the assets from intentional (including malicious) and unintentional acts and environmental events; and (4) identifying the vulnerabilities of the identified assets. • Analyzes Threats and Vulnerabilities From Vendors, Business Partners, and Other Parties — The entity's risk assessment process includes the analysis of potential threats and vulnerabilities arising from vendors providing goods and services, as well as threats and vulnerabilities arising from business partners, customers, and others with access to the entity's information systems. • Considers the Significance of the Risk — The entity’s consideration of the potential significance of the identified risks includes (1) determining the criticality of identified assets in meeting objectives; (2) assessing the impact of identified threats and vulnerabilities in meeting objectives; (3) assessing the likelihood of identified threats; and (4) determining the risk associated with assets based on asset criticality, threat impact, and likelihood. | count: 011 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Categorize information (93fa357f-2e38-22a9-5138-8cc5124e1923), Determine information protection needs (dbcef108-7a04-38f5-8609-99da110a2a57), Develop business classification schemes (11ba0508-58a8-44de-5f3a-9e05d80571da), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Regulatory Compliance, Security Center, SQL | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC3.3 | SOC_2_CC3.3 | SOC 2 Type 2 CC3.3 | Risk Assessment | COSO Principle 8 | Shared | The customer is responsible for implementing this recommendation. | • Considers Various Types of Fraud — The assessment of fraud considers fraudulent Page 24 TSP Ref. # TRUST SERVICES CRITERIA AND POINTS OF FOCUS reporting, possible loss of assets, and corruption resulting from the various ways that fraud and misconduct can occur. • Assesses Incentives and Pressures — The assessment of fraud risks considers incentives and pressures. • Assesses Opportunities — The assessment of fraud risk considers opportunities for unauthorized acquisition, use, or disposal of assets, altering the entity’s reporting records, or committing other inappropriate acts. • Assesses Attitudes and Rationalizations — The assessment of fraud risk considers how management and other personnel might engage in or justify inappropriate actions. Additional point of focus specifically related to all engagements using the trust services criteria: • Considers the Risks Related to the Use of IT and Access to Information — The assessment of fraud risks includes consideration of threats and vulnerabilities that arise specifically from the use of IT and access to information | count: 001 Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC3.4 | SOC_2_CC3.4 | SOC 2 Type 2 CC3.4 | Risk Assessment | COSO Principle 9 | Shared | The customer is responsible for implementing this recommendation. | • Assesses Changes in the External Environment — The risk identification process considers changes to the regulatory, economic, and physical environment in which the entity operates. • Assesses Changes in the Business Model — The entity considers the potential impacts of new business lines, dramatically altered compositions of existing business lines, acquired or divested business operations on the system of internal control, rapid growth, changing reliance on foreign geographies, and new technologies. • Assesses Changes in Leadership — The entity considers changes in management and respective attitudes and philosophies on the system of internal control. Page 25 TSP Ref. # TRUST SERVICES CRITERIA AND POINTS OF FOCUS Additional point of focus specifically related to all engagements using the trust services criteria: • Assesses Changes in Systems and Technology — The risk identification process considers changes arising from changes in the entity’s systems and changes in the technology environment. • Assesses Changes in Vendor and Business Partner Relationships — The risk identification process considers changes in vendor and business partner relationships | count: 006 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC4.1 | SOC_2_CC4.1 | SOC 2 Type 2 CC4.1 | Monitoring Activities | COSO Principle 16 | Shared | The customer is responsible for implementing this recommendation. | • Considers a Mix of Ongoing and Separate Evaluations — Management includes a balance of ongoing and separate evaluations. • Considers Rate of Change — Management considers the rate of change in business and business processes when selecting and developing ongoing and separate evaluations. • Establishes Baseline Understanding — The design and current state of an internal control system are used to establish a baseline for ongoing and separate evaluations. • Uses Knowledgeable Personnel — Evaluators performing ongoing and separate evaluations have sufficient knowledge to understand what is being evaluated. • Integrates With Business Processes — Ongoing evaluations are built into the business processes and adjust to changing conditions. • Adjusts Scope and Frequency — Management varies the scope and frequency of separate evaluations depending on risk. Page 26 TSP Ref. # TRUST SERVICES CRITERIA AND POINTS OF FOCUS • Objectively Evaluates — Separate evaluations are performed periodically to provide objective feedback. Additional point of focus specifically related to all engagements using the trust services criteria: • Considers Different Types of Ongoing and Separate Evaluations — Management uses a variety of different types of ongoing and separate evaluations, including penetration testing, independent certification made against established specifications (for example, ISO certifications), and internal audit assessments | count: 003 Assess Security Controls (c423e64d-995c-9f67-0403-b540f65ba42a), Develop security assessment plan (1c258345-5cd4-30c8-9ef3-5ee4dd5231d6), Select additional testing for security control assessments (f78fc35e-1268-0bca-a798-afcba9d2330a) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC4.2 | SOC_2_CC4.2 | SOC 2 Type 2 CC4.2 | Monitoring Activities | COSO Principle 17 | Shared | The customer is responsible for implementing this recommendation. | • Assesses Results — Management and the board of directors, as appropriate, assess results of ongoing and separate evaluations. • Communicates Deficiencies — Deficiencies are communicated to parties responsible for taking corrective action and to senior management and the board of directors, as appropriate. • Monitors Corrective Action — Management tracks whether deficiencies are reme | count: 002 Deliver security assessment results (8e49107c-3338-40d1-02aa-d524178a2afe), Produce Security Assessment report (70a7a065-a060-85f8-7863-eb7850ed2af9) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC5.1 | SOC_2_CC5.1 | SOC 2 Type 2 CC5.1 | Control Activities | COSO Principle 10 | Shared | The customer is responsible for implementing this recommendation. | • Integrates With Risk Assessment — Control activities help ensure that risk responses that address and mitigate risks are carried out. • Considers Entity-Specific Factors — Management considers how the environment, complexity, nature, and scope of its operations, as well as the specific characteristics of its organization, affect the selection and development of control activities. • Determines Relevant Business Processes — Management determines which relevant business processes require control activities. • Evaluates a Mix of Control Activity Types — Control activities include a range and variety of controls and may include a balance of approaches to mitigate risks, considering both manual and automated controls, and preventive and detective controls. • Considers at What Level Activities Are Applied — Management considers control activities at various levels in the entity. • Addresses Segregation of Duties — Management segregates incompatible duties and, where such segregation is not practical, management selects and develops alternative control activities. | count: 002 Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC5.2 | SOC_2_CC5.2 | SOC 2 Type 2 CC5.2 | Control Activities | COSO Principle 11 | Shared | The customer is responsible for implementing this recommendation. | • Determines Dependency Between the Use of Technology in Business Processes and Technology General Controls — Management understands and determines the dependency and linkage between business processes, automated control activities, and technology general controls. • Establishes Relevant Technology Infrastructure Control Activities — Management selects and develops control activities over the technology infrastructure, which are designed and implemented to help ensure the completeness, accuracy, and availability of technology processing. • Establishes Relevant Security Management Process Controls Activities — Management selects and develops control activities that are designed and implemented to restrict technology access rights to authorized users commensurate with their job responsibilities and to protect the entity’s assets from external threats. • Establishes Relevant Technology Acquisition, Development, and Maintenance Process Control Activities — Management selects and develops control activities over the acquisition, development and maintenance of technology and its infrastructure to achieve management's objectives. | count: 018 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Regulatory Compliance, Security Center | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC5.3 | SOC_2_CC5.3 | SOC 2 Type 2 CC5.3 | Control Activities | COSO Principle 12 | Shared | The customer is responsible for implementing this recommendation. | Establishes Policies and Procedures to Support Deployment of Management’s Directives — Management establishes control activities that are built into business processes and employees’ day-to-day activities through policies establishing what is expected and relevant procedures specifying actions. • Establishes Responsibility and Accountability for Executing Policies and Procedures — Management establishes responsibility and accountability for control activities with management (or other designated personnel) of the business unit or function in which the relevant risks reside. • Performs in a Timely Manner — Responsible personnel perform control activities in a timely manner as defined by the policies and procedures. • Takes Corrective Action — Responsible personnel investigate and act on matters identified as a result of executing control activities. • Performs Using Competent Personnel — Competent personnel with sufficient authority perform control activities with diligence and continuing focus. • Reassesses Policies and Procedures — Management periodically reviews control activities to determine their continued relevance and refreshes them when necessary | count: 004 Configure detection whitelist (2927e340-60e4-43ad-6b5f-7a1468232cc2), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC6.1 | SOC_2_CC6.1 | SOC 2 Type 2 CC6.1 | Logical and Physical Access Controls | Logical access security software, infrastructure, and architectures | Shared | The customer is responsible for implementing this recommendation. | The following points of focus, specifically related to all engagements using the trust services criteria, highlight important characteristics relating to this criterion: • Identifies and Manages the Inventory of Information Assets — The entity identifies, Page 29 TSP Ref. # TRUST SERVICES CRITERIA AND POINTS OF FOCUS inventories, classifies, and manages information assets. • Restricts Logical Access — Logical access to information assets, including hardware, data (at-rest, during processing, or in transmission), software, administrative authorities, mobile devices, output, and offline system components is restricted through the use of access control software and rule sets. • Identifies and Authenticates Users — Persons, infrastructure, and software are identified and authenticated prior to accessing information assets, whether locally or remotely. • Considers Network Segmentation — Network segmentation permits unrelated portions of the entity's information system to be isolated from each other. • Manages Points of Access — Points of access by outside entities and the types of data that flow through the points of access are identified, inventoried, and managed. The types of individuals and systems using each point of access are identified, documented, and managed. • Restricts Access to Information Assets — Combinations of data classification, separate data structures, port restrictions, access protocol restrictions, user identification, and digital certificates are used to establish access-control rules for information assets. • Manages Identification and Authentication — Identification and authentication requirements are established, documented, and managed for individuals and systems accessing entity information, infrastructure, and software. • Manages Credentials for Infrastructure and Software — New internal and external infrastructure and software are registered, authorized, and documented prior to being granted access credentials and implemented on the network or access point. Credentials are removed and access is disabled when access is no longer required or the infrastructure and software are no longer in use. • Uses Encryption to Protect Data — The entity uses encryption to supplement other measures used to protect data at rest, when such protections are deemed appropriate based on assessed risk. • Protects Encryption Keys — Processes are in place to protect encryption keys during generation, storage, use, and destruction | count: 080 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Certificates should have the specified maximum validity period (0a075868-4c26-42ef-914c-5bc007359560), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Create a data inventory (043c1e56-5a16-52f8-6af8-583098ff3e60), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Key Vault keys should have an expiration date (152b15f7-8e1f-4c1f-ab71-8c010ba5dbc0), Key Vault secrets should have an expiration date (98728c90-32c7-4049-8429-847dc0f4fe37), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Maintain records of processing of personal data (92ede480-154e-0e22-4dca-8b46a74a3a51), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account containing the container with activity logs must be encrypted with BYOK (fbb99e8e-e444-4da0-9ff1-75c92f5a85b2), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Automation, Cache, Cognitive Services, Container Registry, Cosmos DB, Guest Configuration, Key Vault, Kubernetes, Machine Learning, Monitoring, Regulatory Compliance, Security Center, Service Fabric, SQL, Storage | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC6.2 | SOC_2_CC6.2 | SOC 2 Type 2 CC6.2 | Logical and Physical Access Controls | Access provisioning and removal | Shared | The customer is responsible for implementing this recommendation. | Controls Access Credentials to Protected Assets — Information asset access credentials are created based on an authorization from the system's asset owner or authorized custodian. • Removes Access to Protected Assets When Appropriate — Processes are in place to remove credential access when an individual no longer requires such access. • Reviews Appropriateness of Access Credentials — The appropriateness of access credentials is reviewed on a periodic basis for unnecessary and inappropriate indIviduals with credentials. | count: 011 Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289) |
Regulatory Compliance, Security Center | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC6.3 | SOC_2_CC6.3 | SOC 2 Type 2 CC6.3 | Logical and Physical Access Controls | Rol based access and least privilege | Shared | The customer is responsible for implementing this recommendation. | • Creates or Modifies Access to Protected Information Assets — Processes are in place to create or modify access to protected information assets based on authorization from the asset’s owner. • Removes Access to Protected Information Assets — Processes are in place to remove access to protected information assets when an individual no longer requires access. • Uses Role-Based Access Controls — Role-based access control is utilized to support segregation of incompatible functions. • Reviews Access Roles and Rules — The appropriateness of access roles and access rules is reviewed on a periodic basis for unnecessary and inappropriate individuals with access and access rules are modified as appropriate | count: 020 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
General, Regulatory Compliance, Security Center | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC6.4 | SOC_2_CC6.4 | SOC 2 Type 2 CC6.4 | Logical and Physical Access Controls | Restricted physical access | Shared | The customer is responsible for implementing this recommendation. | • Creates or Modifies Physical Access — Processes are in place to create or modify physical access to facilities such as data centers, office spaces, and work areas, based on authorization from the system's asset owner. • Removes Physical Access — Processes are in place to remove access to physical resources when an individual no longer requires access. • Reviews Physical Access — Processes are in place to periodically review physical access to ensure consistency with job responsibilities | count: 001 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC6.5 | SOC_2_CC6.5 | SOC 2 Type 2 CC6.5 | Logical and Physical Access Controls | Logical and physical protections over physical assets | Shared | The customer is responsible for implementing this recommendation. | • Identifies Data and Software for Disposal — Procedures are in place to identify data and software stored on equipment to be disposed and to render such data and software unreadable. • Removes Data and Software From Entity Control — Procedures are in place to remove data and software stored on equipment to be removed from the physical control of the entity and to render such data and software unreadable | count: 002 Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC6.6 | SOC_2_CC6.6 | SOC 2 Type 2 CC6.6 | Logical and Physical Access Controls | Security measures against threats outside system boundaries | Shared | The customer is responsible for implementing this recommendation. | • Restricts Access — The types of activities that can occur through a communication channel (for example, FTP site, router port) are restricted. • Protects Identification and Authentication Credentials — Identification and authentication credentials are protected during transmission outside its system boundaries. • Requires Additional Authentication or Credentials — Additional authentication information or credentials are required when accessing the system from outside its boundaries. • Implements Boundary Protection Systems — Boundary protection systems (for example, firewalls, demilitarized zones, and intrusion detection systems) are implemented to protect external access points from attempts and unauthorized access and are monitored to detect such attempts | count: 041 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, Kubernetes, Network, Regulatory Compliance, Security Center, SQL, Storage | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC6.7 | SOC_2_CC6.7 | SOC 2 Type 2 CC6.7 | Logical and Physical Access Controls | Restrict the movement of information to authorized users | Shared | The customer is responsible for implementing this recommendation. | • Restricts the Ability to Perform Transmission — Data loss prevention processes and technologies are used to restrict ability to authorize and execute transmission, movement, and removal of information. • Uses Encryption Technologies or Secure Communication Channels to Protect Data — Encryption technologies or secured communication channels are used to protect transmission of data and other communications beyond connectivity access points. • Protects Removal Media — Encryption technologies and physical asset protections are used for removable media (such as USB drives and backup tapes), as appropriate. • Protects Mobile Devices — Processes are in place to protect mobile devices (such as laptops, smart phones, and tablets) that serve as information assets | count: 030 Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Define mobile device requirements (9ca3a3ea-3a1f-8ba0-31a8-6aed0fe1a7a4), Employ a media sanitization mechanism (eaaae23f-92c9-4460-51cf-913feaea4d52), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, Kubernetes, Regulatory Compliance, Security Center, SQL, Storage | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC6.8 | SOC_2_CC6.8 | SOC 2 Type 2 CC6.8 | Logical and Physical Access Controls | Prevent or detect against unauthorized or malicious software | Shared | The customer is responsible for implementing this recommendation. | Restricts Application and Software Installation — The ability to install applications and software is restricted to authorized individuals. • Detects Unauthorized Changes to Software and Configuration Parameters — Processes are in place to detect changes to software and configuration parameters that may be indicative of unauthorized or malicious software. • Uses a Defined Change Control Process — A management-defined change control process is used for the implementation of software. • Uses Antivirus and Anti-Malware Software — Antivirus and anti-malware software is implemented and maintained to provide for the interception or detection and remediation of malware. • Scans Information Assets from Outside the Entity for Malware and Other Unauthorized Software — Procedures are in place to scan information assets that have been transferred or returned to the entity’s custody for malware and other unauthorized software and to remove any items detected prior to its implementation on the network. | count: 053 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines (672fe5a1-2fcd-42d7-b85d-902b6e28c6ff), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines scale sets (a21f8c92-9e22-4f09-b759-50500d1d2dda), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines (1cb4d9c2-f88f-4069-bee0-dba239a57b09), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines scale sets (f655e522-adff-494d-95c2-52d4f6d56a42), [Preview]: Secure Boot should be enabled on supported Windows virtual machines (97566dd7-78ae-4997-8b36-1c7bfe0d8121), [Preview]: vTPM should be enabled on supported virtual machines (1c30f9cd-b84c-49cc-aa2c-9288447cc3b3), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Azure Arc enabled Kubernetes clusters should have the Azure Policy extension installed (6b2122c1-8120-4ff5-801b-17625a355590), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Endpoint protection health issues should be resolved on your machines (8e42c1f2-a2ab-49bc-994a-12bcd0dc4ac2), Endpoint protection should be installed on your machines (1f7c564c-0a90-4d44-b7e1-9d456cffaee8), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should disable automounting API credentials (423dd1ba-798e-40e4-9c4d-b6902674b423), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Kubernetes clusters should not grant CAP_SYS_ADMIN security capabilities (d2e7ea85-6b44-4317-a0be-1b951587f626), Kubernetes clusters should not use the default namespace (9f061a12-e40d-4183-a00e-171812443373), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Only approved VM extensions should be installed (c0e996f8-39cf-4af9-9f45-83fbde810432), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review threat protection status weekly (fad161f5-5261-401a-22dd-e037bae011bd), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Compute, Guest Configuration, Kubernetes, Regulatory Compliance, Security Center, Storage | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC7.1 | SOC_2_CC7.1 | SOC 2 Type 2 CC7.1 | System Operations | Detection and monitoring of new vulnerabilities | Shared | The customer is responsible for implementing this recommendation. | • Uses Defined Configuration Standards — Management has defined configuration standards. • Monitors Infrastructure and Software — The entity monitors infrastructure and software for noncompliance with the standards, which could threaten the achievement of the entity's objectives. • Implements Change-Detection Mechanisms — The IT system includes a changedetection mechanism (for example, file integrity monitoring tools) to alert personnel to unauthorized modifications of critical system files, configuration files, or content files. • Detects Unknown or Unauthorized Components — Procedures are in place to detect the introduction of unknown or unauthorized components. • Conducts Vulnerability Scans — The entity conducts vulnerability scans designed to identify potential vulnerabilities or misconfigurations on a periodic basis and after any significant change in the environment and takes action to remediate identified deficiencies on a timely basis | count: 017 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enable detection of network devices (426c172c-9914-10d1-25dd-669641fc1af4), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Regulatory Compliance, Security Center, SQL | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC7.2 | SOC_2_CC7.2 | SOC 2 Type 2 CC7.2 | System Operations | Monitor system components for anomalous behavior | Shared | The customer is responsible for implementing this recommendation. | • Implements Detection Policies, Procedures, and Tools — Detection policies and procedures are defined and implemented and detection tools are implemented on infrastructure and software to identify anomalies in the operation or unusual activity on systems. Procedures may include (1) a defined governance process for security event detection and management that includes provision of resources; (2) use of intelligence sources to identify newly discovered threats and vulnerabilities; and (3) logging of unusual system activities. • Designs Detection Measures — Detection measures are designed to identify anomalies that could result from actual or attempted (1) compromise of physical barriers; (2) unauthorized actions of authorized personnel; (3) use of compromised identification and authentication credentials; (4) unauthorized access from outside the system boundaries; (5) compromise of authorized external parties; and (6) implementation or connection of unauthorized hardware and software. • Implements Filters to Analyze Anomalies — Management has implemented procedures to filter, summarize, and analyze anomalies to identify security events. • Monitors Detection Tools for Effective Operation — Management has implemented processes to monitor the effectiveness of detection tools | count: 020 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), An activity log alert should exist for specific Administrative operations (b954148f-4c11-4c38-8221-be76711e194a), An activity log alert should exist for specific Policy operations (c5447c04-a4d7-4ba8-a263-c9ee321a6858), An activity log alert should exist for specific Security operations (3b980d31-7904-4bb7-8575-5665739a8052), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for open-source relational databases should be enabled (0a9fbe0d-c5c4-4da8-87d8-f4fd77338835), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Kubernetes Service clusters should have Defender profile enabled (a1840de2-8088-4ea8-b153-b4c723e9cb01), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Govern and monitor audit processing activities (333b4ada-4a02-0648-3d4d-d812974f1bb2), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
Guest Configuration, Kubernetes, Monitoring, Regulatory Compliance, Security Center, SQL | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC7.3 | SOC_2_CC7.3 | SOC 2 Type 2 CC7.3 | System Operations | Security incidents detection | Shared | The customer is responsible for implementing this recommendation. | Responds to Security Incidents — Procedures are in place for responding to security incidents and evaluating the effectiveness of those policies and procedures on a periodic basis. • Communicates and Reviews Detected Security Events — Detected security events are communicated to and reviewed by the individuals responsible for the management of the security program and actions are taken, if necessary. • Develops and Implements Procedures to Analyze Security Incidents — Procedures are in place to analyze security incidents and determine system impact Additional points of focus that apply only in an engagement using the trust services criteria for privacy: • Assesses the Impact on Personal Information — Detected security events are evaluated to determine whether they could or did result in the unauthorized disclosure or use of personal information and whether there has been a failure to comply with applicable laws or regulations. • Determines Personal Information Used or Disclosed — When an unauthorized use or disclosure of personal information has occurred, the affected information is identified | count: 001 Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC7.4 | SOC_2_CC7.4 | SOC 2 Type 2 CC7.4 | System Operations | Security incidents response | Shared | The customer is responsible for implementing this recommendation. | Assigns Roles and Responsibilities — Roles and responsibilities for the design, implementation, maintenance, and execution of the incident response program are assigned, including the use of external resources when necessary. • Contains Security Incidents — Procedures are in place to contain security incidents that actively threaten entity objectives. • Mitigates Ongoing Security Incidents — Procedures are in place to mitigate the effects of ongoing security incidents. • Ends Threats Posed by Security Incidents — Procedures are in place to end the threats posed by security incidents through closure of the vulnerability, removal of unauthorized access, and other remediation actions. • Restores Operations — Procedures are in place to restore data and business operations to an interim state that permits the achievement of entity objectives. • Develops and Implements Communication Protocols for Security Incidents — Protocols for communicating security incidents and actions taken to affected parties are developed and implemented to meet the entity's objectives. • Obtains Understanding of Nature of Incident and Determines Containment Strategy — An understanding of the nature (for example, the method by which the incident occurred and the affected system resources) and severity of the security incident is obtained to determine the appropriate containment strategy, including (1) a determination of the appropriate response time frame, and (2) the determination and execution of the containment approach. • Remediates Identified Vulnerabilities — Identified vulnerabilities are remediated through the development and execution of remediation activities. • Communicates Remediation Activities — Remediation activities are documented and communicated in accordance with the incident-response program. • Evaluates the Effectiveness of Incident Response — The design of incident-response activities is evaluated for effectiveness on a periodic basis. • Periodically Evaluates Incidents — Periodically, management reviews incidents related to security, availability, processing integrity, confidentiality, and privacy and identifies the need for system changes based on incident patterns and root causes Communicates Unauthorized Use and Disclosure — Events that resulted in unauthorized use or disclosure of personal information are communicated to the data subjects, legal and regulatory authorities, and others as required. • Application of Sanctions — The conduct of individuals and organizations operating under the authority of the entity and involved in the unauthorized use or disclosure of personal information is evaluated and, if appropriate, sanctioned in accordance with entity policies and legal and regulatory requirements | count: 017 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Include dynamic reconfig of customer deployed resources (1e0d5ba8-a433-01aa-829c-86b06c9631ec), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Network, Regulatory Compliance, Security Center | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC7.5 | SOC_2_CC7.5 | SOC 2 Type 2 CC7.5 | System Operations | Recovery from identified security incidents | Shared | The customer is responsible for implementing this recommendation. | • Restores the Affected Environment — The activities restore the affected environment to functional operation by rebuilding systems, updating software, installing patches, and changing configurations, as needed. • Communicates Information About the Event — Communications about the nature of the incident, recovery actions taken, and activities required for the prevention of future security events are made to management and others as appropriate (internal and external). • Determines Root Cause of the Event — The root cause of the event is determined. • Implements Changes to Prevent and Detect Recurrences — Additional architecture or changes to preventive and detective controls, or both, are implemented to prevent and detect recurrences on a timely basis. • Improves Response and Recovery Procedures — Lessons learned are analyzed and the incident-response plan and recovery procedures are improved. • Implements Incident-Recovery Plan Testing — Incident-recovery plan testing is performed on a periodic basis. The testing includes (1) development of testing scenarios based on threat likelihood and magnitude; (2) consideration of relevant system components from across the entity that can impair availability; (3) scenarios that consider the potential for the lack of availability of key personnel; and (4) revision of continuity plans and systems based on test results | count: 019 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Coordinate with external organizations to achieve cross org perspective (d4e6a629-28eb-79a9-000b-88030e4823ca), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Network, Regulatory Compliance, Security Center | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC8.1 | SOC_2_CC8.1 | SOC 2 Type 2 CC8.1 | Change Management | Changes to infrastructure, data, and software | Shared | The customer is responsible for implementing this recommendation. | Manages Changes Throughout the System Life Cycle — A process for managing system changes throughout the life cycle of the system and its components (infrastructure, data, software, and procedures) is used to support system availability and processing integrity. • Authorizes Changes — A process is in place to authorize system changes prior to development. • Designs and Develops Changes — A process is in place to design and develop system changes. • Documents Changes — A process is in place to document system changes to support ongoing maintenance of the system and to support system users in performing their responsibilities. • Tracks System Changes — A process is in place to track system changes prior to implementation. • Configures Software — A process is in place to select and implement the configuration parameters used to control the functionality of software. • Tests System Changes — A process is in place to test system changes prior to implementation. • Approves System Changes — A process is in place to approve system changes prior to implementation. • Deploys System Changes — A process is in place to implement system changes. • Identifies and Evaluates System Changes — Objectives affected by system changes are identified and the ability of the modified system to meet the objectives is evaluated throughout the system development life cycle. • Identifies Changes in Infrastructure, Data, Software, and Procedures Required to Remediate Incidents — Changes in infrastructure, data, software, and procedures required to remediate incidents to continue to meet objectives are identified and the change process is initiated upon identification. • Creates Baseline Configuration of IT Technology — A baseline configuration of IT and control systems is created and maintained. • Provides for Changes Necessary in Emergency Situations — A process is in place for authorizing, designing, testing, approving, and implementing changes necessary in emergency situations (that is, changes that need to be implemented in an urgent time frame). Additional points of focus that apply only in an engagement using the trust services criteria for confidentiality: • Protects Confidential Information — The entity protects confidential information during system design, development, testing, implementation, and change processes to meet the entity’s objectives related to confidentiality. Additional points of focus that apply only in an engagement using the trust services criteria for privacy: • Protects Personal Information — The entity protects personal information during system design, development, testing, implementation, and change processes to meet the entity’s objectives related to privacy. | count: 052 [Deprecated]: Function apps should have 'Client Certificates (Incoming client certificates)' enabled (eaebaea7-8013-4ceb-9d14-7eb32271373c), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines (672fe5a1-2fcd-42d7-b85d-902b6e28c6ff), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines scale sets (a21f8c92-9e22-4f09-b759-50500d1d2dda), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines (1cb4d9c2-f88f-4069-bee0-dba239a57b09), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines scale sets (f655e522-adff-494d-95c2-52d4f6d56a42), [Preview]: Secure Boot should be enabled on supported Windows virtual machines (97566dd7-78ae-4997-8b36-1c7bfe0d8121), [Preview]: vTPM should be enabled on supported virtual machines (1c30f9cd-b84c-49cc-aa2c-9288447cc3b3), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), App Service apps should use latest 'HTTP Version' (8c122334-9d20-4eb8-89ea-ac9a705b74ae), Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Azure Arc enabled Kubernetes clusters should have the Azure Policy extension installed (6b2122c1-8120-4ff5-801b-17625a355590), Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters (0a15ec92-a229-4763-bb14-0ea34a568f8d), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits (e345eecc-fa47-480f-9e88-67dcc122b164), Kubernetes cluster containers should not share host process ID or host IPC namespace (47a1ee2f-2a2a-4576-bf2a-e0e36709c2b8), Kubernetes cluster containers should only use allowed AppArmor profiles (511f5417-5d12-434d-ab2e-816901e72a5e), Kubernetes cluster containers should only use allowed capabilities (c26596ff-4d70-4e6a-9a30-c2506bd2f80c), Kubernetes cluster containers should only use allowed images (febd0533-8e55-448f-b837-bd0e06f16469), Kubernetes cluster containers should run with a read only root file system (df49d893-a74c-421d-bc95-c663042e5b80), Kubernetes cluster pod hostPath volumes should only use allowed host paths (098fc59e-46c7-4d99-9b16-64990e543d75), Kubernetes cluster pods and containers should only run with approved user and group IDs (f06ddb64-5fa3-4b77-b166-acb36f7f6042), Kubernetes cluster pods should only use approved host network and port range (82985f06-dc18-4a48-bc1c-b9f4f0098cfe), Kubernetes cluster services should listen only on allowed ports (233a2a17-77ca-4fb1-9b6b-69223d272a44), Kubernetes cluster should not allow privileged containers (95edb821-ddaf-4404-9732-666045e056b4), Kubernetes clusters should disable automounting API credentials (423dd1ba-798e-40e4-9c4d-b6902674b423), Kubernetes clusters should not allow container privilege escalation (1c6e92c9-99f0-4e55-9cf2-0c234dc48f99), Kubernetes clusters should not grant CAP_SYS_ADMIN security capabilities (d2e7ea85-6b44-4317-a0be-1b951587f626), Kubernetes clusters should not use the default namespace (9f061a12-e40d-4183-a00e-171812443373), Linux machines should meet requirements for the Azure compute security baseline (fc9b3da7-8347-4380-8e70-0a0361d8dedd), Only approved VM extensions should be installed (c0e996f8-39cf-4af9-9f45-83fbde810432), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Storage accounts should allow access from trusted Microsoft services (c9d007d0-c057-4772-b18c-01e546713bcd), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a), Windows machines should meet requirements of the Azure compute security baseline (72650e9f-97bc-4b2a-ab5f-9781a9fcecbc) |
App Service, Compute, Guest Configuration, Kubernetes, Regulatory Compliance, Security Center, Storage | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC9.1 | SOC_2_CC9.1 | SOC 2 Type 2 CC9.1 | Risk Mitigation | Risk mitigation activities | Shared | The customer is responsible for implementing this recommendation. | • Considers Mitigation of Risks of Business Disruption — Risk mitigation activities include the development of planned policies, procedures, communications, and alternative processing solutions to respond to, mitigate, and recover from security events that disrupt business operations. Those policies and procedures include monitoring processes, information, and communications to meet the entity's objectives during response, mitigation, and recovery efforts. • Considers the Use of Insurance to Mitigate Financial Impact Risks — The risk management activities consider the use of insurance to offset the financial impact of loss events that would otherwise impair the ability of the entity to meet its objectives | count: 003 Determine information protection needs (dbcef108-7a04-38f5-8609-99da110a2a57), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | CC9.2 | SOC_2_CC9.2 | SOC 2 Type 2 CC9.2 | Risk Mitigation | Vendors and business partners risk management | Shared | The customer is responsible for implementing this recommendation. | Establishes Requirements for Vendor and Business Partner Engagements — The entity establishes specific requirements for a vendor and business partner engagement that includes (1) scope of services and product specifications, (2) roles and responsibilities, (3) compliance requirements, and (4) service levels. • Assesses Vendor and Business Partner Risks — The entity assesses, on a periodic basis, the risks that vendors and business partners (and those entities’ vendors and business partners) represent to the achievement of the entity's objectives. • Assigns Responsibility and Accountability for Managing Vendors and Business Partners — The entity assigns responsibility and accountability for the management of risks associated with vendors and business partners. • Establishes Communication Protocols for Vendors and Business Partners — The entity establishes communication and resolution protocols for service or product issues related to vendors and business partners. • Establishes Exception Handling Procedures From Vendors and Business Partners — The entity establishes exception handling procedures for service or product issues related to vendors and business partners. • Assesses Vendor and Business Partner Performance — The entity periodically assesses the performance of vendors and business partners. • Implements Procedures for Addressing Issues Identified During Vendor and Business Partner Assessments — The entity implements procedures for addressing issues identified with vendor and business partner relationships. • Implements Procedures for Terminating Vendor and Business Partner Relationships — The entity implements procedures for terminating vendor and business partner relationships. Additional points of focus that apply only to an engagement using the trust services criteria for confidentiality: • Obtains Confidentiality Commitments from Vendors and Business Partners — The entity obtains confidentiality commitments that are consistent with the entity’s confidentiality commitments and requirements from vendors and business partners who have access to confidential information. • Assesses Compliance With Confidentiality Commitments of Vendors and Business Partners — On a periodic and as-needed basis, the entity assesses compliance by vendors and business partners with the entity’s confidentiality commitments and requirements. Additional points of focus that apply only to an engagement using the trust services criteria for privacy: • Obtains Privacy Commitments from Vendors and Business Partners — The entity obtains privacy commitments, consistent with the entity’s privacy commitments and requirements, from vendors and business partners who have access to personal information. • Assesses Compliance with Privacy Commitments of Vendors and Business Partners — On a periodic and as-needed basis, the entity assesses compliance by vendors and business partners with the entity’s privacy commitments and requirements and takes corrective action as necessary | count: 020 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Define the duties of processors (52375c01-4d4c-7acc-3aa4-5b3d53a047ec), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Establish third-party personnel security requirements (3881168c-5d38-6f04-61cc-b5d87b2c4c58), Monitor third-party provider compliance (f8ded0c6-a668-9371-6bb6-661d58787198), Record disclosures of PII to third parties (8b1da407-5e60-5037-612e-2caa1b590719), Require third-party providers to comply with personnel security policies and procedures (e8c31e15-642d-600f-78ab-bad47a5787e6), Train staff on PII sharing and its consequences (8019d788-713d-90a1-5570-dac5052f517d) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P1.1 | SOC_2_P1.1 | SOC 2 Type 2 P1.1 | Additional Criteria For Privacy | Privacy notice | Shared | The customer is responsible for implementing this recommendation. | • Communicates to Data Subjects — Notice is provided to data subjects regarding the following: — Purpose for collecting personal information — Choice and consent — Types of personal information collected — Methods of collection (for example, use of cookies or other tracking techniques) — Use, retention, and disposal — Access — Disclosure to third parties — Security for privacy — Quality, including data subjects’ responsibilities for quality — Monitoring and enforcement • Provides Notice to Data Subjects — Notice is provided to data subjects (1) at or before the time personal information is collected or as soon as practical thereafter, (2) at or before the entity changes its privacy notice or as soon as practical thereafter, or (3) before personal information is used for new purposes not previously identified. • Covers Entities and Activities in Notice — An objective description of the entities and activities covered is included in the entity’s privacy notice. • Uses Clear and Conspicuous Language — The entity’s privacy notice is conspicuous and uses clear language. | count: 005 Document and distribute a privacy policy (ee67c031-57fc-53d0-0cca-96c4c04345e8), Ensure privacy program information is publicly available (1beb1269-62ee-32cd-21ad-43d6c9750eb6), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Provide privacy notice to the public and to individuals (5023a9e7-8e64-2db6-31dc-7bce27f796af) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P2.1 | SOC_2_P2.1 | SOC 2 Type 2 P2.1 | Additional Criteria For Privacy | Privacy consent | Shared | The customer is responsible for implementing this recommendation. | • Communicates to Data Subjects — Data subjects are informed (a) about the choices available to them with respect to the collection, use, and disclosure of personal information and (b) that implicit or explicit consent is required to collect, use, and disclose personal information, unless a law or regulation specifically requires or allows otherwise. • Communicates Consequences of Denying or Withdrawing Consent — When personal information is collected, data subjects are informed of the consequences of refusing to provide personal information or denying or withdrawing consent to use personal information for purposes identified in the notice. • Obtains Implicit or Explicit Consent — Implicit or explicit consent is obtained from data subjects at or before the time personal information is collected or soon there-after. The individual’s preferences expressed in his or her consent are confirmed and implemented. • Documents and Obtains Consent for New Purposes and Uses — If information that was previously collected is to be used for purposes not previously identified in the privacy notice, the new purpose is documented, the data subject is notified, and implicit or explicit consent is obtained prior to such new use or purpose. • Obtains Explicit Consent for Sensitive Information — Explicit consent is obtained directly from the data subject when sensitive personal information is collected, used, or disclosed, unless a law or regulation specifically requires otherwise. • Obtains Consent for Data Transfers — Consent is obtained before personal information is transferred to or from an individual’s computer or other similar device. | count: 004 Document personnel acceptance of privacy requirements (271a3e58-1b38-933d-74c9-a580006b80aa), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P3.1 | SOC_2_P3.1 | SOC 2 Type 2 P3.1 | Additional Criteria For Privacy | Consistent personal information collection | Shared | The customer is responsible for implementing this recommendation. | • Limits the Collection of Personal Information — The collection of personal information is limited to that necessary to meet the entity’s objectives. • Collects Information by Fair and Lawful Means — Methods of collecting personal information are reviewed by management before they are implemented to confirm that personal information is obtained (a) fairly, without intimidation or deception, and (b) lawfully, adhering to all relevant rules of law, whether derived from statute or common law, relating to the collection of personal information. • Collects Information From Reliable Sources — Management confirms that third parties from whom personal information is collected (that is, sources other than the individual) are reliable sources that collect information fairly and lawfully. • Informs Data Subjects When Additional Information Is Acquired — Data subjects are informed if the entity develops or acquires additional information about them for its use. | count: 004 Determine legal authority to collect PII (7d70383a-32f4-a0c2-61cf-a134851968c2), Document process to ensure integrity of PII (18e7906d-4197-20fa-2f14-aaac21864e71), Evaluate and review PII holdings regularly (b6b32f80-a133-7600-301e-398d688e7e0c), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P3.2 | SOC_2_P3.2 | SOC 2 Type 2 P3.2 | Additional Criteria For Privacy | Personal information explicit consent | Shared | The customer is responsible for implementing this recommendation. | • Obtains Explicit Consent for Sensitive Information — Explicit consent is obtained directly from the data subject when sensitive personal information is collected, used, or disclosed, unless a law or regulation specifically requires otherwise. • Documents Explicit Consent to Retain Information — Documentation of explicit consent for the collection, use, or disclosure of sensitive personal information is retained in accordance with objectives related to privacy. | count: 002 Collect PII directly from the individual (964b340a-43a4-4798-2af5-7aedf6cb001b), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P4.1 | SOC_2_P4.1 | SOC 2 Type 2 P4.1 | Additional Criteria For Privacy | Personal information use | Shared | The customer is responsible for implementing this recommendation. | • Uses Personal Information for Intended Purposes — Personal information is used only for the intended purposes for which it was collected and only when implicit or explicit consent has been obtained, unless a law or regulation specifically requires otherwise. | count: 005 Document the legal basis for processing personal information (79c75b38-334b-1a69-65e0-a9d929a42f75), Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Obtain consent prior to collection or processing of personal data (069101ac-4578-31da-0cd4-ff083edd3eb4), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P4.2 | SOC_2_P4.2 | SOC 2 Type 2 P4.2 | Additional Criteria For Privacy | Personal information retention | Shared | The customer is responsible for implementing this recommendation. | • Retains Personal Information — Personal information is retained for no longer than necessary to fulfill the stated purposes, unless a law or regulation specifically requires otherwise. • Protects Personal Information — Policies and procedures have been implemented to protect personal information from erasure or destruction during the specified retention period of the information. | count: 002 Adhere to retention periods defined (1ecb79d7-1a06-9a3b-3be8-f434d04d1ec1), Document process to ensure integrity of PII (18e7906d-4197-20fa-2f14-aaac21864e71) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P4.3 | SOC_2_P4.3 | SOC 2 Type 2 P4.3 | Additional Criteria For Privacy | Personal information disposal | Shared | The customer is responsible for implementing this recommendation. | • Captures, Identifies, and Flags Requests for Deletion — Requests for deletion of personal information are captured and information related to the requests is identified and flagged for destruction to meet the entity’s objectives related to privacy. • Disposes of, Destroys, and Redacts Personal Information — Personal information no longer retained is anonymized, disposed of, or destroyed in a manner that prevents loss, theft, misuse, or unauthorized access. • Destroys Personal Information — Policies and procedures are implemented to erase or otherwise destroy personal information that has been identified for destruction. | count: 002 Perform disposition review (b5a4be05-3997-1731-3260-98be653610f6), Verify personal data is deleted at the end of processing (c6b877a6-5d6d-1862-4b7f-3ccc30b25b63) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P5.1 | SOC_2_P5.1 | SOC 2 Type 2 P5.1 | Additional Criteria For Privacy | Personal information access | Shared | The customer is responsible for implementing this recommendation. | • Authenticates Data Subjects’ Identity — The identity of data subjects who request access to their personal information is authenticated before they are given access to that information. • Permits Data Subjects Access to Their Personal Information — Data subjects are able to determine whether the entity maintains personal information about them and, upon request, may obtain access to their personal information. • Provides Understandable Personal Information Within Reasonable Time — Personal information is provided to data subjects in an understandable form, in a reasonable time frame, and at a reasonable cost, if any. • Informs Data Subjects If Access Is Denied — When data subjects are denied access to their personal information, the entity informs them of the denial and the reason for the denial in a timely manner, unless prohibited by law or regulation. | count: 002 Implement methods for consumer requests (b8ec9ebb-5b7f-8426-17c1-2bc3fcd54c6e), Publish rules and regulations accessing Privacy Act records (ad1d562b-a04b-15d3-6770-ed310b601cb5) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P5.2 | SOC_2_P5.2 | SOC 2 Type 2 P5.2 | Additional Criteria For Privacy | Personal information correction | Shared | The customer is responsible for implementing this recommendation. | • Communicates Denial of Access Requests — Data subjects are informed, in writing, of the reason a request for access to their personal information was denied, the source of the entity’s legal right to deny such access, if applicable, and the individual’s right, if any, to challenge such denial, as specifically permitted or required by law or regulation. • Permits Data Subjects to Update or Correct Personal Information — Data subjects are able to update or correct personal information held by the entity. The entity provides such updated or corrected information to third parties that were previously provided with the data subject’s personal information consistent with the entity’s objectives related to privacy. • Communicates Denial of Correction Requests — Data subjects are informed, in writing, about the reason a request for correction of personal information was denied and how they may appeal. | count: 001 Respond to rectification requests (27ab3ac0-910d-724d-0afa-1a2a01e996c0) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P6.1 | SOC_2_P6.1 | SOC 2 Type 2 P6.1 | Additional Criteria For Privacy | Personal information third party disclosure | Shared | The customer is responsible for implementing this recommendation. | • Communicates Privacy Policies to Third Parties — Privacy policies or other specific instructions or requirements for handling personal information are communicated to third parties to whom personal information is disclosed. • Discloses Personal Information Only When Appropriate — Personal information is disclosed to third parties only for the purposes for which it was collected or created and only when implicit or explicit consent has been obtained from the data subject, unless a law or regulation specifically requires otherwise. • Discloses Personal Information Only to Appropriate Third Parties — Personal information is disclosed only to third parties who have agreements with the entity to protect personal information in a manner consistent with the relevant aspects of the entity’s privacy notice or other specific instructions or requirements. The entity has procedures in place to evaluate that the third parties have effective controls to meet the terms of the agreement, instructions, or requirements. • Discloses Information to Third Parties for New Purposes and Uses — Personal information is disclosed to third parties for new purposes or uses only with the prior implicit or explicit consent of data subjects. | count: 015 Define the duties of processors (52375c01-4d4c-7acc-3aa4-5b3d53a047ec), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Establish privacy requirements for contractors and service providers (f8d141b7-4e21-62a6-6608-c79336e36bc9), Record disclosures of PII to third parties (8b1da407-5e60-5037-612e-2caa1b590719), Train staff on PII sharing and its consequences (8019d788-713d-90a1-5570-dac5052f517d) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P6.2 | SOC_2_P6.2 | SOC 2 Type 2 P6.2 | Additional Criteria For Privacy | Authorized disclosure of personal information record | Shared | The customer is responsible for implementing this recommendation. | • Creates and Retains Record of Authorized Disclosures — The entity creates and maintains a record of authorized disclosures of personal information that is complete, accurate, and timely. | count: 001 Keep accurate accounting of disclosures of information (0bbfd658-93ab-6f5e-1e19-3c1c1da62d01) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P6.3 | SOC_2_P6.3 | SOC 2 Type 2 P6.3 | Additional Criteria For Privacy | Unauthorized disclosure of personal information record | Shared | The customer is responsible for implementing this recommendation. | • Creates and Retains Record of Detected or Reported Unauthorized Disclosures — The entity creates and maintains a record of detected or reported unauthorized disclosures of personal information that is complete, accurate, and timely. | count: 001 Keep accurate accounting of disclosures of information (0bbfd658-93ab-6f5e-1e19-3c1c1da62d01) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P6.4 | SOC_2_P6.4 | SOC 2 Type 2 P6.4 | Additional Criteria For Privacy | Third party agreements | Shared | The customer is responsible for implementing this recommendation. | • Discloses Personal Information Only to Appropriate Third Parties — Personal information is disclosed only to third parties who have agreements with the entity to protect personal information in a manner consistent with the relevant aspects of the entity’s privacy notice or other specific instructions or requirements. The entity has procedures in place to evaluate that the third parties have effective controls to meet the terms of the agreement, instructions, or requirements. • Remediates Misuse of Personal Information by a Third Party — The entity takes remedial action in response to misuse of personal information by a third party to whom the entity has transferred such information. | count: 001 Define the duties of processors (52375c01-4d4c-7acc-3aa4-5b3d53a047ec) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P6.5 | SOC_2_P6.5 | SOC 2 Type 2 P6.5 | Additional Criteria For Privacy | Third party unauthorized disclosure notification | Shared | The customer is responsible for implementing this recommendation. | • Remediates Misuse of Personal Information by a Third Party — The entity takes remedial action in response to misuse of personal information by a third party to whom the entity has transferred such information. • Reports Actual or Suspected Unauthorized Disclosures — A process exists for obtaining commitments from vendors and other third parties to report to the entity actual or suspected unauthorized disclosures of personal information. | count: 012 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629), Information security and personal data protection (34738025-5925-51f9-1081-f2d0060133ed) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P6.6 | SOC_2_P6.6 | SOC 2 Type 2 P6.6 | Additional Criteria For Privacy | Privacy incident notification | Shared | The customer is responsible for implementing this recommendation. | • Remediates Misuse of Personal Information by a Third Party — The entity takes remedial action in response to misuse of personal information by a third party to whom the entity has transferred such information. • Provides Notice of Breaches and Incidents — The entity has a process for providing notice of breaches and incidents to affected data subjects, regulators, and others to meet the entity’s objectives related to privacy. | count: 002 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Information security and personal data protection (34738025-5925-51f9-1081-f2d0060133ed) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P6.7 | SOC_2_P6.7 | SOC 2 Type 2 P6.7 | Additional Criteria For Privacy | Accounting of disclosure of personal information | Shared | The customer is responsible for implementing this recommendation. | • Identifies Types of Personal Information and Handling Process — The types of personal information and sensitive personal information and the related processes, systems, and third parties involved in the handling of such information are identified. • Captures, Identifies, and Communicates Requests for Information — Requests for an accounting of personal information held and disclosures of the data subjects’ personal information are captured and information related to the requests is identified and communicated to data subjects to meet the entity’s objectives related to privacy. | count: 005 Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Keep accurate accounting of disclosures of information (0bbfd658-93ab-6f5e-1e19-3c1c1da62d01), Make accounting of disclosures available upon request (d4f70530-19a2-2a85-6e0c-0c3c465e3325), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P7.1 | SOC_2_P7.1 | SOC 2 Type 2 P7.1 | Additional Criteria For Privacy | Personal information quality | Shared | The customer is responsible for implementing this recommendation. | • Ensures Accuracy and Completeness of Personal Information — Personal information is accurate and complete for the purposes for which it is to be used. • Ensures Relevance of Personal Information — Personal information is relevant to the purposes for which it is to be used. | count: 003 Confirm quality and integrity of PII (8bb40df9-23e4-4175-5db3-8dba86349b73), Issue guidelines for ensuring data quality and integrity (0a24f5dc-8c40-94a7-7aee-bb7cd4781d37), Verify inaccurate or outdated PII (0461cacd-0b3b-4f66-11c5-81c9b19a3d22) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | P8.1 | SOC_2_P8.1 | SOC 2 Type 2 P8.1 | Additional Criteria For Privacy | Privacy complaint management and compliance management | Shared | The customer is responsible for implementing this recommendation. | • Communicates to Data Subjects — Data subjects are informed about how to contact the entity with inquiries, complaints, and disputes. • Addresses Inquiries, Complaints, and Disputes — A process is in place to address inquiries, complaints, and disputes. • Documents and Communicates Dispute Resolution and Recourse — Each complaint is addressed and the resolution is documented and communicated to the individual. • Documents and Reports Compliance Review Results — Compliance with objectives related to privacy are reviewed and documented and the results of such reviews are reported to management. If problems are identified, remediation plans are developed and implemented. • Documents and Reports Instances of Noncompliance — Instances of noncompliance with objectives related to privacy are documented and reported and, if needed, corrective and disciplinary measures are taken on a timely basis. • Performs Ongoing Monitoring — Ongoing procedures are performed for monitoring the effectiveness of controls over personal information and for taking timely corrective actions when necessary. | count: 005 Document and implement privacy complaint procedures (eab4450d-9e5c-4f38-0656-2ff8c78c83f3), Evaluate and review PII holdings regularly (b6b32f80-a133-7600-301e-398d688e7e0c), Information security and personal data protection (34738025-5925-51f9-1081-f2d0060133ed), Respond to complaints, concerns, or questions timely (6ab47bbf-867e-9113-7998-89b58f77326a), Train staff on PII sharing and its consequences (8019d788-713d-90a1-5570-dac5052f517d) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | PI1.1 | SOC_2_PI1.1 | SOC 2 Type 2 PI1.1 | Additional Criteria For Processing Integrity | Data processing definitions | Shared | The customer is responsible for implementing this recommendation. | • Identifies Information Specifications — The entity identifies information specifications required to support the use of products and services. • Defines Data Necessary to Support a Product or Service — When data is provided as part of a service or product or as part of a reporting obligation related to a product or service: 1. The definition of the data is available to the users of the data 2. The definition of the data includes the following information: a. The population of events or instances included in the data b. The nature of each element (for example, field) of the data (that is, the event or instance to which the data element relates, for example, transaction price of a sale of XYZ Corporation stock for the last trade in that stock on a given day) c. Source(s) of the data d. The unit(s) of measurement of data elements (for example, fields) e. The accuracy/correctness/precision of measurement f. The uncertainty or confidence interval inherent in each data element and in the population of those elements g. The date the data was observed or the period of time during which the events relevant to the data occurred h. The factors in addition to the date and period of time used to determine the inclusion and exclusion of items in the data elements and population 3. The definition is complete and accurate. 4. The description of the data identifies any information that is necessary to understand each data element and the population in a manner consistent with its definition and intended purpose (metadata) that has not been included within the data. The following point of focus, which applies only to an engagement using the trust services criteria for processing integrity for a system that produces, manufactures, or distributes products, highlights important characteristics relating to this criterion: • Defines Information Necessary to Support the Use of a Good or Product — When information provided by the entity is needed to use the good or product in accordance with its specifications: 1. The required information is available to the user of the good or product. 2. The required information is clearly identifiable. 3. The required information is validated for completeness and accuracy | count: 003 Implement privacy notice delivery methods (06f84330-4c27-21f7-72cd-7488afd50244), Provide privacy notice (098a7b84-1031-66d8-4e78-bd15b5fd2efb), Restrict communications (5020f3f4-a579-2f28-72a8-283c5a0b15f9) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | PI1.2 | SOC_2_PI1.2 | SOC 2 Type 2 PI1.2 | Additional Criteria For Processing Integrity | System inputs over completeness and accuracy | Shared | The customer is responsible for implementing this recommendation. | • Defines Characteristics of Processing Inputs — The characteristics of processing inputs that are necessary to meet requirements are defined. • Evaluates Processing Inputs — Processing inputs are evaluated for compliance with defined input requirements. • Creates and Maintains Records of System Inputs — Records of system input activities are created and maintained completely and accurately in a timely manner. | count: 001 Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | PI1.3 | SOC_2_PI1.3 | SOC 2 Type 2 PI1.3 | Additional Criteria For Processing Integrity | System processing | Shared | The customer is responsible for implementing this recommendation. | • Defines Processing Specifications — The processing specifications that are necessary to meet product or service requirements are defined. • Defines Processing Activities — Processing activities are defined to result in products or services that meet specifications. • Detects and Corrects Production Errors — Errors in the production process are detected and corrected in a timely manner. • Records System Processing Activities — System processing activities are recorded completely and accurately in a timely manner. • Processes Inputs — Inputs are processed completely, accurately, and timely as authorized in accordance with defined processing activities | count: 005 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Generate error messages (c2cb4658-44dc-9d11-3dad-7c6802dd5ba3), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Perform information input validation (8b1f29eb-1b22-4217-5337-9207cb55231e), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | PI1.4 | SOC_2_PI1.4 | SOC 2 Type 2 PI1.4 | Additional Criteria For Processing Integrity | System output is complete, accurate, and timely | Shared | The customer is responsible for implementing this recommendation. | • Protects Output — Output is protected when stored or delivered, or both, to prevent theft, destruction, corruption, or deterioration that would prevent output from meeting specifications. • Distributes Output Only to Intended Parties — Output is distributed or made available only to intended parties. • Distributes Output Completely and Accurately — Procedures are in place to provide for the completeness, accuracy, and timeliness of distributed output. • Creates and Maintains Records of System Output Activities — Records of system output activities are created and maintained completely and accurately in a timely manner. | count: 003 Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa) |
Regulatory Compliance | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SOC_2 | PI1.5 | SOC_2_PI1.5 | SOC 2 Type 2 PI1.5 | Additional Criteria For Processing Integrity | Store inputs and outputs completely, accurately, and timely | Shared | The customer is responsible for implementing this recommendation. | • Protects Stored Items — Stored items are protected to prevent theft, corruption, destruction, or deterioration that would prevent output from meeting specifications. • Archives and Protects System Records — System records are archived and archives are protected against theft, corruption, destruction, or deterioration that would prevent them from being used. • Stores Data Completely and Accurately — Procedures are in place to provide for the complete, accurate, and timely storage of data. • Creates and Maintains Records of System Storage Activities — Records of system storage activities are created and maintained completely and accurately in a timely manner | count: 010 Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the input, output, processing, and storage of data (e603da3a-8af7-4f8a-94cb-1bcc0e0333d2), Review label activity and analytics (e23444b9-9662-40f3-289e-6d25c02b48fa), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7) |
Backup, Regulatory Compliance, SQL | SOC 2 Type 2 (4054785f-702b-4a98-9215-009cbd58b141) | |
| SWIFT_CSCF_v2021 | 1.1 | SWIFT_CSCF_v2021_1.1 | SWIFT CSCF v2021 1.1 | SWIFT Environment Protection | SWIFT Environment Protection | n/a | Ensure the protection of the user's local SWIFT infrastructure from potentially compromised elements of the general IT environment and external environment. | link | count: 030 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Container Registry should use a virtual network service endpoint (c4857be7-912a-4c75-87e6-e30292bcdf78), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should use a virtual network service endpoint (2d21331d-a4c2-4def-a9ad-ee4e1e023beb), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), Cosmos DB should use a virtual network service endpoint (e0a2b1a3-f7f9-4569-807f-2a9edebdf4d9), Event Hub should use a virtual network service endpoint (d63edb4a-c612-454d-b47d-191a724fcbf0), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Key Vault should use a virtual network service endpoint (ea4d6841-2173-4317-9747-ff522a45120f), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Private endpoint should be enabled for MariaDB servers (0a1302fb-a631-4106-9753-f3d494733990), Private endpoint should be enabled for MySQL servers (7595c971-233d-4bcf-bd18-596129188c49), Private endpoint should be enabled for PostgreSQL servers (0564d078-92f5-4f97-8398-b9f58a51f70b), SQL Server should use a virtual network service endpoint (ae5d2f14-d830-42b6-9899-df6cfe9c71a3), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage Accounts should use a virtual network service endpoint (60d21c4f-21a3-4d94-85f4-b924e6aeeda4), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
App Service, Container Registry, Key Vault, Monitoring, Network, Security Center, SQL, Storage, VM Image Builder | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 1.2 | SWIFT_CSCF_v2021_1.2 | SWIFT CSCF v2021 1.2 | SWIFT Environment Protection | Operating System Privileged Account Control | n/a | Restrict and control the allocation and usage of administrator-level operating system accounts. | link | count: 012 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
App Service, Security Center, Service Fabric, SQL | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 1.3 | SWIFT_CSCF_v2021_1.3 | SWIFT CSCF v2021 1.3 | SWIFT Environment Protection | Virtualisation Platform Protection | n/a | Secure virtualisation platform and virtual machines (VM???s) hosting SWIFT related components to the same level as physical systems. | link | count: 001 Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d) |
Compute | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 1.4 | SWIFT_CSCF_v2021_1.4 | SWIFT CSCF v2021 1.4 | SWIFT Environment Protection | Restriction of Internet Access | n/a | Control/Protect Internet access from operator PCs and other within the secure zone | link | count: 001 Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea) |
Security Center | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 2.1 | SWIFT_CSCF_v2021_2.1 | SWIFT CSCF v2021 2.1 | Reduce Attack Surface and Vulnerabilities | Internal Data Flow Security | n/a | Ensure the confidentiality, integrity, and authenticity of application data flows between local SWIFT-related applications. | link | count: 014 App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure SQL Database should be running TLS version 1.2 or newer (32e6bbec-16b6-44c2-be37-c5b672d103cf), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), SQL Managed Instance should have the minimal TLS version of 1.2 (a8793640-60f7-487c-b5c3-1d37215905c4), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Automation, Guest Configuration, Kubernetes, Service Fabric, SQL | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 2.2 | SWIFT_CSCF_v2021_2.2 | SWIFT CSCF v2021 2.2 | Reduce Attack Surface and Vulnerabilities | Security Updates | n/a | Minimise the occurrence of known technical vulnerabilities on operator PCs and within the local SWIFT infrastructure by ensuring vendor support, applying mandatory software updates, and applying timely security updates aligned to the assessed risk. | link | count: 003 Audit Windows VMs with a pending reboot (4221adbc-5c0f-474f-88b7-037a99e6114c), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60) |
Guest Configuration, Security Center | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 2.3 | SWIFT_CSCF_v2021_2.3 | SWIFT CSCF v2021 2.3 | Reduce Attack Surface and Vulnerabilities | System Hardening | n/a | Reduce the cyber attack surface of SWIFT-related components by performing system hardening. | link | count: 005 Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that contain certificates expiring within the specified number of days (1417908b-4bff-46ee-a2a6-4acc899320ab), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
Guest Configuration, Security Center, VM Image Builder | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 2.4A | SWIFT_CSCF_v2021_2.4A | SWIFT CSCF v2021 2.4A | Reduce Attack Surface and Vulnerabilities | Back-office Data Flow Security | n/a | Ensure the confidentiality, integrity, and mutual authenticity of data flows between local or remote SWIFT infrastructure components and the back office first hops they connect to. | link | count: 007 App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Automation, Cache, Guest Configuration | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 2.5A | SWIFT_CSCF_v2021_2.5A | SWIFT CSCF v2021 2.5A | Reduce Attack Surface and Vulnerabilities | External Transmission Data Protection | n/a | Protect the confidentiality of SWIFT-related data transmitted or stored outside of the secure zone as part of operational processes. | link | count: 012 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Long-term geo-redundant backup should be enabled for Azure SQL Databases (d38fc420-0735-4ef3-ac11-c806f651a570), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
App Service, Automation, Backup, Compute, Container Registry, Security Center, SQL, Storage | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 2.6 | SWIFT_CSCF_v2021_2.6 | SWIFT CSCF v2021 2.6 | Reduce Attack Surface and Vulnerabilities | Operator Session Confidentiality and Integrity | n/a | Protect the confidentiality and integrity of interactive operator sessions connecting to the local or the remote (operated by a service provider) SWIFT-related infrastructure or applications. | link | count: 008 App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure SQL Database should be running TLS version 1.2 or newer (32e6bbec-16b6-44c2-be37-c5b672d103cf), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), SQL Managed Instance should have the minimal TLS version of 1.2 (a8793640-60f7-487c-b5c3-1d37215905c4), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, SQL | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 2.7 | SWIFT_CSCF_v2021_2.7 | SWIFT CSCF v2021 2.7 | Reduce Attack Surface and Vulnerabilities | Vulnerability Scanning | n/a | Identify known vulnerabilities within the local SWIFT environment by implementing a regular vulnerability scanning process and act upon results. | link | count: 012 Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 3.1 | SWIFT_CSCF_v2021_3.1 | SWIFT CSCF v2021 3.1 | Physically Secure the Environment | Physical Security | n/a | Prevent unauthorised physical access to sensitive equipment, workplace environments, hosting sites, and storage. | link | count: 001 Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d) |
Compute | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 4.1 | SWIFT_CSCF_v2021_4.1 | SWIFT CSCF v2021 4.1 | Prevent Compromise of Credentials | Password Policy | n/a | Ensure passwords are sufficiently resistant against common password attacks by implementing and enforcing an effective password policy. | link | count: 007 Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2) |
Guest Configuration | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 4.2 | SWIFT_CSCF_v2021_4.2 | SWIFT CSCF v2021 4.2 | Prevent Compromise of Credentials | Multi-factor Authentication | n/a | Prevent that a compromise of a single authentication factor allows access into SWIFT systems or applications, by implementing multi-factor authentication.. | link | count: 003 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52) |
Security Center | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 5.1 | SWIFT_CSCF_v2021_5.1 | SWIFT CSCF v2021 5.1 | Manage Identities and Segregate Privileges | Logical Access Control | n/a | Enforce the security principles of need-to-know access, least privilege, and segregation of duties for operator accounts. | link | count: 007 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Security Center | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 5.2 | SWIFT_CSCF_v2021_5.2 | SWIFT CSCF v2021 5.2 | Manage Identities and Segregate Privileges | Token Management | n/a | Ensure the proper management, tracking, and use of connected hardware authentication or personal tokens (if tokens are used). | link | count: 003 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c) |
App Service, Security Center | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 5.4 | SWIFT_CSCF_v2021_5.4 | SWIFT CSCF v2021 5.4 | Manage Identities and Segregate Privileges | Physical and Logical Password Storage | n/a | Protect physically and logically repository of recorded passwords. | link | count: 004 App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53) |
App Service, Guest Configuration, Key Vault | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 6.1 | SWIFT_CSCF_v2021_6.1 | SWIFT CSCF v2021 6.1 | Detect Anomalous Activity to Systems or Transaction Records | Malware Protection | n/a | Ensure that local SWIFT infrastructure is protected against malware. | link | count: 004 Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9) |
Compute, Security Center | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 6.2 | SWIFT_CSCF_v2021_6.2 | SWIFT CSCF v2021 6.2 | Detect Anomalous Activity to Systems or Transaction Records | Software Integrity | n/a | Ensure the software integrity of the SWIFT-related applications. | link | count: 003 App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9) |
App Service, Kubernetes | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 6.3 | SWIFT_CSCF_v2021_6.3 | SWIFT CSCF v2021 6.3 | Detect Anomalous Activity to Systems or Transaction Records | Database Integrity | n/a | Ensure the integrity of the database records for the SWIFT messaging interface and act upon results | link | count: 012 Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Cosmos DB should use a virtual network service endpoint (e0a2b1a3-f7f9-4569-807f-2a9edebdf4d9), Disconnections should be logged for PostgreSQL database servers. (eb6f77b9-bd53-4e35-a23d-7f65d5f0e446), Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12) |
Network, SQL | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 6.4 | SWIFT_CSCF_v2021_6.4 | SWIFT CSCF v2021 6.4 | Detect Anomalous Activity to Systems or Transaction Records | Logging and Monitoring | n/a | Record security events and detect anomalous actions and operations within the local SWIFT environment. | link | count: 034 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Activity log should be retained for at least one year (b02aacc0-b073-424e-8298-42b22829ee0a), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Azure Monitor solution 'Security and Audit' must be deployed (3e596b57-105f-48a6-be97-03e9243bad6e), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
Backup, Batch, Compute, Data Lake, Event Hub, Guest Configuration, Internet of Things, Key Vault, Logic Apps, Monitoring, Search, Security Center, Service Bus, SQL, Stream Analytics | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 6.5A | SWIFT_CSCF_v2021_6.5A | SWIFT CSCF v2021 6.5A | Detect Anomalous Activity to Systems or Transaction Records | Intrusion Detection | n/a | Detect and prevent anomalous network activity into and within the local or remote SWIFT environment. | link | count: 016 [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), App Service apps should not have CORS configured to allow every resource to access your apps (5744710e-cc2f-4ee8-8809-3b11e89f4bc9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Function apps should not have CORS configured to allow every resource to access your apps (0820b7b9-23aa-4725-a1ce-ae4558f718e5), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb) |
App Service, Cache, Kubernetes, Monitoring, Network, Security Center | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2021 | 7.1 | SWIFT_CSCF_v2021_7.1 | SWIFT CSCF v2021 7.1 | Plan for Incident Response and Information Sharing | Cyber Incident Response Planning | n/a | Ensure a consistent and effective approach for the management of cyber incidents. | link | count: 003 Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Security Center | [Preview]: SWIFT CSP-CSCF v2021 (abf84fac-f817-a70c-14b5-47eec767458a) | |
| SWIFT_CSCF_v2022 | 1.1 | SWIFT_CSCF_v2022_1.1 | SWIFT CSCF v2022 1.1 | 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | Ensure the protection of the user's local SWIFT infrastructure from potentially compromised elements of the general IT environment and external environment. | Shared | n/a | A separated secure zone safeguards the user's SWIFT infrastructure from compromises and attacks on the broader enterprise and external environments. | link | count: 022 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Allowlist rules in your adaptive application control policy should be updated (123a3936-f020-408a-ba0c-47873faf1534), App Service apps should use a virtual network service endpoint (2d21331d-a4c2-4def-a9ad-ee4e1e023beb), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Check for privacy and security compliance before establishing internal connections (ee4bbbbb-2e52-9adb-4e3a-e641f7ac68ab), Ensure external providers consistently meet interests of the customers (3eabed6d-1912-2d3c-858b-f438d08d0412), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Key Vault should use a virtual network service endpoint (ea4d6841-2173-4317-9747-ff522a45120f), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage Accounts should use a virtual network service endpoint (60d21c4f-21a3-4d94-85f4-b924e6aeeda4), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
Key Vault, Monitoring, Network, Regulatory Compliance, Security Center, Storage, VM Image Builder | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 1.2 | SWIFT_CSCF_v2022_1.2 | SWIFT CSCF v2022 1.2 | 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | Restrict and control the allocation and usage of administrator-level operating system accounts. | Shared | n/a | Access to administrator-level operating system accounts is restricted to the maximum extent possible. Usage is controlled, monitored, and only permitted for relevant activities such as software installation and configuration, maintenance, and emergency activities. At all other times, an account with the least privilege access is used. | link | count: 022 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Define and enforce conditions for shared and group accounts (f7eb1d0b-6d4f-2d59-1591-7563e11a9313), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Develop and establish a system security plan (b2ea1058-8998-3dd1-84f1-82132ad482fd), Develop information security policies and procedures (af227964-5b8b-22a2-9364-06d2cb9d6d7c), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Establish a privacy program (39eb03c1-97cc-11ab-0960-6209ed2869f7), Establish security requirements for the manufacturing of connected devices (afbecd30-37ee-a27b-8e09-6ac49951a0ee), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Implement security engineering principles of information systems (df2e9507-169b-4114-3a52-877561ee3198), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Monitor privileged role assignment (ed87d27a-9abf-7c71-714c-61d881889da4), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b), Use privileged identity management (e714b481-8fac-64a2-14a9-6f079b2501a4) |
Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 1.3 | SWIFT_CSCF_v2022_1.3 | SWIFT CSCF v2022 1.3 | 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | Secure the virtualisation platform and virtual machines (VMs) that host SWIFT-related components to the same level as physical systems. | Shared | n/a | Secure the virtualisation platform, virtualised machines, and the supporting virtual infrastructure (such as firewalls) to the same level as physical systems. | link | count: 002 Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409) |
Compute, Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 1.4 | SWIFT_CSCF_v2022_1.4 | SWIFT CSCF v2022 1.4 | 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | Control/Protect Internet access from operator PCs and systems within the secure zone. | Shared | n/a | All general-purpose and dedicated operator PCs, as well as systems within the secure zone, have controlled direct internet access in line with business. | link | count: 011 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d) |
Network, Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 1.5A | SWIFT_CSCF_v2022_1.5A | SWIFT CSCF v2022 1.5A | 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | Ensure the protection of the customer’s connectivity infrastructure from external environment and potentially compromised elements of the general IT environment. | Shared | n/a | A separated secure zone safeguards the customer's infrastructure used for external connectivity from external environments and compromises or attacks on the broader enterprise environment. | link | count: 026 [Preview]: All Internet traffic should be routed via your deployed Azure Firewall (fc5e4038-4584-4632-8c85-c0448d374b2c), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should use a virtual network service endpoint (2d21331d-a4c2-4def-a9ad-ee4e1e023beb), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Employ restrictions on external system interconnections (80029bc5-834f-3a9c-a2d8-acbc1aab4e9f), Establish firewall and router configuration standards (398fdbd8-56fd-274d-35c6-fa2d3b2755a1), Establish network segmentation for card holder data environment (f476f3b0-4152-526e-a209-44e5f8c968d7), Identify and manage downstream information exchanges (c7fddb0e-3f44-8635-2b35-dc6b8e740b7c), Implement managed interface for each external service (b262e1dd-08e9-41d4-963a-258909ad794b), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Key Vault should use a virtual network service endpoint (ea4d6841-2173-4317-9747-ff522a45120f), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage Accounts should use a virtual network service endpoint (60d21c4f-21a3-4d94-85f4-b924e6aeeda4), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
Key Vault, Monitoring, Network, Regulatory Compliance, Security Center, Storage, VM Image Builder | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 10.1 | SWIFT_CSCF_v2022_10.1 | SWIFT CSCF v2022 10.1 | 10. Be Ready in case of Major Disaster | Business continuity is ensured through a documented plan communicated to the potentially affected parties (service bureau and customers). | Shared | n/a | Business continuity is ensured through a documented plan communicated to the potentially affected parties (service bureau and customers). | link | count: 005 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928), Resume all mission and business functions (91a54089-2d69-0f56-62dc-b6371a1671c0) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 11.1 | SWIFT_CSCF_v2022_11.1 | SWIFT CSCF v2022 11.1 | 11. Monitor in case of Major Disaster | Ensure a consistent and effective approach for the event monitoring and escalation. | Shared | n/a | Ensure a consistent and effective approach for the event monitoring and escalation. | link | count: 005 Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 11.2 | SWIFT_CSCF_v2022_11.2 | SWIFT CSCF v2022 11.2 | 11. Monitor in case of Major Disaster | Ensure a consistent and effective approach for the management of incidents (Problem Management). | Shared | n/a | Ensure a consistent and effective approach for the management of incidents (Problem Management). | link | count: 020 Assess information security events (37b0045b-3887-367b-8b4d-b9a6fa911bb9), Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Develop security safeguards (423f6d9c-0c73-9cc6-64f4-b52242490368), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Incorporate simulated events into incident response training (1fdeb7c4-4c93-8271-a135-17ebe85f1cc7), Maintain data breach records (0fd1ca29-677b-2f12-1879-639716459160), Maintain incident response plan (37546841-8ea1-5be0-214d-8ac599588332), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Protect incident response plan (2401b496-7f23-79b2-9f80-89bb5abf3d4a), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 11.4 | SWIFT_CSCF_v2022_11.4 | SWIFT CSCF v2022 11.4 | 11. Monitor in case of Major Disaster | Ensure an adequate escalation of operational malfunctions in case of customer impact. | Shared | n/a | Ensure an adequate escalation of operational malfunctions in case of customer impact. | link | count: 014 Automate process to document implemented changes (43ac3ccb-4ef6-7d63-9a3f-6848485ba4e8), Automate process to highlight unreviewed change proposals (92b49e92-570f-1765-804a-378e6c592e28), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Establish relationship between incident response capability and external providers (b470a37a-7a47-3792-34dd-7a793140702e), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 11.5 | SWIFT_CSCF_v2022_11.5 | SWIFT CSCF v2022 11.5 | 11. Monitor in case of Major Disaster | Effective support is offered to customers in case they face problems during their business hours. | Shared | n/a | Effective support is offered to customers in case they face problems during their business hours. | link | count: 010 Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Enable network protection (8c255136-994b-9616-79f5-ae87810e0dcf), Eradicate contaminated information (54a9c072-4a93-2a03-6a43-a060d30383d7), Establish relationship between incident response capability and external providers (b470a37a-7a47-3792-34dd-7a793140702e), Execute actions in response to information spills (ba78efc6-795c-64f4-7a02-91effbd34af9), Identify incident response personnel (037c0089-6606-2dab-49ad-437005b5035f), Implement incident handling (433de59e-7a53-a766-02c2-f80f8421469a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), View and investigate restricted users (98145a9b-428a-7e81-9d14-ebb154a24f93) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 12.1 | SWIFT_CSCF_v2022_12.1 | SWIFT CSCF v2022 12.1 | 12. Ensure Knowledge is Available | Ensure quality of service to customers through SWIFT certified employees. | Shared | n/a | Ensure quality of service to customers through SWIFT certified employees. | link | count: 003 Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.1 | SWIFT_CSCF_v2022_2.1 | SWIFT CSCF v2022 2.1 | 2. Reduce Attack Surface and Vulnerabilities | Ensure the confidentiality, integrity, and authenticity of application data flows between local SWIFT-related components. | Shared | n/a | Confidentiality, integrity, and authentication mechanisms are implemented to protect SWIFT-related component-to-component or system-to-system data flows. | link | count: 036 Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Define cryptographic use (c4ccd607-702b-8ae6-8eeb-fc3339cd4b42), Define organizational requirements for cryptographic key management (d661e9eb-4e15-5ba1-6f02-cdc467db0d6c), Determine assertion requirements (7a0ecd94-3699-5273-76a5-edb8499f655a), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Employ boundary protection to isolate information systems (311802f9-098d-0659-245a-94c5d47c0182), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Enforce random unique session identifiers (c7d57a6a-7cc2-66c0-299f-83bf90558f5d), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish a data leakage management procedure (3c9aa856-6b86-35dc-83f4-bc72cec74dea), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Information flow control using security policy filters (13ef3484-3a51-785a-9c96-500f21f84edd), Isolate SecurID systems, Security Incident Management systems (dd6d00a8-701a-5935-a22b-c7b9c0c698b2), Issue public key certificates (97d91b33-7050-237b-3e23-a77d57d84e13), Maintain availability of information (3ad7f0bc-3d03-0585-4d24-529779bb02c2), Manage symmetric cryptographic keys (9c276cf3-596f-581a-7fbd-f5e46edaa0f4), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Produce, control and distribute asymmetric cryptographic keys (de077e7e-0cc8-65a6-6e08-9ab46c827b05), Produce, control and distribute symmetric cryptographic keys (16c54e01-9e65-7524-7c33-beda48a75779), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Restrict access to private keys (8d140e8b-76c7-77de-1d46-ed1b2e112444), Secure the interface to external systems (ff1efad2-6b09-54cc-01bf-d386c4d558a8), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
Automation, Guest Configuration, Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.11A | SWIFT_CSCF_v2022_2.11A | SWIFT CSCF v2022 2.11A | 2. Reduce Attack Surface and Vulnerabilities | Restrict transaction activity to validated and approved business counterparties. | Shared | n/a | Implement RMA controls to restrict transaction activity with effective business counterparties. | link | count: 010 Authorize access to security functions and information (aeed863a-0f56-429f-945d-8bb66bd06841), Authorize and manage access (50e9324a-7410-0539-0662-2c1e775538b7), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Enforce logical access (10c4210b-3ec9-9603-050d-77e4d26c7ebb), Enforce mandatory and discretionary access control policies (b1666a13-8f67-9c47-155e-69e027ff6823), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Review user groups and applications with access to sensitive data (eb1c944e-0e94-647b-9b7e-fdb8d2af0838), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.2 | SWIFT_CSCF_v2022_2.2 | SWIFT CSCF v2022 2.2 | 2. Reduce Attack Surface and Vulnerabilities | Minimise the occurrence of known technical vulnerabilities on operator PCs and within the local SWIFT infrastructure by ensuring vendor support, applying mandatory software updates, and applying timely security updates aligned to the assessed risk. | Shared | n/a | All hardware and software inside the secure zone and on operator PCs are within the support life cycle of the vendor, have been upgraded with mandatory software updates, and have had security updates promptly applied. | link | count: 011 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Windows VMs with a pending reboot (4221adbc-5c0f-474f-88b7-037a99e6114c), Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Disseminate security alerts to personnel (9c93ef57-7000-63fb-9b74-88f2e17ca5d2), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Use automated mechanisms for security alerts (b8689b2e-4308-a58b-a0b4-6f3343a000df) |
Guest Configuration, Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.3 | SWIFT_CSCF_v2022_2.3 | SWIFT CSCF v2022 2.3 | 2. Reduce Attack Surface and Vulnerabilities | Reduce the cyber-attack surface of SWIFT-related components by performing system hardening. | Shared | n/a | Security hardening is conducted and maintained on all in-scope components. | link | count: 025 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Windows machines that contain certificates expiring within the specified number of days (1417908b-4bff-46ee-a2a6-4acc899320ab), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Automate proposed documented changes (5c40f27b-6791-18c5-3f85-7b863bd99c11), Conduct a security impact analysis (203101f5-99a3-1491-1b56-acccd9b66a9e), Configure actions for noncompliant devices (b53aa659-513e-032c-52e6-1ce0ba46582f), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Develop and maintain a vulnerability management standard (055da733-55c6-9e10-8194-c40731057ec4), Develop and maintain baseline configurations (2f20840e-7925-221c-725d-757442753e7c), Enforce security configuration settings (058e9719-1ff9-3653-4230-23f76b6492e0), Establish a configuration control board (7380631c-5bf5-0e3a-4509-0873becd8a63), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Establish and document a configuration management plan (526ed90e-890f-69e7-0386-ba5c0f1f784f), Establish and document change control processes (bd4dc286-2f30-5b95-777c-681f3a7913d3), Establish configuration management requirements for developers (8747b573-8294-86a0-8914-49e9b06a5ace), Implement an automated configuration management tool (33832848-42ab-63f3-1a55-c0ad309d44cd), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Perform a privacy impact assessment (d18af1ac-0086-4762-6dc8-87cdded90e39), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Perform audit for configuration change control (1282809c-9001-176b-4a81-260a085f4872), Retain previous versions of baseline configs (5e4e9685-3818-5934-0071-2620c4fa2ca5), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa) |
Guest Configuration, Regulatory Compliance, Security Center, VM Image Builder | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.4 | SWIFT_CSCF_v2022_2.4 | SWIFT CSCF v2022 2.4 | 2. Reduce Attack Surface and Vulnerabilities | Ensure the confidentiality, integrity, and mutual authenticity of data flows between local or remote SWIFT infrastructure components and the back-office first hops they connect to. | Shared | n/a | Confidentiality, integrity, and authentication mechanisms (at system, transport or message level) are implemented to protect data flows between SWIFT infrastructure components and the back-office first hops they connect to. | link | count: 007 Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Notify users of system logon or access (fe2dff43-0a8c-95df-0432-cb1c794b17d0), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.4A | SWIFT_CSCF_v2022_2.4A | SWIFT CSCF v2022 2.4A | 2. Reduce Attack Surface and Vulnerabilities | Back-office Data Flow Security | Customer | n/a | Ensure the confidentiality, integrity, and mutual authenticity of data flows between local or remote SWIFT infrastructure components and the back office first hops they connect to. | link | count: 003 Authentication to Linux machines should require SSH keys (630c64f9-8b6b-4c64-b511-6544ceff6fd6), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
Automation, Guest Configuration | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.5 | SWIFT_CSCF_v2022_2.5 | SWIFT CSCF v2022 2.5 | 2. Reduce Attack Surface and Vulnerabilities | Protect the confidentiality of SWIFT-related data transmitted or stored outside of the secure zone as part of operational processes. | Shared | n/a | Sensitive SWIFT-related data that leaves the secure zone as a result of operating system/application back-ups, business transaction data replication for archiving or recovery purposes, or extraction for offline processing is protected when stored outside of a secure zone and is encrypted while in transit. | link | count: 007 Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Establish backup policies and procedures (4f23967c-a74b-9a09-9dc2-f566f61a87b9), Implement controls to secure all media (e435f7e3-0dd9-58c9-451f-9b44b96c0232), Manage the transportation of assets (4ac81669-00e2-9790-8648-71bc11bc91eb), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.5A | SWIFT_CSCF_v2022_2.5A | SWIFT CSCF v2022 2.5A | 2. Reduce Attack Surface and Vulnerabilities | External Transmission Data Protection | Customer | n/a | Protect the confidentiality of SWIFT-related data transmitted or stored outside of the secure zone as part of operational processes. | link | count: 007 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Geo-redundant storage should be enabled for Storage Accounts (bf045164-79ba-4215-8f95-f8048dc1780b), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Automation, Backup, Compute, Security Center, Storage | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.6 | SWIFT_CSCF_v2022_2.6 | SWIFT CSCF v2022 2.6 | 2. Reduce Attack Surface and Vulnerabilities | Protect the confidentiality and integrity of interactive operator sessions that connect to the local or remote (operated by a service provider) SWIFT infrastructure or service provider SWIFT-related applications | Shared | n/a | The confidentiality and integrity of interactive operator sessions that connect to service provider SWIFT-related applications or into the secure zone are safeguarded. | link | count: 017 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Authorize remote access (dad8a2e9-6f27-4fc2-8933-7e99fe700c9c), Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Document and implement wireless access guidelines (04b3e7f6-4841-888d-4799-cda19a0084f6), Document mobility training (83dfb2b8-678b-20a0-4c44-5c75ada023e6), Document remote access guidelines (3d492600-27ba-62cc-a1c3-66eb919f6a0d), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198), Implement controls to secure alternate work sites (cd36eeec-67e7-205a-4b64-dbfe3b4e3e4e), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Protect wireless access (d42a8f69-a193-6cbc-48b9-04a9e29961f1), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Reauthenticate or terminate a user session (d6653f89-7cb5-24a4-9d71-51581038231b), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112), Windows machines should meet requirements for 'Security Options - Interactive Logon' (d472d2c9-d6a3-4500-9f5f-b15f123005aa) |
Guest Configuration, Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.7 | SWIFT_CSCF_v2022_2.7 | SWIFT CSCF v2022 2.7 | 2. Reduce Attack Surface and Vulnerabilities | Identify known vulnerabilities within the local SWIFT environment by implementing a regular vulnerability scanning process and act upon results. | Shared | n/a | Secure zone (including dedicated operator PC) systems are scanned for vulnerabilities using an up-to-date, reputable scanning tool and results are considered for appropriate resolving actions. | link | count: 016 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f), Implement privileged access for executing vulnerability scanning activities (5b802722-71dd-a13d-2e7e-231e09589efb), Incorporate flaw remediation into configuration management (34aac8b2-488a-2b96-7280-5b9b481a317a), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Vulnerabilities in container security configurations should be remediated (e8cbc669-f12d-49eb-93e7-9273119e9933), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4) |
Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.8.5 | SWIFT_CSCF_v2022_2.8.5 | SWIFT CSCF v2022 2.8.5 | 2. Reduce Attack Surface and Vulnerabilities | Ensure a consistent and effective approach for the customers’ messaging monitoring. | Shared | n/a | Ensure a consistent and effective approach for the customers’ messaging monitoring. | link | count: 008 Assess risk in third party relationships (0d04cb93-a0f1-2f4b-4b1b-a72a1b510d08), Define and document government oversight (cbfa1bd0-714d-8d6f-0480-2ad6a53972df), Define requirements for supplying goods and services (2b2f3a72-9e68-3993-2b69-13dcdecf8958), Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Establish policies for supply chain risk management (9150259b-617b-596d-3bf5-5ca3fce20335), Require external service providers to comply with security requirements (4e45863d-9ea9-32b4-a204-2680bc6007a6), Review cloud service provider's compliance with policies and agreements (ffea18d9-13de-6505-37f3-4c1f88070ad7), Undergo independent security review (9b55929b-0101-47c0-a16e-d6ac5c7d21f8) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.8A | SWIFT_CSCF_v2022_2.8A | SWIFT CSCF v2022 2.8A | 2. Reduce Attack Surface and Vulnerabilities | Ensure the protection of the local SWIFT infrastructure from risks exposed by the outsourcing of critical activities. | Shared | n/a | Critical outsourced activities are protected, at a minimum, to the same standard of care as if operated within the originating organisation. | link | count: 011 Determine supplier contract obligations (67ada943-8539-083d-35d0-7af648974125), Document acquisition contract acceptance criteria (0803eaa7-671c-08a7-52fd-ac419f775e75), Document protection of personal data in acquisition contracts (f9ec3263-9562-1768-65a1-729793635a8d), Document protection of security information in acquisition contracts (d78f95ba-870a-a500-6104-8a5ce2534f19), Document requirements for the use of shared data in contracts (0ba211ef-0e85-2a45-17fc-401d1b3f8f85), Document security assurance requirements in acquisition contracts (13efd2d7-3980-a2a4-39d0-527180c009e8), Document security documentation requirements in acquisition contract (a465e8e9-0095-85cb-a05f-1dd4960d02af), Document security functional requirements in acquisition contracts (57927290-8000-59bf-3776-90c468ac5b4b), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Document the protection of cardholder data in third party contracts (77acc53d-0f67-6e06-7d04-5750653d4629) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 2.9 | SWIFT_CSCF_v2022_2.9 | SWIFT CSCF v2022 2.9 | 2. Reduce Attack Surface and Vulnerabilities | Ensure outbound transaction activity within the expected bounds of normal business. | Shared | n/a | Implement transaction detection, prevention, and validation controls to ensure outbound transaction activity within the expected bounds of normal business. | link | count: 007 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Control information flow (59bedbdc-0ba9-39b9-66bb-1d1c192384e6), Employ flow control mechanisms of encrypted information (79365f13-8ba4-1f6c-2ac4-aa39929f56d0), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 3.1 | SWIFT_CSCF_v2022_3.1 | SWIFT CSCF v2022 3.1 | 3. Physically Secure the Environment | Prevent unauthorised physical access to sensitive equipment, workplace environments, hosting sites, and storage. | Shared | n/a | Physical security controls are in place to protect access to sensitive equipment, hosting sites, and storage. | link | count: 008 Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Control physical access (55a7f9a0-6397-7589-05ef-5ed59a8149e7), Define a physical key management process (51e4b233-8ee3-8bdc-8f5f-f33bd0d229b7), Establish and maintain an asset inventory (27965e62-141f-8cca-426f-d09514ee5216), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Install an alarm system (aa0ddd99-43eb-302d-3f8f-42b499182960), Manage a secure surveillance camera system (f2222056-062d-1060-6dc2-0107a68c34b2), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2) |
Compute, Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 4.1 | SWIFT_CSCF_v2022_4.1 | SWIFT CSCF v2022 4.1 | 4. Prevent Compromise of Credentials | Ensure passwords are sufficiently resistant against common password attacks by implementing and enforcing an effective password policy. | Shared | n/a | All application and operating system accounts enforce passwords with appropriate parameters such as length, complexity, validity, and the number of failed login attempts. Similarly, personal tokens and mobile devices enforce passwords or a Personal Identification Number (PIN) with appropriate parameters. | link | count: 017 Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Manage authenticator lifetime and reuse (29363ae1-68cd-01ca-799d-92c9197c8404), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Guest Configuration, Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 4.2 | SWIFT_CSCF_v2022_4.2 | SWIFT CSCF v2022 4.2 | 4. Prevent Compromise of Credentials | Prevent that a compromise of a single authentication factor allows access into SWIFT-related systems or applications by implementing multi-factor authentication. | Shared | n/a | Multi-factor authentication is used for interactive user access to SWIFT-related applications and operating system accounts. | link | count: 005 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Adopt biometric authentication mechanisms (7d7a8356-5c34-9a95-3118-1424cfaf192a), Identify and authenticate network devices (ae5345d5-8dab-086a-7290-db43a3272198) |
Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 5.1 | SWIFT_CSCF_v2022_5.1 | SWIFT CSCF v2022 5.1 | 5. Manage Identities and Segregate Privileges | Enforce the security principles of need-to-know access, least privilege, and separation of duties for operator accounts. | Shared | n/a | Accounts are defined according to the security principles of need-to-know access, least privilege, and separation of duties. | link | count: 035 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), Assign account managers (4c6df5ff-4ef2-4f17-a516-0da9189c603b), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Audit Windows machines that contain certificates expiring within the specified number of days (1417908b-4bff-46ee-a2a6-4acc899320ab), Automate account management (2cc9c165-46bd-9762-5739-d2aae5ba90a1), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Define access authorizations to support separation of duties (341bc9f1-7489-07d9-4ec6-971573e1546a), Define information system account types (623b5f0a-8cbd-03a6-4892-201d27302f0c), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Design an access control model (03b6427e-6072-4226-4bd9-a410ab65317e), Disable authenticators upon termination (d9d48ffb-0d8c-0bd5-5f31-5a5826d19f10), Document access privileges (a08b18c7-9e0a-89f1-3696-d80902196719), Document separation of duties (e6f7b584-877a-0d69-77d4-ab8b923a9650), Employ least privilege access (1bc7fd64-291f-028e-4ed6-6e07886e163f), Establish conditions for role membership (97cfd944-6f0c-7db2-3796-8e890ef70819), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Manage system and admin accounts (34d38ea7-6754-1838-7031-d7fd07099821), Monitor access across the organization (48c816c5-2190-61fc-8806-25d6f3df162f), Monitor account activity (7b28ba4f-0a87-46ac-62e1-46b7c09202a8), Notify when account is not needed (8489ff90-8d29-61df-2d84-f9ab0f4c5e84), Protect audit information (0e696f5a-451f-5c15-5532-044136538491), Reassign or remove user privileges as needed (7805a343-275c-41be-9d62-7215b96212d8), Require approval for account creation (de770ba6-50dd-a316-2932-e0d972eaa734), Restrict access to privileged accounts (873895e8-0e3a-6492-42e9-22cd030e9fcd), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review user accounts (79f081c7-1634-01a1-708e-376197999289), Review user privileges (f96d2186-79df-262d-3f76-f371e3b71798), Revoke privileged roles as appropriate (32f22cfa-770b-057c-965b-450898425519), Separate duties of individuals (60ee1260-97f0-61bb-8155-5d8b75743655), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b) |
Guest Configuration, Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 5.2 | SWIFT_CSCF_v2022_5.2 | SWIFT CSCF v2022 5.2 | 5. Manage Identities and Segregate Privileges | Ensure the proper management, tracking, and use of connected and disconnected hardware authentication or personal tokens (when tokens are used). | Shared | n/a | Connected and disconnected hardware authentication or personal tokens are managed appropriately during their assignment, distribution, revocation, use, and storage. | link | count: 005 Distribute authenticators (098dcde7-016a-06c3-0985-0daaf3301d3a), Establish authenticator types and processes (921ae4c1-507f-5ddb-8a58-cfa9b5fd96f0), Establish procedures for initial authenticator distribution (35963d41-4263-0ef9-98d5-70eb058f9e3c), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Verify identity before distributing authenticators (72889284-15d2-90b2-4b39-a1e9541e1152) |
Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 5.3A | SWIFT_CSCF_v2022_5.3A | SWIFT CSCF v2022 5.3A | 5. Manage Identities and Segregate Privileges | To the extent permitted and practicable, ensure the trustworthiness of staff operating the local SWIFT environment by performing regular staff screening. | Shared | n/a | Staff operating the local SWIFT infrastructure are screened prior to initial appointment in that role and periodically thereafter. | link | count: 005 Clear personnel with access to classified information (c42f19c9-5d88-92da-0742-371a0ea03126), Ensure access agreements are signed or resigned timely (e7589f4e-1e8b-72c2-3692-1e14d7f3699f), Implement personnel screening (e0c480bf-0d68-a42d-4cbb-b60f851f8716), Protect special information (a315c657-4a00-8eba-15ac-44692ad24423), Rescreen individuals at a defined frequency (c6aeb800-0b19-944d-92dc-59b893722329) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 5.4 | SWIFT_CSCF_v2022_5.4 | SWIFT CSCF v2022 5.4 | 5. Manage Identities and Segregate Privileges | Protect physically and logically the repository of recorded passwords. | Shared | n/a | Recorded passwords are stored in a protected physical or logical location, with access restricted on a need-to-know basis. | link | count: 006 Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Document security strength requirements in acquisition contracts (ebb0ba89-6d8c-84a7-252b-7393881e43de), Establish a password policy (d8bbd80e-3bb1-5983-06c2-428526ec6a63), Implement parameters for memorized secret verifiers (3b30aa25-0f19-6c04-5ca4-bd3f880a763d), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93) |
Guest Configuration, Key Vault, Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 6.1 | SWIFT_CSCF_v2022_6.1 | SWIFT CSCF v2022 6.1 | 6. Detect Anomalous Activity to Systems or Transaction Records | Ensure that local SWIFT infrastructure is protected against malware and act upon results. | Shared | n/a | Anti-malware software from a reputable vendor is installed, kept up-to-date on all systems, and results are considered for appropriate resolving actions. | link | count: 031 Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Block untrusted and unsigned processes that run from USB (3d399cf3-8fc6-0efc-6ab0-1412f1198517), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Correlate Vulnerability scan information (e3905a3c-97e7-0b4f-15fb-465c0927536f), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Implement privileged access for executing vulnerability scanning activities (5b802722-71dd-a13d-2e7e-231e09589efb), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Antimalware for Azure should be configured to automatically update protection signatures (c43e4a30-77cb-48ab-a4dd-93f175c63b57), Microsoft IaaSAntimalware extension should be deployed on Windows servers (9b597639-28e4-48eb-b506-56b05d366257), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), Observe and report security weaknesses (ff136354-1c92-76dc-2dab-80fb7c6a9f1a), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Perform threat modeling (bf883b14-9c19-0f37-8825-5e39a8b66d5b), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review exploit protection events (a30bd8e9-7064-312a-0e1f-e1b485d59f6e), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review malware detections report weekly (4a6f5cbd-6c6b-006f-2bb1-091af1441bce), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Update antivirus definitions (ea9d7c95-2f10-8a4d-61d8-7469bd2e8d65), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Compute, Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 6.2 | SWIFT_CSCF_v2022_6.2 | SWIFT CSCF v2022 6.2 | 6. Detect Anomalous Activity to Systems or Transaction Records | Ensure the software integrity of the SWIFT-related components and act upon results. | Shared | n/a | A software integrity check is performed at regular intervals on messaging interface, communication interface, and other SWIFT-related components and results are considered for appropriate resolving actions. | link | count: 006 Configure workstations to check for digital certificates (26daf649-22d1-97e9-2a8a-01b182194d59), Employ automatic shutdown/restart when violations are detected (1b8a7ec3-11cc-a2d3-8cd0-eedf074424a4), Protect data in transit using encryption (b11697e8-9515-16f1-7a35-477d5c8a1344), Protect passwords with encryption (b2d3e5a2-97ab-5497-565a-71172a729d93), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 6.3 | SWIFT_CSCF_v2022_6.3 | SWIFT CSCF v2022 6.3 | 6. Detect Anomalous Activity to Systems or Transaction Records | Ensure the integrity of the database records for the SWIFT messaging interface or the customer connector and act upon results. | Shared | n/a | A database integrity check is performed at regular intervals on databases that record SWIFT transactions and results are considered for appropriate resolving actions. | link | count: 002 Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0), View and configure system diagnostic data (0123edae-3567-a05a-9b05-b53ebe9d3e7e) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 6.4 | SWIFT_CSCF_v2022_6.4 | SWIFT CSCF v2022 6.4 | 6. Detect Anomalous Activity to Systems or Transaction Records | Record security events and detect anomalous actions and operations within the local SWIFT environment. | Shared | n/a | Capabilities to detect anomalous activity are implemented, and a process or tool is in place to keep and review logs. | link | count: 052 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Activity log should be retained for at least one year (b02aacc0-b073-424e-8298-42b22829ee0a), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), All flow log resources should be in enabled state (27960feb-a23c-4577-8d36-ef8b5f35e0be), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit privileged functions (f26af0b1-65b6-689a-a03f-352ad2d00f98), Audit user account status (49c23d9b-02b0-0e42-4f94-e8cef1b8381b), Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' (1a4e592a-6a6e-44a5-9814-e36264ca96e7), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Monitor Logs for Application Insights should be linked to a Log Analytics workspace (d550e854-df1a-4de9-bf44-cd894b39a95e), Azure Monitor should collect activity logs from all regions (41388f1c-2db0-4c25-95b2-35d7f5ccbfa9), Azure Monitor solution 'Security and Audit' must be deployed (3e596b57-105f-48a6-be97-03e9243bad6e), Correlate audit records (10874318-0bf7-a41f-8463-03e395482080), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Determine auditable events (2f67e567-03db-9d1f-67dc-b6ffb91312f4), Establish requirements for audit review and reporting (b3c8cc83-20d3-3890-8bc8-5568777670f4), Flow logs should be configured for every network security group (c251913d-7d24-4958-af87-478ed3b9ba41), Integrate audit review, analysis, and reporting (f741c4e6-41eb-15a4-25a2-61ac7ca232f0), Integrate cloud app security with a siem (9fdde4a9-85fa-7850-6df4-ae9c4a2e56f9), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher flow logs should have traffic analytics enabled (2f080164-9f4d-497e-9db6-416dc9f7b48a), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Provide real-time alerts for audit event failures (0f4fa857-079d-9d3d-5c49-21f616189e03), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Review account provisioning logs (a830fe9e-08c9-a4fb-420c-6f6bf1702395), Review administrator assignments weekly (f27a298f-9443-014a-0d40-fef12adf0259), Review audit data (6625638f-3ba1-7404-5983-0ea33d719d34), Review cloud identity report overview (8aec4343-9153-9641-172c-defb201f56b3), Review controlled folder access events (f48b60c6-4b37-332f-7288-b6ea50d300eb), Review exploit protection events (a30bd8e9-7064-312a-0e1f-e1b485d59f6e), Review file and folder activity (ef718fe4-7ceb-9ddf-3198-0ee8f6fe9cba), Review role group changes weekly (70fe686f-1f91-7dab-11bf-bca4201e183b), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Storage account containing the container with activity logs must be encrypted with BYOK (fbb99e8e-e444-4da0-9ff1-75c92f5a85b2), The Log Analytics extension should be installed on Virtual Machine Scale Sets (efbde977-ba53-4479-b8e9-10b957924fbf), Virtual machines should have the Log Analytics extension installed (a70ca396-0a34-413a-88e1-b956c1e683be) |
App Service, Backup, Batch, Compute, Guest Configuration, Key Vault, Logic Apps, Monitoring, Network, Regulatory Compliance, Search, Security Center, Service Bus | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 6.5A | SWIFT_CSCF_v2022_6.5A | SWIFT CSCF v2022 6.5A | 6. Detect Anomalous Activity to Systems or Transaction Records | Detect and contain anomalous network activity into and within the local or remote SWIFT environment. | Shared | n/a | Intrusion detection is implemented to detect unauthorised network access and anomalous activity. | link | count: 018 [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), Alert personnel of information spillage (9622aaa9-5c49-40e2-5bf8-660b7cd23deb), Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Detect network services that have not been authorized or approved (86ecd378-a3a0-5d5b-207c-05e6aaca43fc), Develop an incident response plan (2b4e134f-1e4c-2bff-573e-082d85479b6e), Document security operations (2c6bee3a-2180-2430-440d-db3c7a849870), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156), Set automated notifications for new and trending cloud applications in your organization (af38215f-70c4-0cd6-40c2-c52d86690a45), Turn on sensors for endpoint security solution (5fc24b95-53f7-0ed1-2330-701b539b97fe) |
Monitoring, Network, Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 7.1 | SWIFT_CSCF_v2022_7.1 | SWIFT CSCF v2022 7.1 | 7. Plan for Incident Response and Information Sharing | Ensure a consistent and effective approach for the management of cyber incidents. | Shared | n/a | The user has a defined and tested cyber-incident response plan. | link | count: 008 Address information security issues (56fb5173-3865-5a5d-5fad-ae33e53e1577), Email notification for high severity alerts should be enabled (6e2593d9-add6-4083-9c9b-4b7d2188c899), Email notification to subscription owner for high severity alerts should be enabled (0b15565f-aa9e-48ba-8619-45960f2c314d), Identify classes of Incidents and Actions taken (23d1a569-2d1e-7f43-9e22-1f94115b7dd5), Incorporate simulated events into incident response training (1fdeb7c4-4c93-8271-a135-17ebe85f1cc7), Provide information spillage training (2d4d0e90-32d9-4deb-2166-a00d51ed57c0), Review and update incident response policies and procedures (b28c8687-4bbd-8614-0b96-cdffa1ac6d9c), Subscriptions should have a contact email address for security issues (4f4f78b8-e367-4b10-a341-d9a4ad5cf1c7) |
Regulatory Compliance, Security Center | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 7.2 | SWIFT_CSCF_v2022_7.2 | SWIFT CSCF v2022 7.2 | 7. Plan for Incident Response and Information Sharing | Ensure all staff are aware of and fulfil their security responsibilities by performing regular awareness activities, and maintain security knowledge of staff with privileged access. | Shared | n/a | Annual security awareness sessions are conducted for all staff members with access to SWIFT-related systems. All staff with privileged access maintain knowledge through specific training or learning activities when relevant or appropriate (at management’s discretion). | link | count: 011 Document security and privacy training activities (524e7136-9f6a-75ba-9089-501018151346), Provide periodic role-based security training (9ac8621d-9acd-55bf-9f99-ee4212cc3d85), Provide periodic security awareness training (516be556-1353-080d-2c2f-f46f000d5785), Provide privacy training (518eafdd-08e5-37a9-795b-15a8d798056d), Provide role-based practical exercises (d041726f-00e0-41ca-368c-b1a122066482), Provide role-based security training (4c385143-09fd-3a34-790c-a5fd9ec77ddc), Provide role-based training on suspicious activities (f6794ab8-9a7d-3b24-76ab-265d3646232b), Provide security awareness training for insider threats (9b8b05ec-3d21-215e-5d98-0f7cf0998202), Provide security training before providing access (2b05dca2-25ec-9335-495c-29155f785082), Provide security training for new users (1cb7bf71-841c-4741-438a-67c65fdd7194), Provide updated security awareness training (d136ae80-54dd-321c-98b4-17acf4af2169) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 7.3A | SWIFT_CSCF_v2022_7.3A | SWIFT CSCF v2022 7.3A | 7. Plan for Incident Response and Information Sharing | Validate the operational security configuration and identify security gaps by performing penetration testing. | Shared | n/a | Application, host, and network penetration testing is conducted towards the secure zone and the operator PCs or, when used, the jump server. | link | count: 002 Employ independent team for penetration testing (611ebc63-8600-50b6-a0e3-fef272457132), Require developers to build security architecture (f131c8c5-a54a-4888-1efc-158928924bc1) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 7.4A | SWIFT_CSCF_v2022_7.4A | SWIFT CSCF v2022 7.4A | 7. Plan for Incident Response and Information Sharing | Evaluate the risk and readiness of the organisation based on plausible cyber-attack scenarios. | Shared | n/a | Scenario-based risk assessments are conducted regularly to improve incident response preparedness and to increase the maturity of the organisation’s security programme. | link | count: 007 Conduct Risk Assessment (677e1da4-00c3-287a-563d-f4a1cf9b99a0), Conduct risk assessment and distribute its results (d7c1ecc3-2980-a079-1569-91aec8ac4a77), Conduct risk assessment and document its results (1dbd51c2-2bd1-5e26-75ba-ed075d8f0d68), Establish a risk management strategy (d36700f2-2f0d-7c2a-059c-bdadd1d79f70), Implement the risk management strategy (c6fe3856-4635-36b6-983c-070da12a953b), Perform a risk assessment (8c5d3d8d-5cba-0def-257c-5ab9ea9644dc), Review and update risk assessment policies and procedures (20012034-96f0-85c2-4a86-1ae1eb457802) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 8.1 | SWIFT_CSCF_v2022_8.1 | SWIFT CSCF v2022 8.1 | 8. Set and Monitor Performance | Ensure availability by formally setting and monitoring the objectives to be achieved | Shared | n/a | Ensure availability by formally setting and monitoring the objectives to be achieved | link | count: 008 Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Obtain legal opinion for monitoring system activities (d9af7f88-686a-5a8b-704b-eafdab278977), Perform a trend analysis on threats (50e81644-923d-33fc-6ebb-9733bc8d1a06), Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310), Plan for resumption of essential business functions (7ded6497-815d-6506-242b-e043e0273928), Provide monitoring information as needed (7fc1f0da-0050-19bb-3d75-81ae15940df6), Resume all mission and business functions (91a54089-2d69-0f56-62dc-b6371a1671c0) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 8.4 | SWIFT_CSCF_v2022_8.4 | SWIFT CSCF v2022 8.4 | 8. Set and Monitor Performance | Ensure availability, capacity, and quality of services to customers | Shared | n/a | Ensure availability, capacity, and quality of services to customers | link | count: 007 Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Create alternative actions for identified anomalies (cc2f7339-2fac-1ea9-9ca3-cd530fbb0da2), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Notify personnel of any failed security verification tests (18e9d748-73d4-0c96-55ab-b108bfbd5bc3), Perform security function verification at a defined frequency (f30edfad-4e1d-1eef-27ee-9292d6d89842), Plan for continuance of essential business functions (d9edcea6-6cb8-0266-a48c-2061fbac4310) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 8.5 | SWIFT_CSCF_v2022_8.5 | SWIFT CSCF v2022 8.5 | 8. Set and Monitor Performance | Ensure early availability of SWIFTNet releases and of the FIN standards for proper testing by the customer before going live. | Shared | n/a | Ensure early availability of SWIFTNet releases and of the FIN standards for proper testing by the customer before going live. | link | count: 011 Address coding vulnerabilities (318b2bd9-9c39-9f8b-46a7-048401f33476), Develop and document application security requirements (6de65dc4-8b4f-34b7-9290-eb137a2e2929), Document the information system environment in acquisition contracts (c148208b-1a6f-a4ac-7abc-23b1d41121b1), Establish a secure software development program (e750ca06-1824-464a-2cf3-d0fa754d1cb4), Perform vulnerability scans (3c5e0e1a-216f-8f49-0a15-76ed0d8b8e1f), Remediate information system flaws (be38a620-000b-21cf-3cb3-ea151b704c3b), Require developers to document approved changes and potential impact (3a868d0c-538f-968b-0191-bddb44da5b75), Require developers to implement only approved changes (085467a6-9679-5c65-584a-f55acefd0d43), Require developers to manage change integrity (b33d61c1-7463-7025-0ec0-a47585b59147), Require developers to produce evidence of security assessment plan execution (f8a63511-66f1-503f-196d-d6217ee0823a), Verify software, firmware and information integrity (db28735f-518f-870e-15b4-49623cbe3aa0) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 9.1 | SWIFT_CSCF_v2022_9.1 | SWIFT CSCF v2022 9.1 | 9. Ensure Availability through Resilience | Providers must ensure that the service remains available for customers in the event of a local disturbance or malfunction. | Shared | n/a | Providers must ensure that the service remains available for customers in the event of a local disturbance or malfunction. | link | count: 008 Conduct incident response testing (3545c827-26ee-282d-4629-23952a12008b), Coordinate contingency plans with related plans (c5784049-959f-6067-420c-f4cefae93076), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Develop contingency planning policies and procedures (75b42dcf-7840-1271-260b-852273d7906e), Distribute policies and procedures (eff6e4a5-3efe-94dd-2ed1-25d56a019a82), Establish an information security program (84245967-7882-54f6-2d34-85059f725b47), Provide contingency training (de936662-13dc-204c-75ec-1af80f994088), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 9.2 | SWIFT_CSCF_v2022_9.2 | SWIFT CSCF v2022 9.2 | 9. Ensure Availability through Resilience | Providers must ensure that the service remains available for customers in the event of a site disaster. | Shared | n/a | Providers must ensure that the service remains available for customers in the event of a site disaster. | link | count: 013 Conduct backup of information system documentation (b269a749-705e-8bff-055a-147744675cdf), Create separate alternate and primary storage sites (81b6267b-97a7-9aa5-51ee-d2584a160424), Ensure alternate storage site safeguards are equivalent to primary site (178c8b7e-1b6e-4289-44dd-2f1526b678a1), Establish alternate storage site that facilitates recovery operations (245fe58b-96f8-9f1e-48c5-7f49903f66fd), Establish alternate storage site to store and retrieve backup information (0a412110-3874-9f22-187a-c7a81c8a6704), Establish an alternate processing site (af5ff768-a34b-720e-1224-e6b3214f3ba6), Establish requirements for internet service providers (5f2e834d-7e40-a4d5-a216-e49b16955ccf), Identify and mitigate potential issues at alternate storage site (13939f8c-4cd5-a6db-9af4-9dfec35e3722), Prepare alternate processing site for use as operational site (0f31d98d-5ce2-705b-4aa5-b4f6705110dd), Recover and reconstitute resources after any disruption (f33c3238-11d2-508c-877c-4262ec1132e1), Restore resources to operational state (f801d58e-5659-9a4a-6e8d-02c9334732e5), Separately store backup information (fc26e2fd-3149-74b4-5988-d64bb90f8ef7), Transfer backup information to an alternate storage site (7bdb79ea-16b8-453e-4ca4-ad5b16012414) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 9.3 | SWIFT_CSCF_v2022_9.3 | SWIFT CSCF v2022 9.3 | 9. Ensure Availability through Resilience | Service bureaux must ensure that the service remains available for their customers in the event of a disturbance, a hazard, or an incident. | Shared | n/a | Service bureaux must ensure that the service remains available for their customers in the event of a disturbance, a hazard, or an incident. | link | count: 007 Develop and document a business continuity and disaster recovery plan (bd6cbcba-4a2d-507c-53e3-296b5c238a8e), Develop contingency plan (aa305b4d-8c84-1754-0c74-dec004e66be0), Employ automatic emergency lighting (aa892c0d-2c40-200c-0dd8-eac8c4748ede), Implement a penetration testing methodology (c2eabc28-1e5c-78a2-a712-7cc176c44c07), Implement physical security for offices, working areas, and secure areas (05ec66a2-137c-14b8-8e75-3d7a2bef07f8), Review and update physical and environmental policies and procedures (91cf132e-0c9f-37a8-a523-dc6a92cd2fb2), Run simulation attacks (a8f9c283-9a66-3eb3-9e10-bdba95b85884) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| SWIFT_CSCF_v2022 | 9.4 | SWIFT_CSCF_v2022_9.4 | SWIFT CSCF v2022 9.4 | 9. Ensure Availability through Resilience | Providers' availability and quality of service is ensured through usage of the recommended SWIFT connectivity packs and the appropriate line bandwidth | Shared | n/a | Providers' availability and quality of service is ensured through usage of the recommended SWIFT connectivity packs and the appropriate line bandwidth | link | count: 005 Authorize, monitor, and control voip (e4e1f896-8a93-1151-43c7-0ad23b081ee2), Conduct capacity planning (33602e78-35e3-4f06-17fb-13dd887448e4), Implement system boundary protection (01ae60e2-38bb-0a32-7b20-d3a091423409), Manage gateways (63f63e71-6c3f-9add-4c43-64de23e554a7), Route traffic through managed network access points (bab9ef1d-a16d-421a-822d-3fa94e808156) |
Regulatory Compliance | SWIFT CSP-CSCF v2022 (7bc7cd6c-4114-ff31-3cac-59be3157596d) |
| U.03 - Business Continuity services | U.03 - Business Continuity services | 404 not found | n/a | n/a | count: 003 Geo-redundant backup should be enabled for Azure Database for MariaDB (0ec47710-77ff-4a3d-9181-6aa50af424d0), Geo-redundant backup should be enabled for Azure Database for MySQL (82339799-d096-41ae-8538-b108becf0970), Geo-redundant backup should be enabled for Azure Database for PostgreSQL (48af4db5-9b8b-401c-8e74-076be876a430) |
SQL | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.03.1 - Redundancy | U.03.1 - Redundancy | 404 not found | n/a | n/a | count: 002 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d) |
Backup, Compute | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.03.2 - Continuity requirements | U.03.2 - Continuity requirements | 404 not found | n/a | n/a | count: 002 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d) |
Backup, Compute | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.04.1 - Restore function | U.04.1 - Restore function | 404 not found | n/a | n/a | count: 003 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Compute, Key Vault | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.04.2 - Restore function | U.04.2 - Restore function | 404 not found | n/a | n/a | count: 003 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Compute, Key Vault | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.04.3 - Tested | U.04.3 - Tested | 404 not found | n/a | n/a | count: 003 Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Key vaults should have deletion protection enabled (0b60c0b2-2dc2-4e1c-b5c9-abbed971de53), Key vaults should have soft delete enabled (1e66c121-a66a-4b1f-9b83-0fd99bf0fc2d) |
Compute, Key Vault | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.05.1 - Cryptographic measures | U.05.1 - Cryptographic measures | 404 not found | n/a | n/a | count: 018 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Azure Batch pools should have disk encryption enabled (1760f9d4-7206-436e-a28f-d9f3a5c8a227), Azure Edge Hardware Center devices should have double encryption support enabled (08a6b96f-576e-47a2-8511-119a212d344d), Azure Front Door Standard and Premium should be running minimum TLS version of 1.2 (679da822-78a7-4eff-8fff-a899454a9970), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Azure SQL Database should be running TLS version 1.2 or newer (32e6bbec-16b6-44c2-be37-c5b672d103cf), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Azure Edge Hardware Center, Batch, Cache, CDN, Guest Configuration, HDInsight, Kubernetes, Security Center, SQL, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.05.2 - Cryptographic measures | U.05.2 - Cryptographic measures | 404 not found | n/a | n/a | count: 052 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines (672fe5a1-2fcd-42d7-b85d-902b6e28c6ff), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines scale sets (a21f8c92-9e22-4f09-b759-50500d1d2dda), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines (1cb4d9c2-f88f-4069-bee0-dba239a57b09), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines scale sets (f655e522-adff-494d-95c2-52d4f6d56a42), [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) (47031206-ce96-41f8-861b-6a915f3de284), [Preview]: Secure Boot should be enabled on supported Windows virtual machines (97566dd7-78ae-4997-8b36-1c7bfe0d8121), [Preview]: vTPM should be enabled on supported virtual machines (1c30f9cd-b84c-49cc-aa2c-9288447cc3b3), Azure API for FHIR should use a customer-managed key to encrypt data at rest (051cba44-2429-45b9-9649-46cec11c7119), Azure Automation accounts should use customer-managed keys to encrypt data at rest (56a5ee18-2ae6-4810-86f7-18e39ce5629b), Azure Batch account should use customer-managed keys to encrypt data (99e9ccd8-3db9-4592-b0d1-14b1715a4d8a), Azure Batch pools should have disk encryption enabled (1760f9d4-7206-436e-a28f-d9f3a5c8a227), Azure Container Instance container group should use customer-managed key for encryption (0aa61e00-0a01-4a3c-9945-e93cffedf0e6), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password (86efb160-8de7-451d-bc08-5d475b0aadae), Azure Data Explorer encryption at rest should use a customer-managed key (81e74cea-30fd-40d5-802f-d72103c2aaaa), Azure data factories should be encrypted with a customer-managed key (4ec52d6d-beb7-40c4-9a9e-fe753254690e), Azure Edge Hardware Center devices should have double encryption support enabled (08a6b96f-576e-47a2-8511-119a212d344d), Azure HDInsight clusters should use customer-managed keys to encrypt data at rest (64d314f6-6062-4780-a861-c23e8951bee5), Azure HDInsight clusters should use encryption at host to encrypt data at rest (1fd32ebd-e4c3-4e13-a54a-d7422d4d95f6), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Stream Analytics jobs should use customer-managed keys to encrypt data (87ba29ef-1ab3-4d82-b763-87fcd4f531f7), Azure Synapse workspaces should use customer-managed keys to encrypt data at rest (f7d52b2d-e161-4dfa-a82b-55e564167385), Bot Service should be encrypted with a customer-managed key (51522a96-0869-4791-82f3-981000c2c67f), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Event Hub namespaces should use a customer-managed key for encryption (a1ad735a-e96f-45d2-a7b2-9a4932cab7ec), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Logic Apps Integration Service Environment should be encrypted with customer-managed keys (1fafeaf6-7927-4059-a50a-8eb2a7a6f2b5), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), OS and data disks should be encrypted with a customer-managed key (702dd420-7fcc-42c5-afe8-4026edd20fe0), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Service Bus Premium namespaces should use a customer-managed key for encryption (295fc8b1-dc9f-4f53-9c61-3f313ceab40a), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
API for FHIR, Automation, Azure Data Explorer, Azure Edge Hardware Center, Backup, Batch, Bot Service, Cognitive Services, Compute, Container Instance, Container Registry, Cosmos DB, Data Box, Data Factory, Event Hub, HDInsight, Internet of Things, Kubernetes, Logic Apps, Machine Learning, Monitoring, Security Center, Service Bus, SQL, Storage, Stream Analytics, Synapse | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.07.1 - Isolated | U.07.1 - Isolated | 404 not found | n/a | n/a | count: 056 [Preview]: Storage account public access should be disallowed (4fa4b6c0-31ca-4c0d-b10d-24b96f62a751), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), API Management services should use a virtual network (ef619a2c-cc4d-4d03-b2ba-8c94a834d85b), App Configuration should use private link (ca610c1d-041c-4332-9d88-7ed3094967c7), Authorized IP ranges should be defined on Kubernetes Services (0e246bcf-5f6f-4f87-bc6f-775d4712c7ea), Azure AI Services resources should restrict network access (037eea7a-bd0a-46c5-9a66-03aea78705d3), Azure API for FHIR should use private link (1ee56206-5dd1-42ab-b02d-8aae8b1634ce), Azure Cache for Redis should use private link (7803067c-7d34-46e3-8c79-0ca68fc4036d), Azure Cognitive Search service should use a SKU that supports private link (a049bf77-880b-470f-ba6d-9f21c530cf83), Azure Cognitive Search services should disable public network access (ee980b6d-0eca-4501-8d54-f6290fd512c3), Azure Cognitive Search services should use private link (0fda3595-9f2b-4592-8675-4231d6fa82fe), Azure Cosmos DB accounts should have firewall rules (862e97cf-49fc-4a5c-9de4-40d4e2e7c8eb), Azure Cosmos DB should disable public network access (797b37f7-06b8-444c-b1ad-fc62867f335a), Azure Data Factory should use private link (8b0323be-cc25-4b61-935d-002c3798c6ea), Azure Databricks Clusters should disable public IP (51c1490f-3319-459c-bbbc-7f391bbed753), Azure Databricks Workspaces should be in a virtual network (9c25c9e4-ee12-4882-afd2-11fb9d87893f), Azure Databricks Workspaces should disable public network access (0e7849de-b939-4c50-ab48-fc6b0f5eeba2), Azure Databricks Workspaces should use private link (258823f2-4595-4b52-b333-cc96192710d8), Azure Event Grid domains should use private link (9830b652-8523-49cc-b1b3-e17dce1127ca), Azure Event Grid topics should use private link (4b90e17e-8448-49db-875e-bd83fb6f804f), Azure File Sync should use private link (1d320205-c6a1-4ac6-873d-46224024e8e2), Azure Front Door profiles should use Premium tier that supports managed WAF rules and private link (dfc212af-17ea-423a-9dcb-91e2cb2caa6b), Azure Key Vault should have firewall enabled (55615ac9-af46-4a59-874e-391cc3dfb490), Azure Key Vaults should use private link (a6abeaec-4d90-4a02-805f-6b26c4d3fbe9), Azure Machine Learning Computes should be in a virtual network (7804b5c7-01dc-4723-969b-ae300cc07ff1), Azure Machine Learning Workspaces should disable public network access (438c38d2-3772-465a-a9cc-7a6666a275ce), Azure Machine Learning workspaces should use private link (45e05259-1eb5-4f70-9574-baf73e9d219b), Azure Service Bus namespaces should use private link (1c06e275-d63d-4540-b761-71f364c2111d), Azure SignalR Service should use private link (2393d2cf-a342-44cd-a2e2-fe0188fd1234), Azure SQL Managed Instances should disable public network access (9dfea752-dd46-4766-aed1-c355fa93fb91), Azure Synapse workspaces should use private link (72d11df1-dd8a-41f7-8925-b05b960ebafc), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Azure Web PubSub Service should use private link (eb907f70-7514-460d-92b3-a5ae93b4f917), Cognitive Services should use private link (cddd188c-4b82-4c48-a19d-ddf74ee66a01), Container registries should not allow unrestricted network access (d0793b48-0edc-4296-a390-4c75d1bdfd71), Container registries should use private link (e8eef0a8-67cf-4eb4-9386-14b0e78733d4), CosmosDB accounts should use private link (58440f8a-10c5-4151-bdce-dfbaad4a20b7), Disk access resources should use private link (f39f5f49-4abf-44de-8c70-0756997bfb51), Event Hub namespaces should use private link (b8564268-eb4a-4337-89be-a19db070c59d), Internet-facing virtual machines should be protected with network security groups (f6de0be7-9a8a-4b8a-b349-43cf02d22f7c), IoT Hub device provisioning service instances should use private link (df39c015-56a4-45de-b4a3-efe77bed320d), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Management ports should be closed on your virtual machines (22730e10-96f6-4aac-ad84-9383d35b5917), Non-internet-facing virtual machines should be protected with network security groups (bb91dfba-c30d-4263-9add-9c2384e659a6), Private endpoint connections on Azure SQL Database should be enabled (7698e800-9299-47a6-b3b6-5a0fee576eed), Public network access on Azure SQL Database should be disabled (1b8ca024-1d5c-4dec-8995-b1a932b41780), Public network access should be disabled for MariaDB servers (fdccbe47-f3e3-4213-ad5d-ea459b2fa077), Public network access should be disabled for MySQL servers (d9844e8a-1437-4aeb-a32c-0c992f056095), Public network access should be disabled for PostgreSQL servers (b52376f7-9612-48a1-81cd-1ffe4b61032c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Storage accounts should restrict network access using virtual network rules (2a1a9cdf-e04d-429a-8416-3bfb72a1b26f), Storage accounts should use private link (6edd7eda-6dd8-40f7-810d-67160c639cd9), Subnets should be associated with a Network Security Group (e71308d3-144b-4262-b144-efdc3cc90517), VM Image Builder templates should use private link (2154edb9-244f-4741-9970-660785bccdaa), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
API for FHIR, API Management, App Configuration, Azure Ai Services, Azure Databricks, Cache, CDN, Cognitive Services, Compute, Container Registry, Cosmos DB, Data Factory, Event Grid, Event Hub, Internet of Things, Key Vault, Machine Learning, Network, Search, Security Center, Service Bus, SignalR, SQL, Storage, Synapse, VM Image Builder, Web PubSub | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.07.3 - Management features | U.07.3 - Management features | 404 not found | n/a | n/a | count: 019 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), App Service Environment should have internal encryption enabled (fb74e86f-d351-4b8d-b034-93da7391c01f), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should prevent shared key access (8c6a50c6-9ffd-4ae7-986f-5fa6111f9a54), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), VPN gateways should use only Azure Active Directory (Azure AD) authentication for point-to-site users (21a6bc25-125e-4d13-b82d-2e19b7208ab7) |
App Service, Automation, Azure Ai Services, General, Network, Security Center, Service Fabric, SQL, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.09.3 - Detection, prevention and recovery | U.09.3 - Detection, prevention and recovery | 404 not found | n/a | n/a | count: 027 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Function apps should use latest 'HTTP Version' (e2c1c086-2d84-4019-bff3-c44ccd95113c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version (fb893a29-21bb-418c-a157-e99480ec364c), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66), Windows Defender Exploit Guard should be enabled on your machines (bed48b13-6647-468e-aa2f-1af1d3f4dd40) |
App Service, Guest Configuration, Kubernetes, Network, Security Center, SQL | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.10.2 - Users | U.10.2 - Users | 404 not found | n/a | n/a | count: 025 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Azure Machine Learning Computes should have local authentication methods disabled (e96a9a5f-07ca-471b-9bc5-6a0f33cbd68f), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Storage accounts should prevent shared key access (8c6a50c6-9ffd-4ae7-986f-5fa6111f9a54), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d), VPN gateways should use only Azure Active Directory (Azure AD) authentication for point-to-site users (21a6bc25-125e-4d13-b82d-2e19b7208ab7) |
App Service, Azure Ai Services, Compute, General, Guest Configuration, Machine Learning, Network, Security Center, Service Fabric, SQL, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.10.3 - Users | U.10.3 - Users | 404 not found | n/a | n/a | count: 026 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should have Client Certificates (Incoming client certificates) enabled (19dd1db6-f442-49cf-a838-b0786b4401ef), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Azure Machine Learning Computes should have local authentication methods disabled (e96a9a5f-07ca-471b-9bc5-6a0f33cbd68f), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), SQL servers with auditing to storage account destination should be configured with 90 days retention or higher (89099bee-89e0-4b26-a5f4-165451757743), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Storage accounts should prevent shared key access (8c6a50c6-9ffd-4ae7-986f-5fa6111f9a54), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d), VPN gateways should use only Azure Active Directory (Azure AD) authentication for point-to-site users (21a6bc25-125e-4d13-b82d-2e19b7208ab7) |
App Service, Azure Ai Services, Compute, General, Guest Configuration, Machine Learning, Network, Security Center, Service Fabric, SQL, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.10.5 - Competent | U.10.5 - Competent | 404 not found | n/a | n/a | count: 024 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), App Service apps should use managed identity (2b9ad585-36bc-4615-b300-fd4435808332), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit usage of custom RBAC roles (a451c1ef-c6ca-483d-87ed-f49761e3ffb5), Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Azure AI Services resources should have key access disabled (disable local authentication) (71ef260a-8f18-47b7-abcb-62d0673d94dc), Azure Machine Learning Computes should have local authentication methods disabled (e96a9a5f-07ca-471b-9bc5-6a0f33cbd68f), Azure Role-Based Access Control (RBAC) should be used on Kubernetes Services (ac4a19c2-fa67-49b4-8ae5-0b2e78c49457), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Function apps should use managed identity (0da106f2-4ca3-48e8-bc85-c638fe6aea8f), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Storage accounts should prevent shared key access (8c6a50c6-9ffd-4ae7-986f-5fa6111f9a54), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d), VPN gateways should use only Azure Active Directory (Azure AD) authentication for point-to-site users (21a6bc25-125e-4d13-b82d-2e19b7208ab7) |
App Service, Azure Ai Services, Compute, General, Guest Configuration, Machine Learning, Network, Security Center, Service Fabric, SQL, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.11.1 - Policy | U.11.1 - Policy | 404 not found | n/a | n/a | count: 019 Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Automation, Cache, Guest Configuration, HDInsight, Kubernetes, Security Center, Service Fabric, SQL, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.11.2 - Cryptographic measures | U.11.2 - Cryptographic measures | 404 not found | n/a | n/a | count: 019 Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), App Service apps should require FTPS only (4d24b6d4-5e53-4a4f-a7f4-618fa573ee4b), App Service apps should use the latest TLS version (f0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b), Audit Windows machines that do not store passwords using reversible encryption (da0f98fe-a24b-4ad5-af69-bd0400233661), Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Azure HDInsight clusters should use encryption in transit to encrypt communication between Azure HDInsight cluster nodes (d9da03a1-f3c3-412a-9709-947156872263), Enforce SSL connection should be enabled for MySQL database servers (e802a67a-daf5-4436-9ea6-f6d821dd0c5d), Enforce SSL connection should be enabled for PostgreSQL database servers (d158790f-bfb0-486c-8631-2dc6b4e8e6af), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Function apps should require FTPS only (399b2637-a50f-4f95-96f8-3a145476eb15), Function apps should use the latest TLS version (f9d614c5-c173-4d56-95a7-b4437057d193), Kubernetes clusters should be accessible only over HTTPS (1a5b4dca-0b6f-4cf5-907c-56316bc1bf3d), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Automation, Cache, Guest Configuration, HDInsight, Kubernetes, Security Center, Service Fabric, SQL, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.11.3 - Encrypted | U.11.3 - Encrypted | 404 not found | n/a | n/a | count: 052 [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data (2e94d99a-8a36-4563-bc77-810d8893b671), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines (672fe5a1-2fcd-42d7-b85d-902b6e28c6ff), [Preview]: Guest Attestation extension should be installed on supported Linux virtual machines scale sets (a21f8c92-9e22-4f09-b759-50500d1d2dda), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines (1cb4d9c2-f88f-4069-bee0-dba239a57b09), [Preview]: Guest Attestation extension should be installed on supported Windows virtual machines scale sets (f655e522-adff-494d-95c2-52d4f6d56a42), [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) (47031206-ce96-41f8-861b-6a915f3de284), [Preview]: Secure Boot should be enabled on supported Windows virtual machines (97566dd7-78ae-4997-8b36-1c7bfe0d8121), [Preview]: vTPM should be enabled on supported virtual machines (1c30f9cd-b84c-49cc-aa2c-9288447cc3b3), Azure API for FHIR should use a customer-managed key to encrypt data at rest (051cba44-2429-45b9-9649-46cec11c7119), Azure Automation accounts should use customer-managed keys to encrypt data at rest (56a5ee18-2ae6-4810-86f7-18e39ce5629b), Azure Batch account should use customer-managed keys to encrypt data (99e9ccd8-3db9-4592-b0d1-14b1715a4d8a), Azure Batch pools should have disk encryption enabled (1760f9d4-7206-436e-a28f-d9f3a5c8a227), Azure Container Instance container group should use customer-managed key for encryption (0aa61e00-0a01-4a3c-9945-e93cffedf0e6), Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest (1f905d99-2ab7-462c-a6b0-f709acca6c8f), Azure Data Box jobs should enable double encryption for data at rest on the device (c349d81b-9985-44ae-a8da-ff98d108ede8), Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password (86efb160-8de7-451d-bc08-5d475b0aadae), Azure Data Explorer encryption at rest should use a customer-managed key (81e74cea-30fd-40d5-802f-d72103c2aaaa), Azure data factories should be encrypted with a customer-managed key (4ec52d6d-beb7-40c4-9a9e-fe753254690e), Azure Edge Hardware Center devices should have double encryption support enabled (08a6b96f-576e-47a2-8511-119a212d344d), Azure HDInsight clusters should use customer-managed keys to encrypt data at rest (64d314f6-6062-4780-a861-c23e8951bee5), Azure HDInsight clusters should use encryption at host to encrypt data at rest (1fd32ebd-e4c3-4e13-a54a-d7422d4d95f6), Azure Machine Learning workspaces should be encrypted with a customer-managed key (ba769a63-b8cc-4b2d-abf6-ac33c7204be8), Azure Monitor Logs clusters should be created with infrastructure-encryption enabled (double encryption) (ea0dfaed-95fb-448c-934e-d6e713ce393d), Azure Monitor Logs clusters should be encrypted with customer-managed key (1f68a601-6e6d-4e42-babf-3f643a047ea2), Azure Stream Analytics jobs should use customer-managed keys to encrypt data (87ba29ef-1ab3-4d82-b763-87fcd4f531f7), Azure Synapse workspaces should use customer-managed keys to encrypt data at rest (f7d52b2d-e161-4dfa-a82b-55e564167385), Bot Service should be encrypted with a customer-managed key (51522a96-0869-4791-82f3-981000c2c67f), Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys (7d7be79c-23ba-4033-84dd-45e2a5ccdd67), Cognitive Services accounts should enable data encryption with a customer-managed key (67121cc7-ff39-4ab8-b7e3-95b84dab487d), Container registries should be encrypted with a customer-managed key (5b9159ae-1701-4a6f-9a7a-aa9c8ddd0580), Disk encryption should be enabled on Azure Data Explorer (f4b53539-8df9-40e4-86c6-6b607703bd4e), Double encryption should be enabled on Azure Data Explorer (ec068d99-e9c7-401f-8cef-5bdde4e6ccf1), Event Hub namespaces should use a customer-managed key for encryption (a1ad735a-e96f-45d2-a7b2-9a4932cab7ec), HPC Cache accounts should use customer-managed key for encryption (970f84d8-71b6-4091-9979-ace7e3fb6dbb), Infrastructure encryption should be enabled for Azure Database for MySQL servers (3a58212a-c829-4f13-9872-6371df2fd0b4), Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers (24fba194-95d6-48c0-aea7-f65bf859c598), Logic Apps Integration Service Environment should be encrypted with customer-managed keys (1fafeaf6-7927-4059-a50a-8eb2a7a6f2b5), Managed disks should be double encrypted with both platform-managed and customer-managed keys (ca91455f-eace-4f96-be59-e6e2c35b4816), MySQL servers should use customer-managed keys to encrypt data at rest (83cef61d-dbd1-4b20-a4fc-5fbc7da10833), OS and data disks should be encrypted with a customer-managed key (702dd420-7fcc-42c5-afe8-4026edd20fe0), PostgreSQL servers should use customer-managed keys to encrypt data at rest (18adea5e-f416-4d0f-8aa8-d24321e3e274), Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption (fa298e57-9444-42ba-bf04-86e8470e32c7), Service Bus Premium namespaces should use a customer-managed key for encryption (295fc8b1-dc9f-4f53-9c61-3f313ceab40a), SQL managed instances should use customer-managed keys to encrypt data at rest (ac01ad65-10e5-46df-bdd9-6b0cad13e1d2), SQL servers should use customer-managed keys to encrypt data at rest (0a370ff3-6cab-4e85-8995-295fd854c5b8), Storage account encryption scopes should use customer-managed keys to encrypt data at rest (b5ec538c-daa0-4006-8596-35468b9148e8), Storage accounts should have infrastructure encryption (4733ea7b-a883-42fe-8cac-97454c2a9e4a), Storage accounts should use customer-managed key for encryption (6fac406b-40ca-413b-bf8e-0bf964659c25), Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host (41425d9f-d1a5-499a-9932-f8ed8453932c), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines and virtual machine scale sets should have encryption at host enabled (fc4d8e41-e223-45ea-9bf5-eada37891d87), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
API for FHIR, Automation, Azure Data Explorer, Azure Edge Hardware Center, Backup, Batch, Bot Service, Cognitive Services, Compute, Container Instance, Container Registry, Cosmos DB, Data Box, Data Factory, Event Hub, HDInsight, Internet of Things, Kubernetes, Logic Apps, Machine Learning, Monitoring, Security Center, Service Bus, SQL, Storage, Stream Analytics, Synapse | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.12.1 - Network connections | U.12.1 - Network connections | 404 not found | n/a | n/a | count: 006 All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Network, Security Center, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.12.2 - Network connections | U.12.2 - Network connections | 404 not found | n/a | n/a | count: 006 All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Azure Web Application Firewall should be enabled for Azure Front Door entry-points (055aa869-bc98-4af8-bafc-23f1ab6ffe2c), IP Forwarding on your virtual machine should be disabled (bd352bd5-2853-4985-bf0d-73806b4a5744), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c), Web Application Firewall (WAF) should be enabled for Application Gateway (564feb30-bf6a-4854-b4bb-0d2d2d1e6c66) |
Network, Security Center, Storage | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.15.1 - Events logged | U.15.1 - Events logged | 404 not found | n/a | n/a | count: 043 [Preview]: Azure Arc enabled Kubernetes clusters should have Microsoft Defender for Cloud extension installed (8dfab9c4-fe7b-49ad-85e4-1e9be085358f), [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), [Preview]: Log Analytics extension should be installed on your Linux Azure Arc machines (842c54e8-c2f9-4d79-ae8d-38d8b8019373), [Preview]: Log Analytics extension should be installed on your Windows Azure Arc machines (d69b1763-b96d-40b8-a2d9-ca31e9fd0d3e), [Preview]: Network traffic data collection agent should be installed on Linux virtual machines (04c4380f-3fae-46e8-96c9-30193528f602), [Preview]: Network traffic data collection agent should be installed on Windows virtual machines (2f2ee1de-44aa-4762-b6bd-0893fc3f306d), App Service apps should have resource logs enabled (91a78b24-f231-4a8a-8da9-02c35b2b6510), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Auto provisioning of the Log Analytics agent should be enabled on your subscription (475aae12-b88a-4572-8b36-9b712b2b3a17), Azure Defender for App Service should be enabled (2913021d-f2fd-4f3d-b958-22354e2bdbcb), Azure Defender for Azure SQL Database servers should be enabled (7fe3b40f-802b-4cdd-8bd4-fd799c948cc2), Azure Defender for Key Vault should be enabled (0e6763cc-5078-4e64-889d-ff4d9a839047), Azure Defender for Resource Manager should be enabled (c3d20c29-b36d-48fe-808b-99a87530ad99), Azure Defender for servers should be enabled (4da35fc9-c9e7-4960-aec9-797fe7d9051d), Azure Defender for SQL servers on machines should be enabled (6581d072-105e-4418-827f-bd446d56421b), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Azure Front Door should have Resource logs enabled (8a04f872-51e9-4313-97fb-fc1c35430fd8), Azure Front Door Standard or Premium (Plus WAF) should have resource logs enabled (cd906338-3453-47ba-9334-2d654bf845af), Dependency agent should be enabled for listed virtual machine images (11ac78e3-31bc-4f0c-8434-37ab963cea07), Dependency agent should be enabled in virtual machine scale sets for listed virtual machine images (e2dd799a-a932-4e9d-ac17-d473bc3c6c10), Guest Configuration extension should be installed on your machines (ae89ebca-1c92-4898-ac2c-9f63decb045c), Log Analytics agent should be installed on your virtual machine for Azure Security Center monitoring (a4fe33eb-e377-4efb-ab31-0784311bc499), Log Analytics agent should be installed on your virtual machine scale sets for Azure Security Center monitoring (a3a6ea0c-e018-4933-9ef0-5aaa1501449b), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138), Microsoft Defender for Containers should be enabled (1c988dd6-ade4-430f-a608-2a3e5b0a6d38), Microsoft Defender for Storage should be enabled (640d2586-54d2-465f-877f-9ffc1d2109f4), Network Watcher should be enabled (b6e2945c-0b7b-40f5-9233-7a5323b5cdc6), Resource logs in Azure Data Lake Store should be enabled (057ef27e-665e-4328-8ea3-04b3122bd9fb), Resource logs in Azure Databricks Workspaces should be enabled (138ff14d-b687-4faa-a81c-898c91a87fa2), Resource logs in Azure Kubernetes Service should be enabled (245fc9df-fa96-4414-9a0b-3738c2f7341c), Resource logs in Azure Machine Learning Workspaces should be enabled (afe0c3be-ba3b-4544-ba52-0c99672a8ad6), Resource logs in Azure Stream Analytics should be enabled (f9be5368-9bf5-4b84-9e0a-7850da98bb46), Resource logs in Batch accounts should be enabled (428256e6-1fac-4f48-a757-df34c2b3336d), Resource logs in Data Lake Analytics should be enabled (c95c74d9-38fe-4f0d-af86-0c7d626a315c), Resource logs in Event Hub should be enabled (83a214f7-d01a-484b-91a9-ed54470c9a6a), Resource logs in IoT Hub should be enabled (383856f8-de7f-44a2-81fc-e5135b5c2aa4), Resource logs in Key Vault should be enabled (cf820ca0-f99e-4f3e-84fb-66e913812d21), Resource logs in Logic Apps should be enabled (34f95f76-5386-4de7-b824-0d8478470c9d), Resource logs in Search services should be enabled (b4330a05-a843-4bc8-bf9a-cacce50c67f4), Resource logs in Service Bus should be enabled (f8d36e2f-389b-4ee4-898d-21aeb69a0f45), Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity (d26f7642-7545-4e18-9b75-8c9bbdee3a9a) |
App Service, Azure Databricks, Batch, Data Lake, Event Hub, Internet of Things, Key Vault, Kubernetes, Logic Apps, Machine Learning, Monitoring, Network, Search, Security Center, Service Bus, SQL, Stream Analytics | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.15.3 - Events logged | U.15.3 - Events logged | 404 not found | n/a | n/a | count: 006 [Preview]: Log Analytics Extension should be enabled for listed virtual machine images (32133ab0-ee4b-4b44-98d6-042180979d50), Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Dependency agent should be enabled for listed virtual machine images (11ac78e3-31bc-4f0c-8434-37ab963cea07), Dependency agent should be enabled in virtual machine scale sets for listed virtual machine images (e2dd799a-a932-4e9d-ac17-d473bc3c6c10), Log Analytics extension should be enabled in virtual machine scale sets for listed virtual machine images (5c3bc7b8-a64c-4e08-a9cd-7ff0f31e1138) |
Monitoring, SQL | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| U.17.1 - Encrypted | U.17.1 - Encrypted | 404 not found | n/a | n/a | count: 005 A maximum of 3 owners should be designated for your subscription (4f11b553-d42e-4e3a-89be-32ca364cad4c), Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Azure Backup should be enabled for Virtual Machines (013e242c-8828-4970-87b3-ab247555486d), There should be more than one owner assigned to your subscription (09024ccc-0c5f-475e-9457-b7c0d9ed487b), Vulnerability assessment should be enabled on your Synapse workspaces (0049a6b3-a662-4f3e-8635-39cf44ace45a) |
Backup, Compute, Security Center, Synapse | NL BIO Cloud Theme (6ce73208-883e-490f-a2ac-44aac3b3687f) | |||||
| UK_NCSC_CSP | 1 | UK_NCSC_CSP_1 | UK NCSC CSP 1 | Data in transit protection | Data in transit protection | Shared | n/a | User data transiting networks should be adequately protected against tampering and eavesdropping. | link | count: 005 App Service apps should only be accessible over HTTPS (a4af4a39-4135-47fb-b175-47fbdf85311d), Function apps should only be accessible over HTTPS (6d555dd1-86f2-4f1c-8ed7-5abae7c6cbab), Only secure connections to your Azure Cache for Redis should be enabled (22bee202-a82f-4305-9a2a-6d7f44d4dedb), Secure transfer to storage accounts should be enabled (404c3081-a854-4457-ae30-26a93ef643f9), Windows machines should be configured to use secure communication protocols (5752e6d6-1206-46d8-8ab1-ecc2f71a8112) |
App Service, Cache, Guest Configuration, Storage | UK OFFICIAL and UK NHS (3937f550-eedd-4639-9c5e-294358be442e) |
| UK_NCSC_CSP | 10 | UK_NCSC_CSP_10 | UK NCSC CSP 10 | Identity and authentication | Identity and authentication | Shared | n/a | All access to service interfaces should be constrained to authenticated and authorised individuals. | link | count: 025 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities (3cf2ab00-13f1-4d0c-8971-2ac904541a7e), Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity (497dff13-db2a-4c0f-8603-28fa3b331ab6), An Azure Active Directory administrator should be provisioned for SQL servers (1f314764-cb73-4fc9-b863-8eca98ac36e9), Audit Linux machines that allow remote connections from accounts without passwords (ea53dbee-c6c9-4f0e-9f9e-de0039b78023), Audit Linux machines that do not have the passwd file permissions set to 0644 (e6955644-301c-44b5-a4c4-528577de6861), Audit Linux machines that have accounts without passwords (f6ec09a3-78bf-4f8f-99dc-6c77182d0f99), Audit VMs that do not use managed disks (06a78e20-9358-41c9-923c-fb736d382a4d), Audit Windows machines that allow re-use of the passwords after the specified number of unique passwords (5b054a0d-39e2-4d53-bea3-9734cad2c69b), Audit Windows machines that do not have the maximum password age set to specified number of days (4ceb8dc2-559c-478b-a15b-733fbf1e3738), Audit Windows machines that do not have the minimum password age set to specified number of days (237b38db-ca4d-4259-9e47-7882441ca2c0), Audit Windows machines that do not have the password complexity setting enabled (bf16e0bb-31e1-4646-8202-60a235cc7e74), Audit Windows machines that do not restrict the minimum password length to specified number of characters (a2d0e922-65d0-40c4-8f87-ea6da2d307a2), Blocked accounts with owner permissions on Azure resources should be removed (0cfea604-3201-4e14-88fc-fae4c427a6c5), Blocked accounts with read and write permissions on Azure resources should be removed (8d7e1fde-fe26-4b5f-8108-f8e432cbc2be), Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs (331e8ea8-378a-410f-a2e5-ae22f38bb0da), Deploy the Windows Guest Configuration extension to enable Guest Configuration assignments on Windows VMs (385f5831-96d4-41db-9a3c-cd3af78aaae6), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87), Service Fabric clusters should only use Azure Active Directory for client authentication (b54ed75b-3e1a-44ac-a333-05ba39b99ff0), Storage accounts should be migrated to new Azure Resource Manager resources (37e0d2fe-28a5-43d6-a273-67d37d1f5606), Virtual machines should be migrated to new Azure Resource Manager resources (1d84d5fb-01f6-4d12-ba4f-4a26081d403d) |
Compute, Guest Configuration, Security Center, Service Fabric, SQL, Storage | UK OFFICIAL and UK NHS (3937f550-eedd-4639-9c5e-294358be442e) |
| UK_NCSC_CSP | 11 | UK_NCSC_CSP_11 | UK NCSC CSP 11 | External interface protection | External interface protection | Shared | n/a | All external or less trusted interfaces of the service should be identified and appropriately defended. | link | count: 008 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Adaptive network hardening recommendations should be applied on internet facing virtual machines (08e6af2d-db70-460a-bfe9-d5bd474ba9d6), All network ports should be restricted on network security groups associated to your virtual machine (9daedab3-fb2d-461e-b861-71790eead4f6), App Service apps should have remote debugging turned off (cb510bfd-1cba-4d9f-a230-cb0976f4bb71), Endpoint protection solution should be installed on virtual machine scale sets (26a828e1-e88f-464e-bbb3-c134a282b9de), Function apps should have remote debugging turned off (0e60b895-3786-45da-8377-9c6b4b6ac5f9), Management ports of virtual machines should be protected with just-in-time network access control (b0f33259-77d7-4c9e-aac6-3aabcfae693c), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
App Service, Security Center, Storage | UK OFFICIAL and UK NHS (3937f550-eedd-4639-9c5e-294358be442e) |
| UK_NCSC_CSP | 13 | UK_NCSC_CSP_13 | UK NCSC CSP 13 | Audit information for users | Audit information for users | Shared | n/a | You should be provided with the audit records needed to monitor access to your service and the data held within it. The type of audit information available to you will have a direct impact on your ability to detect and respond to inappropriate or malicious activity within reasonable timescales. | link | count: 003 Audit diagnostic setting for selected resource types (7f89b1eb-583c-429a-8828-af049802c1d9), Auditing on SQL server should be enabled (a6fb4358-5bf4-4ad7-ba82-2cd2f41ce5e9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9) |
Monitoring, SQL | UK OFFICIAL and UK NHS (3937f550-eedd-4639-9c5e-294358be442e) |
| UK_NCSC_CSP | 2.3 | UK_NCSC_CSP_2.3 | UK NCSC CSP 2.3 | Asset protection and resilience | Data at rest protection | Shared | n/a | To ensure data is not available to unauthorised parties with physical access to infrastructure, user data held within the service should be protected regardless of the storage media on which it’s held. Without appropriate measures in place, data may be inadvertently disclosed on discarded, lost or stolen media. | link | count: 004 Automation account variables should be encrypted (3657f5a0-770e-44a3-b44e-9431ba1e9735), Service Fabric clusters should have the ClusterProtectionLevel property set to EncryptAndSign (617c02be-7f02-4efd-8836-3180d47b6c68), Transparent Data Encryption on SQL databases should be enabled (17k78e20-9358-41c9-923c-fb736d382a12), Virtual machines should encrypt temp disks, caches, and data flows between Compute and Storage resources (0961003e-5a0a-4549-abde-af6a37f2724d) |
Automation, Security Center, Service Fabric, SQL | UK OFFICIAL and UK NHS (3937f550-eedd-4639-9c5e-294358be442e) |
| UK_NCSC_CSP | 5.2 | UK_NCSC_CSP_5.2 | UK NCSC CSP 5.2 | Operational security | Vulnerability management | Shared | n/a | Service providers should have a management processes in place to identify, triage and mitigate vulnerabilities. Services which don’t, will quickly become vulnerable to attack using publicly known methods and tools. | link | count: 011 A vulnerability assessment solution should be enabled on your virtual machines (501541f7-f7e7-4cd6-868c-4190fdad3ac9), Azure Defender for SQL should be enabled for unprotected Azure SQL servers (abfb4388-5bf4-4ad7-ba82-2cd2f41ceae9), Azure Defender for SQL should be enabled for unprotected SQL Managed Instances (abfb7388-5bf4-4ad7-ba99-2cd2f41cebb9), Monitor missing Endpoint Protection in Azure Security Center (af6cd1bd-1635-48cb-bde7-5b15693900b9), SQL databases should have vulnerability findings resolved (feedbf84-6b99-488c-acc2-71c829aa5ffc), System updates on virtual machine scale sets should be installed (c3f317a7-a95c-4547-b7e7-11017ebdf2fe), System updates should be installed on your machines (86b3d65f-7626-441e-b690-81a8b71cff60), Vulnerabilities in security configuration on your machines should be remediated (e1e5fd5d-3e4c-4ce1-8661-7d1873ae6b15), Vulnerabilities in security configuration on your virtual machine scale sets should be remediated (3c735d8a-a4ba-4a3a-b7cf-db7754cf57f4), Vulnerability assessment should be enabled on SQL Managed Instance (1b7aa243-30e4-4c9e-bca8-d0d3022b634a), Vulnerability assessment should be enabled on your SQL servers (ef2a8f2a-b3d9-49cd-a8a8-9a3aaaf647d9) |
Security Center, SQL | UK OFFICIAL and UK NHS (3937f550-eedd-4639-9c5e-294358be442e) |
| UK_NCSC_CSP | 5.3 | UK_NCSC_CSP_5.3 | UK NCSC CSP 5.3 | Operational security | Protective Monitoring | Shared | n/a | A service which does not effectively monitor for attack, misuse and malfunction will be unlikely to detect attacks (both successful and unsuccessful). As a result, it will be unable to quickly respond to potential compromises of your environments and data. | link | count: 004 Adaptive application controls for defining safe applications should be enabled on your machines (47a6b606-51aa-4496-8bb7-64b11cf66adc), Audit virtual machines without disaster recovery configured (0015ea4d-51ff-4ce3-8d8c-f3f8f0179a56), Azure DDoS Protection should be enabled (a7aca53f-2ed4-4466-a25e-0b45ade68efd), Storage accounts should restrict network access (34c877ad-507e-4c82-993e-3452a6e0ad3c) |
Compute, Security Center, Storage | UK OFFICIAL and UK NHS (3937f550-eedd-4639-9c5e-294358be442e) |
| UK_NCSC_CSP | 9.1 | UK_NCSC_CSP_9.1 | UK NCSC CSP 9.1 | Secure user management | Authentication of users to management interfaces and support channels | Shared | n/a | In order to maintain a secure service, users need to be properly authenticated before being allowed to perform management activities, report faults or request changes to the service. | link | count: 006 Accounts with owner permissions on Azure resources should be MFA enabled (e3e008c3-56b9-4133-8fd7-d3347377402a), Accounts with read permissions on Azure resources should be MFA enabled (81b3ccb4-e6e8-4e4a-8d05-5df25cd29fd4), Accounts with write permissions on Azure resources should be MFA enabled (931e118d-50a1-4457-a5e4-78550e086c52), Guest accounts with owner permissions on Azure resources should be removed (339353f6-2387-4a45-abe4-7f529d121046), Guest accounts with read permissions on Azure resources should be removed (e9ac8f8e-ce22-4355-8f04-99b911d6be52), Guest accounts with write permissions on Azure resources should be removed (94e1c2ac-cbbe-4cac-a2b5-389c812dee87) |
Security Center | UK OFFICIAL and UK NHS (3937f550-eedd-4639-9c5e-294358be442e) |