Skip to main content
Checks that AWS credentials unused for 90+ days are disabled.

​
About

When you connect Amazon Web Services (AWS) to DSALTA, the platform syncs your users, roles, and access settings using read-only API access. DSALTA evaluates this control on every sync. If the requirement is not met, DSALTA activates this check.

​
Why This Matters

Stale, unused, or overly powerful credentials are a primary attack vector. Rotating and removing them limits how much damage a compromised key can do — a core hygiene control in SOC 2 and the CIS Benchmarks.

​
How to Fix

Before you begin
  • Ensure you have IAM admin permissions in the AWS account.
Rotate or disable stale credentials
  1. Sign in to the AWS Console and navigate to IAM → Users → Credential report (download it).
  2. Identify access keys older than 90 days or unused for 90+ days.
  3. Create a replacement key, update your applications, then deactivate and later delete the old key.
Once stale credentials are rotated or disabled, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Amazon Web Services (AWS) integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Amazon Web Services (AWS).