Encryption
Encryption is the cryptographic transformation of readable data into ciphertext to conceal its contents, reversible through decryption with appropriate information.
Software Security for Developers
Encryption is the transformation of readable data into an encoded form intended to prevent unauthorized access.
- How it is used
- Protects user data, service-to-service files, cloud services, and communications crossing untrusted networks.
- How deep it goes
- Explains practical AES, RSA, ECC, and TLS usage through Java examples while deferring mathematical foundations and exhaustive protocol internals.
- Examples
- Uses AES modes, encrypted refunds.json files, warehouse and payments services, RSA signatures, ECC key pairs, and intercepted TLS traffic.
- What you can do after
- Apply encryption with Java cryptographic APIs and configure TLS while recognizing eavesdropping, tampering, and impersonation risks.
Read how Software Security for Developers explains encryption →
Spring Security in Action, Second Edition
Encryption is the transformation of readable data into ciphertext using a cryptographic key so that only authorized parties can recover the original data.
- How it is used
- Protects persisted data, secrets, and data exchanged between system components from readable exposure or unauthorized access.
- How deep it goes
- Defines encryption, decryption, symmetric keys, and asymmetric key pairs, then contrasts encoding and hashing without detailing algorithm internals.
- Examples
- Uses stored secrets, component-to-component communication, and the keyed transformation (x, k) -> y as examples.
- What you can do after
- Evaluate encryption against hashing and encoding, and recognize whether a scenario requires symmetric or asymmetric keys.
Read how Spring Security in Action, Second Edition explains encryption →
Real-World Cryptography
Encryption is the transformation of plaintext into ciphertext so that the information is concealed from unauthorized parties.
- How it is used
- Protects confidentiality by concealing messages from unwanted observers during communication.
- How deep it goes
- Defines encryption through black-box ENCRYPT and DECRYPT functions, stopping short of describing their internal construction.
- Examples
- Uses Alice’s letter, an untrusted messenger, a shared secret key, and the ENCRYPT–DECRYPT exchange.
- What you can do after
- Evaluate/understand how a shared-key protocol conceals a message and lets an intended recipient recover it.
Grokking Relational Database Design
Encryption is the transformation of readable data into encoded information that cannot be understood without the appropriate decryption capability.
- How it is used
- Protects sensitive database information from disclosure, including payment-method data exposed through unauthorized access.
- How deep it goes
- Gives storage-design steps—choose a method, encrypt data, and size columns—without explaining encryption algorithms or decryption.
- Examples
- Uses customers’ credit-card information and payment_method card_number and expiry_date columns as storage examples.
- What you can do after
- Apply it by selecting an encryption method and designing database columns with room for encrypted sensitive values.
Read how Grokking Relational Database Design explains encryption →
Grokking Web Application Security
Encryption is the cryptographic transformation of readable data into a protected representation that can be reversed with the appropriate key.
- How it is used
- Secures web data in transit, at rest, and in client-visible session state.
- How deep it goes
- Defines encryption practically and gives deployment steps, while deferring algorithm internals and advanced mathematics.
- Examples
- Uses a historical cipher, a password-database breach, hash comparison, and signed cookies or JWTs.
- What you can do after
- Operate/configure it by deploying HTTPS protections and choosing encryption or hashing for sensitive application data.
Read how Grokking Web Application Security explains encryption →
Kafka for Architects
Encryption is the transformation of readable data into a form accessible only through an appropriate cryptographic key.
- How it is used
- Protects Kafka communications and stored or sensitive data as part of an enterprise deployment security strategy.
- How deep it goes
- Explains transport, disk-level, and end-to-end choices with design constraints, but defers detailed configuration properties and setup instructions.
- Examples
- Uses a Customer 360 protocol matrix and producer-side encryption with consumer-side decryption to illustrate distinct protection boundaries.
- What you can do after
- Evaluate/understand encryption choices for Kafka traffic and stored data, including their exposure, performance, compliance, and operational trade-offs.
Acing the CCNA Exam: Volume 2 Advanced Networking and Security
Encryption is the transformation of readable data into ciphertext that can be recovered only with the appropriate decryption capability.
- How it is used
- Protects communications from unauthorized reading, particularly across wireless networks and SNMP management exchanges.
- How deep it goes
- Defines terminology, distinguishes confidentiality from integrity, compares protocol support, and demonstrates SNMPv3 configuration without detailing encryption algorithms.
- Examples
- Uses overheard wireless login information, bit-flipping attacks, SNMPv3 security levels, and Cisco IOS AES-256 configuration.
- What you can do after
- Evaluate encryption choices, distinguish plaintext from ciphertext, and configure an SNMPv3 user with encrypted AuthPriv security.
Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains encryption →
AI-Powered Developer: Build software with ChatGPT and Copilot
Encryption is the cryptographic transformation of readable data into an encoded form that unauthorized parties cannot readily interpret.
- How it is used
- Uses encryption to protect sensitive application data at rest and traffic moving between REST controllers and browsers.
- How deep it goes
- Explains encryption categories, algorithm choices, Python implementation, database storage, key management, and operational trade-offs.
- Examples
- Demonstrates Python Fernet code, SQLite3 storage, Flask REST endpoint protection, and the Ashley Madison breach.
- What you can do after
- Apply it via Python and HTTPS while reviewing key handling, database integration, security layers, and performance consequences.
Read how AI-Powered Developer: Build software with ChatGPT and Copilot explains encryption →
Apache Kafka in Action
Encryption transforms readable data into an encoded form that requires a corresponding decryption method to recover.
- How it is used
- Protects Kafka data in transit and at rest, with end-to-end encryption for highly sensitive data.
- How deep it goes
- Distinguishes transport, disk, and end-to-end encryption, explains their limits, and notes ZooKeeper TLS without detailing its configuration.
- Examples
- Contrasts Kafka network traffic, stored disks, sensitive messages, and broker-to-ZooKeeper connections.
- What you can do after
- Apply TLS to Kafka transport, encrypt storage through underlying systems, and use client-level end-to-end encryption for sensitive data.
Build AI-Enhanced Web Apps
Encryption is the transformation of readable data into an encoded form that requires a corresponding key or process to recover.
- How it is used
- Protects sensitive chat histories and supports data privacy in AI application deployment.
- How deep it goes
- Identifies encryption’s role and names AES, but provides no implementation steps.
- Examples
- Uses chat histories containing personally identifiable or financial information, and sensitive data at rest and in transit.
- What you can do after
- Apply encryption as a production privacy control for sensitive data at rest and in transit.
Data Pipelines with Apache Airflow, Second Edition
Encryption is the transformation of readable data into ciphertext that requires a cryptographic key for recovery.
- How it is used
- Protects Airflow database secrets at rest and provides encryption for HTTPS connections.
- How deep it goes
- Explains symmetric Fernet encryption, key configuration, and key risks; HTTPS coverage focuses on certificate trust.
- Examples
- Demonstrates generating a Fernet key in Python, configuring Airflow, and creating a self-signed certificate with OpenSSL.
- What you can do after
- Operate Airflow secret encryption by generating and configuring a Fernet key while guarding against key loss or exposure.
Read how Data Pipelines with Apache Airflow, Second Edition explains encryption →
The Art of AI Product Development
The transformation of data into a protected representation that requires authorized decryption to read.
- How it is used
- Protects customer data sent to and from commercial LLMs as part of privacy risk management.
- How deep it goes
- Specifies encryption in transit and at rest, but does not explain cryptographic implementation.
- Examples
- Uses third-party LLM data flows and a ChatGPT data-leakage case to contextualize encryption safeguards.
- What you can do after
- Apply encryption to data sent to and received from third-party LLMs, both in transit and at rest.
Read how The Art of AI Product Development explains encryption →
Microsoft Azure in Action
Encryption is the transformation of data into an encoded form that requires a key or equivalent secret to recover the original content.
- How it is used
- Protects stored Azure Storage data and Azure SQL connections as part of data protection and defense in depth.
- How deep it goes
- Explains transparent AES-256 storage encryption and TLS/SSL in transit, then demonstrates setting an Azure SQL minimum TLS version.
- Examples
- Uses Azure Storage's transparent AES-256 encryption and an Azure CLI command setting Azure SQL's minimum TLS version.
- What you can do after
- Configure Azure SQL's minimum TLS version using Azure CLI.
Generative AI in Action
Encryption is the transformation of readable data into a protected form that requires a key or equivalent mechanism to recover.
- How it is used
- Protects sensitive user, application, and model data in enterprise GenAI systems.
- How deep it goes
- Defines protection for data at rest and in transit but does not detail algorithms or key management.
- Examples
- Uses TLS for data in transit and cloud-provider encryption features for data at rest.
- What you can do after
- Apply encryption to data at rest and in transit using TLS and cloud-provider features.
Server-Side WebAssembly
Encryption is the process of transforming readable plaintext into ciphertext using a key so that unauthorized parties cannot read it.
- How it is used
- Protects sensitive data by executing encryption and decryption inside a libSQL database through sandboxed Wasm UDFs.
- How deep it goes
- Explains project setup, dependencies, bindings, exported functions, and runtime constraints, but does not develop cryptographic theory.
- Examples
- Uses encrypt and decrypt UDFs with string data, a key, Base64 output, and an access-denied fallback.
- What you can do after
- Build it from scratch as a Rust cdylib exposing libSQL-compatible encrypt and decrypt functions.
Data for All
Encryption is the transformation of readable data into coded form so that it cannot be understood without the appropriate key or decryption process.
- How it is used
- Protects sensitive health data and private communications while supporting carefully controlled data sharing.
- How deep it goes
- Defines encryption through coded, unreadable data and discusses protections and risks without implementation detail.
- Examples
- Uses Telegram, Signal, Threema, and WhatsApp as encrypted messaging examples and healthcare data as a protection case.
- What you can do after
- Evaluate how encryption can protect privacy while also obstructing monitoring and shielding misuse.
Related concepts
- ciphertextproduces · Ciphertext is data produced by encryption whose original content is intended to be unreadable without the required decryption capability.
- Base64contrasts with · Base64 is a binary-to-text encoding scheme that represents arbitrary bytes using a fixed 64-character alphabet and provides no confidentiality.
- plaintextproduces · Plaintext is information in a directly readable, unencrypted form rather than a cryptographically encoded form.
- hash functioncontrasts with · A hash function deterministically maps input data to a value in a bounded output range, commonly for indexing, lookup, comparison, or integrity checking.
- homomorphic encryptionincludes · Homomorphic encryption is encryption that permits specified computations on ciphertexts whose decrypted results correspond to computations on the underlying plaintexts.
- symmetric key encryptionincludes · Symmetric-key encryption is cryptography that uses the same shared secret key, or equivalent derived key material, to encrypt and decrypt data.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.