Topic starter
19/08/2026 3:35 pm
TL;DR: The global 4.8 million-role shortage can be offset by using AI agents to normalise logs, reduce false positives, accelerate investigations, and automate compliance evidence, turning repetitive work into managed machine support, according to Edge Delta. The governance question is no longer whether automation helps, but whether identity, auditability, and human approval boundaries are strict enough to trust it.
Editorial analysis by NHI Mgmt Group, based on content published by Edge Delta: “How to Turn Your AI Security Agent into a Force Multiplier”.
By the numbers:
- The cybersecurity industry faces 4.8 million unfilled positions globally in 2025, according to Edge Delta.
- A financial services client went from spending 20 hours per week on log source management to zero, according to Edge Delta.
- Most organizations take 6-12 months to progress through the AI agent adoption phases described by Edge Delta.
Key questions
Q: What breaks when AI agents are allowed to manage security findings without clear approval controls?
A: False positives can be promoted into accepted state too easily, while real issues can be dismissed before review.
Q: Why do AI agents reduce security capacity pressure without removing accountability?
A: They absorb repetitive work such as log correlation, evidence gathering, and classification, but they do not understand business context the way human analysts do.
Q: What are the signs that an AI risk management programme is failing?
A: An AI risk programme is failing when risk controls stay ad hoc, metrics are absent or superficial, and teams only react after deployment issues surface.
Practitioner guidance
- Define the first use case around mechanical work Start with log normalisation, evidence collection, or alert triage where the task is repetitive and low judgement, then measure before expanding scope.
- Build auditability into every agent action Require source traceability, decision rationale, and human review for any agent output that affects compliance evidence or security response.
- Set approval gates before enabling execution Use read-only analysis first, then supervised recommendations, then approval-gated actions so the team can validate behaviour before trust expands.
Bottom line: AI agents can help close the security capacity gap, but only when they are introduced as governed assistants rather than implicit replacements for analysts.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:16 pm
AI agents are becoming a governance problem before they are a workforce solution. The article is framed as a headcount story, but the real shift is that security teams are delegating parts of control execution to software systems that must be trusted, reviewed, and constrained. That means the operating model now depends on approval boundaries, evidence integrity, and traceable actions. For practitioners, AI augmentation only scales if governance scales with it.
A few things that frame the scale:
- 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.
- 52% of respondents see AI security decision-making power shifting toward platform and infrastructure teams rather than the executive suite, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should organisations use AI agents first for compliance work or investigation workflows?
A: Most teams should start with the workflow that is most repetitive and least dependent on judgement. In practice, that is often compliance evidence collection or log normalisation, because those tasks expose data quality issues early and let teams prove value before extending agent scope.
👉 Read our full editorial: AI agents can close the security capability gap without adding headcount