This article updates a topic from the Concise Courses webcast archive. See the full InfoSec archive for more.
Cryptography underpins almost everything in security: secure websites, encrypted messages, software updates, password storage and digital identity. You do not need to be a mathematician to work in security, but you do need to understand the building blocks and how they are used, and misused.
The Building Blocks
| Primitive | What it does | Common examples |
|---|---|---|
| Symmetric encryption | Encrypts and decrypts with the same secret key; fast | AES, ChaCha20 |
| Asymmetric encryption | Uses a public and private key pair; solves key exchange | RSA, elliptic curve cryptography |
| Hash functions | Create a fixed-size fingerprint of data; one-way | SHA-256, SHA-3 |
| Password hashing | Deliberately slow hashing for stored passwords | Argon2, bcrypt, scrypt |
| Digital signatures | Prove who created data and that it was not changed | ECDSA, Ed25519, RSA signatures |
| Message authentication codes | Verify integrity and authenticity with a shared key | HMAC |
Public Key Infrastructure
Public key infrastructure (PKI) ties public keys to identities through certificates issued by trusted certificate authorities. It is what lets your browser trust that it is really talking to your bank. Free, automated certificate authorities have made HTTPS the default across the web.
How It Comes Together: TLS
When you visit a secure website, TLS uses asymmetric cryptography to authenticate the server and agree on keys, then fast symmetric encryption to protect the data, with integrity checks throughout. It is a good example of how primitives combine into a protocol.
Common Mistakes
- Inventing your own algorithms or protocols instead of using well-reviewed libraries.
- Using outdated algorithms such as MD5, SHA-1, DES or RC4.
- Storing passwords with fast hashes rather than password-hashing functions.
- Hard-coding keys in source code or failing to rotate them.
- Confusing encoding (such as Base64) with encryption.
Key Management
Strong algorithms are useless if keys are poorly protected. Use hardware security modules or cloud key management services for important keys, limit who can use them, rotate them and plan for recovery.
The Post-Quantum Transition
Large quantum computers could one day break today’s widely used public key algorithms. In 2024, the US National Institute of Standards and Technology published its first post-quantum cryptography standards, and organizations are beginning to inventory where they use vulnerable algorithms and plan their migration.
Related reading: encryption tools and security protocols every secure website uses.
Frequently Asked Questions
Should developers write their own encryption code?
No. Use well-reviewed libraries and standard protocols. Small mistakes in custom cryptography can completely undermine security.
What is a cryptographic salt?
A salt is a random value added to each password before hashing, so identical passwords produce different hashes and precomputed attacks become impractical.
What is end-to-end encryption?
End-to-end encryption means only the communicating users can read messages; even the service provider cannot.
What is AES?
AES is the most widely used symmetric encryption standard.
Switzerland’s Cryptography Tradition
Switzerland combines world-class cryptography research at institutions such as ETH Zurich and EPFL with Zug’s ‘Crypto Valley’ blockchain industry, making it a natural home for applied cryptography talks. See the latest cybersecurity conferences in Switzerland.