InfraScan Cloud

Repository scan

cztack

chanzuckerberg/cztack · branch main · scanned 25 Jun 2026 · 421 resources

DOverall
FSecurity
–Reliability · N/A
BCost
254findings · 0 critical, 0 high
$36.10estimated savings per month, from the code

Medium 250

Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 21 places
Medium Ensure IAM policies does not allow write access without constraints Security · 18 places
Medium Ensure Terraform module sources use a commit hash Security · 16 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 8 places
Medium Ensure KMS key Policy is defined Security · 7 places
Medium Ensure S3 buckets should have event notifications enabled Security · 6 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 6 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 6 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 6 places
Medium X-Ray tracing is enabled for Lambda Security · 6 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 5 places
Medium Ensure every security group and rule has a description Security · 5 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 5 places
Medium Ensure rotation for customer created CMKs is enabled Security · 5 places
Medium Missing S3 Lifecycle Policy Cost · 5 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 that an S3 bucket has a lifecycle configuration Security · 4 places
Medium Ensure IAM policies does not allow data exfiltration Security · 4 places
Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 4 places
Medium Missing Cost and Usage Report Cost · 4 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 that Security Groups are attached to another resource Security · 3 places
Medium Ensure that S3 bucket has a Public Access block Security · 3 places
Medium Ensure the S3 bucket has access logging enabled Security · 3 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 3 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 3 places
Medium Ensure Lambda Runtime is not deprecated Security · 3 places
Medium Ensure that ALB redirects HTTP requests into HTTPS ones Security · 2 places

Ensure that ALB redirects HTTP requests into HTTPS ones

Documentation

Where

Medium Ensure public facing ALB are protected by WAF Security · 2 places
Medium Ensure CloudFront distribution has a response headers policy attached Security · 2 places

Ensure CloudFront distribution has a response headers policy attached

Documentation

Where

Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 2 places

Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability

Documentation

Where

Medium Ensure AWS API gateway request is validated Security · 2 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 2 places

Ensure Secrets Manager secrets should have automatic rotation enabled

Documentation

Where

Medium Ensure that load balancer is using at least TLS 1.2 Security · 2 places

Ensure that load balancer is using at least TLS 1.2

Documentation

Where

Medium Ensure that ALB drops HTTP headers Security · 2 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 2 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 2 places

Ensure that Load Balancer has deletion protection enabled

Documentation

Where

Medium Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher Security · 2 places

Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher

Documentation

Where

Medium Ensure ALB protocol is HTTPS Security · 2 places
Medium Ensure Kinesis Firehose delivery stream is encrypted Security · 2 places
Medium Ensure that Kinesis Firehose Delivery Streams are encrypted with CMK Security · 2 places

Ensure that Kinesis Firehose Delivery Streams are encrypted with CMK

Documentation

Where

Medium Ensure CloudFront distributions should have origin failover configured Security · 2 places

Ensure CloudFront distributions should have origin failover configured

Documentation

Where

and 53 more groups with 61 findings

Low 4

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