CIS Microsoft Azure Foundations Benchmark v1.4.0/Logging and Monitoring/72 of 115
5.1.3Ensure the storage container storing the activity logs is not publicly accessible
Control family: Logging and Monitoring
Control description
The storage account container containing the activity log export should not be publicly accessible.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
If the activity log is archived to a storage account, the container it lands in (insights-activity-logs) holds a full record of how the environment is run. It must never be readable anonymously.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree that the storage account holding the activity log is readable only by named log readers, and never anonymously.
Evidence
- The log storage access standard
On Azure the tasks set the container to private and turn off anonymous access on its storage account, then keep it checked with the CIS standard.
Task 1Make the log container private
- Sign in to the Azure portal at portal.azure.com and open the storage account that receives the activity log.
- Select Data storage > Containers and find insights-activity-logs.
- Select it, then Change access level, choose Private (no anonymous access) and select OK.
- In Settings > Configuration, set Allow Blob anonymous access to Disabled and select Save.
- Check it: the container shows Private and the account blocks anonymous access.
Task 2Keep it checked with the CIS v1.4.0 standard in Defender for Cloud
- Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
- Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
- Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 5.1.3.
- Open the assessment for Storage account public access should be disallowed and fix the resources it lists as non-compliant.
- Check it: every resource under recommendation 5.1.3 shows as passing after the next evaluation.
Evidence
- The insights-activity-logs container, showing Private
- The CIS v1.4.0 standard, with recommendation 5.1.3 passing
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.