Notifications
Clear all
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.
NHIMG editorial — based on content published by JumpCloud: automation, efficiency, security, and ROI in IT operations
Questions worth separating out
Q: How should security teams govern automation in identity and IT operations?
A: Security teams should govern automation the same way they govern any other control: assign ownership, define the policy it enforces, track exceptions, and review it on a schedule.
Q: Why do fragmented automation workflows create security and efficiency problems?
A: Fragmented workflows create gaps because different automations often enforce different assumptions, use different approval paths, or depend on undocumented handoffs.
Q: How do you know if automation is actually improving control quality?
A: You know automation is improving control quality when it reduces manual errors, shortens remediation time, and produces the same compliant outcome across repeated runs.
Practitioner guidance
- Inventory every automated workflow by control owner Document who owns each workflow, what policy it enforces, and which exception path applies when the automation fails or drifts.
- Tie each automation to a measurable control outcome Define a specific outcome for every automated process, such as fewer manual errors, faster remediation, or more consistent policy enforcement.
- Review fragmented workflows for hidden dependencies Look for automations that depend on another tool, team, or manual step that is not documented in the workflow itself.
What's in the full article
JumpCloud's full article covers the operational detail this post intentionally leaves for the source:
- Survey framing and respondent context from more than 900 IT leaders across three regions.
- Practical examples of repetitive IT tasks that teams are automating to free up time.
- The article's own guidance on balancing efficiency gains with ongoing workflow review.
- JumpCloud's webinar tie-in on automation use cases for day-to-day IT operations.
👉 Read JumpCloud's analysis of automation in IT operations and governance →
Automation in IT operations: are your controls keeping up?
Explore further
12/06/2026 11:09 pm
Automation is a governance problem before it is an efficiency problem. The article is right that repetitive work belongs in automated workflows, but the real security question is whether those workflows remain observable and accountable once they scale. In identity programmes, efficiency gains disappear quickly when automation becomes a black box of exceptions, partial coverage, and unclear ownership. Practitioners should treat automation as a control surface, not a productivity slogan.
A few things that frame the scale:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to The 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to The 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should teams do when automated workflows no longer match current operations?
A: Teams should reassess the workflow, document where the environment has changed, and either refactor or retire the automation before it becomes a source of drift. A control that no longer matches current systems, policies, or access patterns is not a stable control. Regular review is what keeps automation aligned with reality.
👉 Read our full editorial: Automation in IT operations: efficiency gains and governance gaps
