Secure the storage data plane behind AI retrieval
Separate ingestion and serving authority, close Shared Key and anonymous paths, constrain SAS use, and validate Blob and Data Lake access independently.
Explore the topic
Protect document permissions, ingestion integrity and the storage behind AI grounding.
Questions this collection helps you answer
Build your understanding
Separate ingestion and serving authority, close Shared Key and anonymous paths, constrain SAS use, and validate Blob and Data Lake access independently.
Choose between application security filters and native preview permissions, preserve access metadata on chunks, and enforce the same boundary across keyword and vector retrieval.
Separate source access from content trust, preserve provenance through chunking, and verify publication, deletion, and rollback without assuming a prompt filter proves integrity.
Move from control to evidence
Use these as investigation leads. Table coverage and context determine what the results can establish.
Identify tenant-qualified OAuth principals whose completed daily GetBlob volume exceeds a fixed historical average, retaining response-byte and object-diversity context.
Group successful DeleteBlob requests by account and caller evidence, retaining object samples while distinguishing request counts from permanent data destruction.
Separate successful anonymous reads from rejected requests, with sanitized object paths and response-size context rather than assuming every anonymous hit exposed data.
Follow the connections