Case · DiggingBeagle record

AI SOC triage methods cover different alerts, but transfer across tenants breaks

A retrospective security-operations study found almost disjoint cluster selections across detectors; near-zero benign escalation was configuration-specific and did not transfer.

Public disclosure: Nov 3, 2026

Scope

Offline retrospective experiment posted November 3, 2026, not a production deployment or verified incident.

UnratedAI role: WITH AIAssessment method

At a glance

Mechanism and trust boundary

  1. 01

    Analyst-labeled SOC alerts are grouped by feature pattern and divided into temporal train and test sets.

  2. 02

    Three ranking methods select limited alert clusters under the same budget.

  3. 03

    Reported benign escalation rates and pairwise overlap are measured at the constrained cluster budget.

  4. 04

    Transferred models encounter a different tenant feature schema and fail to generalize their ranking.

Claims & evidence

CLM-NOV03-SOC-BENIGN-CLUSTERAt a constrained 32-cluster selection point, the authors report benign escalation fractions PPO 0.000, autoencoder 0.007 and Isolation Forest 0.041; these are cluster-level results, not full-dataset false-positive rates.supported

Basis: reported finding

Link to claim
CLM-NOV03-SOC-TRANSFER-IF-AEIn the paper's separate cross-tenant experiment, the zero-shot ROC-AUC of Isolation Forest decreased from 0.7126 to 0.4681 and the autoencoder from 0.7682 to 0.4730; these were not reported as PPO transfer scores.supported

Basis: reported finding

Link to claim
CLM-NOV03-SOC-ZERO-SHOT-TRANSFERThe reported PPO policy performed worse than random ranking when transferred without retraining to a second tenant with a different feature schema.supported

Basis: reported finding

Link to claim

Implications

Independent signals can cover complementary threat categories, but apparent low-noise performance is meaningless without the denominator and tenant-specific schema constraints.

Unknowns and contradictions

  • The event-level appendix metrics need reconciliation with reported cluster-level numbers.
  • No prospective analyst utilization or incident outcomes are supplied.
  • Normalization or tenant-specific retraining could materially change cross-tenant results.
  • Zero-shot transfer numbers in Table 11 concern Isolation Forest and the autoencoder; no prospective cross-tenant PPO run is established.

Sources and citation

Material revision history

  1. Nov 6, 2026 · Published version · first publication · revision 224