| name | cis-azure-storage-17.1.4 |
| description | Ensure that shared access signature (SAS) tokens expire within an hour |
| category | cis-azure-storage |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","storage","storage-accounts","sas","keys"] |
| cis_id | 17.1.4 |
| cis_benchmark | CIS Microsoft Azure Storage Services Benchmark v1.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
17.1.4 Ensure that shared access signature (SAS) tokens expire within an hour (Manual)
Description
Shared access signature (SAS) tokens provide restricted access to Azure Storage resources (such as blobs, files, queues, or tables) for a defined time period with specific permissions. It enables users to interact with the resources without exposing account keys, offering precise control over the permitted actions (e.g., read, write) and the duration of access. To minimize security risks, SAS tokens should be configured with the shortest possible lifespan, ideally lasting no longer than an hour.
Rationale
A short lifespan for SAS tokens is recommended to minimize the risk of unauthorized access. SAS tokens grant time-limited access to resources, and a longer duration increases the opportunity for misuse if the token is compromised. By setting a shorter lifespan, the potential for security breaches is reduced.
Impact
SAS can pose security risks if they are not managed carefully.
Audit Procedure
Currently, SAS token expiration times cannot be audited. Until Microsoft makes the token expiration time a setting rather than a token creation parameter, this recommendation will require manual verification.
Expected Result
All SAS tokens are configured with an expiration time of one hour or less. Manual verification confirms that SAS token creation processes enforce a maximum expiration period of one hour.
Remediation
Remediate from Azure Portal
If SAS have been created without a short lifespan and were created with a stored access policy (SAP), the SAS can be revoked by deleting the SAP or updating the SAP expiration time to a time in the past:
- Go to
Storage accounts.
- Click on a storage account.
- Under
Data storage, click Containers, File shares, Queues, or Tables.
- Click the three dots next to a listed item.
- Click
Access policy.
- Click the three dots next to an access policy.
- Click
Delete.
- Click
Save.
- Repeat steps 1-8 as needed to revoke SAS created with SAP.
If SAS have been created without a short lifespan and were not created with a SAP, the SAS can be revoked by regenerating the storage account access keys:
Note: Regenerating access keys can affect any applications or Azure services that are dependent on the storage account key.
- Go to
Storage accounts.
