Repository scan
provability-fabric
SentinelOps-CI/provability-fabric · branch main · scanned 25 Jun 2026 · 118 resources
High 3
High Expensive NAT Gateway
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
High Missing VPC Endpoints for S3/DynamoDB
NAT Gateway and S3/DynamoDB resources are present but no aws_vpc_endpoint is defined. All S3 and DynamoDB traffic is routed through the NAT Gateway, incurring per-GB data-processing charges ($0.045/GB).
How to fix
Add Gateway VPC Endpoints for S3 (com.amazonaws.<region>.s3) and DynamoDB (com.amazonaws.<region>.dynamodb). Gateway endpoints are free and eliminate NAT data-processing charges for these services.
Where
Medium 210
Medium Ensure top-level permissions are not set to write-all
Ensure top-level permissions are not set to write-all
How to fix
See Checkov documentation for remediation guidance.
Where
- ../../.github/workflows/ci-nightly-pytest.yml
- ../../.github/workflows/dfa.yaml
- ../../.github/workflows/sbom-diff.yaml
- ../../.github/workflows/lean-offline.yaml
- ../../.github/workflows/dr-cross.yaml
- ../../.github/workflows/chaos-nightly.yaml
- ../../.github/workflows/revocation-sync.yaml
- ../../.github/workflows/lean-style.yaml
- ../../.github/workflows/evidence.yaml:53
- ../../.github/workflows/privacy-test.yaml
- ../../.github/workflows/reusable-ci-rust.yml
- ../../.github/workflows/pf-reusable-caller.yaml
- ../../.github/workflows/billing-test.yaml
- ../../.github/workflows/paper-conformance.yaml
- ../../.github/workflows/spec-ai.yaml
- ../../.github/workflows/pf-cross-repo-consumer.yaml
- ../../.github/workflows/standards-pin.yml
- ../../.github/workflows/proof-fuzz.yaml
- ../../.github/workflows/performance-gate.yaml
- ../../.github/workflows/platform-replay.yml
- and 50 more
Medium Ensure that HEALTHCHECK instructions have been added to container images
Ensure that HEALTHCHECK instructions have been added to container images
Where
- ../../services/proof-service/Dockerfile:1
- ../../runtime/admission-controller/Dockerfile:1
- ../../services/build-orchestrator/Dockerfile:1
- ../../runtime/jwks-manager/Dockerfile:1
- ../../console/Dockerfile:1
- ../../adapters/alpha-beta-crown/Dockerfile:1
- ../../services/api-gateway/Dockerfile:1
- ../../runtime/sidecar-watcher/Dockerfile:1
- ../../runtime/ledger/Dockerfile:1
- ../../runtime/telemetry-service/Dockerfile:1
- ../../recipes/saas-egress-guard/saas-app/Dockerfile:1
- ../../services/replay-service/Dockerfile:1
- ../../services/evidence-service/Dockerfile:1
- ../../services/spec-service/Dockerfile:1
Medium The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty.
The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty.
How to fix
See Checkov documentation for remediation guidance.
Where
- ../../.github/workflows/dr-cross.yaml:12
- ../../.github/workflows/evidence.yaml:12
- ../../.github/workflows/lean-morph.yml:6
- ../../.github/workflows/performance-gate.yaml:19
- ../../.github/workflows/morph-replay.yml:6
- ../../.github/workflows/edge-load.yaml:9
- ../../.github/workflows/trust-fire-ga-test.yaml:12
- ../../.github/workflows/operational-excellence.yaml:16
- ../../.github/workflows/incident-e2e.yaml:6
- ../../.github/workflows/multiarch-build.yaml:14
- ../../.github/workflows/release.yaml:12
Medium Ensure that a user for the container has been created
Ensure that a user for the container has been created
Where
- ../../services/proof-service/Dockerfile:1
- ../../runtime/admission-controller/Dockerfile:1
- ../../services/build-orchestrator/Dockerfile:1
- ../../console/Dockerfile:1
- ../../adapters/alpha-beta-crown/Dockerfile:1
- ../../services/api-gateway/Dockerfile:1
- ../../recipes/saas-egress-guard/saas-app/Dockerfile:1
- ../../services/replay-service/Dockerfile:1
- ../../services/evidence-service/Dockerfile:1
- ../../services/spec-service/Dockerfile:1
Medium Ensure VPC subnets do not assign public IP by default
Ensure VPC subnets do not assign public IP by default
Where
Medium Ensure every security group and rule has a description
Ensure every security group and rule has a description
Where
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Where
Medium Ensure the base image uses a non latest version tag
Ensure the base image uses a non latest version tag
Where
Medium Ensure VPC flow logging is enabled in all VPCs
Ensure VPC flow logging is enabled in all VPCs
Where
Medium Ensure the default security group of every VPC restricts all traffic
Ensure the default security group of every VPC restricts all traffic
Where
Medium Ensure that S3 bucket has a Public Access block
Ensure that S3 bucket has a Public Access block
Where
Medium Ensure RDS instance with copy tags to snapshots is enabled
Ensure RDS instance with copy tags to snapshots is enabled
Where
Medium Ensure that an S3 bucket has a lifecycle configuration
Ensure that an S3 bucket has a lifecycle configuration
Where
Medium Ensure S3 buckets should have event notifications enabled
Ensure S3 buckets should have event notifications enabled
Where
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances
Ensure that enhanced monitoring is enabled for Amazon RDS instances
Where
Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled
Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled
Where
Medium Ensure that S3 buckets are encrypted with KMS by default
Ensure that S3 buckets are encrypted with KMS by default
Where
Medium Ensure that RDS instances have Multi-AZ enabled
Ensure that RDS instances have Multi-AZ enabled
Where
Medium Ensure RDS database has IAM authentication enabled
Ensure RDS database has IAM authentication enabled
Where
Medium Ensure the S3 bucket has access logging enabled
Ensure the S3 bucket has access logging enabled
Where
Medium Ensure DB instance gets all minor upgrades automatically
Ensure DB instance gets all minor upgrades automatically
Where
Medium Ensure that RDS instances have performance insights enabled
Ensure that RDS instances have performance insights enabled
Where
Medium Ensure Postgres RDS as aws_db_instance has Query Logging enabled
Ensure Postgres RDS as aws_db_instance has Query Logging enabled
Where
Medium Ensure public facing ALB are protected by WAF
Ensure public facing ALB are protected by WAF
Where
Medium Ensure that Security Groups are attached to another resource
Ensure that Security Groups are attached to another resource
Where
Medium Ensure that ALB drops HTTP headers
Ensure that ALB drops HTTP headers
Where
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80
Ensure no security groups allow ingress from 0.0.0.0:0 to port 80
Where
Medium Ensure the ELBv2 (Application/Network) has access logging enabled
Ensure the ELBv2 (Application/Network) has access logging enabled
Where
Medium Missing S3 Lifecycle Policy
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 Missing Cost and Usage Report
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 Load Balancer for Single Instance
Load balancer detected. Verify it's needed - load balancers cost $15-20/month even if unused.
How to fix
Consider if load balancer is necessary for single-instance deployments or low-traffic applications.
Where
Medium Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones
Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones
Where
Medium Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones
Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones
Where
Medium Ensure that RDS instances has backup policy
Ensure that RDS instances has backup policy
Where
Medium Ensure that AWS database instances have deletion protection enabled
Ensure that AWS database instances have deletion protection enabled
Where
Medium Basic Auth Credentials
Medium Multiple NAT Gateways (Potential Redundancy)
More than one aws_nat_gateway defined. In development or staging environments a single NAT Gateway is usually sufficient; multiple gateways add ~$32/month each plus data-processing fees.
How to fix
Verify that each additional NAT Gateway is needed for HA in production. For dev/staging environments consider consolidating to a single gateway.
Where
- ops/terraform/regions/networking.tf:125 $17.96 / mo
Low 6
Low Route53 Health Checks
Route53 health checks incur monthly costs. May not be necessary for all resources.
How to fix
Remove health checks for non-critical resources or personal projects.
Where
- ops/terraform/regions/cross-region-dr.tf:159 $0.50 / mo
- ops/terraform/regions/cross-region-dr.tf:173 $0.50 / mo
- ops/terraform/regions/main.tf:401 $0.50 / mo
- ops/terraform/regions/main.tf:414 $0.50 / mo
Low Missing AWS Budget
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.