Aikido

Scan and catch IaC misconfigurations early

Scan every Terraform, CloudFormation, and Helm change for critical misconfigurations.

Your data won't be shared · Read-only access · No CC required
Trusted by 50k+ orgs
|
Loved by 100k+ devs
|
4.7/5
Infrastructure as Code Scanning

Why IaC scanning matters

Infrastructure as Code (IaC) scanning is crucial because it shifts security to the start of development. It checks your infrastructure definition scripts (Terraform, CloudFormation, Helm, etc.) for misconfigurations before they provision your cloud resources.

CI/CD integration

By integrating Aikido into your CI/CD pipeline, IaC misconfigurations are identified before they reach your main branch.

Only shows security issues

Shows only misconfigurations that pose a security risk, so you aren’t overwhelmed by noise.

Features

Aikido's IaC features

Also scans dockerfiles

By scanning dockerfiles Aikido is able to, for example, already detect imdsv1 instances that are SSRF sensitive in AWS.

AI Autofix for IaC (& SAST)

Save time using Aikido’s LLM-based autofix. Preview the proposed solution, and generate a PR with a single click.

Scans production environment

IaC scans your code pre-deployment. Do you want to secure your production environment? Check our CSPM Scanner.

“Aikido is used by different departments (Dev teams, infra, CISO) to view our security posture. This improves security awareness as well as helps us to place the right priorities to solve issues”

Patrick LCISO at HRlinkIT

GEA switched from Sonarqube to Aikido
No items found.
Faq

FAQs about IaC scanning

What is Infrastructure-as-Code (IaC) scanning, and why should I scan my Terraform or CloudFormation code for security issues?

IaC scanning analyzes your infrastructure code (e.g., Terraform, CloudFormation, Kubernetes YAML) for misconfigurations before deployment. It helps catch issues like open S3 buckets or weak firewall rules early in the dev cycle. Fixing them in code is far easier than after they're live. Scanning ensures your cloud is secure by design - no surprises in production.

What kinds of misconfigurations can Aikido's IaC scanner catch (for example, open S3 buckets or overly permissive security groups)?

Aikido flags public storage buckets, overly open security groups (e.g., 0.0.0.0/0), unencrypted databases, excessive IAM permissions, and public VMs. It checks your code against best practices to catch common and critical misconfigs before deployment.

Which IaC frameworks does Aikido support (Terraform, CloudFormation, Kubernetes manifests, Helm charts, etc.)?

Aikido supports Terraform, CloudFormation, Kubernetes manifests, Helm charts, Azure ARM/Bicep templates, and more. Whether you use HCL, YAML, or JSON, Aikido can scan it for risks. Pulumi support is coming soon.

Can Aikido automatically fix or suggest fixes for issues found in my IaC configuration files?

Yes. Aikido suggests best-practice fixes and can auto-generate code patches or pull requests. For example, it can fix open security groups or missing encryption with one click. The fix will be available as a PR/MR for you to review and merge.

How do I integrate Aikido's IaC scanning into my development workflow or CI/CD pipeline?

You can integrate Aikido into CI/CD tools (GitHub Actions, GitLab, Jenkins, etc.), pre-commit hooks, or IDEs. Scans run automatically on commits or PRs and can block misconfigurations before merge or deploy.

Is Aikido's IaC scan fast enough for CI use? Will it slow down my Terraform apply or build pipeline?

Yes, it's fast and CI-friendly. Scans typically take seconds and don't interfere with Terraform apply. Even large projects complete quickly, making it practical for everyday use.

How does Aikido's IaC scanning compare to tools like Bridgecrew (Checkov) or Snyk IaC?

Aikido offers similar coverage but integrates with your full security stack. It reduces noise, auto-suggests fixes, and correlates IaC issues with running cloud resources. Unlike using multiple tools, it's all in one platform.

Can I define custom policies or rules for IaC checks in Aikido to fit our internal best practices?

Yes. You can create custom rules - e.g., "S3 buckets must have logging" or "disallow region X." Aikido supports flexible policy controls so your scans reflect your internal security standards.

If the IaC scanner flags something I consider acceptable, can I override it or prevent it from blocking deployments?

You can mark findings as ignored, accepted risk, or false positive. You can also customize rules to avoid blocking your CI/CD pipeline for intentional configs.

What if Aikido's IaC scanner reports a false positive or flags an intended config? How do I handle that?

You can adjust severity, add code annotations, or use config files to suppress specific checks. Aikido is built to adapt to your environment and reduce friction - not to block intended workflows.

Secure your cload configurations today

Secure your code, cloud, and runtime in one central system.
Find and fix vulnerabilities fast automatically.