Who is accountable when cloud changes are made outside the approved automation process?

Accountability should sit with the teams that own the infrastructure control plane and the change governance process, not with the monitoring layer alone. If manual edits can still happen, the organisation needs clear ownership for approval, review, and remediation. The control objective is simple: every material change must be attributable, authorised, and traceable end to end.

Why This Matters for Security Teams

When cloud changes happen outside the approved automation path, the real risk is not just misconfiguration. It is loss of attribution, broken approval chains, and unclear ownership for rollback or containment. That gap is especially dangerous in environments governed by NHI, where a manual console edit can silently bypass the controls attached to service identities, tokens, and deployment pipelines. NIST’s SP 800-53 Rev. 5 Security and Privacy Controls makes accountability and auditability core control objectives, not optional extras.

The practical failure mode is familiar: teams assume the monitoring layer will catch drift, but monitoring only detects change after it exists. That is why NHI governance has to be tied to the control plane itself, with ownership assigned to the people responsible for the infrastructure state, the change process, and the secrets or workload identities that made the change possible. The Ultimate Guide to NHIs — Lifecycle Processes for Managing NHIs is explicit that lifecycle ownership must include creation, rotation, revocation, and traceability, not only detection. In the 2024 Non-Human Identity Security Report, only 19.6% of security professionals expressed strong confidence in securely managing non-human workload identities, which shows how often accountability is still informal rather than operationalised.

In practice, many security teams discover accountability gaps only after an unapproved console change has already altered production access or exposed a secret, rather than through intentional control design.

How It Works in Practice

Accountability starts by treating approved automation as the default change path and every manual edit as an exception that must be visible, attributable, and reviewed. That means the infrastructure control plane, the CI/CD pipeline, and the identity system all need shared evidence for who requested the change, who approved it, what identity executed it, and what was altered. NIST control guidance for configuration management and audit logging supports this model, while 230M AWS environment compromise and Snowflake breach illustrate how fast control failures become identity and access failures once changes escape the approved path.

In mature environments, the answer is not “the monitoring team owns it.” The monitoring function detects and escalates, but ownership stays with the infrastructure platform team and the change governance process. That group should define:

• Who can make changes directly in the console
• Which changes require pre-approval versus post-approval review
• How drift is remediated and by whom
• Which service identities, API keys, or break-glass accounts can bypass automation
• How evidence is preserved for forensics and audit

For NHI-specific operations, the approved path should also bind each change to a workload identity or short-lived session so the action can be traced back to a task, not just a person. That is especially important when secrets are used to trigger automation, because long-lived credentials make it hard to distinguish a legitimate operator action from an attacker using the same access path. Current guidance suggests using privileged access workflows, just-in-time access, and strong logging together rather than relying on a single control.

These controls tend to break down in highly fragmented multi-cloud environments where teams share admin access across accounts, because no single owner can reliably reconcile the source of truth.

Common Variations and Edge Cases

Tighter change control often increases operational overhead, requiring organisations to balance speed of response against the risk of unauthorised drift. That tradeoff becomes sharper during incidents, where emergency fixes may be necessary before the full approval workflow can complete. Best practice is evolving here, but the current guidance is to define break-glass procedures in advance so emergency access is still attributable and reviewed after the fact.

There are also edge cases where accountability is split. In platform teams, a central cloud operations group may own the control plane, while application teams own the resources affected by the change. In that model, the accountable party is usually the team that can approve, execute, and reverse the change, even if another team requested it. The policy should make that distinction explicit.

For agentic and automated environments, the question gets harder because an AI system may initiate the change, but the platform owner still bears responsibility for the guardrails around it. That is why current practice increasingly pairs workload identity with policy enforcement at request time, rather than trusting static RBAC alone. The 2026 Infrastructure Identity Survey found that 67% of organisations still rely heavily on static credentials despite the risks they pose to autonomous systems, which helps explain why accountability frequently breaks down at the point of execution instead of at the point of approval.

When exceptions become routine, accountability is no longer a process issue. It is a control design failure.

Related resources from NHI Mgmt Group

• Who is accountable when manual identity governance fails to keep up with cloud and SaaS access changes?
• Who is accountable for maintaining SOC 2 evidence when cloud infrastructure changes frequently?
• Who is accountable when API-driven access changes affect contracts, licences, or user permissions?
• Who is accountable when Infrastructure as Code changes create compliance or security failures?