Skip to main content
Checks that AWS GuardDuty is enabled for threat detection.

​
About

When you connect Amazon Web Services (AWS) to DSALTA, the platform retrieves the current security findings using read-only API access. DSALTA tracks their status and activates this check when action is required.

​
Why This Matters

Open security findings represent active or potential threats sitting in your environment. The longer they stay unresolved, the longer your exposure window. Detecting and closing findings promptly is required by the incident-response controls in SOC 2 and ISO 27001.

​
How to Fix

Before you begin
  • Ensure you have Admin access to the AWS account.
Enable GuardDuty
  1. Sign in to the AWS Console and navigate to GuardDuty.
  2. Click Get Started, then Enable GuardDuty.
  3. (Recommended) Enable GuardDuty across all regions and accounts in your organization.
Once GuardDuty is enabled, 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).