Automation index
How much of a CISO’s job can AI already do?
A risk dashboard comes earlier. Saying no to the business and riding out the incident do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
CISO
25%
AI can already do 25% of this job.
#263 / 763
View rankingCISO
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 |
|---|---|---|---|
Risks, policies and the control map.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 44% | +7 |
The incident, the board and talk to press or not.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Budget, vendors and cyber insurance.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Audit, ISO and briefing the board.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The business that wants to ship now, and the no.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Ride out the incident, and not lying to the board.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 25% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- risk map
- security policies
- handle incidents
- ISO 27001
- cyber insurance
- brief the board
- say no to the business
- security controls
Sources for this job· O*NET 11-3021.00· ESCO/ISCO 1330
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