Architecture
The stack underneath, and who gets it.
Marcella sits on four pieces of security infrastructure: an output that proves the conditions it was produced under, a device that has to keep proving it is the device, a compliance record as checkable as the control it records, and a gate that runs before the login. Most firms will not receive it, and this page says so before it describes any of it.
Who actually gets this
The full stack lands at Enterprise. On Verify, Small, Medium and Large you are buying retrieval-first legal research with citation attestation. You are not buying the attestation and entropy infrastructure described below.
We are saying that at the top of the page rather than in a footnote, because a security architecture page that lets every reader assume they are covered is worse than no page at all.
If your firm needs these primitives in its own environment, that is an Enterprise conversation and it is scoped per deployment. The bands are published.
The four pieces, and what each one changes
Each one has its own published technical page. The links go to those pages rather than to a summary of them here, so you can check the claim against the specification. Read on 29 October 2026.
An output that still proves its own conditions later
Marcella Attestation Protocol
Cryptographic environmental attestation. An output carries a record of the conditions it was produced under, and that record can be checked later by someone who was not there. Read the Marcella Attestation Protocol technical page.
A machine that has to keep proving it is the machine
Concentric Entropy Model
Enrolled devices, each holding its own signing key, arranged in rings. A device that cannot present a valid signature is not inside the ring, which is what makes an impersonated machine visible rather than assumed. Read the Concentric Entropy Model technical page.
Evidence of a control that is as checkable as the control
Marcella Compliance Frame
Chain of custody for the compliance record itself, so the proof a control worked can be verified the same way the control can. Read the Marcella Compliance Frame technical page.
A credential stopped before the login evaluates it
Pre-Authentication OSI Gate
A gate that runs before authentication rather than after it, so a credential that should never have reached the login is stopped before it is weighed. Read the Pre-Authentication OSI Gate technical page.
The technical authority page sets out how the four fit together.
The impersonated IT worker
The 2026 legal threat reporting put this at the top: an adversary recruited a person to impersonate IT staff and physically infiltrate law firms to establish remote access. A stolen or issued credential is enough to pass a login, because a login only asks what you know and what you hold.
A real employee leaves a footprint that a stand-in does not. The same person returns to the same places, on the same networks, among the same nearby devices, at hours that look like their hours. Bluetooth and Wi-Fi neighbours, the LAN they join, the addresses they appear from, the times they work and the places they work from accumulate into a history.
Continue, 129 more words
Attestation signs that environment, not just the credential. The record of the conditions an action was taken under travels with the action, and the device has to keep proving it is the device it enrolled as, so a session that presents the right password from the wrong world fails a check rather than passing one.
Enterprise only. This is not on Verify, Small, Medium or Large. On those bands a stolen credential gets the same access the person it was stolen from had, exactly as it would with any other Microsoft 365 application.
It is a signal, not a verdict. It raises the cost of pretending to be someone for long enough to matter; it does not prove identity, and a patient adversary who reproduces the environment defeats it.
What watches, and how far it reaches
Every day it ingests the public National Vulnerability Database and the United States catalogue of vulnerabilities known to be actively exploited, and matches them against the devices enrolled in the deployment. A match raises an event naming the device. That is the class of device the 2026 legal threat reporting put at the centre of several intrusions.
Its reach is exactly the devices that are enrolled, and no further. Nothing is enrolled by default. A firewall, a hypervisor host or a billing server is in scope only if your deployment put it there, and that scoping is part of an Enterprise conversation rather than a switch that is already on.
Continue, 180 more words
It reports. It does not patch. And the known-exploited catalogue identifies a vendor and a product with no version range, so every device of that product raises a flag whether or not it is already patched. A person still reads the build number. The national database half carries versions and is compared numerically, so that half does distinguish a patched device from a vulnerable one.
Every component ships through the same gate, and that is a checkable claim rather than a reassuring one. One pipeline builds the legal research product and the same shape of pipeline builds each piece around it: a secret scan across the full commit history, a dependency vulnerability audit, and a filesystem scan. Each scanner is pinned to an exact version, its binary hash is verified before it runs, and a finding fails the build instead of printing a warning. Application dependencies install under hash verification, so a substituted package fails at install rather than at runtime.
How this maps to the 2026 legal threat vectors, including the three rows where the honest answer is partial.
What this is not
None of this makes Marcella a security product for your firm. It is not endpoint detection, it is not an identity provider, it does not monitor your tenant and it does not replace the controls your IT team already runs.
What it does is make the thing Marcella produces checkable: an output carries a record of the conditions it was produced under, and that record survives being examined by someone who was not there when it was made.
The security review page states what leaves and what stays, per tier.
