Grafana secrets encryption and key management
How Grafana protects data source passwords and tokens in its database: envelope encryption, protecting secret_key, KMS options in Enterprise, re-encrypting after a key change and rotating data keys.

Specific security controls for self-hosted Grafana beyond baseline hardening: secrets encryption, plugin trust, audit trails, patching and sharing exposure.
How Grafana protects data source passwords and tokens in its database: envelope encryption, protecting secret_key, KMS options in Enterprise, re-encrypting after a key change and rotating data keys.
Deciding which plugins to trust: signature levels and statuses, why unsigned plugins do not load, the risk of allow_loading_unsigned_plugins, and a review process for community plugins.
What Grafana audit logging records, the Enterprise requirement, sending audit events to Loki or files, and how teams on the open-source edition reconstruct changes from server logs and dashboard versions instead.
Keeping Grafana patched: following Grafana Labs security advisories, patch release cadence, supported minor versions, plugin updates and a tested path to apply fixes quickly.
Reducing what leaves Grafana through sharing features: external snapshot publishing, externally shared dashboards and their annotation behaviour, anonymous access and the settings that turn them off.
Scoping a security test of a self-hosted Grafana: authentication and role mapping, data source proxying, plugins, sharing features, the hardening settings a tester will check, and retesting after fixes.

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.