liveBook · Manning

Security

Also called cybersecurity

Security is the protection of systems, information, and resources against unauthorized access, use, disclosure, alteration, disruption, or destruction.

How 36 Manning books explain it

AI for Everyday IT

Cybersecurity is the practice of protecting digital systems, networks, applications, and data from threats and unauthorized activity.

How it is used
Applies security practices to AI-assisted document handling, development, email analysis, and application workflows.
How deep it goes
Provides practical checks and safeguards, including adversarial testing, without developing a formal security model.
Examples
Uses support logs, suspicious email headers, AI-generated code, and a natural-language database assistant as workplace examples.
What you can do after
Apply security checks when sharing data with AI, reviewing generated code, and limiting AI function access.

Read how AI for Everyday IT explains security →

The Cloud at Your Service: The when, how, and why of enterprise cloud computing

Protection of information systems and data against threats such as unauthorized access, fraud, and breaches.

How it is used
Frames security as a factor in enterprise decisions about public, private, and virtual private cloud deployment.
How deep it goes
Compares deployment risks, segregation, compliance, and incident response without providing a detailed implementation procedure.
Examples
Uses laptop data leakage, a VPN-connected virtual private cloud, and healthcare privacy requirements to illustrate security choices.
What you can do after
Evaluate security trade-offs among cloud deployment options without assuming that on-premises control or provider features alone guarantee protection.

Read how The Cloud at Your Service: The when, how, and why of enterprise cloud computing explains security →

Grokking Software Architecture

Security is the protection of software systems and their data from unauthorized access, misuse, disruption, or alteration.

How it is used
Treats security as an architectural quality and constraint that shapes decisions from initial design through production.
How deep it goes
Develops a breach-containment mindset into architectural controls and a step-by-step boundary audit.
Examples
Uses the Target vendor-portal breach and an Order Processor blast-radius audit to illustrate security failures and remedies.
What you can do after
Practice performing a boundary audit and documenting least-privilege and secret-handling decisions in an architecture decision record.

Read how Grokking Software Architecture explains security →

Build AI-Enhanced Web Apps

Protection of generative AI capabilities, application resources, and their outputs against unauthorized access, malicious misuse, and harmful exploitation.

How it is used
Protects public generative AI applications against unauthorized access, resource abuse, data exposure, and malicious use of generated content.
How deep it goes
Outlines layered request checks and production practices, distinguishing implemented document safeguards from proposed improvements.
Examples
Uses an AI interview assistant’s middleware and a RAG application’s document uploads to illustrate security measures.
What you can do after
Apply layered safeguards to public AI applications and assess additional protections for document workloads.

Read how Build AI-Enhanced Web Apps explains security →

The Art of AI Product Development

Cybersecurity is the practice of protecting computer systems, networks, software, and data from unauthorized access, disruption, alteration, or attack.

How it is used
Frames security as an AI governance responsibility spanning data, models, and production use.
How deep it goes
Explains AI-specific threats and outlines data classification, access controls, monitoring, and audits without detailed implementation code.
Examples
Uses a recommendation feature exposing proprietary customer data to illustrate exfiltration and corrective controls.
What you can do after
Supports evaluating AI security risks and applying governance controls across data flows and third-party components.

Read how The Art of AI Product Development explains security →

Effective Data Analysis

Data protection is the safeguarding of personal information through controls on its collection, access, processing, storage, sharing, retention, and deletion.

How it is used
Frames responsible analytics practice around protecting personal and sensitive data while honoring individual rights.
How deep it goes
Defines regulatory expectations and practical safeguards, but stops short of detailed implementation procedures or technical security architecture.
Examples
Uses PII, PHI, financial information, authentication credentials, sector-specific laws, and product-analytics consent documents as concrete cases.
What you can do after
Operate/configure data practices by limiting access, reducing collection, protecting storage, explaining use, and supporting deletion or withdrawal.

Read how Effective Data Analysis explains security →

Introduction to Generative AI, Second Edition

Security is the protection of an AI system, its data, and its interactions from unauthorized access, manipulation, disruption, or attack.

How it is used
Addresses both the security of AI systems and the use of AI agents in cybersecurity.
How deep it goes
Surveys attack types, defensive applications, and safeguards without implementation details.
Examples
Illustrates security with PentestGPT, Cortex XSOAR, and voluntary AI company commitments.
What you can do after
Evaluate security risks and safeguards for AI agents and their use in cybersecurity.

Read how Introduction to Generative AI, Second Edition explains security →

Delivering Machine Learning Projects: From design to deployment

Data security is the protection of data from unauthorized access, disclosure, alteration, loss, or destruction.

How it is used
Frames security as a pre-project requirement and delivery risk for ML systems.
How deep it goes
Identifies requirements and governance tasks but does not specify security controls or implementation procedures.
Examples
Names Privacy & Data Impact Assessment and Algorithmic Impact Assessment documents as project artifacts.
What you can do after
Practice identifying data security requirements and documenting related ethical and regulatory considerations before delivery.

Read how Delivering Machine Learning Projects: From design to deployment explains security →

Think Like a CTO

An operational setting in which systems, data, and activities are protected against unauthorized access, misuse, disruption, or compromise.

How it is used
Frames security as a continuing executive responsibility across systems, development, backups, and communication.
How deep it goes
Sets out identify, protect, and monitor as guiding actions, with concrete build and archive precautions rather than implementation-level instructions.
Examples
Uses the SolarWinds update attack, exposed cloud file storage, and accessible backup archives to show how protections can fail.
What you can do after
Practice/perform a recurring security review that includes development and backup access, not just production defenses.

Read how Think Like a CTO explains security →

Machine Learning System Design

Security is the protection of a system, its models, data, and interfaces from unauthorized access, misuse, or compromise.

How it is used
Frames security as a serving and inference design requirement shaped by deployment platform, data exposure, and model accessibility.
How deep it goes
Identifies platform risks and practical controls but defers detailed security treatment beyond protocols, isolation, credentials, and deployment tradeoffs.
Examples
Uses mobile model deployment, large language model jailbreaks, and isolated AWS batch forecasting for sensitive retail data.
What you can do after
Operate/configure serving systems with platform-appropriate protections, secured infrastructure, access controls, and explicit security tradeoffs.

Read how Machine Learning System Design explains security →

Spring Security in Action, Second Edition

Software security is the protection of software applications and their data against unauthorized access, misuse, disruption, and other security threats.

How it is used
Protects applications and data by treating security as an early, cross-cutting concern applied through multiple layers.
How deep it goes
Surveys data, memory, communication, and system layers, but focuses on Spring Security rather than every security layer.
Examples
Uses DDoS participation, heap dumps, intercepted messages, impersonation, and exposed logs or errors as vulnerability examples.
What you can do after
Apply layered protection to Spring applications and identify where application-level security does not address lower-layer threats.

Read how Spring Security in Action, Second Edition explains security →

Data-Driven Cybersecurity

Information security is the protection of information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction.

How it is used
Frames protection of critical data as an ongoing organizational risk-management task.
How deep it goes
Defines data-security goals and identifies protective layers, policies, and metrics, without specifying a complete control implementation.
Examples
Illustrates layered protection with a data-vault analogy and multichannel phishing with a voice-cloned IT call.
What you can do after
Evaluate/understand security controls using access, training, encryption, incident-response, and availability metrics.

Read how Data-Driven Cybersecurity explains security →

Fundamentals of Cybersecurity

Information security is the field concerned with protecting information in physical and digital forms from unauthorized access, alteration, or destruction.

How it is used
Protects organizational information, systems, processes, and people from threats while supporting business continuity.
How deep it goes
Defines information security’s scope, distinguishes it from cybersecurity, and connects CIA properties to controls without detailing implementation.
Examples
Uses a customer record copied across databases, reports, email, laptops, cloud storage, and third-party services.
What you can do after
Apply CIA properties to choose complementary protections such as encryption, hashing, backups, and access controls.

Read how Fundamentals of Cybersecurity explains security →

Kafka for Architects

Security is the protection of systems, data, and operations against unauthorized access, misuse, disruption, or compromise.

How it is used
Secures Kafka deployments end to end while aligning authentication, authorization, encryption, networking, compliance, and operational complexity.
How deep it goes
Defines the security model and architectural trade-offs, then applies protocols and ACLs to a deployment without providing detailed setup instructions.
Examples
Uses a Customer 360 deployment, topic-level ACLs, mTLS client traffic, SASL internal traffic, and documented component communication paths.
What you can do after
Operate/configure Kafka security by selecting authentication, encryption, ACL, and network controls for each communication path.

Read how Kafka for Architects explains security →

Quarkus in Action

Security is the protection of software systems, data, and communications against unauthorized access, misuse, or disruption.

How it is used
Secures Quarkus web applications and multiple cooperating services through authentication, identity providers, tokens, credential stores, and request filters.
How deep it goes
Demonstrates OIDC authentication and Dev Services configuration, but only briefly mentions JWT, credential stores, and CORS without practical examples.
Examples
Uses shared Keycloak development services, a login screen, secured HTTP paths, logout configuration, and authenticated greetings for Alice and Bob.
What you can do after
Operate/configure Quarkus authentication with Keycloak, OIDC settings, shared Dev Services, and authenticated application routes.

Read how Quarkus in Action explains security →

Azure Security

Cybersecurity is the practice of protecting digital systems, data, identities, applications, and networks from unauthorized access, disruption, or misuse.

How it is used
Frames Azure security as continuous protection of identities, data, applications, infrastructure, and networking resources.
How deep it goes
Explains threats, shared responsibility, iterative posture improvement, and layered defense without detailing individual service configurations.
Examples
Uses exposed virtual machines, leaked credentials, unencrypted repository secrets, ransomware, and misconfigurations as concrete threat examples.
What you can do after
Evaluate security posture and apply multiple Azure security services as evolving, layered controls.

Read how Azure Security explains security →

Generative AI in Action

Security is the protection of systems, data, and services against unauthorized access, alteration, disruption, or destruction.

How it is used
Protects enterprise GenAI applications, user data, infrastructure, and services during production deployment.
How deep it goes
Explains encryption, access control, audits, and anomaly detection operationally, while stopping short of detailed implementation procedures.
Examples
Uses TLS, cloud encryption, RBAC, least privilege, compliance audits, anomaly detection, Azure OpenAI controls, and enterprise-controlled RAG data.
What you can do after
Operate/configure production GenAI security using encryption, access controls, audits, anomaly monitoring, and controlled data retrieval.

Read how Generative AI in Action explains security →

Microsoft Azure in Action

Security is the protection of systems, data, applications, and infrastructure against unauthorized access, misuse, disruption, or damage.

How it is used
Frames security as a continuous Azure design responsibility spanning infrastructure, access, data, monitoring, and database choices.
How deep it goes
Explains a layered security continuum with concrete VM, storage, and database controls, but does not provide exhaustive configuration procedures.
Examples
Uses Azure virtual machines, Azure Storage, Banning Books, and competing relational databases to illustrate protection decisions.
What you can do after
Evaluate Azure security choices by balancing access controls, encryption, monitoring, cost, performance, and continuity requirements.

Read how Microsoft Azure in Action explains security →

Vibe Engineering

Security is the protection of software, data, and operations against unauthorized access, misuse, disruption, or alteration.

How it is used
Guides verification and deployment guardrails for AI-assisted software whose functional correctness may conceal security liabilities.
How deep it goes
Connects threat modeling, adversarial tests, insecure defaults, and secret handling, but does not detail individual vulnerability implementations.
Examples
Uses the NX compromise, the Enrichlead breach, threat-model security tests, and a Cloud Run deployment using Secret Manager.
What you can do after
Diagnose generated-code liabilities and configure Cloud Run credentials through Secret Manager rather than exposed environment-variable commands.

Read how Vibe Engineering explains security →

First-Party Data Activation

Security is the protection of data and systems against unauthorized access, disclosure, alteration, or destruction.

How it is used
Protects customer data, preserves trust, and guides privacy-conscious marketing architecture and technology decisions.
How deep it goes
Explains controls, organizational accountability, standards, and data-hosting models without descending into implementation procedures.
Examples
Uses the Equifax breach, encryption, audits, incident response, SOC 2, ISO 27001, and composable data-hosting comparisons.
What you can do after
Evaluate marketing-data solutions by their controls, certifications, hosting model, regulatory fit, and handling of sensitive first-party data.

Read how First-Party Data Activation explains security →

Apache Kafka in Action

Security is the protection of systems, data, and services against unauthorized access, misuse, disruption, or compromise.

How it is used
Protects Kafka data, clients, and services while maintaining trusted access across enterprise streaming environments.
How deep it goes
Explains authentication, authorization, encryption, monitoring, and a staged migration, but does not provide exact configuration commands.
Examples
Uses payment-data exposure, unsecured-to-secured migration, security metrics, and isolated clusters for sensitive departmental data.
What you can do after
Operate/configure Kafka security by adding TLS listeners, migrating clients, managing credentials, enforcing ACLs, and monitoring security signals.

Read how Apache Kafka in Action explains security →

Starting Data Analytics with Generative AI and Python

Protection of systems, data, and operations against unauthorized access, misuse, disruption, or compromise.

How it is used
Protects generative-AI analytics against sensitive-data exposure, unsafe model changes, insecure providers, and regulatory or reputational harm.
How deep it goes
Maps security across models, infrastructure, communications, storage, logs, and providers, then stops short of detailed implementation.
Examples
Uses leaked sensitive information, prompt-history exposure, and downloaded-model checks involving verification, isolation, scanning, and least privilege.
What you can do after
Operate AI workflows more safely by assessing providers, isolating tests, restricting permissions, protecting data, and reviewing model changes.

Read how Starting Data Analytics with Generative AI and Python explains security →

LLMs in Production

Security is the protection of systems, data, and operations against unauthorized access, misuse, disruption, or compromise.

How it is used
Frames security as a production requirement for LLM applications and agent integrations.
How deep it goes
Explains ordinary controls, two major failure cases, prompt injection, sandboxing, and filtering without detailing implementation procedures.
Examples
Uses an email-writing agent, tool integrations, internet browsing, malicious prompts, malware, and proprietary secrets.
What you can do after
Operate/configure LLM agents with sandboxing, containment, standard application controls, and prompt-filtering defenses.

Read how LLMs in Production explains security →

Developer Experience on Kubernetes

Security is the protection of software, data, and execution environments against unauthorized access, misuse, or compromise.

How it is used
Guides container-image construction toward safer runtime privileges and protected credential handling.
How deep it goes
Explains root exposure, layered secret leakage, least privilege, and dedicated secret mechanisms without descending into implementation internals.
Examples
Uses root-based containers, rootless modes, non-privileged entry points, and credentials retained in lower image layers.
What you can do after
Operate/configure containers with non-privileged processes and supply credentials through dedicated secret features.

Read how Developer Experience on Kubernetes explains security →

Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

How it is used
Shifts security left by auditing infrastructure configuration and access policies before systems reach production.
How deep it goes
Explains preventive checks, access auditing, breach remediation, and module review, but defers detailed security patterns.
Examples
Uses object-store policies, firewall rules, and a database module exposing neither secrets nor third-party data.
What you can do after
Evaluate infrastructure configurations and external modules for exposure, unauthorized access, data leakage, and compliance failures.

Read how Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform explains security →

Machine Learning Platform Engineering

Security is the protection of software, models, data, and infrastructure from unauthorized access, misuse, compromise, or attack.

How it is used
Protects data pipelines and deployed models from privacy breaches, information leakage, misuse, and adversarial attacks.
How deep it goes
Identifies security risks across ML operations and deployment but stops short of specifying controls, implementations, or attack procedures.
Examples
Uses data collection, large-scale data management, and model serving as concrete security contexts.
What you can do after
Evaluate security and privacy risks in ML data workflows and deployed model-serving environments.

Read how Machine Learning Platform Engineering explains security →

API Design Patterns

Security is the protection of systems and resources against unauthorized access, misuse, or exploitation.

How it is used
Guides API resource identification, method behavior, and representation boundaries to reduce unauthorized discovery and access leaks.
How deep it goes
Explains key unpredictability, authorization-error ambiguity, and restricted sub-resources, but stops short of implementation code.
Examples
Uses sequential versus random identifiers, 404 versus 403 responses, and employee compensation separated from ordinary employee data.
What you can do after
Apply security by choosing unpredictable identifiers, consistent authorization responses, and separate resources for highly restricted data.

Read how API Design Patterns explains security →

ActiveMQ in Action

Security is the protection of a system and its data against unauthorized access, alteration, or disruption.

How it is used
Secures access to the ActiveMQ broker and its destinations through authentication and authorization.
How deep it goes
Defines authentication and authorization, then covers plug-ins, operation- and message-level controls, and certificate-based security.
Examples
Uses XML-configured credentials, LDAP and properties-file authentication, custom IP-based authentication, message policies, and certificates.
What you can do after
Configure broker authentication, destination permissions, message-level authorization, and certificate-based security.

Read how ActiveMQ in Action explains security →

Google Anthos in Action

Security is the protection of applications, services, and data against unauthorized access, misuse, disruption, or compromise.

How it is used
Frames security as a production-readiness concern spanning cluster configuration, workloads, images, networks, identities, and operational maintenance.
How deep it goes
Explains attack surfaces and enumerates controls, while deferring detailed Policy Controller policy implementation.
Examples
Uses root containers, privileged containers, image scanning, Gatekeeper policies, binary authorization, TLS, and network isolation as concrete security examples.
What you can do after
Operate and configure Kubernetes security with ACM, Gatekeeper, vulnerability scanning, binary authorization, and service-mesh controls.

Read how Google Anthos in Action explains security →

Software Testing with Generative AI

A quality characteristic concerning protection against unauthorized access, misuse, alteration, disclosure, or loss.

How it is used
Uses security as a quality characteristic for analyzing risks during AI-assisted code development and testing.
How deep it goes
Defines security as a risk category and demonstrates prompt structure, but stops short of detailed security-testing procedures.
Examples
Uses a buffer-overflow example and a booking method containing validation, database, and message-posting operations.
What you can do after
Diagnose candidate security risks by applying a structured prompt to delimited code and reviewing the resulting explanations.

Read how Software Testing with Generative AI explains security →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

Data protection is the set of practices for preventing data from being damaged, lost, overwritten, or deleted.

How it is used
Uses security to protect microservice data, infrastructure, customer communications, and application operations from failures and malicious use.
How deep it goes
Explains backups, restoration, source-data immutability, service boundaries, and core controls, but defers comprehensive security treatment.
Examples
Demonstrates automated backups, practiced restoration, three-place storage, gateway exposure, and shielding RabbitMQ and MongoDB.
What you can do after
Apply backups, restoration drills, immutable source capture, service isolation, authentication, authorization, and encryption.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains security →

Inside AI

Security is the protection of systems, data, and operations from threats, misuse, disruption, or unauthorized access.

How it is used
Frames security as a requirement for critical AI systems and links cyber defense with risks from AI-enabled attacks.
How deep it goes
Illustrates security risks through ransomware incidents and broad AI applications, but gives little detail on defensive controls.
Examples
Uses file-encrypting ransomware and the Colonial Pipeline shutdown to illustrate operational disruption and ransom pressure.
What you can do after
Understand how AI can support threat detection while also enabling cyberattacks and operational disruption.

Read how Inside AI explains security →

Data Pipelines with Apache Airflow, Second Edition

Security is the protection of systems and data against unauthorized access, misuse, alteration, or disruption.

How it is used
Protects Airflow installations and connected systems by limiting unauthorized access and reducing the potential attack surface.
How deep it goes
Explains layered controls through RBAC, LDAP, TLS, Fernet encryption, and centralized secrets management.
Examples
Uses RBAC, LDAP, HTTPS, Fernet keys, HashiCorp Vault, and containerized dependencies as security examples.
What you can do after
Configure Airflow access controls, encrypted traffic, database secrets, centralized secret storage, and safer task dependencies.

Read how Data Pipelines with Apache Airflow, Second Edition explains security →

Context Engineering

Security is the protection of systems and information from unauthorized access, disruption, or misuse.

How it is used
Protects context-aware AI systems and their context sources against manipulation, tampering, and exploitation.
How deep it goes
Defines prompt-injection routes and maps risks to layered controls, while explaining why prompt instructions alone cannot enforce boundaries.
Examples
Uses adversarial user instructions and payloads embedded in retrieved documents, web pages, or tool outputs as prompt-injection examples.
What you can do after
Evaluate prompt-injection risks and select layered controls for context sources and tool execution.

Read how Context Engineering explains security →

Financial AI in Practice

The protection of systems, information, and operations against unauthorized access, disruption, or harm.

How it is used
Protects financial AI systems before model processing and supports public trust in a regulated environment.
How deep it goes
Specifies authentication, usage-policy enforcement, and PII stripping or masking before model access, without implementation details.
Examples
Illustrates protecting a user query by masking customer PII before it reaches the model.
What you can do after
Operate/configure a front-door layer to authenticate users, enforce usage policies, and strip or mask PII before model processing.

Read how Financial AI in Practice explains security →

AI Governance

Security is the protection of systems, data, and operations from unauthorized access, misuse, disruption, alteration, or loss.

How it is used
Frames security as a way to reason about attack paths and failure modes as GenAI capabilities expand.
How deep it goes
Frames risk across capability stages and signals a framework, without specifying its controls.
Examples
Uses ClaimAssist’s progression from policy chatbot to personalized, action-taking, and prospective agentic assistant.
What you can do after
Evaluate how added data access, model customization, and actions expand attack paths in a GenAI deployment.

Read how AI Governance explains security →

Also covered in

What to know first

Related concepts

Questions about security

What is security?

Security is the protection of systems, information, and resources against unauthorized access, use, disclosure, alteration, disruption, or destruction.

Which Manning books explain security?

AI for Everyday IT, The Cloud at Your Service: The when, how, and why of enterprise cloud computing, Grokking Software Architecture, Build AI-Enhanced Web Apps, The Art of AI Product Development, Effective Data Analysis, Introduction to Generative AI, Second Edition, Delivering Machine Learning Projects: From design to deployment and 28 more.

What should I know before learning security?

Manning books that teach security usually introduce language model, authorization, GDPR and encryption first.

What is security part of?

Security is part of nonfunctional requirement. A nonfunctional requirement specifies a system quality, constraint, or operating condition rather than a particular function or behavior.

What are the parts of security?

Security includes authorization and authentication.

What is security also called?

Security is also called cybersecurity.

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.