CyberKit

Infrastructure-as-Code Scanning

Also called IaC scanning.

Checking infrastructure definitions for insecure settings before deployment.

What it is

The static analysis of infrastructure-as-code templates and manifests to catch insecure settings, such as public access or disabled encryption, before they are provisioned. It shifts configuration security left into the development pipeline.

Why it matters

Catching misconfiguration in the definition stops it from ever reaching production, and the code history also tells responders when and how a weakness was introduced.

In practice

A pull-request scan blocks a template that would have created a public bucket, the same class of mistake behind a prior leak.

What to look for

  • Templates with public buckets, open security groups or disabled encryption.
  • Hardcoded secrets in Terraform, CloudFormation or manifests.
  • Suppressed findings with no reason recorded.

Common mistake

Scanning code but never comparing it with what is deployed. Manual console changes drift away from the code.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Amazon GuardDuty Cloud service

    AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.

  • Microsoft Defender for Cloud Commercial

    Posture and threat protection for Azure, AWS and Google Cloud.

  • Wiz Commercial

    Maps cloud resources, identities and exposures into one graph of risk.

  • Prowler Open source

    An open source tool that checks cloud accounts against benchmarks such as CIS.

Read next

Sources