Topic starter
12/06/2026 9:14 pm
TL;DR: Automation improves efficiency, security and ROI, but fragmented workflows and unreviewed automations can create new operational blind spots, according to JumpCloud’s survey of 900+ IT leaders across the U.S., U.K. and Australia. The real issue is governance, because automated work still needs ownership, oversight and regular reassessment.
Editorial analysis by NHI Mgmt Group, based on content published by JumpCloud: “Unlock Your IT Potential: The Power of Automation in IT Workflows”.
By the numbers:
- The report surveyed 900+ IT leaders across the U.S., U.K. and Australia.
Key questions
Q: How should security teams govern IT process automation tools?
A: Security teams should govern IT process automation tools by treating every connector, token, and service account as an NHI with an owner, purpose, and expiry.
Q: Why can automated IT workflows still create risk?
A: Automated workflows create risk when they are fragmented, stale or unowned.
Q: What are the signs that automation is becoming fragmented?
A: Common signs include overlapping tools performing similar tasks, inconsistent outcomes across teams, unclear ownership of exceptions and no single view of how workflows interact.
Practitioner guidance
- Inventory automated IT workflows Create a complete inventory of automated tasks that affect identity, devices, security policy or operations, and record the business owner, technical owner and exception path for each one.
- Assign governance to every workflow Require each automation to have an accountable owner who can approve changes, review failures and confirm that the workflow still matches current policy and process.
- Review automation for drift Schedule periodic checks on automated workflows to verify that triggers, scopes, dependencies and outputs still reflect how the business operates today.
Bottom line: Automation can raise efficiency and security, but only when the workflow is governed after it is deployed.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
12/06/2026 11:09 pm
Automation is a governance model, not just a productivity tactic. The article treats automation as a way to remove routine work, but the deeper identity security question is who owns the workflow once the manual step disappears. A workflow that executes reliably can still become a control gap if nobody is accountable for its current scope, exceptions or changes. Practitioners should govern automation like any other operational control, not as a one-time optimisation project.
A question worth separating out:
Q: Should organisations review automation with the same discipline as other controls?
A: Yes. Automated workflows can affect access, security and operational resilience, so they should be reassessed just like any other control. If the business changes, the automation may need to change with it. Regular review is what keeps automation from turning into invisible technical debt.
👉 Read our full editorial: Automation in IT operations: efficiency gains and governance gaps