How It Works
Use IaC scanning to review security misconfigurations in infrastructure definitions before deployment. Run a scan with IaC enabled, then open Issues → IaC and check the affected resource, surrounding configuration, and recommended fix. Full scans use automated policy checks and review candidates in the context of related infrastructure files. PR scans use the code review agent to assess the change. Full-scan candidates whose validation could not finish remain informational. Review the finding’s evidence before deciding whether the resource needs a change.Supported Formats
Full-scan infrastructure checks cover definitions such as Terraform resources and Helm chart templates. The findings depend on the policy checks that apply to the files and resources in scope. For GitHub and GitLab workflow files and release settings, see CI/CD security.Misconfiguration Categories
Network & Access Control
- Overly permissive security groups (e.g.,
0.0.0.0/0ingress) - Missing network policies in Kubernetes
- Unrestricted port exposure
- Public-facing resources without access controls
Encryption & Data Protection
- Unencrypted storage volumes (EBS, S3, Azure Blob)
- Missing TLS/SSL configuration
- Unencrypted database connections
- Missing encryption at rest for managed services
Identity & Permissions
- Overly broad IAM policies (e.g.,
*resource access) - Missing least-privilege constraints
- Root/admin access without MFA requirements
- Service accounts with excessive permissions
Container Security
- Containers running as root
- Missing resource limits (CPU, memory)
- Privileged container mode enabled
- Missing security contexts in Kubernetes pods
- Images pulled without digest pinning
Logging & Monitoring
- Disabled audit logging
- Missing CloudTrail or equivalent
- Containers without health checks
- Missing log aggregation configuration
CI/CD Pipeline Security
Open Issues → CI/CD for workflow findings from code scans. To review pipeline controls, collection coverage, and release settings, use Assets → CI/CD security.Compliance
Use compliance evidence to include relevant IaC findings and scans in a control review.Scan Modes
Full Repository Scan
Full scans run infrastructure policy checks on the repository or partition in scope. The policy scanner reports high-severity matches for contextual review.PR Scan
The PR review analyzes changes and can read supporting files for context. IaC findings appear in Issues → IaC. Findings eligible for inline comments are posted when PR feedback is enabled.Remediation
Issues shows the affected file and finding status. When available, open the finding to review:- Description — what the misconfiguration is and why it matters.
- Severity — the level assigned to the reported risk.
- Affected resource — the specific file, resource type, and configuration block.
- Preconditions — deployment-context factors that affect whether the misconfiguration is actually exploitable. Examples include whether the resource is in a private subnet, whether organizational policies override the setting, or whether the configuration is only used in non-production environments. Each precondition cites evidence from configuration files when available.
- Remediation guidance — AI-generated recommendations for fixing the misconfiguration.
Configuration
IaC scanning is controlled through scanner settings with org/tag/repo-level inheritance:
Use scanner settings to check the effective configuration for a repository. To share findings, filter to IaC and export them from Issues.