N10-009 ยท Remote access, encryption and identity
Encryption and certificates (PKI)
Data in transit vs at rest, PKI, self-signed certificates.
Key points
- Data in transit: protected while crossing a network (TLS, IPsec, SSH).
- Data at rest: protected where stored (disk, database or backup encryption).
- PKI: binds a public key to an identity with an X.509 certificate signed by a certificate authority (CA).
- Clients trust a certificate if its chain leads to a trusted CA.
- Self-signed: signed by its own key, no CA vouches; clients warn unless it is manually trusted.
Practice questions
Which entity signs a certificate to vouch that a public key belongs to a named subject?
- Certificate authority
- DHCP server
- Reverse proxy
- RADIUS client
Show answer
Answer: A. Certificate authority
A certificate authority issues and signs certificates. A DHCP server hands out addresses, a proxy relays requests, and an authenticator is not what signs certificates.
Which measures protect data at rest?
- Full-disk encryption on a laptop
- Encrypting backup volumes before storing them
- Using TLS between a browser and a web server
- Running an IPsec tunnel between two sites
- Using SSH for remote administration
Show answer
Answer: A. Full-disk encryption on a laptop, B. Encrypting backup volumes before storing them
Full-disk and backup encryption protect stored data. TLS and IPsec protect data in transit.
True or false: a server's TLS certificate contains the server's private key, which is why clients can verify it.
Show answer
Answer: False
False. The certificate holds the public key and identity details. The private key stays secret on the server; if it leaked, the identity could be impersonated.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
