docs: add a how-to guide for securing a charm - #2721
Draft
tonyandrewmeyer wants to merge 3 commits into
Draft
Conversation
The security explanation ends with a list of good practices, but there was nowhere task-oriented to send someone who has been asked to harden a charm. Turn those practices into a how-to they can work through, and link the two pages to each other.
tonyandrewmeyer
commented
Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The security explanation finishes with a list of good practices, but there's nowhere task-oriented to send someone who has been asked to harden a charm, so this adds a how-to that turns those practices into sections you can work through: keeping sensitive data out of logs and traces, Juju secrets, HTTPS for tracing, static checks, keeping dependencies patched, restricting what the charm can do on its host, hardening the workload, checking the deployed
opsversion, documenting the posture, and reporting vulnerabilities. The explanation index now points at it, so you can go from why to what.Preview.
Fixes #2656