Information Security Analysts
How information security analysts are reshaped as AGI capability advances.
The bottom line
Roughly 95% of the work in Information Security Analysts is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: Information Security Analysts operate entirely in the digital realm. All 30 tools listed belong to UNSPSC segment 43 (IT and software, prior=0.85), including network software like Tcpdump and Splunk. Top work activities like 'Working with Computers' (4.70) and 'Analyzing Data or Information' (4.08), alongside work contexts such as 'E-Mail' (4.96) and 'Spend Time Sitting' (4.23), confirm this is a pure knowledge-work role.
grounded in the economy graph · digital scalar 0.95 · digital
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Information Security Analysts engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Information Security Analysts involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Autonomous Agents as digital employees
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Information Security Analysts performs 11 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
Information Security Analysts is typically employed by 216 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+204 more via typicallyEmploys
Information Security Analysts is employed across 185 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+173 more via employs
Information Security Analysts is linked from 1 entity via `performedBy` — a real edge on the economy graph, surfaced here so the claim stays grounded in data rather than assertion.
Headless SaaS for Agents
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Information Security Analysts uses 6 tools today. As each gains an agent-consumable surface (API / MCP / SDK), the human UI stops being the only way in — and the work routes straight to an agent.
Information Security Analysts relies on 246 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.
+234 more via uses
The software Information Security Analysts reaches for already exposes 10 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
The problems this exposes
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
Where Information Security Analysts sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
Problems
- Triage False Positive Alertsops
- Contain Active Network Breachesops
- Pass Continuous Security Auditscompliance
- Assess Third-Party Vendor Risksupply-chain
- Backfill Specialized Security Talenttalent
- Neutralize Novel Ransomware Threatscompetitive
- Prevent Breach-Driven Customer Churnretention
Opportunities
- Autonomous Alert TriageAgent
- Vendor Assessment ServiceService-as-Software
- Headless Compliance EngineHeadless SaaS
- AI Incident ResponderAgent
- Virtual SOC ServiceService-as-Software