Automation can compress several manual steps into one execution path. That efficiency is useful, but it can also combine authorities that were intentionally separated. Segregation of duties must be redesigned, not assumed.

Map authority, not just task ownership

For each workflow action, identify who may initiate, prepare, review, approve, execute, change the rule, and inspect the evidence. The same person or service identity should not accumulate incompatible powers without an approved compensating control.

Treat service identities as control subjects

Agent and automation credentials require owners, scoped permissions, rotation, monitoring, and removal. Avoid shared credentials that make actions difficult to attribute or permissions that exceed the approved workflow.

Separate workflow change from production approval

The person who changes a prompt, rule, connector action, or threshold should not unilaterally approve the same change for production when the impact is material. Use review evidence and a release record.

Build a conflict matrix for people and service identities

List initiation, preparation, approval, execution, reconciliation, configuration, access administration, and evidence review for each material process action. Mark combinations that one person or service identity should not hold. Include temporary support access and emergency roles; they can create the same conflict as permanent access if activity is not constrained and reviewed.

Map automation identities to the action they perform, not to a broad application role chosen for convenience. A service identity that prepares a transaction does not need the authority to approve it. Where an application cannot support the required separation, document the limitation and design an approved compensating control.

Make compensating controls specific and reviewable

A compensating control should address the actual conflict and produce evidence. Examples may include independent post-action review, tighter value limits, restricted counterparties, daily reconciliation, enhanced alerts, or a second approval. General monitoring is not sufficient unless the reviewer, population, frequency, procedure, and escalation are defined.

Reassess conflicts when roles, connectors, thresholds, or ownership change. Access recertification should confirm business purpose and incompatible combinations, not only whether an account is still active. Remove permissions that are no longer required and retain the decision record for material exceptions.

Further reading

These primary references informed the operating principles in this guide.

Continue the evaluation

See implementation responsibilitiesBook a process diagnostic →