Skip to content
Skillv1.0.0

cis-azure-storage-11.1

Ensure 'Allowed Protocols' for shared access signature (SAS) tokens is set to 'HTTPS Only'

by CyberStrikeus(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from CyberStrikeus/CyberStrike (.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/cis-microsoft-azure-storage-services/cis-azure-storage-11.1/SKILL.md). Install upstream with npx skills add CyberStrikeus/CyberStrike --skill cis-azure-storage-11.1. Copyright stays with the author.

11.1 Ensure 'Allowed Protocols' for shared access signature (SAS) tokens is set to 'HTTPS Only' (Manual)

Description

Shared access signatures (SAS) can be used to grant limited access to Azure Storage resources. When generating a SAS, it is possible to specify the allowed protocols for a request made with the SAS. It is recommended to allow requests over HTTPS only.

Rationale

If a SAS is passed over HTTP and intercepted, an attacker performing a man-in-the-middle attack can read the SAS. Then, they can use that SAS just as the intended user could have. This can potentially compromise sensitive data or allow for data corruption by the malicious user.

Impact

SAS can pose security risks if they are not managed carefully.

Audit Procedure

It is not possible to audit generated SAS.

Expected Result

All SAS tokens are generated with Allowed protocols set to HTTPS only.

Remediation

Remediate from Azure Portal

If SAS have been created to allow HTTP 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:

  1. Go to Storage accounts.
  2. Click on a storage account.
  3. Under Data storage, click Containers.
  4. Click the three dots next to a container.
  5. Click Access policy.
  6. Click the three dots next to an access policy.
  7. Click Delete.
  8. Click Save.
  9. Repeat steps 1-8 as needed to revoke SAS created with SAP.

If SAS have been created to allow HTTP 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.

  1. Go to Storage accounts.
  2. Click on a storage account.
  3. Under Security + networking, click Access keys.
  4. Next to each key, click Rotate key.
  5. Click Yes to confirm.
  6. Repeat steps 1-5 as needed to revoke SAS.

Default Value

When generating a SAS, the default selection for Allowed protocols is HTTPS only.

References

  1. https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview
  2. https://learn.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage

Additional Information

This recommendation is based on the recommendation Ensure 'Allowed Protocols' for shared access signature (SAS) tokens is set to 'HTTPS Only', from the Common Reference Recommendations > Secrets and Keys > Shared Access Signatures section.

Profile

Level 1 | Manual

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/cyberstrikeus-cyberstrike-cis-azure-storage-11-1/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

cyberstrikeus-cyberstrike-cis-azure-storage-11-1.ocm.jsonjson
{
  "ocm": "1",
  "id": "cyberstrikeus-cyberstrike-cis-azure-storage-11-1",
  "kind": "skill",
  "name": "cis-azure-storage-11.1",
  "description": "Ensure 'Allowed Protocols' for shared access signature (SAS) tokens is set to 'HTTPS Only'",
  "publisher": "CyberStrikeus",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "cis",
      "azure",
      "storage",
      "blob-storage",
      "sas",
      "encryption",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Ensure 'Allowed Protocols' for shared access signature (SAS) tokens is set to 'HTTPS Only'"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/CyberStrikeus/CyberStrike",
      "path": ".cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/cis-microsoft-azure-storage-services/cis-azure-storage-11.1/SKILL.md",
      "ref": "df28ccd3dc6d6c02391169121ee2dcdf4a6a132b",
      "url": "https://github.com/CyberStrikeus/CyberStrike/blob/df28ccd3dc6d6c02391169121ee2dcdf4a6a132b/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/cis-microsoft-azure-storage-services/cis-azure-storage-11.1/SKILL.md",
      "key": "CyberStrikeus/CyberStrike/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/cis-microsoft-azure-storage-services/cis-azure-storage-11.1/SKILL.md"
    }
  },
  "instructions": "# 11.1 Ensure 'Allowed Protocols' for shared access signature (SAS) tokens is set to 'HTTPS Only' (Manual)\n\n## Description\n\nShared access signatures (SAS) can be used to grant limited access to Azure Storage resources. When generating a SAS, it is possible to specify the allowed protocols for a request made with the SAS. It is recommended to allow requests over HTTPS only.\n\n## Rationale\n\nIf a SAS is passed over HTTP and intercepted, an attacker performing a man-in-the-middle attack can read the SAS. Then, they can use that SAS just as the intended user could have. This can potentially compromi",
  "cost": {
    "context_tokens": 640
  }
}

Fetch it by URL: GET /api/v1/registry/cyberstrikeus-cyberstrike-cis-azure-storage-11-1/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.