Governance
Governance is the system of policies, roles, decision rights, processes, controls, and oversight through which an organization, system, or activity is directed and held accountable.
Authorization in Action
A governance framework is a structured system that assigns responsibility, establishes applicable standards, and coordinates work across teams or systems.
- How it is used
- Connects organizational intent, compliance, and accountability to authorization policies and runtime decisions.
- How deep it goes
- Defines governance and details a policy life cycle, federated roles, feedback practices, IGA integration, and compliance evidence.
- Examples
- Uses policy drift across teams, contractor entitlements, and onboarding an accredited security-auditor issuer.
- What you can do after
- Operate/configure governance by assigning policy roles, maintaining review cycles, preserving evidence, and feeding operational findings into updates.
Data-Driven Cybersecurity
The system of leadership, oversight, decision rights, policies, and accountability through which an organization directs and controls cybersecurity.
- How it is used
- Directs cybersecurity decisions and oversight so security work supports organizational goals and risk management.
- How deep it goes
- Defines governance, elaborates roles and reporting, and suggests progress metrics while cautioning against low-value measurement.
- Examples
- Uses a simulated technology-company reporting structure, competing board investment priorities, and board action-item metrics.
- What you can do after
- Operate/configure it by documenting responsibilities and decision authority, then tracking completion of cybersecurity actions assigned after board meetings.
Delivering Machine Learning Projects: From design to deployment
System governance is the set of decision rights, controls, responsibilities, and processes that direct and oversee a system throughout its lifecycle.
- How it is used
- Directs ethical deployment, production handoff, and continuing operational accountability for machine-learning systems.
- How deep it goes
- Defines owners, controls, reviews, impact measures, and remediation, but defers a fully standardized ethical evaluation methodology.
- Examples
- Uses responsibility tables, stakeholder impact assessments, risk-register entries, production monitoring, and The Bike Shop handoff.
- What you can do after
- Operate/configure system ownership, controls, reviews, monitoring, support, and remediation across the production lifecycle.
Read how Delivering Machine Learning Projects: From design to deployment explains governance →
Prompt Engineering in Practice
The policies and processes used to control review, maintenance, and responsible operation of an artifact or system.
- How it is used
- Governs shared prompt libraries so teams can change prompts safely as their libraries and teams grow.
- How deep it goes
- Defines ownership, approval, and traceability, and outlines a seven-phase lifecycle without prescribing deployment infrastructure.
- Examples
- Uses a support bot regression amid scattered, untraceable prompts to illustrate the cost of weak governance.
- What you can do after
- Apply proportionate governance and use management records to prioritize prompt improvements.
Read how Prompt Engineering in Practice explains governance →
Apache Kafka in Action
Governance is the structured oversight of data, security, and resource practices that controls how a technical system is operated and maintained.
- How it is used
- Controls schema consistency, security, access, compliance, and resource allocation in Kafka-based real-time data exchange.
- How deep it goes
- Explains governance responsibilities and risks through schemas, security, quotas, and data-mesh roles without implementation procedures.
- Examples
- Uses evolving product schemas, inventory and pricing errors, payment-data exposure, resource hogging, and departmental data products.
- What you can do after
- Evaluate/understand how governance assigns data, security, access, and resource responsibilities across Kafka departments.
Related concepts
- code reviewuses · Code review is the systematic examination of source code or proposed changes to identify problems and assess or improve quality.
- versioninguses · The practice of identifying and managing successive revisions of files, data, models, interfaces, or other artifacts so changes can be tracked and earlier states recovered.
- authorization decisionhas part · An authorization decision determines whether a principal is permitted to access a resource or perform an action under applicable permissions or policy.
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.