Terraform security scanning tools - Step-by-Step Execution

Process Flow - Terraform security scanning tools

Write Terraform code

↓

Run security scanner

↓

Scanner analyzes code

↓

Report vulnerabilities

↓

Fix issues in code

↓

Re-run scanner to verify

↓

Deploy safely

This flow shows how Terraform code is checked by security tools before deployment to find and fix risks.

Execution Sample

Terraform

terraform validate
terraform fmt
checkov -d .
tfsec .

Run Terraform validation, format code, then scan with Checkov and tfsec for security issues.

Process Table

Step	Action	Tool	Result	Next Step
1	Validate Terraform syntax	terraform validate	Syntax OK	Run formatter
2	Format Terraform code	terraform fmt	Code formatted	Run Checkov scan
3	Scan code for security issues	Checkov	Found 2 issues: open security groups	Fix issues
4	Fix security group rules	Manual edit	Rules tightened	Run tfsec scan
5	Scan code for security issues	tfsec	No critical issues found	Ready to deploy
6	Deploy infrastructure	terraform apply	Infrastructure deployed safely	End

💡 Deployment proceeds only after security scans report no critical issues.

Status Tracker

Variable	Start	After Step 3	After Step 4	Final
security_group_rules	open to all	open to all (issue found)	restricted to ports 80,443	restricted to ports 80,443

Key Moments - 2 Insights

Why do we run both Checkov and tfsec scans?

Checkov and tfsec catch different security issues; running both ensures broader coverage as shown in steps 3 and 5.

What happens if the scanner finds issues?

You must fix the issues manually (step 4) before re-running scans to ensure safe deployment.

Visual Quiz - 3 Questions

Look at the execution table, what tool finds the first security issues?

A Checkov

B terraform validate

C tfsec

D terraform fmt

💡 Hint

Check row 3 in the execution table where Checkov reports issues.

At which step are security group rules fixed?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Look at the 'Action' column in step 4 for manual fixes.

If tfsec found critical issues at step 5, what would be the next step?

A Deploy infrastructure

B Skip deployment

C Fix issues and re-run scans

D Run terraform fmt again

💡 Hint

Refer to the flow where issues require fixing before deployment.

Concept Snapshot

Terraform security scanning tools check your code for risks before deployment.
Common tools: Checkov and tfsec.
Run terraform validate and fmt first.
Fix issues found by scanners.
Re-scan until no critical issues remain.
Then deploy safely.

Full Transcript

Terraform security scanning tools help find risks in your infrastructure code before you deploy it. First, you write your Terraform code. Then, you run 'terraform validate' to check syntax and 'terraform fmt' to format the code. Next, you run security scanners like Checkov and tfsec. These tools analyze your code and report any security problems, such as open security groups. If issues are found, you fix them manually in your code. After fixing, you run the scanners again to confirm the issues are resolved. Once no critical issues remain, you deploy your infrastructure safely using 'terraform apply'. This process helps keep your cloud resources secure.

Practice

1. What is the main purpose of Terraform security scanning tools like tfsec?

easy

A. To monitor cloud resource usage costs

B. To deploy Terraform infrastructure automatically

C. To write Terraform code faster with autocomplete

D. To find security risks in Terraform code before deployment

Solution

1. Step 1: Understand Terraform security scanning tools

   These tools analyze Terraform code to detect potential security issues early.

2. Step 2: Compare options with tool purpose

   Only To find security risks in Terraform code before deployment matches the purpose of finding security risks before deployment.

3. Final Answer:

   To find security risks in Terraform code before deployment -> Option D

4. Quick Check:

   Security scanning = find risks [OK]

Hint: Security tools find risks in code before cloud setup [OK]

Common Mistakes:

• Confusing scanning tools with deployment tools
• Thinking scanning tools write code
• Assuming scanning tools track costs

2. Which command correctly runs tfsec to scan your Terraform project in the current folder?

easy

A. tfsec scan terraform

B. terraform scan

C. tfsec .

D. terraform tfsec run

Solution

1. Step 1: Recall tfsec usage syntax

   The correct way to run tfsec is by specifying the folder, commonly the current folder with a dot.

2. Step 2: Match command to syntax

   Only tfsec . correctly runs tfsec on the current directory.

3. Final Answer:

   tfsec . -> Option C

4. Quick Check:

   Run tfsec with folder path, dot means current folder [OK]

Hint: Run tfsec with dot for current folder scan [OK]

Common Mistakes:

• Using terraform commands instead of tfsec
• Adding extra words like 'scan' or 'run'
• Not specifying folder or using wrong syntax

3. Given this tfsec output snippet:

Warning: AWS S3 bucket is publicly accessible
  File: main.tf:12
  Severity: HIGH

What does this output mean?

medium

A. The S3 bucket in main.tf line 12 allows public access, which is risky

B. The S3 bucket is encrypted and secure

C. The S3 bucket is missing from the Terraform code

D. The S3 bucket is private and safe

Solution

1. Step 1: Interpret tfsec warning message

   The warning says the S3 bucket is publicly accessible, which means anyone can access it.

2. Step 2: Understand security implication

   Public access to S3 buckets is a high-risk security issue, so this is a warning to fix it.

3. Final Answer:

   The S3 bucket in main.tf line 12 allows public access, which is risky -> Option A

4. Quick Check:

   Public access warning = risky bucket [OK]

Hint: Warnings show risky settings like public access [OK]

Common Mistakes:

• Thinking warning means bucket is secure
• Confusing missing resource with public access
• Ignoring file and line number details

4. You ran tfsec . but got an error: command not found: tfsec. What is the most likely fix?

medium

A. Run terraform init first

B. Install tfsec on your system and ensure it's in your PATH

C. Change directory to the Terraform root folder

D. Update Terraform version to latest

Solution

1. Step 1: Understand the error meaning

   The error means the system cannot find the tfsec command, so it is not installed or not accessible.

2. Step 2: Fix by installing tfsec and adding to PATH

   Installing tfsec and ensuring the command is available in the system PATH fixes this error.

3. Final Answer:

   Install tfsec on your system and ensure it's in your PATH -> Option B

4. Quick Check:

   Command not found = install tool [OK]

Hint: Install tfsec if command not found error appears [OK]

Common Mistakes:

• Running terraform commands instead of installing tfsec
• Assuming directory change fixes command not found
• Updating Terraform version unrelated to tfsec error

5. You want to automate security scanning in your CI pipeline using tfsec. Which approach best ensures security issues are caught before deployment?

hard

A. Run tfsec . before Terraform apply and fail pipeline on warnings

B. Run tfsec . after Terraform apply to check deployed resources

C. Run terraform plan and ignore tfsec

D. Run tfsec . only on production branch merges

Solution

1. Step 1: Understand when to run security scans

   Security scanning should happen before deployment to catch issues early.

2. Step 2: Choose pipeline behavior to enforce security

   Failing the pipeline on warnings ensures no risky code is deployed.

3. Step 3: Evaluate other options

   Running after apply is too late; ignoring tfsec misses risks; scanning only production branch misses early detection.

4. Final Answer:

   Run tfsec . before Terraform apply and fail pipeline on warnings -> Option A

5. Quick Check:

   Scan before deploy and fail on warnings [OK]

Hint: Scan before deploy and fail on warnings to block risks [OK]

Common Mistakes:

• Running scans after deployment
• Ignoring tfsec in pipeline
• Scanning only production branch too late