CIS Microsoft Azure Foundations Benchmark v1.4.0/Storage Accounts/41 of 115
3.4Ensure that Shared Access Signature Tokens Expire Within an Hour
Control family: Storage Accounts
Control description
Expire shared access signature tokens within an hour.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A shared access signature is a URL that grants access to storage without a key; anyone holding it can use it until it expires. Keeping the lifetime to an hour or less limits the damage when one leaks. A SAS expiration policy on the account flags signatures created for longer, and user delegation SAS, signed with Entra credentials, are preferred.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree the longest allowed lifetime for a shared access signature (one hour) and any exception, with its approver.
- Ask application owners to move to user delegation SAS where they can.
Evidence
- The SAS standard and the exception register
On Azure the tasks set a SAS expiration policy on each storage account, then move applications to short-lived user delegation SAS.
Task 1Set a one-hour SAS expiration policy
- Sign in to the Azure portal at portal.azure.com and open Storage accounts, then the account.
- Select Settings > Configuration.
- Enable Allow recommended upper limit for shared access signature (SAS) expiry interval and set it to 0 days, 1 hour.
- Select Save.
- Check it: a SAS created for longer than an hour is logged as violating the policy (or refused, if you also set the action to block).
Task 2Prefer short-lived user delegation SAS
- Agree with application owners to create SAS with an end time within an hour of the start time.
- Where possible, sign them with Microsoft Entra credentials (user delegation SAS) rather than the account key.
- In Settings > Configuration, consider setting Allow storage account key access to Disabled once nothing relies on account keys, which also blocks key-signed SAS.
- Check it: the storage logs (3.10) show requests using SAS created within the policy.
Evidence
- Configuration of each account, showing the SAS expiry limit
- The applications' SAS approach, recorded with their owners
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.