Federated share sends and ends: close the remaining audit gaps (#1072 U1 residuals) #1085

Open
opened 2026-11-03 05:32:21 +00:00 by Cordy · 0 comments
Owner

Since v0.6.390, ocm-share-send and ocm-share-end are administrative events, and every start writes audit-tiers. Since v0.6.392 the restore checklist's Federated shares row trusts its lists only when the range [backup, declaration] is covered: gap = !since390 && !AccessFloor && (!AccessNow || flipped) (internal/restores/federated.go).

Three cases still slip through:

  1. Config floor changed by a restart: audit.enabled changed by a restart inside the range is not audited.
  2. Downgrade: a downgrade below v0.6.390 inside the range is not detected.
  3. Rolling upgrade: an instance still on v0.6.389 drops sends for minutes after another instance wrote audit-tiers.

Why it matters. A send or an end creates or ends an outside party's access to the organisation's data.

  • GDPR Art. 19 asks the controller to tell each recipient of an erasure or correction, which needs a record of who received what.
  • NIST SP 800-53 PM-21 (Accounting of Disclosures) asks for the date, nature, purpose and recipient of each disclosure.

Proposal (research first).

  • Record the floor and the binary version in audit-tiers at every start (floor=on|off version=<v>).
  • Let the gap rule require an entry of v0.6.390 or later from every instance seen in the range.
Since v0.6.390, `ocm-share-send` and `ocm-share-end` are administrative events, and every start writes `audit-tiers`. Since v0.6.392 the restore checklist's Federated shares row trusts its lists only when the range [backup, declaration] is covered: `gap = !since390 && !AccessFloor && (!AccessNow || flipped)` (`internal/restores/federated.go`). Three cases still slip through: 1. **Config floor changed by a restart:** `audit.enabled` changed by a restart inside the range is not audited. 2. **Downgrade:** a downgrade below v0.6.390 inside the range is not detected. 3. **Rolling upgrade:** an instance still on v0.6.389 drops sends for minutes after another instance wrote `audit-tiers`. **Why it matters.** A send or an end creates or ends an outside party's access to the organisation's data. - GDPR Art. 19 asks the controller to tell each recipient of an erasure or correction, which needs a record of who received what. - NIST SP 800-53 PM-21 (Accounting of Disclosures) asks for the date, nature, purpose and recipient of each disclosure. **Proposal (research first).** - Record the floor and the binary version in `audit-tiers` at every start (`floor=on|off version=<v>`). - Let the gap rule require an entry of v0.6.390 or later from every instance seen in the range.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1085
No description provided.