Admin-recoverable second stage for "Delete forever" (Microsoft 365 / Google Workspace model) #1152

Closed
opened 2026-11-09 17:08:36 +00:00 by Cordy · 3 comments
Owner

Follow-up from #1104 research G4 (scratch/b7e/backlog/research-1104-g4-unsettled.md), decided by Nikola 2026-11-09: research after #1104.

From v0.6.405 "Delete forever" needs a browser sign-in (device and app passwords refused, alerted). A stolen browser session can still purge. Microsoft 365 (second-stage recycle bin, up to 93 days) and Google Workspace (admin restore 25 days) keep "deleted forever" items recoverable by administrators for a fixed time; Veeam/S3 Object Lock offer immutable windows (NCSC principle 1 "delaying implementation of any deletion").

To research with the playbook: second-stage storage and quota (instance allowance), the window (N days, admin setting), who restores (admins only?), interaction with GDPR erasure (Art. 17; an erasure purge must really erase: separate "erase now" admin path?), legal holds, encryption, the automatic trash clean-up, an admin "who may delete forever" switch (Box/Seafile model), multi-instance (#742).

Follow-up from #1104 research G4 (`scratch/b7e/backlog/research-1104-g4-unsettled.md`), decided by Nikola 2026-11-09: research after #1104. From v0.6.405 "Delete forever" needs a browser sign-in (device and app passwords refused, alerted). A stolen browser session can still purge. Microsoft 365 (second-stage recycle bin, up to 93 days) and Google Workspace (admin restore 25 days) keep "deleted forever" items recoverable by administrators for a fixed time; Veeam/S3 Object Lock offer immutable windows (NCSC principle 1 "delaying implementation of any deletion"). To research with the playbook: second-stage storage and quota (instance allowance), the window (N days, admin setting), who restores (admins only?), interaction with GDPR erasure (Art. 17; an erasure purge must really erase: separate "erase now" admin path?), legal holds, encryption, the automatic trash clean-up, an admin "who may delete forever" switch (Box/Seafile model), multi-instance (#742).
Author
Owner

Research done (2026-11-11, scratch/b7e/backlog/research-1152.md). Sources: Microsoft 365, Google Workspace, Box, Dropbox, Seafile, S3 Object Lock, NCSC, GDPR Art. 17/32, EDPB 2025 erasure report, ICO.

Recommended design

  • Where it lives: an admin-only second stage, 14 days by default, counted from the purge. The entry is marked in place rather than moved.
  • What goes in: every human purge (people, restore runs, single versions, admin purges). The sweep's own automatic purges do not.
  • Restore: administrators only, back into the owner's Deleted files.
  • Erase now: fresh second step, a reason, always audited, refused under a legal hold.
  • Expiry: its own pass under a lease, because the sweep stops when automatic deletion is off.
  • Also included:
    • a "who can delete forever" switch;
    • mass-delete alerts;
    • the space name stays reserved and Destroy key is blocked while the space is in the second stage.

Small findings: security-standards.md:271 is out of date. The IT "Delete forever" button says "per sempre" where every other purge string says "definitivamente".

Next: decisions.

**Research done** (2026-11-11, `scratch/b7e/backlog/research-1152.md`). Sources: Microsoft 365, Google Workspace, Box, Dropbox, Seafile, S3 Object Lock, NCSC, GDPR Art. 17/32, EDPB 2025 erasure report, ICO. **Recommended design** - **Where it lives:** an admin-only second stage, 14 days by default, counted from the purge. The entry is marked in place rather than moved. - **What goes in:** every human purge (people, restore runs, single versions, admin purges). The sweep's own automatic purges do not. - **Restore:** administrators only, back into the owner's Deleted files. - **Erase now:** fresh second step, a reason, always audited, refused under a legal hold. - **Expiry:** its own pass under a lease, because the sweep stops when automatic deletion is off. - **Also included:** - a "who can delete forever" switch; - mass-delete alerts; - the space name stays reserved and Destroy key is blocked while the space is in the second stage. **Small findings:** `security-standards.md:271` is out of date. The IT "Delete forever" button says "per sempre" where every other purge string says "definitivamente". **Next:** decisions.
Author
Owner

Decisions (2026-11-12)

  • Window: Off / 7 / 14 / 30 / 90 days, default 14, counted from the purge. On for new instances; upgraded instances get a one-time bell offering it.
  • Erase now: administrators only, in a browser, with a fresh second step and a required reason. Refused under a legal hold, always audited, other administrators alerted on bulk use.
  • Four-eyes switch, built now: "Erase now needs a second administrator", off by default.
    • It can only be turned on while Cairn knows two or more administrator accounts that are not break-glass accounts.
    • It also covers switching the setting off and shortening or switching off the window.
    • Any other such administrator approves, with a fresh second step.
    • A request expires after 72 h and then counts as rejected.
    • With only one administrator left, Erase now is refused and the data still ends on its date.
    • Research: research-1152-foureyes.md. NIST CP-9(7)/AC-3(2) and BSI ORP.4.A24 recognise it; backup products have it, file-sync products don't.
  • "Who can delete forever": Everyone (default) / Space owners and administrators / Administrators only.
  • The rest as researched:
    • All human purges go into the second stage; the automatic sweep does not.
    • Administrators restore into the owner's Deleted files.
    • The data export lists second-stage items.
    • Mass-delete alert at 100 entries or 1 GiB per hour.
    • Deleted spaces keep their name reserved and Destroy key is blocked while in the second stage.
    • Plus the two small fixes from the research.

Next: mockups.

**Decisions (2026-11-12)** - **Window:** Off / 7 / 14 / 30 / 90 days, default 14, counted from the purge. On for new instances; upgraded instances get a one-time bell offering it. - **Erase now:** administrators only, in a browser, with a fresh second step and a required reason. Refused under a legal hold, always audited, other administrators alerted on bulk use. - **Four-eyes switch, built now:** "Erase now needs a second administrator", off by default. - It can only be turned on while Cairn knows two or more administrator accounts that are not break-glass accounts. - It also covers switching the setting off and shortening or switching off the window. - Any other such administrator approves, with a fresh second step. - A request expires after 72 h and then counts as rejected. - With only one administrator left, Erase now is refused and the data still ends on its date. - Research: `research-1152-foureyes.md`. NIST CP-9(7)/AC-3(2) and BSI ORP.4.A24 recognise it; backup products have it, file-sync products don't. - **"Who can delete forever":** Everyone (default) / Space owners and administrators / Administrators only. - **The rest as researched:** - All human purges go into the second stage; the automatic sweep does not. - Administrators restore into the owner's Deleted files. - The data export lists second-stage items. - Mass-delete alert at 100 entries or 1 GiB per hour. - Deleted spaces keep their name reserved and Destroy key is blocked while in the second stage. - Plus the two small fixes from the research. **Next:** mockups.
Author
Owner

Shipped in v0.6.407 (PR #1170, tag on aad4ca91), live on both dogfoods (pods on v0.6.407, ready, 0 restarts, healthz 200, no new WARN/ERROR).

What shipped:

  • Keep items deleted forever for administrators (Off/7/14/30/90 days; 14 on new instances, Off on upgrades until an admin chooses). Every human Delete forever and Manual purge enters a second stage only session administrators see (Administration › Deleted files › Deleted forever); an hourly pass removes items at their date. Never served by any way out (proven on the real chain).
  • Restore into the owner's Deleted files, Erase now with reason and note, Who can delete forever (3 choices), mass and bulk alerts, size bell.
  • Erase now needs a second administrator (four-eyes): Erase now and weakening the window become requests another eligible, non-break-glass admin approves with a fresh second step; 72 h; reminders; stale/re-entered/requester-not-admin requests close without effect; approvers named before sending.
  • Security mail subjects name no person (house rule kept).
  • With the window off, a deleted space keeps its inner stage-2 items until their date.

Docs: admin-policy.md "Deleted forever", file-browser.md, data-protection-operators.md, ARCHITECTURE.md, CHANGELOG v0.6.407. Follow-ups filed separately.

Shipped in **v0.6.407** (PR #1170, tag on aad4ca91), live on both dogfoods (pods on v0.6.407, ready, 0 restarts, healthz 200, no new WARN/ERROR). What shipped: - **Keep items deleted forever for administrators** (Off/7/14/30/90 days; 14 on new instances, Off on upgrades until an admin chooses). Every human Delete forever and Manual purge enters a second stage only session administrators see (Administration › Deleted files › Deleted forever); an hourly pass removes items at their date. Never served by any way out (proven on the real chain). - **Restore** into the owner's Deleted files, **Erase now** with reason and note, **Who can delete forever** (3 choices), mass and bulk alerts, size bell. - **Erase now needs a second administrator** (four-eyes): Erase now and weakening the window become requests another eligible, non-break-glass admin approves with a fresh second step; 72 h; reminders; stale/re-entered/requester-not-admin requests close without effect; approvers named before sending. - Security mail subjects name no person (house rule kept). - With the window off, a deleted space keeps its inner stage-2 items until their date. Docs: admin-policy.md "Deleted forever", file-browser.md, data-protection-operators.md, ARCHITECTURE.md, CHANGELOG v0.6.407. Follow-ups filed separately.
Cordy closed this issue 2026-11-12 19:12:06 +00:00
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#1152
No description provided.