Security best practices in Kafka - Step-by-Step Execution

Process Flow - Security best practices

Start Kafka Setup

↓

Enable Authentication

↓

Enable Encryption

↓

Set Authorization Rules

↓

Configure Auditing

↓

Monitor and Update

↓

Secure Kafka Cluster Running

This flow shows the main steps to secure a Kafka cluster: start setup, enable authentication, encryption, authorization, auditing, then monitor and update.

Execution Sample

Kafka

security.inter.broker.protocol=SASL_SSL
sasl.mechanism.inter.broker.protocol=SCRAM-SHA-512
authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer
ssl.keystore.location=/var/private/ssl/kafka.server.keystore.jks
ssl.keystore.password=changeit

This config snippet enables encrypted communication, authentication, and authorization in Kafka.

Process Table

Step	Configuration Setting	Value	Effect	Security Impact
1	security.inter.broker.protocol	SASL_SSL	Encrypts broker communication	Prevents eavesdropping
2	sasl.mechanism.inter.broker.protocol	SCRAM-SHA-512	Sets strong authentication	Prevents unauthorized access
3	authorizer.class.name	kafka.security.auth.SimpleAclAuthorizer	Enables ACL authorization	Controls who can do what
4	ssl.keystore.location	/var/private/ssl/kafka.server.keystore.jks	Specifies SSL cert location	Enables SSL encryption
5	ssl.keystore.password	changeit	Protects SSL keystore	Secures private keys
6	Monitoring	Enabled	Tracks security events	Detects suspicious activity
7	Update	Regular patches	Fixes vulnerabilities	Keeps system secure
Exit	-	-	All security layers configured	Kafka cluster secured

💡 All security settings applied, cluster is now secured with authentication, encryption, authorization, and monitoring.

Status Tracker

Setting	Initial	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
security.inter.broker.protocol	PLAINTEXT	SASL_SSL	SASL_SSL	SASL_SSL	SASL_SSL	SASL_SSL	SASL_SSL
sasl.mechanism.inter.broker.protocol	None	None	SCRAM-SHA-512	SCRAM-SHA-512	SCRAM-SHA-512	SCRAM-SHA-512	SCRAM-SHA-512
authorizer.class.name	None	None	None	kafka.security.auth.SimpleAclAuthorizer	kafka.security.auth.SimpleAclAuthorizer	kafka.security.auth.SimpleAclAuthorizer	kafka.security.auth.SimpleAclAuthorizer
ssl.keystore.location	None	None	None	None	/var/private/ssl/kafka.server.keystore.jks	/var/private/ssl/kafka.server.keystore.jks	/var/private/ssl/kafka.server.keystore.jks
ssl.keystore.password	None	None	None	None	None	changeit	changeit

Key Moments - 3 Insights

Why do we need to set security.inter.broker.protocol to SASL_SSL instead of PLAINTEXT?

Setting security.inter.broker.protocol to SASL_SSL encrypts communication between brokers, preventing attackers from reading sensitive data. The execution_table row 1 shows this change and its security impact.

What is the role of authorizer.class.name in Kafka security?

authorizer.class.name enables access control lists (ACLs) to restrict what users can do. Row 3 in the execution_table shows enabling SimpleAclAuthorizer to control permissions.

Why is monitoring important after configuring security settings?

Monitoring tracks security events and detects suspicious activity, helping keep Kafka secure over time. This is shown in row 6 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what value does security.inter.broker.protocol have after step 1?

A SASL_SSL

B PLAINTEXT

C SCRAM-SHA-512

D None

💡 Hint

Check the 'Value' column in row 1 of the execution_table.

At which step is the authorizer.class.name set to enable authorization?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Configuration Setting' column and find when authorizer.class.name is set.

If ssl.keystore.password was not set, what security impact would be missing?

A No encryption of broker communication

B Private keys would not be protected

C No authentication between brokers

D No monitoring of security events

💡 Hint

Refer to the 'Security Impact' column for ssl.keystore.password in the execution_table.

Concept Snapshot

Kafka Security Best Practices:
- Enable authentication with SASL mechanisms
- Encrypt broker communication with SSL/SASL_SSL
- Use ACLs for authorization
- Protect SSL keys with passwords
- Monitor security events regularly
- Keep Kafka updated with patches

Full Transcript

This visual execution shows how to secure a Kafka cluster step-by-step. First, we enable encrypted communication between brokers by setting security.inter.broker.protocol to SASL_SSL. Then, we configure strong authentication using SCRAM-SHA-512. Next, we enable authorization with SimpleAclAuthorizer to control access. We specify SSL keystore location and password to protect encryption keys. Monitoring is enabled to track security events, and regular updates keep the system secure. The execution table traces each setting change and its security impact. Variable tracker shows how configuration values evolve. Key moments clarify common confusions about encryption, authorization, and monitoring. The quiz tests understanding of these steps. This approach helps beginners see how Kafka security builds layer by layer.

Practice

1. Which of the following is the primary purpose of using SSL/TLS in Kafka security?

easy

A. To manage access permissions with ACLs

B. To authenticate users with usernames and passwords

C. To encrypt data transmitted between Kafka clients and brokers

D. To compress messages for faster transmission

Solution

1. Step 1: Understand SSL/TLS role in Kafka

   SSL/TLS is used to encrypt data sent over the network to protect it from eavesdropping.

2. Step 2: Differentiate from other security features

   Authentication uses SASL, and ACLs manage permissions, not encryption.

3. Final Answer:

   To encrypt data transmitted between Kafka clients and brokers -> Option C

4. Quick Check:

   SSL/TLS = Encryption [OK]

Hint: SSL/TLS encrypts data in transit, not authentication or permissions [OK]

Common Mistakes:

• Confusing SSL/TLS with authentication methods
• Thinking ACLs handle encryption
• Assuming SSL/TLS compresses data

2. Which of the following is the correct way to enable SASL authentication in Kafka's server.properties file?

easy

A. acl.enable=true

B. security.protocol=PLAINTEXT

C. ssl.enabled=true

D. sasl.enabled.mechanisms=PLAIN

Solution

1. Step 1: Identify SASL configuration property

   The property sasl.enabled.mechanisms specifies which SASL mechanisms Kafka accepts.

2. Step 2: Check other options for correctness

   security.protocol=PLAINTEXT disables security, ssl.enabled is not a valid property, and acl.enable is unrelated to SASL.

3. Final Answer:

   sasl.enabled.mechanisms=PLAIN -> Option D

4. Quick Check:

   SASL config uses sasl.enabled.mechanisms [OK]

Hint: SASL uses sasl.enabled.mechanisms property in server.properties [OK]

Common Mistakes:

• Using PLAINTEXT disables security
• Confusing SSL properties with SASL
• Assuming acl.enable controls authentication

3. Given the following ACL command, what permission does it grant?

kafka-acls --add --allow-principal User:Alice --operation Read --topic sales-data

medium

A. Alice can read messages from the sales-data topic

B. Alice can create new topics

C. Alice can delete the sales-data topic

D. Alice can write messages to the sales-data topic

Solution

1. Step 1: Analyze the ACL command parameters

   The command adds an ACL allowing User:Alice the Read operation on the topic sales-data.

2. Step 2: Understand the Read operation

   Read permission allows consuming or reading messages from the topic, not writing or deleting.

3. Final Answer:

   Alice can read messages from the sales-data topic -> Option A

4. Quick Check:

   ACL Read = Permission to consume messages [OK]

Hint: Read operation in ACL means permission to consume messages [OK]

Common Mistakes:

• Confusing Read with Write permission
• Assuming Read allows topic deletion
• Mixing topic creation with ACL permissions

4. Identify the error in the following Kafka security configuration snippet:

security.protocol=SASL_PLAINTEXT
sasl.mechanism=SCRAM-SHA-256

medium

A. security.protocol should be SASL_SSL to enable encryption

B. The property should be sasl.mechanism instead of sasl.mechanisms

C. SCRAM-SHA-256 is not a valid SASL mechanism

D. No error, configuration is correct

Solution

1. Step 1: Check security.protocol value

   SASL_PLAINTEXT enables SASL but does not encrypt traffic, which is insecure for sensitive data.

2. Step 2: Recommend secure protocol

   Using SASL_SSL enables SASL authentication with SSL encryption, which is a best practice.

3. Final Answer:

   security.protocol should be SASL_SSL to enable encryption -> Option A

4. Quick Check:

   Use SASL_SSL for encrypted SASL connections [OK]

Hint: SASL_PLAINTEXT lacks encryption; use SASL_SSL for security [OK]

Common Mistakes:

• Thinking SASL_PLAINTEXT encrypts data
• Confusing sasl.mechanism property name
• Believing SCRAM-SHA-256 is invalid

5. You want to secure a Kafka cluster so that only authenticated users can produce or consume messages, and all traffic is encrypted. Which combination of settings achieves this best?

hard

A. Use PLAINTEXT protocol with ACLs to restrict access, no encryption needed

B. Enable SSL encryption with security.protocol=SASL_SSL, configure SASL authentication, and set ACLs for user permissions

C. Enable SASL_PLAINTEXT for authentication and rely on network firewall for encryption

D. Use SSL only without SASL or ACLs to simplify configuration

Solution

1. Step 1: Ensure encryption and authentication

   Using security.protocol=SASL_SSL enables both encryption (SSL) and authentication (SASL).

2. Step 2: Control access with ACLs

   ACLs restrict which authenticated users can produce or consume messages, enforcing permissions.

3. Final Answer:

   Enable SSL encryption with security.protocol=SASL_SSL, configure SASL authentication, and set ACLs for user permissions -> Option B

4. Quick Check:

   Encryption + Authentication + ACLs = Secure Kafka [OK]

Hint: Combine SASL_SSL, SASL auth, and ACLs for full security [OK]

Common Mistakes:

• Using PLAINTEXT disables encryption
• Relying on firewall instead of encryption
• Skipping ACLs allows unauthorized access