An Okta Workflows Automation must disable inactive user accounts. The automation must be ACTIVE, on an ACTIVE schedule, evaluate User Inactivity = 35 days (or less), apply to a group covering every user, and trigger Suspended / Deactivated / Deprovisioned. Threshold override: okta_user_inactivity_max_days. N/A when user sourcing is delegated to Active Directory or LDAP.
Risk
Inactive Okta accounts retained indefinitely give an attacker who exploits one undetected access to downstream applications.
- Account takeover via dormant identities that no one is monitoring
- Lateral movement through SSO sessions of forgotten users
- Stale entitlements that survive role and policy reorganisations
prowler okta --checks user_inactivity_automation_35d_enabled
Recommendation
Create an active Okta Workflows automation that runs daily, evaluates User Inactivity in Okta = 35 days, applies to a group covering every user, and changes the user lifecycle state to Suspended/Deactivated. If user sourcing is delegated to Active Directory or LDAP, document that the connected directory enforces this requirement instead.
Remediation
- Sign in to the Okta Admin Console as a Super Admin.
- Navigate to Workflow > Automations and click Add Automation.
- Name the automation (e.g.,
User Inactivity). - Add a condition: select User Inactivity in Okta and enter
35days. - Configure the schedule to run daily and activate it.
- Apply the automation to a group that covers every user — typically
Everyone. - Add an action: Change User lifecycle state in Okta and choose
Suspended(orDeactivated/Deprovisioned). - Activate the automation.
Source Code
Resource Type
NotDefined