TLS for the Graylog web interface, API and inputs
Encrypting every Graylog connection: HTTPS for the web interface and API, TLS on Beats, Syslog and GELF inputs, certificate file permissions and Data Node TLS to OpenSearch.

Specific security controls for self-hosted Graylog beyond baseline hardening: encryption in transit, roles and sharing, audit trails and protecting the backends.
Encrypting every Graylog connection: HTTPS for the web interface and API, TLS on Beats, Syslog and GELF inputs, certificate file permissions and Data Node TLS to OpenSearch.
Controlling who can search which logs: roles for actions, sharing for streams and dashboards, teams in Enterprise, restricting input creation and reviewing access for compliance.
Recording who changed what in Graylog: Enterprise audit logging, signed entries, retention in MongoDB, exports through the API and backing entries up before they expire.
Locking down the Graylog backends: MongoDB authentication, network restrictions so only Graylog reaches MongoDB and OpenSearch, Data Node managed certificates and protecting support bundles that contain secrets.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.