Compliance
Compliance is conformity with applicable legal, regulatory, contractual, policy, or other governing requirements.
Data-Driven Cybersecurity
Cybersecurity compliance is conformity with applicable security requirements, standards, regulations, or framework controls.
- How it is used
- Uses compliance metrics to demonstrate adherence, support audits, and direct security resources toward gaps.
- How deep it goes
- Works through targets, dashboards, audits, and reporting decisions rather than interpreting individual legal requirements.
- Examples
- Illustrates gaps with healthcare policy dashboards, vendor audits, encryption coverage, and an executive report listing HIPAA, PCI DSS, and GDPR rates.
- What you can do after
- Practice/perform compliance reporting by comparing measured rates with targets, identifying gaps, and recommending actions for leadership.
Effective Platform Engineering
Compliance is adherence to applicable laws, regulations, policies, and prescribed controls.
- How it is used
- Positions compliance as an assurance requirement that a platform must address without recreating developer delivery friction.
- How deep it goes
- Explains responsibilities and stakeholder requirements, then sketches incremental guardrails without specifying control implementations or verification procedures.
- Examples
- Uses critical-vulnerability requirements, SOX deployment evidence, and authorized access to sensitive dataset APIs.
- What you can do after
- Evaluate/understand it by distinguishing platform and application responsibilities and identifying requirements for baseline platform guardrails.
Read how Effective Platform Engineering explains compliance →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
Compliance is adherence of systems, configurations, or operations to applicable policies, standards, regulations, or requirements.
- How it is used
- Uses policy as code to check infrastructure security and compliance before production, after functional testing.
- How deep it goes
- Explains metadata evaluation, test organization, shared repositories, and enforcement categories, but not detailed policy syntax.
- Examples
- Uses GCP infrastructure, database and firewall policies, CIS benchmarks, pytest tests, and shared policy repositories.
- What you can do after
- Apply it via policy engines or pytest to detect noncompliant infrastructure and gate changes before production.
Azure Security
Compliance is the state of satisfying the requirements defined by an applicable policy or rule set.
- How it is used
- Assesses Azure resource configurations against technical controls and regulatory standards to track compliance posture and remediation work.
- How deep it goes
- Explains dashboard-based assessment, failing-control investigation, refresh timing, and policy evaluation without covering manual process-control assessment.
- Examples
- Uses PCI DSS 3.2.1 failing controls and an Allowed virtual machine size SKUs policy assignment with a waiver exemption.
- What you can do after
- Operate/configure continuous compliance assessment by reviewing standards, remediating failed resources, and assigning scoped Azure Policy definitions.
The Cloud at Your Service: The when, how, and why of enterprise cloud computing
Compliance is conformity with applicable laws, regulations, standards, or other formal requirements.
- How it is used
- Frames compliance as both a cloud deployment constraint and an operational concern.
- How deep it goes
- Explains deployment trade-offs and provider versus application responsibility, without a detailed compliance checklist.
- Examples
- Uses healthcare patient data and HIPAA to distinguish provider support from a compliant application.
- What you can do after
- Evaluate cloud deployment options and provider assurances against application compliance concerns.
Generative AI in Action
Compliance is conformity with applicable laws, regulations, standards, policies, and contractual requirements.
- How it is used
- Places compliance within production GenAI deployment alongside security, reliability, observability, and lifecycle management.
- How deep it goes
- Details regulatory identification, privacy design, encryption, access control, audits, anomaly detection, and incident response without interpreting individual regulations.
- Examples
- Uses GDPR, HIPAA, PCI-DSS, and CCPA as regulatory examples, with TLS, encryption, RBAC, audits, vulnerability scans, and anomaly detection as controls.
- What you can do after
- Operate/configure GenAI applications with documented privacy, security, audit, monitoring, vendor, and breach-response safeguards.
Architecting Autonomous Agentic Systems
Compliance is continuous alignment between information use and applicable enterprise, legal, regulatory, policy, and evidentiary obligations.
- How it is used
- Enforces enterprise obligations wherever information influences agent behavior.
- How deep it goes
- Traces obligations across the information lifecycle and names runtime controls, but does not detail their implementation.
- Examples
- Uses a legal-agent dispute involving privilege, jurisdiction, external communication, and evidence reconstruction.
- What you can do after
- Operate agent workflows by enforcing obligations across retrieval, generation, tool use, disclosure, retention, and action.
Read how Architecting Autonomous Agentic Systems explains compliance →
AI Governance
Compliance is conformity with applicable laws, regulations, standards, policies, and contractual requirements.
- How it is used
- Frames compliance within GenAI GRC as guardrails that support trustworthy AI projects rather than bureaucracy.
- How deep it goes
- Briefly situates compliance within GRC and defers concrete maturity-level implementation examples.
- Examples
- Uses a startup’s monthly AI-risk discussion and an enterprise’s formal committees and dedicated roles.
- What you can do after
- Apply proportionate GRC by embedding practices in existing risk-management, IT-governance, or product-development routines.
Architecting an Apache Iceberg Lakehouse
A compliance posture is an organization's current condition of adherence to applicable laws, regulations, policies, and data-handling requirements.
- How it is used
- Guides storage, catalog, access, and consumption architecture when laws, residency rules, privacy, and auditability constrain lakehouse design.
- How deep it goes
- Explains controls across storage and catalog layers, then applies them to a governed healthcare workload without descending into regulatory interpretation.
- Examples
- Uses regulated banking storage, archived regulatory reports, and regional healthcare analytics with dashboards, notebooks, and federated queries.
- What you can do after
- Operate/configure a lakehouse that localizes regulated data, restricts access, protects metadata, preserves audit trails, and supports compliant analytics.
Read how Architecting an Apache Iceberg Lakehouse explains compliance →
Authorization in Action
Compliance is adherence to applicable legal, regulatory, contractual, or organizational requirements.
- How it is used
- Uses authorization policies and governance processes to enforce regulatory requirements and demonstrate that access rules were followed.
- How deep it goes
- Connects regulations to dynamic policies, audit logging, version control, testing, approvals, and review schedules.
- Examples
- Uses HIPAA treatment access, SOX report restrictions, GDPR consent, and ACME policy evidence artifacts as examples.
- What you can do after
- Evaluate access controls by linking obligations to enforceable policies, validation tests, runtime logs, approvals, and review evidence.
Introduction to Generative AI, Second Edition
Compliance is adherence to applicable laws, regulations, policies, standards, or contractual requirements.
- How it is used
- Deploys compliance as a practical use case for AI tools that interpret complex regulations and support legal, regulatory, and tax questions.
- How deep it goes
- Explains AI-assisted determinations and governance safeguards, but stops short of implementation detail.
- Examples
- Uses Norm.ai, Harvey AI, sandbox testing, privacy reviews, consent, and usage monitoring as concrete examples.
- What you can do after
- Operate/configure AI-assisted compliance cautiously through sandbox testing, workplace policies, privacy review, consent, and monitoring.
Read how Introduction to Generative AI, Second Edition explains compliance →
AI for Everyday IT
Compliance is adherence to applicable laws, regulations, standards, policies, or other governing requirements.
- How it is used
- Guides safe AI use and supports checks of system configurations and workplace documents against governing requirements.
- How deep it goes
- Connects compliance to data handling and document checks, while treating AI review as preliminary rather than legal counsel.
- Examples
- Uses cloud AI data sharing, system-configuration audits, and policy-aligned memos, warnings, and write-ups.
- What you can do after
- Evaluate documents for common policy and legal issues and check system configurations, while retaining human judgment.
Build AI-Enhanced Web Apps
Conformance of a system and its data practices with applicable legal, regulatory, contractual, or organizational requirements.
- How it is used
- Guides production AI web applications toward lawful data handling, privacy protection, content authenticity, and controlled provider usage.
- How deep it goes
- Explains operational safeguards for PII and chat histories, but does not specify implementation code or detailed legal interpretations.
- Examples
- Uses chat histories, PII, financial and medical information, user deletion requests, retention periods, and temporary impersonation review.
- What you can do after
- Operate/configure privacy controls for AI applications by managing consent, storage, access, retention, deletion, and sensitive prompt data.
The Art of AI Product Development
Compliance is adherence to applicable laws, regulations, policies, standards, and organizational requirements.
- How it is used
- Guides AI teams in meeting regulatory, privacy, fairness, security, and organizational requirements while building stakeholder trust.
- How deep it goes
- Details privacy controls, provider audits, jurisdictional checks, monitoring, bias checks, and incident response without specifying legal interpretations.
- Examples
- Uses commercial LLM safeguards, anonymized customer data, bias detection, regional fairness checks, provider audits, and incident response plans.
- What you can do after
- Operate/configure AI initiatives with documented data practices, access controls, audits, fairness checks, monitoring, and clear compliance communication.
Read how The Art of AI Product Development explains compliance →
Decision Engineering
Adherence to applicable laws, regulations, standards, or other obligations.
- How it is used
- Surfaces legal obligations as constraints during architectural discovery, before solution choices are fixed.
- How deep it goes
- Distinguishes obligations from controls and gives proportionality guidance without prescribing a universal control set.
- Examples
- Uses storage encryption, access reviews, and proposed AI-agent bans to illustrate proportionality and uncertainty.
- What you can do after
- Evaluate safeguards collaboratively by surfacing constraints early and matching controls to risk and sensitivity.
Financial AI in Practice
Regulatory compliance is adherence to applicable laws, regulations, supervisory requirements, and prescribed financial controls.
- How it is used
- Uses compliance to frame fraud-risk controls and safeguards around financial AI outputs.
- How deep it goes
- Describes AML benefits and output safeguards, but does not detail specific laws or control procedures.
- Examples
- Cites Danske Bank’s AML screening results and compliance filters for generated financial advice.
- What you can do after
- Understand how compliance informs fraud controls and safeguards for generated financial responses.
Also covered in
- Software Architecture Decision-MakingIn early access (MEAP)
- Think Like a CTO
- Architecture Modernization: Socio-technical alignment of software, strategy, and structure
- Fundamentals of CybersecurityIn early access (MEAP)
- Designing Deep Learning Systems: A guide for software engineers
- Data Without Labels
- WordPress Power Toolkit: Harness AI to build next-level websites
- Digital Twins in Action
- LLM Customization and Fine-TuningIn early access (MEAP)
- Machines that ThinkIn early access (MEAP)
- GitHub Actions in Action: Continuous integration and delivery for DevOps
- Tech Startup Toolkit
What to know first
- language modelA language model is a computational model that represents patterns in linguistic sequences to assign probabilities, predict, generate, or evaluate language.
- GDPRThe General Data Protection Regulation (GDPR) is a European Union regulation governing the processing and protection of personal data and establishing related rights for individuals.
- personal dataPersonal data is information relating to an identified or identifiable individual, directly or indirectly, alone or in combination with other information.
- promptA prompt is text or other input supplied to an AI model to provide instructions, context, or other information that guides its response or generated output.
Related concepts
- versioningaddressed by · Versioning is the practice of assigning or maintaining identifiable revisions of artifacts over time so their changes, histories, or compatibility can be tracked.
- Azure Policymeasured by · Azure Policy is an Azure governance service that evaluates resources against organizational rules and audits or enforces compliance.
- CCPAuses · The California Consumer Privacy Act is a California privacy law establishing consumer rights and business obligations concerning personal information.
- commitmentcontrasts with · A commitment is an undertaking, choice, or investment that constrains future actions or decisions, either by creating an obligation or by making reversal costly.
- data privacy regulationuses · A data privacy regulation is a legal or regulatory rule governing the collection, handling, use, retention, disclosure, transfer, or protection of personal data.
Questions about compliance
What is compliance?
Compliance is conformity with applicable legal, regulatory, contractual, policy, or other governing requirements.
Which Manning books explain compliance?
Data-Driven Cybersecurity, Effective Platform Engineering, Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform, Azure Security, The Cloud at Your Service: The when, how, and why of enterprise cloud computing, Generative AI in Action, Architecting Autonomous Agentic Systems, AI Governance and 8 more.
What should I know before learning compliance?
Manning books that teach compliance usually introduce language model, GDPR, personal data and prompt first.
What is the difference between compliance and commitment?
Compliance is conformity with applicable legal, regulatory, contractual, policy, or other governing requirements. A commitment is an undertaking, choice, or investment that constrains future actions or decisions, either by creating an obligation or by making reversal costly.
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.















