Security model
Trust boundaries and security controls of myriarchd, its agents and the myriarch-updater, with the setting, default and remaining risk of each control.
Security
How myriarch protects the control plane, its agents and the software it delivers, and where to report a vulnerability.
This section describes the security controls of myriarch. It is written for operators who decide how to deploy the system and for reviewers who assess it.
- Security model lists the trust boundaries and, for each area, the control, the setting that governs it, its default and the risk that remains.
- Verify releases shows how to check a release before you run it:
checksums.txt, its keyless Sigstore bundle and the exact signing identity, then the build provenance, the immutable release, the container images, the Helm charts and the macOS binaries. - Export control is the maintainers’ assessment of the cryptography in the published software.
- Authentication is the operator guide for sign-in: the bootstrap admin, single sign-on with OpenID Connect and enrollment tokens.
- Production checklist collects the settings of
myriarchd servethat matter for a production installation.
To report a vulnerability, follow SECURITY.md. Please do not open a public issue for it.
Verify releases
Check a myriarch release before you run it: checksums, the Sigstore bundle, build provenance, container images, Helm charts and macOS binaries.
Export control
Assessment of the export-control status of the published software and its cryptography, for the maintainers; not legal advice.