InfraScan Cloud

Repository scan

integration-adaptor-mhs

NHSDigital/integration-adaptor-mhs · branch main · scanned 25 Jun 2026 · 359 resources

DOverall
DSecurity
–Reliability · N/A
CCost
214findings · 0 critical, 1 high
$231–$372estimated savings per month, from the code

High 1

High Expensive NAT Gateway Cost · 1 place

NAT Gateways are expensive managed services. Ensure they are strictly necessary.

How to fix

Consider using VPC Endpoints, NAT Instances for non-critical workloads, or share a single NAT Gateway across multiple subnets.

Where

Medium 210

Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 11 places
Medium Ensure that a user for the container has been created Security · 10 places
Medium The default namespace should not be used Security · 10 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 7 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 7 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 7 places
Medium Ensure that CloudWatch Log Group specifies retention days Security · 7 places
Medium CloudWatch Logs Without Retention Cost · 7 places

CloudWatch log group without retention_in_days. Logs are kept indefinitely by default, silently growing to hundreds $/month.

How to fix

Set appropriate retention periods for log groups (e.g., 7, 14, or 30 days).

Where

Medium Load Balancer for Single Instance Cost · 7 places
Medium Ensure that ALB drops HTTP headers Security · 5 places
Medium Ensure that key vault secrets have "content_type" set Security · 5 places
Medium Ensure that the expiration date is set on all secrets Security · 5 places
Medium Ensure that Auto Scaling is enabled on your DynamoDB tables Security · 4 places
Medium Ensure VNET subnet is configured with a Network Security Group (NSG) Security · 4 places
Medium Ensure top-level permissions are not set to write-all Security · 4 places

Ensure top-level permissions are not set to write-all

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK Security · 4 places
Medium Ensure DynamoDB point in time recovery (backup) is enabled Reliability · 4 places
Medium Ensure ECS Fargate services run on the latest Fargate platform version Security · 3 places
Medium Private Key Security · 3 places
Medium Missing Cost and Usage Report Cost · 3 places

No AWS Cost and Usage Report (CUR) configured. CUR provides detailed cost tracking and analysis.

How to fix

Enable AWS Cost and Usage Reports to track spending patterns and identify optimization opportunities.

Where

Medium Ensure VPC flow logging is enabled in all VPCs Security · 2 places
Medium Ensure the default security group of every VPC restricts all traffic Security · 2 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 2 places
Medium Ensure S3 buckets should have event notifications enabled Security · 2 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 2 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 2 places
Medium Ensure the S3 bucket has access logging enabled Security · 2 places
Medium Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK) Security · 2 places

Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK)

Documentation

Where

Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 2 places
Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token Security · 2 places

Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token

Documentation

Where

Medium Ensure that Network Interfaces don't use public IPs Security · 2 places
Medium Ensure Virtual Machine Extensions are not Installed Security · 2 places
Medium Ensure that the global security field has rules defined Security · 2 places

Ensure that the global security field has rules defined

Documentation

Where

Medium Ensure that security operations is not empty. Security · 2 places

Ensure that security operations is not empty.

Documentation

Where

Medium Missing S3 Lifecycle Policy Cost · 2 places

S3 bucket without lifecycle rules. Objects are retained indefinitely, increasing storage costs.

How to fix

Define lifecycle rules to transition objects to cheaper storage classes (e.g., Glacier) or delete them after a retention period.

Where

Medium Expensive Premium Storage Cost · 2 places

Using premium storage tiers (Premium_LRS, io1, io2) which are significantly more expensive.

How to fix

Evaluate if Standard storage or gp3 volumes meet performance requirements. Premium storage should only be used when necessary.

Where

Medium Ensure that ALB redirects HTTP requests into HTTPS ones Security · 1 place

Ensure that ALB redirects HTTP requests into HTTPS ones

Documentation

Where

Medium Ensure storage for critical data are encrypted with Customer Managed Key Security · 1 place

Ensure storage for critical data are encrypted with Customer Managed Key

Documentation

Where

Medium Ensure Storage logging is enabled for Blob service for read requests Security · 1 place

Ensure Storage logging is enabled for Blob service for read requests

Documentation

Where

Medium Ensure private endpoint is configured to key vault Security · 1 place

Ensure private endpoint is configured to key vault

Documentation

Where

and 57 more groups with 57 findings

Low 3

Low Missing AWS Budget Cost · 3 places

No AWS budget configured. Budgets help monitor and control spending with alerts.

How to fix

Create AWS budgets with alerts for forecasted and actual costs to avoid unexpected charges.

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 25 Jun 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.