Cryptographic solutions for SY0-701

Exam objectiveExplain the importance of using appropriate cryptographic solutions

The short answer

What objective 1.4 asks you to know

Objective 1.4 covers applied cryptography: key and certificate management, encryption levels, hardware that protects keys, ways to hide or replace data, and how hashing, signatures, and ledgers prove integrity.

Keys and certificates. PKI lets you trust that a public key belongs to its claimed owner. The public key is shared and verifies or encrypts; the private key stays secret and signs or decrypts. Key escrow gives a third party a key copy under controlled release. A certificate binds a public key to a named entity; it is requested with a certificate signing request (CSR), signed by a third-party CA that chains to a root of trust, or self-signed, and can cover many hosts as a wildcard certificate. Revocation is checked through a downloaded CRL or an on-demand OCSP query.

Encryption and key protection. Encryption applies at the full-disk, partition, volume, file, database, or record level, or in transport. Symmetric encryption uses one shared key; asymmetric encryption uses a public and private pair, which supports key exchange, signatures, and certificates. A TPM ties keys to one device, an HSM performs key operations for many systems, a key management system manages the key lifecycle, and a secure enclave isolates code and data from the main operating system.

Integrity and obfuscation. Hashing is one-way. Salting and key stretching make password hashes harder to crack. A digital signature, made with the signer's private key, proves origin and integrity, and a blockchain is a hash-linked ledger that makes altered history detectable. Steganography hides that data exists, tokenization swaps a value for a token mapped in a vault, and data masking hides or fakes part of a value.

Exam questions ask you to pick the right tool for a scenario: which key encrypts or verifies, why a salt helps, or what a TPM or HSM does.

Written by Knotch · reviewed Nov 15, 2026 · 8 study articles behind this page

Practice the rest

This page is the map. Knotch is where you drill it until it sticks.

  • 8step-by-step lessons with predict-and-reveal and look-alike duels
  • 65exam-style questions with a rationale for every wrong answer
  • 1review queue that brings back what you missed
Start practicing freeFree to start. No card needed.
Tell them apart

Pairs people mix up

  • Hashing vs. Encryption

    Hashing is one-way, so it suits integrity checks and password storage. Encryption is reversible with a key, so it protects data you need to read later.

  • Symmetric encryption vs. Asymmetric encryption

    Symmetric encryption uses one shared key for both encrypting and decrypting. Asymmetric encryption uses a pair, one public and one private, so the public key can be shared openly.

  • CRL vs. OCSP

    A CRL is a list of revoked certificates the client downloads and reuses, so it can be out of date between publications. OCSP asks the CA's responder about one certificate at connection time, or the server staples a recent signed response.

  • Tokenization vs. Data masking

    Vault-based tokenization keeps the real value in a vault so an approved system can look it up. Masking hides part of the value or swaps in a fake, and the masked copy holds nothing to look up.

The full set of look-alike pairs for this objective is inside Knotch.

Know these cold

Key terms

Salting
Adding a unique random value, stored beside each password hash, before hashing, so identical passwords get different hashes and precomputed rainbow tables become useless.
Key stretching
Using deliberately slow algorithms such as PBKDF2, bcrypt, or Argon2, which repeat the hashing work many times, and in Argon2's case use a lot of memory, so each password guess costs more.
OCSP
Online Certificate Status Protocol, which asks the CA's OCSP responder about one certificate's revocation status on demand instead of downloading a full list.
Hardware security module (HSM)
A dedicated tamper-resistant appliance or card that signs or decrypts for applications so the private key never leaves it.
Trusted Platform Module (TPM)
A chip, or firmware equivalent, built into one machine that stores keys bound to it, measures the boot process, and can release a disk key only if the system state matches.
Tokenization
Replacing a sensitive value with a substitute token. Commonly a random token mapped in a protected vault; other designs exist, such as cryptographic token generation or irreversible tokens. In the vault design, approved systems retrieve the real value through the mapping.
Try one

Sample question

Question 1.4-002 · medium

An attacker steals a password table that stores unsalted SHA-1 hashes and cracks most of them within hours using precomputed tables.

Which change most improves resistance to offline cracking?

  1. A. Store passwords with a slow, salted hash such as bcrypt or Argon2
  2. B. Encrypt each hash with AES using a key stored in the same database
  3. C. Switch to another fast, unsalted hash such as SHA-256 or SHA-512
  4. D. Base64 encode the existing hashes before storing them again
Show the answer and why
Answer: A, Store passwords with a slow, salted hash such as bcrypt or Argon2

Unique salts defeat precomputed tables and a tunable work factor makes each guess expensive.

Password storage needs salting and key stretching so that each guess costs significant computation.

Why not B: Compromise of the database exposes the key too; the weakness of fast, unsalted hashing remains.

Why not C: A different fast hash without salts is still vulnerable to rapid brute force and tables.

Why not D: Encoding adds no security at all.

Quick answers

Common questions on this objective

What is the difference between a TPM and an HSM?

Both hold keys in dedicated hardware. A TPM is part of one machine and ties keys to how that machine started, while an HSM is a separate high-capacity appliance that signs and decrypts for many servers.

Does a digital signature encrypt the data?

No. A signature, made with the signer's private key, proves who produced the data and that it has not changed, but it does not hide the content. To keep it secret, encrypt it as well.

Why do password hashes need a salt?

A unique salt per password means two users with the same password get different hashes, which makes precomputed rainbow tables useless.

Know it. Now spot it in a scenario.

Start practicing free