Authorize the Data Element Before the Request Happens The mechanism: what decides, at which point, with which defaults, what it costs, and what it writes down.
Authorize the Data Element explains how B5 Secure makes element-level authorization enforceable before data is queried, retrieved, placed in memory, or sent to another system: the narrowing authority lattice, pre-request authorization, permitted-field projection, atomic and partial response modes, data-element entitlement, bounded list processing, and the decision ledger that records which data elements were released and withheld.
What’s inside
The sections, in the order the paper makes its argument.
- Every layer may only narrow: authority as an intersection, absence as denial
- Request — decide before the request happens
- Access — narrow the outbound query to permitted fields
- Delivery — atomic and partial response modes, and who may choose them
- Lists — where this gets expensive, and bounded processing
- Evidence — what the ledger records, element by element
- The gate — why nothing reaches data without a decision
- What this paper does not claim
Who it’s for
Three readers, three reasons.
Engineers implementing per-field authorization
Written to be argued with: every trade-off is stated, every default is the closed one.
Data-protection and privacy officers
Minimisation enforced before the fetch, with a record of what was withheld.
Reviewers of the Never Trust whitepaper
Section 5 of the whitepaper argues the decision belongs in the application; this is how.
Get the paper
Enter your work e-mail and we send a download link, valid for 72 hours. No attachments, no drip campaign — one message with the paper.
Get the document
See how B5 Secure authorizes each data element before retrieval, returns only permitted fields, records what was withheld, and blocks unprotected data-access paths at build time.
Companion reading
The three papers are written to be read together.
Never Trust
v1.4 · 31 pages — Continuous authorization from the record down to the data element.
Seven Field-Proven Authorization Patterns
v1.3 · 15 pages — The seven ways authorization fails, and the repeatable answer to each.
The Never Trust overview
The doctrine in one page, and the six principles behind it.
Figures cited in the papers describe the security and processing-integrity record of the lineage platform (first deployed to Forge Trust, now owned by Charles Schwab) as of December 31, 2025 — $16B+ in assets, 2.3M+ accounts, $0 of loss to security or processing-integrity failure. They are not a claim that B5SecurityKit is deployed at any named institution today.
Read it, then see it run.
The pipeline the paper describes is what the demos execute.