InfraScan Cloud

Repository scan

orphaned-record-continuity-infrastructure

NHSDigital/orphaned-record-continuity-infrastructure · branch main · scanned 10 Feb 2026 · 1,022 resources

DOverall
FSecurity
–Reliability · N/A
CCost
426findings · 0 critical, 17 high
—no cost findings with a savings estimate

High 17

High Missing AWS Budget Cost · 16 places
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 407

Medium AWS SSM Parameter should be Encrypted Security · 74 places
Medium Ensure every security group and rule has a description Security · 29 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 28 places
Medium Ensure IAM policies does not allow write access without constraints Security · 24 places
Medium Missing Cost and Usage Report Cost · 16 places
Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 15 places
Medium Ensure that ECR repositories are encrypted using KMS Security · 14 places
Medium Ensure ECR image scanning on push is enabled Security · 14 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 12 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 12 places
Medium Ensure that CloudWatch Log Group specifies retention days Security · 12 places
Medium Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances Security · 9 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 9 places
Medium Ensure S3 buckets should have event notifications enabled Security · 9 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 9 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 9 places
Medium Load Balancer for Single Instance Cost · 7 places
Medium Ensure that Security Groups are attached to another resource Security · 6 places
Medium Ensure NACL ingress does not allow all Ports Security · 6 places
Medium Ensure that ALB redirects HTTP requests into HTTPS ones Security · 5 places
Medium Ensure that load balancer is using at least TLS 1.2 Security · 5 places
Medium Ensure ALB protocol is HTTPS Security · 5 places
Medium Ensure Create before destroy for ACM certificates Security · 5 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 4 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 4 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 4 places
Medium Check encryption settings for Lambda environmental variable Security · 4 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 4 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 4 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 4 places
Medium X-Ray tracing is enabled for Lambda Security · 4 places
Medium Missing S3 Lifecycle Policy Cost · 4 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 Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones Security · 3 places

Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones

Documentation

Where

Medium Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones Security · 3 places

Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones

Documentation

Where

Medium Ensure the S3 bucket has access logging enabled Security · 3 places
Medium Ensure Terraform module sources use a commit hash Security · 3 places
Medium Ensure that all NACL are attached to subnets Security · 2 places
Medium Ensure that Auto Scaling is enabled on your DynamoDB tables Security · 2 places

Ensure that Auto Scaling is enabled on your DynamoDB tables

Documentation

Where

Medium Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK Security · 2 places

Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK

Documentation

Where

Medium Disallow IAM roles, users, and groups from using the AWS AdministratorAccess policy Security · 2 places

and 15 more groups with 17 findings

Low 2

Low Elastic IP Usage Cost · 2 places

Elastic IPs are charged if not attached to a running instance or if you have more than one per instance.

How to fix

Release unattached Elastic IPs.

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.