Attack Chain

1. A user attempts to access a protected application integrated with Okta.
2. Okta evaluates the user’s authentication status and group memberships against the application’s access policies.
3. The user lacks the necessary permissions or roles assigned to access the requested application.
4. Okta denies access to the application for the user.
5. Okta generates a system log event with the “User attempted unauthorized access to app” message.
6. The security monitoring system ingests the Okta log event.
7. The detection rule triggers based on the specific log message.
8. An alert is generated, prompting security analysts to investigate the unauthorized access attempt and take appropriate remedial actions.

Impact

Successful unauthorized access to applications can lead to significant data breaches, compromise sensitive information, and disrupt business operations. While this detection identifies attempted unauthorized access, repeated attempts or eventual success due to misconfiguration can result in severe consequences. A single successful breach can lead to data exfiltration, financial loss, and reputational damage. Identifying and remediating these attempts is crucial to preventing these outcomes.

Recommendation

• Deploy the provided Sigma rule to your SIEM or security monitoring platform to detect unauthorized application access attempts in Okta (Sigma rule: “Okta Unauthorized Access to App”).
• Investigate all triggered alerts promptly to determine the root cause of the unauthorized access attempt (Okta logs).
• Review and validate application access policies within Okta to ensure users have appropriate permissions and roles assigned.
• Implement multi-factor authentication (MFA) for all users to reduce the risk of compromised accounts being used for unauthorized access (Okta configuration).
• Monitor Okta system logs for related events, such as account lockouts or password reset attempts, which might indicate account compromise (Okta logs).