Say which half of the model is enforced (ios#65, android#15) #9

Merged
paulhitt merged 1 commits from docs/say-which-half-of-the-model into main 2026-09-07 11:58:05 +00:00
paulhitt commented 2026-09-07 11:44:42 +00:00 (Migrated from gitlab.com)

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

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>
paulhitt commented 2026-09-07 11:44:43 +00:00 (Migrated from gitlab.com)

assigned to @paulhitt

assigned to @paulhitt
paulhitt commented 2026-09-07 11:58:05 +00:00 (Migrated from gitlab.com)

mentioned in commit b9ec330c6d

mentioned in commit b9ec330c6dc965929ab27ae99cc6b2ac11559473
paulhitt (Migrated from gitlab.com) merged commit b9ec330c6d into main 2026-09-07 11:58:05 +00:00
This repo is archived. You cannot comment on pull requests.
No Reviewers
No labels
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: extant2000/flamenet-files#9