Loading content
Sensitive data exposure covers unintended disclosure of secrets, personal data, source code, or business information. Agentic workflows increase the number of data paths and therefore require explicit access boundaries and output controls.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
Concrete cog in the system that works inside larger relationships.
Sensitive Data Exposure is the unintended disclosure of confidential information by a system or its outputs.
The risk comes from information security and privacy: inadequate access controls, logs, or responses can reveal protected data. OWASP lists sensitive information disclosure as a distinct risk for applications built with large language models.
Imagine an information desk opening an internal file even though someone asked a general question. A correct answer is still an incident when it reveals more than the requester is allowed to see.
Data whose exposure could harm people, organizations, or systems.
Rules determine who may read or process which data.
Confidential parts are removed before storage, processing, or output.
The category highlights data leakage through prompts, logs, tools, and responses. It requires minimization, permission checks, and testing; an after-the-fact filter cannot recall a secret already disclosed.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.