In X.509 architecture, a root certificate would be the trust anchor from which the whole chain of trust is derived. The trust anchor must be in the possession of the trusting party beforehand to make any further certificate path validation possible.
Most operating systems provide a built-in list of self-signed root certificates to act as trust anchors for applications. The Firefox web browser also provides its own list of trust anchors. The end-user of an operating system or web browser is implicitly trusting in the correct operation of that software, and the software manufacturer in turn is delegating trust for certain cryptographic operations to the certificate authorities responsible for the root certificates.
Hardware-based trust anchors include fenced-off memory regions or separate circuitry assumed to be secure.
- "Trust Anchor Format". RFC 5914. IETF. Retrieved February 21, 2013.
- Lily Hay Newman (2019-05-13). "A Cisco Router Bug Has Massive Global Implications". Wired.
|This computer security article is a stub. You can help Wikipedia by expanding it.|