ios#65 ends with a line worth acting on before anything else in it:
"'we implement Bell-LaPadula' should not be said anywhere until this is
settled, and I have not checked whether it already is."
It is said, here, in a public repository:
It implements the *model*, for commercial multi-tenancy.
Only half of it does. Naming a model is a claim about which of its rules
hold, so the half that does not hold has to be named too.
What is enforced, checked rather than recalled: the server's Policy.decide gates every mode on subject.dominates(object) — no read
up — and its default WriteRule.equal allows a write only at exactly the
session label. Both clients gate on Clearance.permits.
What is not: a principal cleared to a high label may open a session at a
lower one and write there, carrying down what they read above it. Neither
client stops that, and neither does the server, because a session label
inside a principal's clearance range is a legitimate session. That is the
★-property, and it is the half a lattice exists for — no-read-up stops
somebody reaching material above them, which most systems get right;
no-write-down stops it leaking downward through somebody allowed to see
it.
⚠️ Filed under "What it does not protect" rather than fixed, which is the
issue's own reading and worth restating: a rule enforced on one client
and not the other is worse than the gap, and strict enforcement with no
downgrade path produces a workaround culture. Doing it properly needs an
explicit downgrade action with an audit trail. Until that exists this is
written down rather than implied away.
ios#65 ends with a line worth acting on before anything else in it:
"'we implement Bell-LaPadula' should not be said anywhere until this is
settled, and I have not checked whether it already is."
It is said, here, in a public repository:
It implements the *model*, for commercial multi-tenancy.
Only half of it does. Naming a model is a claim about which of its rules
hold, so the half that does not hold has to be named too.
What is enforced, checked rather than recalled: the server's
`Policy.decide` gates every mode on `subject.dominates(object)` — no read
up — and its default `WriteRule.equal` allows a write only at exactly the
session label. Both clients gate on `Clearance.permits`.
What is not: a principal cleared to a high label may open a session at a
lower one and write there, carrying down what they read above it. Neither
client stops that, and neither does the server, because a session label
inside a principal's clearance range is a legitimate session. That is the
★-property, and it is the half a lattice exists for — no-read-up stops
somebody reaching material above them, which most systems get right;
no-write-down stops it leaking downward through somebody allowed to see
it.
⚠️ Filed under "What it does not protect" rather than fixed, which is the
issue's own reading and worth restating: a rule enforced on one client
and not the other is worse than the gap, and strict enforcement with no
downgrade path produces a workaround culture. Doing it properly needs an
explicit downgrade action with an audit trail. Until that exists this is
written down rather than implied away.
79 tests.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ios#65 ends with a line worth acting on before anything else in it:
"'we implement Bell-LaPadula' should not be said anywhere until this is
settled, and I have not checked whether it already is."
It is said, here, in a public repository:
Only half of it does. Naming a model is a claim about which of its rules
hold, so the half that does not hold has to be named too.
What is enforced, checked rather than recalled: the server's
Policy.decidegates every mode onsubject.dominates(object)— no readup — and its default
WriteRule.equalallows a write only at exactly thesession label. Both clients gate on
Clearance.permits.What is not: a principal cleared to a high label may open a session at a
lower one and write there, carrying down what they read above it. Neither
client stops that, and neither does the server, because a session label
inside a principal's clearance range is a legitimate session. That is the
★-property, and it is the half a lattice exists for — no-read-up stops
somebody reaching material above them, which most systems get right;
no-write-down stops it leaking downward through somebody allowed to see
it.
⚠️ Filed under "What it does not protect" rather than fixed, which is the
issue's own reading and worth restating: a rule enforced on one client
and not the other is worse than the gap, and strict enforcement with no
downgrade path produces a workaround culture. Doing it properly needs an
explicit downgrade action with an audit trail. Until that exists this is
written down rather than implied away.
79 tests.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
assigned to @paulhitt
mentioned in commit
b9ec330c6d