A background job still needs a subject
Cron and queue workers often skip authorization because "there is no user." That creates a god-mode path. Give the job a service identity with the narrowest permissions it needs, and still check those
Search for a command to run...
Articles tagged with #access-control
Cron and queue workers often skip authorization because "there is no user." That creates a god-mode path. Give the job a service identity with the narrowest permissions it needs, and still check those
Feature flags are great for rollouts. They are a poor substitute for authorization. A flag answers: “Is this code path on for this cohort?” An authz check answers: “Is this principal allowed to do thi
A successful login answers one question: who is this? Authorization answers a different one: may this principal do this action on this resource right now? Treating "the user is authenticated" as enoug
When your policy engine, PDP, or permissions service times out, what does the API do? Returning 200 “just this once” so the page keeps working is fail-open. An attacker who can jam or delay that depen
Break-glass and "just this once" admin grants are where authorization quietly becomes permanent. If someone needs elevated access to fix production, grant it with: A hard expiry (minutes or hours, no
A standing admin or superuser role is a long-lived blast radius. The privilege sits there after the incident ends, ready to be copied, phished, or reused on a quiet afternoon. Prefer time-boxed elevat