Kafka Amq Security logo

Kafka Amq Security

Organization
RedHatProductSecurity
kafka-amq-security

Secure Kafka and AMQ Streams deployments with encryption, authentication, and authorization. Use when building, reviewing, or auditing Kafka broker configuration, AMQ Streams custom resources, or Kafka client connectivity.

Overview

PublisherRedHatProductSecurity
Repositoryprodsec-skills
Skill namekafka-amq-security
Stars
56
Forks
9
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by RedHatProductSecurity on GitHub. Read the source before you install it.

Installation

Install the Kafka Amq Security AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/kafka-amq-security
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-skills.git /tmp/prodsec-skills
mkdir -p .claude/skills
cp -r /tmp/prodsec-skills/module/skills/kafka-amq-security .claude/skills/kafka-amq-security
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Kafka Amq Security in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Kafka Amq Security on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Kafka Amq Security is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Kafka and AMQ Streams Security

Encryption

By default, Kafka transmits data in plaintext, leaving it vulnerable to man-in-the-middle attacks.

  • Enable TLS/SSL encryption for all client-to-broker and broker-to-broker communication
  • The performance cost of TLS is typically negligible on modern hardware
  • TLS only protects data in transit; apply additional controls for data at rest

AMQ Streams Encryption

AMQ Streams encrypts communication between brokers and operators using TLS by default. Client encryption depends on Kafka listener configuration:

  • Cluster CA signs broker certificates; Clients CA signs client certificates
  • The Cluster Operator automatically generates and renews CA certificates
  • Users may provide their own CA certificates (must be renewed manually)
  • Client applications must trust Cluster CA certificates unless TLS is explicitly disabled on external listeners

Authentication

Kafka Authentication

Use SSL or SASL for client-to-broker and broker-to-broker authentication:

MethodUse Case
SSL (mutual TLS)Most common for managed services; two-way certificate authentication
SASL SCRAM-SHA-512Password-based; suitable for environments without certificate infrastructure
SASL KerberosEnterprise environments with existing Kerberos infrastructure
OAuth 2.0Token-based; integrates with RHSSO/Keycloak

AMQ Streams Authentication

Authentication is disabled by default in AMQ Streams. Enable it per listener in the Kafka custom resource:

  • Configure the authentication property on each broker listener
  • Each listener can use a different authentication mechanism
  • Clients must use KafkaUser credentials to connect once authentication is enabled

Authorization

Access Control Lists (ACLs)

Limit which clients can read and write to specific topics:

  • Use ACLs with the format: "Principal P is Allowed/Denied Operation O From Host H on Resource R"
  • Apply ACLs to Topics, Consumer Groups, Clusters, and Transactional IDs
  • Restrict super users to the minimum necessary; super users bypass all ACL checks

AMQ Streams Authorization Options

MechanismDescription
Simple ACLDefault Apache Kafka ACL plugin; rules stored in ZooKeeper, loaded at broker startup
OAuth 2.0 / KeycloakAuthorization rules managed in RHSSO/Keycloak; requires OAuth authentication
Open Policy Agent (OPA)Externalized policy engine for fine-grained authorization

Authorization is configured via the authorization property in the Kafka custom resource. If omitted, authorization is disabled.

Network Security

  • Place brokers in a private network
  • Use port-based firewalls to restrict access to broker and ZooKeeper ports
  • Use web-access firewalls to limit the set of allowed requests
  • Do not expose broker ports to the public Internet unless required

Monitoring

  • Monitor access patterns to detect unknown entities accessing topics
  • Alert on anomalous client behavior (unusual topic access, volume spikes)
  • Integrate with Elasticsearch/Kibana or equivalent for real-time KPI monitoring

Implementation Checklist

  • TLS/SSL is enabled for all client-to-broker communication
  • TLS is enabled for broker-to-broker (inter-broker) communication
  • Authentication is configured on every listener (SSL, SASL, or OAuth)
  • ACLs restrict topic access to authorized clients only
  • Super users are limited to cluster administration accounts
  • Brokers are deployed in a private network with firewall rules
  • Monitoring and alerting are configured for access anomalies
  • AMQ Streams CA certificates are managed and rotated

References

Frequently asked questions

What does the Kafka Amq Security AI skill do?

Secure Kafka and AMQ Streams deployments with encryption, authentication, and authorization. Use when building, reviewing, or auditing Kafka broker configuration, AMQ Streams custom resources, or Kafka client connectivity.

Why use Kafka Amq Security on TypingMind?

Because you install it once and use it with any model. Kafka Amq Security is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Kafka Amq Security in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/kafka-amq-security. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Kafka Amq Security?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Kafka Amq Security?

As many as you like. As long as a model supports skills, you can use Kafka Amq Security with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Kafka Amq Security AI skill free?

Yes. It is published on GitHub by RedHatProductSecurity under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇