docs(security): ratify AR-1 MFA for platform roles
AR-1 option B (BDR-083): aal2 for every platform role change. Contract 5.7 rule, path inventory, bootstrap, factors, recovery, sessions; F17-F19; M4 scope, tests, DEV preconditions; fresh security review integrated (19.4).
This commit is contained in:
1 parent
41d3b09120
commit
9c13bae4bc
5 files changed
+447
-57
No files matched your search
@@ -90,6 +90,9 @@ enforced by an RLS helper `has_mfa()` on admin tables. Today:
|
||||
- app: no enrolment UI (QR + code), no `aal2` step-up on sign-in;
|
||||
- there is no admin table or screen yet to protect.
|
||||
|
||||
V1-2 decision (BDR-083): `aal2` is required for every platform role change,
|
||||
see `V1-2_ANATOMICAL_SHEETS.md` §5.7 (rule, bootstrap, recovery).
|
||||
|
||||
The Security section shows a note instead. To close the gap (a later step):
|
||||
migration adding `private.has_mfa()` and folding it into `is_platform_*` (or
|
||||
into the policies of the first admin table) with pgTAP allowed/denied cases;
|
||||
|
||||
Reference in new issue
Block a user