Skip to content
Omkar Khadamkar
Where security software is heading

Evidence log

Each forecast below, and the dated signals that support it or cut against it. Items are added as they happen and never removed, so the forecasts can be scored in public. A line that turns out wrong is corrected where it stands and marked, and its old wording stays in the changes at the end.

Last entry 7 Oct 2026 · 10 entries · summaries, not legal advice; every entry links its source

Hypothesis

By 2029, AI agents do most of the work inside security products

The scarce skill becomes designing where a person reviews, overrides and audits them.

being testedresolves 2029first scored 1 Jan 20275 for · 0 against · 0 mixed

  1. Cloudflare runs agent investigation of application-security alerts in its managed SOC, in early beta, with the analyst keeping the decision

    A large vendor has moved agent triage into a production service with evidence states in the engine; the screens have not caught up

    supportsCloudflare

  2. Wikimedia reports agents it believes were OpenAI's editing wikis and querying its services without the approvals required of bots

    Agents are already acting on third-party systems with no declared owner, which is the governance gap the forecast assumes products must close

    supportsWikimedia Foundation

  3. The same integrated SOC puts AI inside the case view, next to the evidence an analyst weighs.

    The AI works inside the case; the analyst's job moves to reviewing and overriding it.

    supportsMicrosoft Learn

  4. Wiz extends its partner network with MCP-powered agent integrations.

    Another company's agent is now a user of the product, so its answers become a design surface.

    supportsFuturum

  5. Preprint: in a university SOC, six analysts used an AI companion on 108 tickets. They reused its draft text in 91% of tickets but agreed with its verdict in 67%.

    People kept the AI's words more often than its verdict, and most verdicts they didn't keep were ones it had left uncertain: the review-and-override moment is where the design work is. One SOC, six analysts; not peer-reviewed.

    supportsarXiv (Banstola et al., University of South Florida)corrected 26 Oct 2026

Force 1

The areas are merging

Access, Data, Identity and detection stop being separate products; the hardest calls sit between them.

being testedresolves ongoing2 for · 0 against · 0 mixed

  1. Microsoft previews an integrated SOC in Defender: XDR, SIEM, threat intelligence, automation and AI in one portal, with third-party data added through an ISOC workspace.

    Detection tools that used to be separate products now share one portal.

    supportsMicrosoft Learncorrected 26 Oct 2026

  2. The same integrations let agents act across products through one layer.

    Decisions that start in one product finish in another.

    supportsFuturum

Force 2

Laws now set the clock

Reporting deadlines measured in hours turn compliance into screens people use under pressure.

being testedresolves ongoing3 for · 0 against · 0 mixed

  1. Sophos: 46% of MSPs say customers rely on them to act as their CISO, and 55% still do part of their security reporting by hand.

    The reporting that deadlines demand is still partly manual: a design gap under a legal clock.

    supportsHelp Net Security

  2. The EU Cyber Resilience Act's reporting duty starts: an early warning on an actively exploited weakness within 24 hours.

    A 24-hour clock is now law for product makers.

    supportsEuropean Commission

  3. NIS2 applies in the EU: early warning within 24 hours, notification within 72 hours, final report within a month.

    The first broad hours-not-weeks reporting clock for essential and important entities.

    supportsEuropean Commission

Related

Changes to this page (3)
  1. Corrected the 5 Sep 2026 entry (why). Overstated the paper: 72 of 108 tickets agreed with the AI's verdict, and most of the other 36 were tickets it had called uncertain; only 7 were outright conflicts.

    Was: People kept the AI's words but overruled its verdict about a third of the time: the review-and-override moment is where the design work is. One SOC, six analysts; not peer-reviewed.

  2. Corrected the 23 Sep 2026 entry (what). Microsoft describes one portal, with third-party data added through an ISOC workspace; it doesn't say one case mixes native and ingested evidence.

    Was: Microsoft previews an integrated SOC in Defender: XDR, SIEM and AI in one portal, so one case can mix native and ingested evidence.

  3. Corrected the 23 Sep 2026 entry (why). Same correction: one portal, not one case and one screen.

    Was: Detection tools that used to be separate products now share one case and one screen.