InfraScan Cloud

Repository scan

cloud-platform-infrastructure

ministryofjustice/cloud-platform-infrastructure · branch main · scanned 10 Feb 2026 · 237 resources

FOverall
FSecurity
–Reliability · N/A
DCost
249findings · 0 critical, 20 high
—no cost findings with a savings estimate

High 20

High Missing AWS Budget Cost · 14 places
High Unencrypted EBS Volume Cost · 4 places
High Provisioned IOPS (io1/io2) Cost · 2 places

Usage of Provisioned IOPS SSD (io1/io2). These are very expensive.

How to fix

Verify if gp3 can meet performance requirements at a lower cost.

Where

Medium 225

Medium Ensure Terraform module sources use a commit hash Security · 86 places

Ensure Terraform module sources use a commit hash

Documentation

Where

Medium Missing Cost and Usage Report Cost · 14 places
Medium Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones Security · 10 places
Medium Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones Security · 10 places
Medium AWS SSM Parameter should be Encrypted Security · 6 places
Medium Ensure no IAM policies documents allow ALL or any AWS principal permissions to the resource Security · 6 places
Medium Missing Spot Instance Usage Cost · 6 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 5 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 5 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 4 places
Medium Ensure that Elasticsearch is configured inside a VPC Security · 4 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 4 places
Medium Ensure that Elasticsearch is not using the default Security Group Security · 4 places
Medium Ensure Elasticsearch Domain Audit Logging is enabled Security · 4 places
Medium Ensure Elasticsearch domains are configured with at least three dedicated master nodes for HA Security · 4 places
Medium Ensure WAF2 has a Logging Configuration Security · 3 places
Medium Ensure KMS key Policy is defined Security · 3 places
Medium Ensure WAF prevents message lookup in Log4j2. See CVE-2021-44228 aka log4jshell Security · 3 places
Medium Ensure SSM parameters are using KMS CMK Security · 3 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 3 places
Medium Ensure rotation for customer created CMKs is enabled Security · 3 places
Medium Ensure Elasticsearch Domain Logging is enabled Security · 3 places
Medium Ensure that Security Groups are attached to another resource Security · 2 places
Medium Ensure IAM policies does not allow write access without constraints Security · 2 places
Medium Ensure access is controlled through SSO and not AWS IAM defined users Security · 2 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 2 places
Medium Ensure IAM policies are attached only to groups or roles (Reducing access management complexity may in-turn reduce opportunity for a principal to inadvertently receive or retain excessive privileges.) Security · 2 places

Ensure IAM policies are attached only to groups or roles (Reducing access management complexity may in-turn reduce opportunity for a principal to inadvertently receive or retain excessive privileges.)

Documentation

Where

Medium Ensure that Auto Scaling is enabled on your DynamoDB tables Security · 1 place

Ensure that Auto Scaling is enabled on your DynamoDB tables

Documentation

Where

Medium Ensure AWS ElasticSearch/OpenSearch Fine-grained access control is enabled Security · 1 place

Ensure AWS ElasticSearch/OpenSearch Fine-grained access control is enabled

Documentation

Where

Medium Ensure access control lists for S3 buckets are disabled Security · 1 place

Ensure access control lists for S3 buckets are disabled

Documentation

Where

Medium Ensure IAM policies does not allow credentials exposure Security · 1 place
Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 1 place

Ensure IAM policies does not allow permissions management / resource exposure without constraints

Documentation

Where

Medium Ensure IAM policies does not allow privilege escalation Security · 1 place
Medium Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK Security · 1 place

Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK

Documentation

Where

Medium Ensure S3 bucket Object is encrypted by KMS using a customer managed Key (CMK) Security · 1 place

Ensure S3 bucket Object is encrypted by KMS using a customer managed Key (CMK)

Documentation

Where

Medium Verify Elasticsearch domain is using an up to date TLS policy Security · 1 place

Verify Elasticsearch domain is using an up to date TLS policy

Documentation

Where

Medium Ensure every security group and rule has a description Security · 1 place

Ensure every security group and rule has a description

Documentation

Where

Medium Ensure all data stored in the Elasticsearch is encrypted with a CMK Security · 1 place

Ensure all data stored in the Elasticsearch is encrypted with a CMK

Documentation

Where

Medium Ensure DynamoDB point in time recovery (backup) is enabled Reliability · 1 place

Ensure DynamoDB point in time recovery (backup) is enabled

Documentation

Where

Medium Ensure all data stored in the Elasticsearch is securely encrypted at rest Security · 1 place

Ensure all data stored in the Elasticsearch is securely encrypted at rest

Documentation

Where

and 9 more groups with 9 findings

Low 4

Low Large Root Volume Cost · 4 places

Oversized root block device. Many workloads don't require large root volumes.

How to fix

Reduce root volume size to minimum required (typically 8-20 GB for most Linux instances).

Where

Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 10 Feb 2026; it may have changed since.

Scan your own repository

InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.