Many cloud controls exist only in the document that describes them.
The policy says encryption is mandatory, storage is private by default and a second person reviews production changes. The architecture standard repeats it. The audit evidence is a screenshot taken the week before the audit. Then someone changes the console and nobody records it.
Organisations write controls for an environment that people no longer build by hand. Pipelines build it. The pipeline decides what is deployed, with which permissions, into which account. A control that does not run in the pipeline is a recommendation.
In practice, the gap shows up in three places. Drift comes first. A team defines infrastructure in code, an engineer alters it by hand during an incident, and the code never catches up. Every control assertion now describes the wrong state. Privilege comes second. Teams give pipeline service accounts broad rights because narrow ones broke a release. Those accounts then hold more access than any engineer, and they often escape review. Exceptions come third. A policy check fails a build, a team obtains a waiver, and the waiver never expires.
None of this is exotic. It happens when an organisation treats DevOps as an engineering matter and governance as a separate matter. The two functions meet once a year in an audit and find they have described different systems.
Regulation points the same way. DORA expects financial entities to manage ICT risk across the lifecycle of their systems. NIS2 expects security measures that an entity can demonstrate. Both are easier to meet when the pipeline enforces the control at the point of change and produces the evidence as it runs. Manual evidence gathering makes both harder.
The practical move is to make the pipeline the system of record for controls. Teams that do this write policy as code and evaluate it before deployment. A failed check blocks the release. Each exception is a logged decision with a named owner and an end date. Pipeline identities get only the rights they need to deploy, and security reviews them like any privileged user. A continuous comparison against the declared state catches drift, and the team handles it as an incident.
This changes the conversation between security, engineering and audit. Auditors test the mechanism directly. Engineers meet governance as a failing build they can fix. Security owns controls that actually run.
Ask whether a non-compliant change could reach production tonight. If the honest answer depends on someone noticing, the control does not exist.
Sources: None cited. General reference to Regulation (EU) 2022/2554 (DORA) and Directive (EU) 2022/2555 (NIS2).





