docs: add Azure SAS policy evidence gates#1366
Open
catcherintheroad-hub wants to merge 1 commit into
Open
Conversation
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Created from review issue
Fixes #1329
What was wrong
The Azure review could treat storage accounts as safe when public access was disabled, HTTPS/TLS were configured, and network rules were hardened. That misses broad bearer-token paths such as long-lived account SAS, service SAS without stored access policies, Shared Key access, external RBAC principals, and ADLS Gen2 ACL divergence.
What changed
azure-review/SKILL.mdfor storage bearer access evidence.tests/storage-sas-policy-edge-cases.md.Validation
git diff --check