Detections
Analytics
5.3 Ensure that Diagnostic Logs are enabled for all services which support it.
Information
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'
Rationale:
A lack of Diagnostic Logs 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, Diagnostic Logs are not enabled by default. Specifically, without Diagnostic Logs it would be impossible to tell which entities had accessed a data store that which was breached. In addition, alerts for failed attempts to access APIs for Web Services or Databases are only possible when Diagnostic Logging is enabled.
Impact:
Costs for Log Analytics Workspaces varies with Log Volume.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Azure Subscriptions should log every access and operation for all resources.Logs should be sent to Storage and a Log Analytics Workspace or equivalent third-party system.
Logs should be kept in readily accessible storage for a minimum of one year, and then moved to inexpensive cold storage for a duration of time as necessary. If retention policies are set but storing logs in a Storage Account is disabled (for example, if only Event Hubs or Log Analytics options are selected), the retention policies have no effect.
Enable all logging at first, and then be more aggressive moving data to cold storage if the volume of data
becomes a cost concern.
From Azure Console
The specific steps for configuring resources within the Azure console vary depending on resource, but typically the steps are:
Go to the resource
Click on Diagnostic settings
In the blade that appears, click 'Add diagnostic setting'
Configure the diagnostic settings
Click on Save
Using Azure Command Line Interface
Enable logging for all resources which support Diagnostic Logs to ensure interactions within the resource are logged and available. The skeleton command for creating
logs and metrics with unlimited retention on a
generic resource are shown below.
az monitor diagnostic-settings create --resource {ID} -n {name}
--event-hub-rule {eventHubRuleID} --storage-account {storageAccount}
--logs '[
{
'category': 'WorkflowRuntime',
'enabled': true,
'retentionPolicy': {
'enabled': false,
'days': 0
}
}
]'
--metrics '[
{
'category': 'WorkflowRuntime',
'enabled': true,
'retentionPolicy': {
'enabled': false,
'days': 0
}
}
]'
Default Value:
Disabled
See Also
Item Details
Audit Name: CIS Microsoft Azure Foundations v1.3.1 L1
References: CSCv7|6.3, CSCv7|6.5, CSCv7|7.6
Plugin: microsoft_azure
Control ID: 5af8125adf6de7b35d4f8047f981bd6ec11bb631c1ea41c6bc0310cb4d643f9e