Menu

An Azure SAS needs a signing scope and a revocation path
📰

An Azure SAS needs a signing scope and a revocation path

#devcommunity#dev#access#policy#service
Reading 0:00
15s threshold

An Azure SAS needs a signing scope and a revocation path

Shared access signatures are convenient because they move a narrow permission into a URL. The convenience is also the risk. Anyone who obtains the URL can attempt the operation until the signature expires or its server-side policy changes. A SAS design without a revocation plan is an access-control design that assumes the URL will never leak.

Azure Storage distinguishes account SAS, service SAS, and user delegation SAS. A service SAS is scoped to one storage service, such as Blob, Queue, Table, or Files. A stored access policy can provide server-side control over a service SAS and can revoke access without rotating the storage account key. Account SAS supports storage-account-level operations and does not support stored access policies in the same way.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.