Automation index
How much of a SOC analyst’s job can AI already do?
An alert and a playbook come earlier. Calling it an incident and cutting it off in time do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
SOC analyst
28%
AI can already do 28% of this job.
#80 / 763
View rankingSOC analyst
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Triage, SIEM and the alert playbook.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
The false positive and the one that is ransomware.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
IOCs, correlation and the ticket.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
24x7 shift, handoff and the note to the CISO.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Contain, isolate and not killing the business.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Cut it off in time, and not ignoring the awkward alert.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- alert triage
- SIEM
- SOC playbooks
- IOCs
- contain incidents
- 24x7 shift
- ransomware
- event correlation
Sources for this job· O*NET 15-1212.00· ESCO/ISCO 2529
IS WORK OVER?
Backend developer
27%
#151 / 763
View rankingBackend developer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512