Execution safety, control 1 of 9
S-01 Default to read-only and least privilege
P0Hard gateNeeds your evidence
A request to optimise a site does not grant unrestricted production, billing, DNS or third-party account access. Permissions must be explicit and bounded.
- Priority
- Gate. A FAIL stops publish or launch.
- Hard gate
- Yes. A FAIL stops publication, whatever the score.
- Change class
- READ_ONLY: Inspect authorised evidence.
- Quality bucket
- Not scored: hard gate only
Evidence to review
- Trusted permission manifest and a denied-action test.
How to implement
- Discover available capabilities without escalating them.
- Keep research, repository writes and production deployment separate.
- Restrict access by site, tenant, environment, path and action.
- Require explicit approval before adding credentials or broadening permissions.
How UltimateSEO checks this
Needs your evidence. No automated check covers this control, so it stays UNKNOWN until evidence is supplied.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.