Least privilege
Standing access shouldn’t stay standing.
Timed access for high-risk resources. Drift handling for when reality diverges from intent. Access reviews that actually close. Revocation that runs through the same provisioning pipeline as the original grant.
Timed access → expiry → revoke
Expiring access row reaching its expiry, followed by the execution journal showing the revocation step.
Four mechanics. One pipeline.
Timed access.
High-risk resources can be configured to expire by default. Access revokes automatically at expiry.
Drift handling.
Sync observes what’s actually granted downstream. When reality diverges from intent, policy decides: adopt, flag, ignore, or enforce.
Access reviews.
Certification campaigns with reviewer accountability and exportable evidence. Where remediation is set to automatic, revoke decisions flow through the provisioning pipeline.
Accountable revocation.
Every revocation is a versioned provisioning operation with a step-by-step journal. When a review decision would be undone by automation recreating the access, Owlie holds that revoke until the source is addressed — so “revoked” means actually revoked, with evidence.
What least privilege usually looks like.
Manual least-privilege programs often depend on quarterly spreadsheets and email follow-up. A decision to remove access can remain unresolved unless someone tracks the removal.
In Owlie, review decisions can trigger revocations, drift is handled by policy, and timed access expires automatically.
One grant, one expiry, one journal.
A sensitive resource — production database write access — is configured with 5-hour timed access and a Function-backed approval policy. An engineer requests it during an outage. The Function checks their on-call schedule and auto-approves. Access is granted.
At expiry, Owlie revokes the access automatically. The next sync run confirms the revocation happened downstream. Evidence lives in the execution journal. No one has to remember to clean up.
Timed access + expiry + revoke journal
The full lifecycle — request, approval, grant, expiry, revoke — with each step recorded in the execution journal.
Keep reading.
Security persona.
The Security-framed view of the same mechanics.
Access reviews.
Certification campaigns, reviewer accountability, exportable evidence.
Provisioning.
Intent-based, versioned. The pipeline that every grant and revoke runs through.
Governance model.
Drift handling, adopt/flag/ignore/enforce policies, sync semantics.
Put least-privilege controls into practice.
Sign up free. Bring a real high-risk resource and watch Owlie expire it on a timer, through the same pipeline as any other grant.