compliance controls are associated with this Policy definition 'Audit privileged functions' (f26af0b1-65b6-689a-a03f-352ad2d00f98)
Control Domain |
Control |
Name |
MetadataId |
Category |
Title |
Owner |
Requirements |
Description |
Info |
Policy# |
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 |
10 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
4 |
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 |
5 |
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 |
5 |
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 |
6 |
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 |
10 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
20 |
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 |
10 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
20 |
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 |
10 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
5 |
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 |
8 |
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 |
5 |
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 |
20 |
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 |
10 |
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 |
6 |
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 |
34 |
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 |
15 |
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 |
10 |
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 |
6 |
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 |
34 |
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 |
15 |
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. |
|
25 |
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. |
|
16 |
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. |
|
19 |
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. |
|
17 |
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. |
|
12 |
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. |
|
8 |
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. |
|
7 |
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. |
|
9 |
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. |
|
13 |
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. |
|
11 |
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. |
|
9 |
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. |
|
13 |
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. |
|
21 |
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. |
|
18 |
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. |
|
18 |
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. |
|
21 |
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 |
53 |
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 |
29 |
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 |
33 |
|
mp.s.2 Protection of web services and applications |
mp.s.2 Protection of web services and applications |
404 not found |
|
|
|
n/a |
n/a |
|
102 |
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 |
31 |
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 |
6 |
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 |
7 |
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 |
10 |
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 |
6 |
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 |
34 |
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 |
15 |
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 |
10 |
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 |
6 |
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 |
34 |
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 |
15 |
|
op.acc.1 Identification |
op.acc.1 Identification |
404 not found |
|
|
|
n/a |
n/a |
|
66 |
|
op.acc.3 Segregation of functions and tasks |
op.acc.3 Segregation of functions and tasks |
404 not found |
|
|
|
n/a |
n/a |
|
43 |
|
op.acc.4 Access rights management process |
op.acc.4 Access rights management process |
404 not found |
|
|
|
n/a |
n/a |
|
40 |
|
op.acc.5 Authentication mechanism (external users) |
op.acc.5 Authentication mechanism (external users) |
404 not found |
|
|
|
n/a |
n/a |
|
72 |
|
op.exp.8 Recording of the activity |
op.exp.8 Recording of the activity |
404 not found |
|
|
|
n/a |
n/a |
|
67 |
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 |
4 |
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 |
7 |
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 |
8 |
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 |
13 |
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 |
8 |
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 |
10 |
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 |
|
20 |
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 |
22 |
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 |
29 |
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 |
51 |