liveBook · Manning

Automated governance

As explained in Effective Platform Engineering

Automated governance verifies that required security, compliance, or delivery activities occurred through automated platform controls.

Automated governance verifies that required security, compliance, or delivery activities occurred through platform controls. It separates doing compliant work from verifying it, preserving developer autonomy without sacrificing stakeholder assurance. section 1.3.3

The implementation pattern centers on compliance at the point of change:

  • Provide developers with self-service platform tools that make compliant delivery the normal path. section 1.3.3
  • Move confirmation of compliance out of the delivery pipeline and into the platform control plane. section 1.3.3
  • Verify the required state before permitting a change, rather than making another team a delivery bottleneck. section 1.3.3

How Effective Platform Engineering covers it

How deep it goes
Defines compliance at the point of change and separates compliance work from platform-based verification, without detailing control implementations.
Examples
Uses platform self-service tools and pre-change control-plane confirmation as its concrete implementation pattern.
What you can do after
Operate a platform control plane that verifies compliance before changes while developers retain delivery autonomy.
How it connects
Connects platform engineering with self-service tools, software delivery processes, compliance, security, governance, and the control plane.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.