此内容没有您所选择的语言版本。

Chapter 11. Securing Kafka


A secure deployment of Streams for Apache Kafka might encompass one or more of the following security measures:

Encryption

Streams for Apache Kafka supports Transport Layer Security (TLS), a protocol for encrypted communication.

  • Communication is always encrypted between Streams for Apache Kafka components.
  • To set up TLS-encrypted communication between Kafka and clients, you configure listeners in the Kafka custom resource.
Authentication

Kafka listeners use authentication to ensure a secure client connection to the Kafka cluster. Clients can also be configured for mutual authentication. Security credentials are created and managed by the Cluster and User Operator.

Supported authentication mechanisms:

  • mTLS authentication (on listeners with TLS-enabled encryption)
  • SASL SCRAM-SHA-512
  • OAuth 2.0 token based authentication
  • Custom authentication (supported by Kafka)
Authorization

Authorization controls the operations that are permitted on Kafka brokers by specific clients or users.

Supported authorization mechanisms:

  • Simple authorization using ACL rules
  • OAuth 2.0 authorization (if you are using OAuth 2.0 token-based authentication)
  • Open Policy Agent (OPA) authorization (deprecated)
  • Custom authorization (supported by Kafka)
Federal Information Processing Standards (FIPS)
Streams for Apache Kafka is designed to run on FIPS-enabled OpenShift clusters to ensure data security and system interoperability. For more information about the NIST validation program and validated modules, see Cryptographic Module Validation Program on the NIST website.
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat
返回顶部