Certificate Authority
Also called CA.
A trusted entity that issues and signs digital certificates.
What it is
An organization that verifies the identity of certificate requesters and issues digitally signed certificates binding a public key to that identity. Operating systems and browsers ship with a set of trusted root CAs.
Why it matters
A CA is a single point of trust for everyone relying on its certificates, so a compromised or rogue CA can issue valid certificates for any domain and enable undetected interception. CA mis-issuance is one of the most serious failures in web security.
In practice
An attacker who fraudulently obtains a certificate from a CA being able to impersonate a bank's website.
What to look for
- Certificates for your domains from CAs you do not use.
- New root certificates added to device trust stores.
- Unusual issuance volume from an internal CA.
Common mistake
Trusting every CA in the store equally. Watch certificate transparency for your domains to spot rogue issuance.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
OpenSSL Open source
The command line toolkit for inspecting certificates, keys and TLS connections.
-
HashiCorp Vault Source available
Manages secrets and encryption keys, and can encrypt data as a service.
-
AWS Key Management Service Cloud service
AWS's managed service for creating and controlling encryption keys.
Read next
- Public Key Infrastructure: The system of authorities and certificates that binds keys to identities.
- Certificate Transparency: Public append-only logs of every issued TLS certificate.
- Certificate Pinning: Hardcoding a known certificate or key so others are rejected.