Encryption at rest in Kafka - Step-by-Step Execution

Process Flow - Encryption at rest

Data Written to Kafka

↓

Kafka Broker Receives Data

↓

Encrypt Data on Disk

↓

Store Encrypted Data

↓

Data at Rest is Encrypted

↓

Authorized Read Requests

↓

Decrypt Data Before Sending

↓

Send Plain Data to Consumer

Data sent to Kafka is encrypted before saving on disk and decrypted only when authorized consumers read it.

Execution Sample

Kafka

props.put("security.inter.broker.protocol", "SSL");
props.put("ssl.keystore.location", "/path/to/keystore.jks");
props.put("ssl.keystore.password", "password");
props.put("ssl.key.password", "password");
// Data is encrypted on disk using SSL keys

This code configures Kafka brokers to encrypt data in transit using SSL certificates.

Process Table

Step	Action	Data State	Result
1	Data sent to Kafka broker	Plain text	Data received by broker
2	Broker applies encryption	Encrypted	Data ready to store
3	Data stored on disk	Encrypted	Data saved securely
4	Consumer requests data	Encrypted	Broker prepares to decrypt
5	Broker decrypts data	Plain text	Data ready to send
6	Data sent to consumer	Plain text	Consumer receives readable data
7	End	Plain text	Process complete

💡 Process ends after data is decrypted and sent to authorized consumer.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
data_state	Plain text	Encrypted	Encrypted	Plain text	Plain text

Key Moments - 3 Insights

Why is data encrypted before storing on disk?

Data is encrypted before storing (see Step 2 in execution_table) to protect it from unauthorized access if disk is compromised.

When does data become readable again?

Data is decrypted just before sending to the consumer (Step 5), so only authorized users see plain text.

Is data encrypted during transmission between client and broker?

Encryption at rest focuses on disk storage; transmission encryption uses SSL/TLS separately, not shown in this flow.

Visual Quiz - 3 Questions

Look at the execution_table, what is the data state after Step 3?

A Encrypted

B Plain text

C Decrypted

D Corrupted

💡 Hint

Check the 'Data State' column for Step 3 in the execution_table.

At which step does the broker decrypt the data?

A Step 4

B Step 5

C Step 2

D Step 6

💡 Hint

Look for the step where 'Broker decrypts data' in the 'Action' column.

If encryption was skipped, how would the 'data_state' variable change after Step 3?

A It would become 'Corrupted'

B It would become 'Encrypted'

C It would remain 'Plain text'

D It would be 'Decrypted'

💡 Hint

Refer to variable_tracker and consider what happens if encryption is not applied.

Concept Snapshot

Encryption at rest in Kafka means data is encrypted before saving on disk.
Kafka brokers use SSL keys to encrypt and decrypt data.
Data stays encrypted on disk to protect from unauthorized access.
Decryption happens only when authorized consumers read data.
This ensures data security even if storage is compromised.

Full Transcript

Encryption at rest in Kafka protects data by encrypting it before storing on disk. When data is sent to the Kafka broker, it is initially plain text. The broker encrypts the data before saving it to disk, so the stored data is secure. When a consumer requests the data, the broker decrypts it and sends the readable data to the consumer. This process ensures that data remains protected while stored and only authorized users can read it. The execution table shows each step from data reception, encryption, storage, decryption, and delivery. The variable tracker follows the data state changes from plain text to encrypted and back to plain text. Key moments clarify why encryption is done before storage and when data becomes readable again. The visual quiz tests understanding of these steps and data states.

Practice

1. What does encryption at rest mean in the context of Kafka?

easy

A. Encrypting data while it is being sent between Kafka brokers

B. Protecting stored Kafka data by making it unreadable without a key

C. Compressing Kafka messages to save disk space

D. Authenticating users before they access Kafka topics

Solution

1. Step 1: Understand encryption at rest

   Encryption at rest means data stored on disk is encrypted to prevent unauthorized reading.

2. Step 2: Differentiate from other security concepts

   Encryption in transit protects data moving between systems, not stored data.

3. Final Answer:

   Protecting stored Kafka data by making it unreadable without a key -> Option B

4. Quick Check:

   Encryption at rest = Protect stored data [OK]

Hint: Encryption at rest means stored data is unreadable without keys [OK]

Common Mistakes:

• Confusing encryption at rest with encryption in transit
• Thinking compression is encryption
• Mixing authentication with encryption

2. Which of the following is the correct way to enable encryption at rest in Kafka?

easy

A. Use disk-level encryption or external tools since Kafka does not encrypt data on disk by default

B. Add encryption.at.rest=true in the Kafka topic configuration

C. Set ssl.enabled=true in the Kafka broker configuration

D. Configure kafka.security.encryption=true in the producer settings

Solution

1. Step 1: Check Kafka's default encryption behavior

   Kafka does not encrypt data on disk by default; it requires external disk encryption or tools.

2. Step 2: Review configuration options

   Options A, B, and D are not valid Kafka configurations for encryption at rest.

3. Final Answer:

   Use disk-level encryption or external tools since Kafka does not encrypt data on disk by default -> Option A

4. Quick Check:

   Kafka disk encryption = external tools [OK]

Hint: Kafka needs external disk encryption for data at rest [OK]

Common Mistakes:

• Assuming SSL enables encryption at rest
• Trying to set non-existent Kafka config keys
• Confusing topic or producer configs with disk encryption

3. Given the following Kafka broker configuration snippet, what is the effect on data security?

listeners=PLAINTEXT://:9092
ssl.enabled.protocols=TLSv1.2,TLSv1.3
ssl.keystore.location=/var/private/keystore.jks
ssl.keystore.password=changeit

medium

A. Data is encrypted both on disk and during transmission

B. Data is encrypted on disk but not during transmission

C. Data is encrypted during transmission but not on disk

D. No encryption is enabled

Solution

1. Step 1: Analyze the configuration

   The listeners are set to PLAINTEXT://:9092, which means connections are not encrypted (no SSL/TLS in transit). The SSL keystore settings are present but not activated for this listener.

2. Step 2: Confirm no encryption at rest

   There are no settings for disk encryption; data on disk is unencrypted.

3. Final Answer:

   Data is encrypted during transmission but not on disk -> Option C

4. Quick Check:

   PLAINTEXT listener + no disk encryption = no encryption at rest, but SSL settings indicate encryption possible if listener changed [OK]

Hint: PLAINTEXT listener means no encryption in transit or at rest [OK]

Common Mistakes:

• Assuming SSL encrypts data on disk
• Ignoring the PLAINTEXT listener setting
• Confusing keystore with disk encryption

4. You want to enable encryption at rest for Kafka data. You added the following to your broker config:

encryption.at.rest=true

But it does not work. What is the likely problem?

medium

A. You need to restart the Kafka producer, not the broker

B. The config key is case sensitive and should be Encryption.At.Rest

C. You must set ssl.enabled=true instead

D. Kafka does not support encryption.at.rest config; disk encryption must be external

Solution

1. Step 1: Verify Kafka config support

   Kafka does not have a built-in encryption.at.rest configuration option.

2. Step 2: Understand how to enable encryption at rest

   Encryption at rest requires external disk encryption tools or file system encryption.

3. Final Answer:

   Kafka does not support encryption.at.rest config; disk encryption must be external -> Option D

4. Quick Check:

   No native encryption at rest config in Kafka [OK]

Hint: Kafka needs external disk encryption, no native config key [OK]

Common Mistakes:

• Trying to use non-existent Kafka config keys
• Restarting wrong components
• Confusing SSL with encryption at rest

5. You want to ensure Kafka data is encrypted at rest on a Linux server. Which approach correctly applies encryption at rest while keeping Kafka running smoothly?

hard

A. Use Linux LUKS disk encryption on the Kafka data directory and configure Kafka normally

B. Enable SSL in Kafka broker config to encrypt data on disk

C. Set Kafka topic config encryption.enabled=true to encrypt data at rest

D. Use Kafka producer encryption settings to encrypt data before writing to disk

Solution

1. Step 1: Identify how to encrypt data at rest on Linux

   Linux LUKS provides full disk encryption, protecting Kafka data on disk transparently.

2. Step 2: Confirm Kafka compatibility

   Kafka works normally on encrypted disks without special config; SSL and topic configs do not encrypt at rest.

3. Final Answer:

   Use Linux LUKS disk encryption on the Kafka data directory and configure Kafka normally -> Option A

4. Quick Check:

   Disk encryption tool + normal Kafka = encryption at rest [OK]

Hint: Use OS-level disk encryption for Kafka data at rest [OK]

Common Mistakes:

• Thinking SSL encrypts data on disk
• Expecting Kafka topic configs to encrypt data at rest
• Trying to encrypt data only at producer level