Information barriers on Salesforce: platform rules, not etiquette

Etiquette versus architecture

Every investment bank has information barriers. The question an audit asks is what they're made of. In many firms the honest answer is etiquette: training, attestations, and the assumption that people don't open what they shouldn't. That survives until the first time someone does — and then the firm discovers that "we told people not to" is not a control, it's a hope with a paper trail.

On a properly architected platform, the wall is not advice. It is the sharing model — and the sharing model does not have lapses of judgement.

Walls as platform rules

A wall-crossing, end to end

The tooling around the wall keeps improving: Salesforce Shield now offers unified security management and guided compliance configuration, which makes encryption, event monitoring and field audit trails — the wall’s instrumentation — considerably less painful to run. The architecture is the control; Shield is how you prove it operated.

The honest caveat

Platform rules don't replace the compliance function — they give it teeth. Conduct, conflicts judgement and the decision to approve a crossing remain human. What the architecture removes is the gap between the decision and its enforcement: once compliance says no, there is no quiet way around it.

Three questions for your control room

How Eminence VSP helps

We design information barriers on Salesforce as architecture: Compliant Data Sharing for need-to-know, wall-crossings as governed records, and Shield instrumentation your control room can stand behind in an audit. See Corporate & Investment Banking or talk to the architect.