Skip to content

interdict/cloud

See what's misconfigured in AWS.

Give Interdict a read-only IAM role (connected with OIDC, so there are no long-lived keys to leak) and it checks your AWS account for the misconfigurations attackers look for first.

Clouds / AWS · eu-west-2

Read-only role
  • Root account has no MFACritical
  • S3 bucket readable by anyoneHigh
  • Security group opens port 22 to 0.0.0.0/0High
  • EC2 instance allows IMDSv1Medium
  • Access key unused for 90+ daysLow

Sample data.

What’s inside interdict/cloud

Identity & MFA checks

Root account and admin users without MFA, and access keys unused for 90+ days.

Public exposure

Public S3 buckets, public RDS databases and security groups open to the world.

Hardening

EC2 instances still on IMDSv1 and unencrypted RDS storage.

Monitoring gaps

GuardDuty switched off in a scanned region, and missing budget alerts.

Keyless connection

Connect with an IAM role and external ID. Interdict never asks for access keys.

Azure, Google Cloud & Kubernetes

Read-only Prowler checks for Azure subscriptions, Google Cloud projects and Kubernetes clusters (in-cluster agent or kubeconfig).