A digital certificate is an electronic document that binds a public key to a verified identity and is signed by a trusted certificate authority (CA). When you open an HTTPS site, the server presents its certificate to prove it controls that domain, and your browser checks the CA signature and the validity dates before trusting the connection. The certificate is what makes an anonymous public key actually mean something.
Each certificate carries the subject name, the public key, a validity period, issuer details, and the CA’s signature, all structured in the X.509 format. Certificates come in validation levels, from domain validation, which only proves control of a name, up to organization and extended validation, which involve checks on the entity itself. A practical warning: a self signed certificate encrypts traffic but proves no identity, so treating it as equal to a CA issued one defeats the whole point of the trust model.
Why do digital certificates matter for the CISSP exam?
Certificates appear in Domain 3: Security Architecture and Engineering, worth 13 percent of the exam. Know the certificate contents, the validation process, and the gap between self signed and CA issued certificates.
The format is defined in ITU-T X.509.