InfraScan Cloud

Repository scan

wellcomecollection.org

wellcomecollection/wellcomecollection.org · branch main · scanned 25 Jun 2026 · 82 resources

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

Medium 226

Medium Ensure Terraform module sources use a commit hash Security · 45 places
Medium Ensure every security group and rule has a description Security · 9 places
Medium Missing Cost and Usage Report Cost · 9 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 CloudFront distribution has a response headers policy attached Security · 7 places
Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 7 places
Medium Ensure CloudFront distributions should have origin failover configured Security · 7 places
Medium Ensure AWS CloudFront web distribution has geo restriction enabled Security · 7 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 6 places
Medium Ensure that S3 bucket has a Public Access block Security · 5 places
Medium Ensure S3 buckets should have event notifications enabled Security · 5 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 5 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 5 places
Medium Ensure the S3 bucket has access logging enabled Security · 5 places
Medium Ensure CloudFront distribution has a default root object configured Security · 5 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 4 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 inside a VPC Security · 4 places
Medium Ensure that ECR repositories are encrypted using KMS Security · 4 places
Medium Ensure ECR image scanning on push is enabled 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 X-Ray tracing is enabled for Lambda Security · 4 places
Medium Ensure ECR Image Tags are immutable Security · 4 places
Medium Ensure public facing ALB are protected by WAF Security · 3 places
Medium Ensure WAF2 has a Logging Configuration Security · 3 places
Medium Ensure that Security Groups are attached to another resource Security · 3 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 3 places

Ensure Secrets Manager secrets should have automatic rotation enabled

Documentation

Where

Medium Ensure AWS Load Balancers use strong ciphers Security · 3 places
Medium Ensure that load balancer is using at least TLS 1.2 Security · 3 places
Medium Ensure that ALB drops HTTP headers Security · 3 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 3 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 3 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 3 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 3 places
Medium Ensure container insights are enabled on ECS cluster Security · 3 places
Medium CloudFront Distribution should have WAF enabled Security · 3 places
Medium Ensure CloudFront distribution has Access Logging enabled Security · 3 places
Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 3 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 2 places

Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)

Documentation

Where

Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 2 places

and 10 more groups with 14 findings

Low 9

Low Missing AWS Budget Cost · 9 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.