| name | cis-azure-storage-16.3 |
| description | Ensure stored access policies (SAP) are used when generating shared access signature (SAS) tokens |
| category | cis-azure-storage |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","storage","queue-storage","sas"] |
| cis_id | 16.3 |
| cis_benchmark | CIS Microsoft Azure Storage Services Benchmark v1.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
16.3 Ensure stored access policies (SAP) are used when generating shared access signature (SAS) tokens (Manual)
Description
Use stored access policies (SAP) when generating shared access signature (SAS) tokens in Azure to centrally manage permissions, expiration, and revocation settings for resource access. Stored access policies can be applied to blob containers, file shares, queues, and tables.
Rationale
Stored access policies provide centralized control over SAS token access, allowing administrators to update permissions or revoke access. This approach strengthens security by reducing the risk of unauthorized access to storage resources.
Impact
There is no cost for creating stored access policies, however there is some administrative overhead involved in managing these policies.
Audit Procedure
It is not currently possible to retrieve a list of all generated SAS tokens to check if they were associated with a SAP during creation.
An SAS token that has been created with a SAP will contain an si parameter that references the stored access policy identifier associated with the SAS, e.g. si=<stored-access-policy-identifier>.
The si parameter will be absent from an SAS token created without a SAP.
Expected Result
All shared access signature (SAS) tokens should contain the si parameter referencing a stored access policy identifier. SAS tokens without the si parameter indicate they were created without a stored access policy, which is non-compliant.
Remediation
Remediate from Azure Portal
To create a SAP for a queue:
- Go to
Storage accounts.
- Click on a storage account.
- Under
Data storage, click Queues.
- Click the name of a queue.
- Under
Settings, click Access policy.
- Under
Stored access policies, click + Add policy.
- Enter an
Identifier.
- From the
Permissions drop-down, select appropriate permissions for the policy.
- Set an appropriate
Start time for the policy.
- Set an appropriate
Expiry time for the policy.
- Click
OK.
- Click
Save.
- Repeat steps 1-12 as needed to create SAP.