Enterprise Data Compartmentalization

Some organizations run programs that are not supposed to know about each other. Legal holds, acquisition teams, classified work and clean room engineering all rely on that separation. A shared assistant is a direct threat to it, because one prompt window serves everyone. This starter is aimed at the security lead who owns those boundaries.

Compartments fail quietly. A person with legitimate access to one program pastes its content into a general assistant. The boundary that took years to design then disappears inside one request. This starter puts that boundary back into the request path.

Identity is the load bearing control here. The access check ships without a role list. It still refuses a request that arrives with no verified identity, because authentication is on by default. Roles come from verified claims and never from a header that a caller supplies. Naming the roles, the required headers and the compartments is your first configuration task.

Redaction and blocked phrases act as a second line behind identity. Case, docket and matter numbers are masked wherever they appear. A request naming controlled unclassified information, a sealed filing or an investigative file is refused. Neither control understands your compartment labels, so treat both as a backstop rather than the boundary itself.

Redacted history capture records every exchange, and it includes the requests that were refused. Failed capture stops the request rather than letting it through unrecorded. Returned text must clear a combined 0.86, and the review point is an empty block that your access owner can turn on.