Okta must off-load audit records to a central log server. At least one Log Stream (AWS EventBridge, Splunk Cloud, etc.) must be configured and ACTIVE in the tenant. Alternatively, an external SIEM pulling the System Log API can satisfy the requirement, but that pull-based path is verified manually.
Risk
Audit records stored only inside the Okta tenant are exposed to accidental or incidental deletion or alteration.
- No central retention of authentication events for incident investigations
- Single point of failure for the audit trail
- No correlation with other identity, network, and endpoint telemetry in the SIEM
prowler okta --checks systemlog_streaming_enabled
Recommendation
Configure at least one ACTIVE Okta Log Stream that off-loads audit records to a central SIEM (AWS EventBridge, Splunk Cloud, or another supported destination). Document any alternative pull-based ingestion via the System Log API.
Remediation
- Sign in to the Okta Admin Console as a Super Admin.
- Navigate to Reports > Log Streaming.
- Click Add Log Stream and select AWS EventBridge, Splunk Cloud, or another supported destination.
- Complete the connection fields and save.
- Activate the stream and verify the destination receives events.
- If the destination SIEM is not natively supported, document the pull-based ingestion that uses the System Log API.
Source Code
Resource Type
NotDefined