What it shows
The number of findings and how it moved over time, then the findings by rule, by account and by resource, each with its severity, region and type and a ↗ to the resource in the AWS console. The rules today: resources without a tag the organization's tag policy asks for, or with a value it does not allow, or whose Environment tag disagrees with the name; security groups open to the internet on an admin port, or beyond HTTP and HTTPS, the default security group in use, and security groups used by nothing; private subnets routed to an internet gateway; S3 buckets public through their policy and databases publicly accessible; database storage, EBS volumes and caches not encrypted; databases without automated backups and production DynamoDB tables without point-in-time recovery; EBS volumes attached to nothing or still on gp2, and Elastic IPs associated with nothing; ECR repositories without a lifecycle policy; instances that allow IMDSv1; instances on an operating system past its end of life or whose support ends soon, on a deprecated image, on an image older than 90 days, or on an image that no longer exists; EKS clusters on a version in extended support, or with their API endpoint open to the internet.
A finding of severity fail (an admin port open to the internet, a public bucket, a public database, an operating system past its end of life) also raises an alert, to the operators and to the companies that turned alerts on. A warning is only listed here.
Questions it answers
- Which EC2 instances still allow IMDSv1, and in which accounts?
- Which volumes are attached to nothing, and which Elastic IPs are idle?
- Which EKS clusters are in extended support and paying six times the control plane price?
- Which resources are missing the tags our tag policy requires?
What it reads
Once a day, right after the inventory of the AWS resources report is read through the read-only role, every resource is checked against the rules. Nothing is probed from outside and nothing is changed. Counts are per day, so stepping the page back shows what the rules found on that day.
What to do with it
Fix the fails first; they also reach you as alerts. Then take one rule at a time across all accounts: a day of IMDSv1 fixes, a day of gp2 volumes, a day of tags. Several of the rules carry money as well as risk, and the savings recommendations price them: unattached volumes, idle addresses, gp2 and extended support. What anyone on the internet can actually reach, rather than what a rule flags, is in Internet exposure.
Related reports
- AWS resources: Every resource the inventory found, with its cost, by type and by its Environment and Team tags.
- Internet exposure: What anyone on the internet can reach: open ports, load balancers, public buckets, and snapshots and images shared with everyone.
- AWS savings recommendations: Changes that would cut the bill, priced per month, largest first, and what the changes made so far save.
- Executive summary: Where AWS stands, for every account, on one page: the run rate as a month, the savings still open and those made, what AWS Health has open or coming up, and what fails the infrastructure rules.
The hosted plan has every report, and is free during early access: see pricing. Like every report, this one splits and filters by account, environment, service and resource, steps back 13 months, downloads as PDF and CSV and keeps the view in its link: what every report does. All reports.