# Security

The security model, the credential and session lifecycle, every key and token in one place, the hardening steps, how to report a vulnerability and the compliance mapping.


- [The security model](https://docs.straza.ai/security/security-model/index.md) explains what Straza protects, the invariants it holds and the residual risks it leaves with you.
- [Credentials and sessions](https://docs.straza.ai/security/credentials-and-sessions/index.md) follows an enrolled machine through token refresh, session limits and revocation.
- [Keys, certificates and tokens](https://docs.straza.ai/security/keys-certificates-and-tokens/index.md) names every key and credential you protect, back up and rotate.
- [Hardening](https://docs.straza.ai/security/hardening/index.md) tightens a deployment beyond the defaults, one control at a time, and pairs with [TLS and exposure](https://docs.straza.ai/guides/operate/tls-and-exposure/index.md).
- [Reporting a vulnerability](https://docs.straza.ai/security/reporting/index.md) says how to report a vulnerability privately and how the response runs.
- [Compliance mapping](https://docs.straza.ai/security/compliance/index.md) maps Straza controls to ISO 27001 Annex A and NIS2 Article 21(2).
- [Supply chain](https://docs.straza.ai/security/supply-chain/index.md) explains how a release is built, signed and verified.

To respond to a login or access incident, lock the person or device out with the [kill-switch runbook](https://docs.straza.ai/guides/operate/kill-switch-runbook/index.md), then read [Credentials and sessions](https://docs.straza.ai/security/credentials-and-sessions/index.md) for what each lockout does.

- [Known limits](https://docs.straza.ai/security/known-limits/index.md) gives one table of each limit, its impact, today's mitigation and the planned fix.


- [The security model in depth](https://docs.straza.ai/security/security-model/index.md): What Straza defends, where each defense holds, the invariants behind it with what each one costs, and the mechanism behind the limits it leaves with you.
- [Known limits](https://docs.straza.ai/security/known-limits/index.md): Every limit of what Straza protects in one table, with what it means for you, what reduces it today and what the roadmap plans, and the scale ceilings of one deployment.
- [Hardening](https://docs.straza.ai/security/hardening/index.md): Every security setting checked against its default in both profiles, and each control the profiles leave to you turned on, with the command that proves it.
- [Credentials and sessions](https://docs.straza.ai/security/credentials-and-sessions/index.md): Which credential sits where on a machine, how long each one lives, how a session renews, and how to stop each one.
- [Keys, certificates and tokens](https://docs.straza.ai/security/keys-certificates-and-tokens/index.md): Every key and token Straza holds, where it lives, how long it lasts, how to rotate or revoke it, and what a stolen copy yields.
- [Reporting a vulnerability](https://docs.straza.ai/security/reporting/index.md): Where to report a vulnerability in private, what a useful report holds, what happens after you send it, and what is in scope.
- [Compliance mapping](https://docs.straza.ai/security/compliance/index.md): Which NIS2 Article 21(2) measures and ISO/IEC 27001:2022 Annex A controls Straza supplies evidence for, and the mechanism behind each one.
- [Supply chain](https://docs.straza.ai/security/supply-chain/index.md): What a release holds, how to verify its signatures and the macOS pkg's Developer ID signature and notarization, how to rebuild its binaries from source, and what CI checks before a tag.
