code-review-iac
Security review of infrastructure-as-code — Terraform, CloudFormation, Ansible, Kubernetes/Helm manifests. Load when reviewing IaC in a repo/PR, on .tf/.yaml/.yml infra files, or "review our Terraform". Signals: *.tf, cloudformation/*.yaml, playbooks, k8s manifests, Helm charts, module registries.
v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/code-review-iacScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto7c4531b8…665cb1ee
7c4531b80fc6…2eed665cb1ee1 file · 1.8 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/code-review/code-review-iac@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
Reviewing the code that provisions cloud/infra. IaC misconfigurations become real, exploitable
exposure the moment they apply — a single line can make a bucket public or an SG world-open — so
this pairs directly with the offensive cloud-* skills.
Why it works
IaC is declarative and repeatable: the same insecure default gets deployed everywhere it's
referenced. Scanning the definitions catches the exposure before it exists, and the patterns
(public access, 0.0.0.0/0, plaintext secrets, missing encryption/logging) are consistent across
providers.
Sinks & patterns (scan, then reason about blast radius)
- Public exposure: S3/GCS/Blob
acl = "public-read"/ public access blocks disabled; security groups / firewall rules0.0.0.0/0on 22/3389/DB ports; public RDS/ELB;publiclyAccessible=true. - Over-broad IAM:
Action:"*"/Resource:"*",iam:PassRolewildcards,AssumeRoletrust to"*", admin-equivalent managed policies attached broadly. - Secrets in code: hardcoded keys/passwords/tokens in
.tf/vars/playbooks; secrets committed in state or plan output;sensitive = falseon secret outputs. - Missing protections: encryption at rest/in transit off (EBS/S3/RDS/SNS), logging/audit disabled (CloudTrail, flow logs, GCP audit), no MFA-delete/versioning, public snapshots/AMIs.
- Kubernetes/Helm:
privileged: true,hostNetwork/hostPID, nosecurityContext/runAsNonRoot, wide RBAC (cluster-admin), secrets as env/plaintext,latestimages, no network policies. - Ansible:
shell/commandwith unquoted vars,no_logmissing on secret tasks, world-readable file modes,validate_certs: no.
Method
- Run
checkov/tfsec/kicsfor a broad first pass; they cover hundreds of provider rules. rg '0.0.0.0/0|public|Action.*\*|password|secret|privileged: true'and review each hit's context.- Trace module inputs/variables — an insecure default in a reused module multiplies everywhere.
- Check state handling (remote, encrypted, access-controlled) and CI that applies it (
code-review-cicd).
Gotchas
- A finding's severity depends on blast radius — a public dev sandbox ≠ a public prod data store.
- Scanners miss cross-resource logic (an SG that's fine until paired with a public subnet) — reason about the whole graph.
- Secrets belong in a manager (Vault/SSM/KMS), never in variables or state — flag any inline secret.
References
CIS Benchmarks (AWS/Azure/GCP/Kubernetes); Checkov/tfsec/KICS rule sets; provider well-architected security pillars.
File di questa versione
- SKILL.md3.1 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 7c4531b8 | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Linux, cloud e container
Vai alla categoria- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- cloud-gcpnoorqureshi/cloud-gcp4
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login