Security teams should set policy, define control requirements, and audit outcomes, while engineering teams should select and implement the access patterns that meet those requirements. This division fits cloud and perimeterless environments where identity is the main control plane. The practical goal is to make access decisions closer to systems and workflows without losing governance, accountability, or security oversight.
How to divide identity security work without blurring accountability
Identity security works best when policy and assurance sit with security, while implementation choices sit with engineering. Security teams should define the required control outcomes, acceptable risk thresholds, and audit evidence; engineering teams should build the access paths, token handling, federation patterns, and platform defaults that satisfy those requirements in the systems they run.
That split is practical because modern infrastructure pushes access decisions into code, cloud services, and runtime workflows. If security owns everything, controls become slow and detached from how systems actually operate; if engineering owns everything, governance fragments and access patterns drift from policy.
For teams designing cloud and platform controls, the useful reference point is the operating model, not a single product. NHIMG’s Shared Responsibility Models Guide helps frame which responsibilities remain with the customer, including identity controls that are always part of the buyer side of the equation.
What security owns and what engineering owns in practice
Security should own the identity policy layer: who can access what, under which conditions, with what evidence, and what level of assurance is required. That includes standards for MFA strength, session lifetime, privileged access, service authentication, logging, review cadence, and exception handling.
Engineering should own the implementation layer: how those policies are expressed in cloud IAM, application code, CI/CD, service meshes, device trust, SSO integrations, and automation. The point is not to hand policy over to engineers, but to ensure they can implement it natively in the systems where access is actually enforced.
This division becomes easier when both sides use a common model for workload and machine access. NHIMG’s Ultimate Guide to NHIs, Standards is useful where teams need a standards view of identity security controls, while the broader Zero Trust Identity Guide helps translate that policy into identity-centric enforcement.
How to make the split work across cloud, apps, and automation
The most effective model is policy-as-requirement and implementation-as-design. Security defines the control objective, for example, no long-lived standing access for privileged systems, or all production access must be attributable and time-bound. Engineering then chooses the control pattern that works best for the environment, such as federation, short-lived credentials, conditional access, or workload identity.
That approach matters most where humans, services, and automation all touch the same control plane. The wrong pattern is to centralise every decision in a ticket queue, or to let each team invent its own identity rules. The better pattern is to standardise the policy outcome and allow engineering to select the secure technical route.
For cloud-native environments, identity often needs to be treated as part of infrastructure rather than as an afterthought. NHIMG’s Infrastructure as Code Security Guide supports that approach by showing how access, drift, and secrets issues surface in delivery pipelines and configuration. For runtime systems and platform services, the AI Infrastructure Workload Identity Guide is a strong example of how engineering owns the mechanics while security owns the control intent.
Risk and Threat Considerations
When the split is unclear, identity security usually fails in one of two ways: either security sets rules that cannot be implemented cleanly, so teams bypass them, or engineering implements access paths that work technically but are never governed properly. In both cases, the result is excessive privilege, weak traceability, and harder containment when credentials, tokens, or sessions are abused.
Failure mechanism: Control intent and technical implementation diverge, leaving gaps in provisioning, review, revocation, and runtime enforcement. That gap is especially dangerous in perimeterless environments because identity becomes the main enforcement layer, so any inconsistency quickly becomes an access path.
Impact: Teams lose confidence that access is both usable and governed, which increases the chance of unauthorized access, privilege creep, and slow incident response. At scale, the blast radius grows because the same weak pattern is often copied across services, environments, and automation workflows.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, NIST SP 800-53 Rev 5 and CSA Cloud Controls Matrix set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.OC-01 — Organizational Context | Identity security ownership depends on clear accountability between teams. |
| Recommendation — Define which team owns policy, implementation, and assurance for identity controls. | ||
| NIST SP 800-53 Rev 5 | PM-23 — Identity Management | The question is about how identity controls are governed across teams. |
| AC-6 — Least Privilege | Splitting responsibility must still produce least-privilege access decisions. | |
| Recommendation — Assign identity management responsibilities across policy, provisioning, and audit roles. Enforce least privilege in the access patterns engineering implements. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | The division of duties affects how access control is defined and enforced. |
| Recommendation — Set access control requirements centrally and implement them consistently in systems. | ||
| CSA Cloud Controls Matrix | IAM — Identity and Access Management | Cloud identity ownership is central to the team split described in the question. |
| Recommendation — Map policy, provisioning, and review duties to the IAM operating model. | ||
Practitioner Guidance
What to verify: Confirm that every required identity control has a named policy owner, an implementation owner, and an audit signal. If a control cannot be measured or evidenced, it is not really owned.
Decision rule: If the issue is about what the organisation permits, security should decide. If the issue is about how the platform enforces that decision, engineering should decide, within the security-defined boundary.
What good looks like: Security publishes the standard, engineering ships the pattern, and audit can show that the deployed access path matches both.
Practitioner takeaway: The healthiest split is not “security versus engineering”, it is policy, implementation, and evidence all staying aligned while the access decision is made as close as possible to the system that enforces it.
Related resources from NHI Mgmt Group
- What breaks when infrastructure access controls are split across security, engineering, and compliance teams?
- How should security teams evaluate modern asset management when infrastructure, identity, and code systems all expose APIs?
- How should security teams split identity governance from implementation work?
- When should security teams treat identity as infrastructure?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org