← Knowledge base

ChromeOS

ChromeOS browser traffic, Android apps, and Linux-container applications can use different TLS implementations and policies.

Evidence to collect

1. Inventory the OS update channel and each relevant application.
2. Run the browser check in the managed or personal profile used for the workflow.
3. Test Android and Linux-container applications independently; the Chrome result does not cover them.

Record the scope and result

Record the tested component, client, peer, protocol, selected algorithm, and date. Keep observed negotiation, documented capability, and unknown distinct. A failed check can reflect local tooling, certificate validation, network policy, or configuration; it does not prove that all PQC is unsupported.

Official references

• Google ChromeOS update guidance

Guidance reviewed 25 September 2026. Verify documentation for your deployed release; vendor capabilities and defaults change.