Skip to content

Update security-guide.md#3362

Draft
Meggielqk wants to merge 2 commits intorelease-5.9from
260213-update-security-guide
Draft

Update security-guide.md#3362
Meggielqk wants to merge 2 commits intorelease-5.9from
260213-update-security-guide

Conversation

@Meggielqk
Copy link
Copy Markdown
Collaborator

No description provided.

@Meggielqk Meggielqk added this to the 5.9.0 milestone Feb 13, 2026
The host operating system is the first line of defense against resource exhaustion and volumetric attacks.

- [Authorization](./authz/authz.md)
- [ ] **Kernel Tuning**: Set `fs.file-max` and `fs.nr_open` > 2 million to ensure the host can allocate enough sockets for massive concurrent connections. For more information, see [Performance Tuning](../performance/tune.md)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please also add: turn off swap memory (see details in the tune doc). it's the 1st item in the tune doce, but yet a lot dont notice.

Hardening the Erlang runtime is critical to defending against lateral movement and unauthorized cluster access.

EMQX provides a blacklisting/banning functionality. System admins can block certain clients from accessing EMQX via Dashboard or HTTP API with their client ID, user name, or IP address.
- [ ] **Cookie**: Replace the default cookie with a high-entropy, 32+ character random string to prevent rogue nodes from joining the cluster.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [ ] **Cookie**: Replace the default cookie with a high-entropy, 32+ character random string to prevent rogue nodes from joining the cluster.
- [ ] **Cookie**: Replace the default cookie with a high-entropy, 32+ character random alphanumeric string to prevent rogue nodes from joining the cluster.

This layer enforces granular access control and resource protection for authenticated clients. Authentication and Authorization mechanisms are essential for verifying client identities and controlling publish/subscribe operations.

- [ ] **Authentication**: Ensure a non-empty authentication chain is configured to prevent anonymous connections.
- [ ] **Authorization**: Implement ACLs with a strict "Deny by Default" final rule to isolate device traffic.
Copy link
Copy Markdown
Member

@zmstone zmstone Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure the last rule in acl.conf is {deny, all}.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants