Ensure customer secret keys are rotated within 90 days
Customer secret keys used for S3-compatible access should be rotated regularly.
Security Impact
Stale secret keys may be exposed in logs or configurations.
How to Remediate
Create new secret keys and update applications. Delete old keys.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your Oracle Cloud environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Oracle Cloud Identity and Access Management resources across your Oracle Cloud tenancies every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for CIS OCI v1.2.0, SOC 2, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- oracle-iam-4
- Service
- Oracle Cloud Identity and Access Management
- Category
- Credential Management
- Severity
- MEDIUM
- CIS Benchmark
- 1.4
Automate This Check
TigerGate automatically scans your Oracle Cloud environment for this and 50+ other security checks.
Start Free TrialRelated Oracle Cloud Identity and Access Management Checks
View all checksEnsure MFA is enabled for all IAM users
Ensure API keys are rotated within 90 days
Ensure auth tokens are rotated within 90 days
Ensure IAM policies are not overly permissive
Ensure tenancy administrator group is restricted