Security best practices in Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable SSL encryption for Kafka client.

Kafka

security.protocol=[1]

Drag options to blanks, or click blank then click option'

ASSL

BPLAINTEXT

CSASL_PLAINTEXT

DSASL_SSL

Attempts:

3 left

💡 Hint

Common Mistakes

Using PLAINTEXT disables encryption.

Confusing SASL options with SSL.

Setting security.protocol to SSL enables SSL encryption for Kafka clients.

2fill in blank

medium

Complete the code to configure SASL mechanism for Kafka authentication.

Kafka

sasl.mechanism=[1]

Drag options to blanks, or click blank then click option'

ANONE

BPLAIN

COAUTHBEARER

DSSL

Attempts:

3 left

💡 Hint

Common Mistakes

Using SSL as a SASL mechanism is incorrect.

Choosing NONE disables authentication.

The PLAIN mechanism is a common SASL authentication method for Kafka.

3fill in blank

hard

Fix the error in the Kafka ACL command to allow user 'alice' to produce to topic 'orders'.

Kafka

kafka-acls --authorizer-properties zookeeper.connect=localhost:2181 --add --allow-principal User:[1] --operation Write --topic orders

Drag options to blanks, or click blank then click option'

Aadmin

Bbob

Calice

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different username than 'alice'.

Confusing principal format.

The principal must match the username 'alice' to grant write permission on the 'orders' topic.

4fill in blank

hard

Fill both blanks to configure Kafka broker to require client authentication and enable SSL.

Kafka

ssl.client.auth=[1]
security.protocol=[2]

Drag options to blanks, or click blank then click option'

Arequired

Bnone

CSSL

DPLAINTEXT

Attempts:

3 left

💡 Hint

Common Mistakes

Setting client auth to none disables authentication.

Using PLAINTEXT disables encryption.

Setting ssl.client.auth to required enforces client authentication. Using SSL for security.protocol enables encrypted communication.

5fill in blank

hard

Fill all three blanks to create a Kafka ACL that allows user 'bob' to consume from topic 'payments' with group 'payment-group'.

Kafka

kafka-acls --authorizer-properties zookeeper.connect=localhost:2181 --add --allow-principal User:[1] --operation [2] --topic payments --group [3]

Drag options to blanks, or click blank then click option'

Aalice

Bbob

CRead

Dpayment-group

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong username or operation.

Omitting the consumer group.

The principal is 'bob', the operation is 'Read', and the group is 'payment-group' to allow consumption from the topic.

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