Cryptography & PKI

Security+ SY0-701 · General Security Concepts

By Abu Anns · Last updated 20 November 2026Exam version: SY0-701

Why cryptography matters on this exam

Cryptography is one of the heaviest single topics in Domain 1, and it is also one of the most testable: the exam asks about encryption algorithms, key lengths, hashing, digital signatures, and certificates in scenarios that reward precise knowledge. The good news is that the concepts are logical once you separate the four jobs cryptography does: keeping data secret (encryption), proving data has not changed (hashing), proving who sent it (digital signatures), and managing the keys that make all of it work (PKI).

Symmetric vs asymmetric encryption

Symmetric encryption uses one shared secret key for both encryption and decryption. It is fast and efficient, which makes it the right choice for encrypting large amounts of data, but it has one hard problem: both sides need the same key, and getting that key to the other party securely is difficult. The standard symmetric algorithm is AES (Advanced Encryption Standard), with key lengths of 128, 192, or 256 bits — AES-256 is the strongest and the most commonly required. Older symmetric algorithms such as DES and 3DES are deprecated and should never be chosen on the exam when a modern alternative is available. ChaCha20 is a modern stream cipher often used on mobile devices.

Asymmetric encryption uses a key pair: a public key that anyone can use to encrypt, and a private key that only the owner holds and uses to decrypt. It solves the key distribution problem, but it is much slower than symmetric encryption, so in practice it is used to exchange a symmetric session key and then the bulk data is encrypted symmetrically — this is how TLS works. The main asymmetric algorithms are RSA (key lengths of 2048 or 4096 bits are current practice) and ECC (elliptic curve cryptography), which provides equivalent security with much shorter keys. Diffie-Hellman is a key exchange protocol that lets two parties agree on a shared secret over an insecure channel; its ephemeral variant, ECDHE, provides forward secrecy, meaning that even if a private key is compromised later, past sessions cannot be decrypted.

Hashing, salting, and digital signatures

A hash is a one-way function: it takes input of any size and produces a fixed-length output (a digest), and it cannot be reversed. Hashing proves integrity — if even one character of the input changes, the digest changes completely. The standard hash algorithms are the SHA-2 family (SHA-256, SHA-512); MD5 and SHA-1 are broken and deprecated. When passwords are stored, they should be hashed with a unique random salt added first, which defeats rainbow table attacks because the same password hashes differently for every user. Key stretching algorithms such as bcrypt, scrypt, and PBKDF2 deliberately make hashing slow, which makes brute-force attacks expensive. An HMAC combines a hash with a secret key, so the receiver can verify both integrity and authenticity.

A digital signature proves who sent a message and that it was not altered. The sender hashes the message and encrypts the hash with their private key; anyone can verify it with the sender's public key. If the message changed, the hash will not match; if the signature verifies, only the holder of the private key could have created it. This provides non-repudiation: the sender cannot later deny signing. Note the direction: signing uses the private key, and verification uses the public key — the opposite of encryption, where the public key encrypts and the private key decrypts. Confusing these two directions is a classic exam error.

PKI and certificates

Public key infrastructure (PKI) is the system that makes asymmetric cryptography trustworthy at scale. At its heart is the certificate authority (CA), a trusted organization that issues digital certificates binding a public key to an identity. The hierarchy runs from a root CA (whose certificate is self-signed and must be protected above all else) through intermediate CAs down to the end-entity certificates used by websites and users. To get a certificate, an applicant generates a key pair and sends a certificate signing request (CSR) to the CA, which verifies the applicant's identity and issues the certificate.

Certificates have a limited lifetime and can be revoked before they expire. Revocation is checked in two ways: a certificate revocation list (CRL), a published list of revoked certificates that clients download, and OCSP (Online Certificate Status Protocol), which lets a client ask the CA about one specific certificate in real time. OCSP stapling improves on this by having the server attach a recent OCSP response to the handshake, so the client does not need to contact the CA. Other certificate types to know: a wildcard certificate covers a domain and all its subdomains (*.example.com), a self-signed certificate is signed by its own creator rather than a trusted CA and triggers browser warnings, and an extended validation (EV) certificate requires the strictest identity checks. A key escrow arrangement stores a copy of private keys with a trusted third party so they can be recovered if lost.

Key management, encryption levels, and obfuscation

Keys must be generated, stored, rotated, and destroyed securely. Hardware helps: a TPM (Trusted Platform Module) is a chip on a device that stores keys and can verify the boot process, an HSM (hardware security module) is a dedicated device that manages keys for servers and applications, and a secure enclave is an isolated area of a processor that protects sensitive operations. Encryption can be applied at different levels: full-disk encryption protects everything on a drive (useful if a laptop is stolen), volume encryption protects a partition, database encryption protects data at rest in a database, and record- or field-level encryption protects individual pieces of data such as credit card numbers. Data in transit is protected by protocols such as TLS; data at rest by disk, volume, or database encryption.

Obfuscation techniques hide data without true encryption. Tokenization replaces sensitive data with a meaningless token (common in payment processing, where the real card number is stored in a secure vault and only the token circulates). Data masking hides part of the data, such as showing only the last four digits of a card number. Steganography hides the existence of a message entirely, for example by embedding text inside an image file. Blockchain uses hashing and distributed consensus to create a tamper-evident ledger; the exam treats it as a cryptographic concept, not as a currency topic. Remember that obfuscation is not encryption: it hides data, but it does not provide the mathematical protection that encryption does.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A company needs to encrypt several terabytes of archived data stored on its servers. The data will rarely be accessed, and encryption speed matters more than key exchange. Which encryption approach is most appropriate?

Report an error

Q2.A developer wants to let users verify that a software update really came from the company and has not been tampered with. Which mechanism provides both authentication of the sender and proof the file is unaltered?

Report an error

Q3.A security audit finds that a web application stores user passwords as unsalted MD5 hashes. Which two problems does this create? (Choose the best answer.)

Report an error

Q4.A company wants its employees' laptops protected so that the data cannot be read if a laptop is stolen. The protection must cover everything on the drive, including the operating system. Which solution should be deployed?

Report an error

Q5.A browser warns a user that a website's certificate is not trusted. The certificate was issued and signed by the website's own administrator rather than by a public certificate authority. What type of certificate is this?

Report an error

Q6.A certificate authority needs to revoke a compromised server certificate immediately. Which mechanism lets a client check the status of that one specific certificate in real time?

Report an error

Q7.Two parties need to agree on a shared secret key over a public network, and the security team requires that past sessions remain secure even if a long-term private key is compromised in the future. Which approach provides this property?

Report an error

Q8.An online retailer wants to process credit card payments without storing actual card numbers on its own servers. It replaces each card number with a random value that has no mathematical relationship to the original, while the real numbers are kept in a separate secure vault. What is this technique called?

Report an error