State file sensitivity and security in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Terraform state file?

A Terraform state file is a file that keeps track of the resources Terraform manages. It stores information about the infrastructure's current state so Terraform knows what to create, update, or delete.

beginner

Why is the Terraform state file sensitive?

The state file contains detailed information about your infrastructure, including resource IDs, IP addresses, and sometimes secrets or passwords. If exposed, it can lead to security risks.

intermediate

Name one best practice to secure Terraform state files.

Store the state file remotely in a secure backend like AWS S3 with encryption and access controls, instead of keeping it locally on your computer.

intermediate

What is Terraform remote state locking and why is it important?

Remote state locking prevents multiple people from changing the state file at the same time. This avoids conflicts and corruption of the state file.

advanced

How can you avoid storing sensitive data in the Terraform state file?

Use Terraform's sensitive variables feature and avoid outputting secrets. Also, use external secret managers to keep secrets outside the state file.

What does the Terraform state file primarily store?

A Current infrastructure resource information

B Terraform source code

C User login credentials

D Cloud provider billing details

The state file stores information about the current infrastructure resources Terraform manages.

Why should Terraform state files be stored securely?

A They are very large files

B They contain Terraform version info

C They contain sensitive infrastructure details

D They are only used for logging

State files contain sensitive details like resource IDs and sometimes secrets, so securing them is important.

Which backend is recommended for storing Terraform state securely?

A Local disk without encryption

B Remote backend with encryption and access control

C Public GitHub repository

D Temporary cloud storage without access control

Using a remote backend with encryption and access control protects the state file from unauthorized access.

What problem does remote state locking solve?

A Prevents multiple users from editing state simultaneously

B Encrypts the state file

C Backs up the state file automatically

D Improves Terraform execution speed

Remote state locking prevents concurrent edits that could corrupt the state file.

How can you keep secrets out of the Terraform state file?

A Ignore the state file in version control

B Store secrets in plain text variables

C Output secrets in Terraform outputs

D Use sensitive variables and external secret managers

Using sensitive variables and external secret managers keeps secrets out of the state file.

Explain why Terraform state files are sensitive and how you can protect them.

Think about what info the state file holds and how to keep it safe.

Describe best practices to avoid exposing sensitive data in Terraform state files.

Focus on how to handle secrets and state storage.

Practice

1. What is the main reason to keep the Terraform state file secure?

easy

A. It holds your Terraform installation files

B. It stores your Terraform version history

C. It contains sensitive information about your cloud resources

D. It contains your Terraform provider plugins

Solution

1. Step 1: Understand the role of the state file

   The Terraform state file records details about your cloud resources, including IDs and configurations.

2. Step 2: Identify sensitive content in the state file

   Because it stores resource details, it may include secrets or private data that must be protected.

3. Final Answer:

   It contains sensitive information about your cloud resources -> Option C

4. Quick Check:

   State file holds sensitive info = A [OK]

Hint: State file stores resource info, so protect it [OK]

Common Mistakes:

• Thinking state file stores Terraform software files
• Confusing state file with version control
• Assuming state file only has public info

2. Which Terraform configuration snippet correctly marks a variable as sensitive?

easy

A. variable "password" { type = sensitive }

B. variable "password" { hidden = true }

C. variable "password" { secret = true }

D. variable "password" { sensitive = true }

Solution

1. Step 1: Recall Terraform variable syntax for sensitivity

   Terraform uses the attribute sensitive = true inside variable blocks to mark secrets.

2. Step 2: Check each option's correctness

   Only variable "password" { sensitive = true } uses the correct attribute sensitive = true. Others use invalid or unsupported attributes.

3. Final Answer:

   variable "password" { sensitive = true } -> Option D

4. Quick Check:

   sensitive = true marks secrets = B [OK]

Hint: Use sensitive = true inside variable block [OK]

Common Mistakes:

• Using 'type = sensitive' instead of 'sensitive = true'
• Using 'secret' or 'hidden' which are invalid
• Omitting the sensitive attribute

3. Given this Terraform output block:

output "db_password" {
  value     = var.db_password
  sensitive = true
}

What will happen when you run terraform apply?

medium

A. The password will be hidden in the output and logs

B. The password will be shown in the output after apply

C. Terraform will throw a syntax error

D. The password will be stored in plain text in the state file

Solution

1. Step 1: Understand the effect of sensitive output

   Marking an output as sensitive = true hides its value from CLI output and logs.

2. Step 2: Check if syntax is correct and state file behavior

   The syntax is valid, so no error occurs. The value is still stored in the state file but hidden from output.

3. Final Answer:

   The password will be hidden in the output and logs -> Option A

4. Quick Check:

   sensitive output hides value in CLI = A [OK]

Hint: sensitive output hides value from CLI, not state file [OK]

Common Mistakes:

• Thinking sensitive outputs cause syntax errors
• Assuming sensitive outputs are not stored in state
• Expecting sensitive outputs to show in CLI

4. You accidentally committed your Terraform state file with secrets to a public GitHub repo. What is the best immediate action to secure your infrastructure?

medium

A. Remove the state file from GitHub and continue as usual

B. Rotate all secrets and credentials stored in the state file

C. Change the Terraform version to encrypt the state file automatically

D. Delete the GitHub repo and do nothing else

Solution

1. Step 1: Understand the risk of leaked secrets

   Once secrets are public, they can be compromised, so immediate rotation is needed.

2. Step 2: Evaluate other options

   Deleting repo or removing files does not guarantee secrets are safe. Changing Terraform version does not fix leaked secrets.

3. Final Answer:

   Rotate all secrets and credentials stored in the state file -> Option B

4. Quick Check:

   Leaked secrets require rotation = D [OK]

Hint: Rotate secrets immediately if state file leaks [OK]

Common Mistakes:

• Thinking deleting repo removes leaked secrets
• Assuming Terraform version change encrypts old state
• Ignoring secret rotation after leak

5. You want to securely store your Terraform state file remotely with encryption and access control. Which setup is the best practice?

hard

A. Use a remote backend like AWS S3 with server-side encryption and IAM policies

B. Store the state file locally and encrypt it manually with a password

C. Commit the state file to a private Git repository with limited access

D. Use Terraform Cloud free tier without enabling state encryption

Solution

1. Step 1: Identify secure remote state storage options

   Using a remote backend like AWS S3 with encryption and access control protects the state file effectively.

2. Step 2: Compare other options

   Local storage with manual encryption is error-prone. Private Git repos are not designed for state files. Terraform Cloud free tier may not encrypt state by default.

3. Final Answer:

   Use a remote backend like AWS S3 with server-side encryption and IAM policies -> Option A

4. Quick Check:

   Remote backend with encryption = C [OK]

Hint: Use remote backend with encryption and access control [OK]

Common Mistakes:

• Relying on local manual encryption
• Storing state in Git repos
• Assuming free tiers always encrypt state