How to manage sas token which has already been shared out?

Question

How to manage sas token which has already been shared out?

贺刘 6

Hi,

I'm an owner of an azure blob, and I have shared some sas token out for reason.

Now, I'm confused about how to manage these tokens.

Is there any way to get the history token list on azure portal or by writing script?
And I also want to know detail information about anyone on anytime access the blob in any ip address.

Thanks a lot.

Anonymous

2024-01-17T18:35:34.44+00:00

I have used the REST API method and it returns a SAS token. However, given the parameters I passed in I would have expected multiple tokens. Is there a way to list them all on a storage account? Perhaps by date created or by who created it?

4 answers

Your answer

Anonymous

2024-01-17T18:35:34.44+00:00

I have used the REST API method and it returns a SAS token. However, given the parameters I passed in I would have expected multiple tokens. Is there a way to list them all on a storage account? Perhaps by date created or by who created it?

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

2 deleted comments

Comments have been turned off. Learn more

Answer 2

dmandm 1

Thanks for the detail. However I find it incredible that such a sensitive security event cannot be audited. Technology has been logging security events on paper and digitally forever.

0 comments

Answer 3

Omer Sen / Serra Consultancy 0

It is really very interesting not to see on Azure Portal

McDonald, Matthew 261 Reputation points

2024-02-13T18:50:29.9933333+00:00

This is unbelievable that this is still an issue in 2024.

Answer 4

Tollaksen, Steve 5

Just to clarify - we can generate tokens for otherwise anonymous access to huge amounts of data, and for years Microsoft has purposefully not logged the generation of tokens so admins cannot understand the exposure their data currently has. As these are public facing, there is a nonzero chance a malactor could stumble across a collision in the URL and get your data without ever actually having the token, and the admins would never know a token was even available, even though the valid token wasn't even used.

0 comments