Skip to content
AI SOC Compared

LESSON 04 · HOW IT WORKS

Context that persists: memory and decision history in an AI SOC

SHORT ANSWER

An analyst who has worked your queue for a year knows which admin logs in from two countries and which alert always fires after patching. AI SOC vendors now try to give their agents that memory: facts about your environment and a record of past decisions. It can make verdicts better, but only if the memory is visible, dated and correctable.

By The Alert Desk · AI SOC Compared · Published 2026-09-30 · 3 min read

Why does context change a verdict?

The same alert can be noise in one company and an incident in another. A login from a new country is routine for a travelling sales team and alarming for a payroll clerk. Without context, an AI SOC either escalates too much or closes too much. With context, it can reach the verdict your senior analyst would.

How vendors describe it

  • Mate Security introduced its Security Context Graph in February 2026, describing it as a graph of memories that captures SOC knowledge the way an experienced analyst sees it. On its platform page Mate lists memories with a source, confidence and freshness, decision traces recording why analysts decided what they did, guardrails, and a map of your architecture.
  • Torq added SOC Brain in July 2026, with three parts it calls Recall, Reflex and Retrospect that learn from past investigations and analyst verdicts; Torq says each customer gets a private model trained only on its own data. In May 2026 Torq also acquired Jit to add AI context graphs to its platform.
  • Conifers says its agents learn from the environment and from analyst feedback.

The names differ; the idea is the same: the platform keeps what it learned instead of starting from zero on every alert.

What can go wrong

Memory can be wrong or stale. A fact learned a year ago, such as who owns a server, may no longer be true. A past decision may have been a mistake that now repeats itself. And a memory nobody can see is a memory nobody can correct.

What to check

  1. Can an analyst see which remembered facts a verdict used?
  2. Does each fact show where it came from and when?
  3. Can the team edit or delete a fact, and does the change take effect at once?
  4. Does an analyst's correction become a lasting memory, or only a note on one case?
  5. Is the memory kept per customer, and where is it stored?

Why it matters for a lean team

A small team cannot write down everything it knows before buying a platform. A platform that learns from the team's own decisions captures that knowledge as a side effect of normal work. That only pays off if the team can review what was learned, which is why this lesson belongs next to the one on verdict records.

A test for the pilot

During a pilot, give the platform one fact it could not know from logs, such as a planned office move or a new contractor group, and watch whether later verdicts use it. Then correct one remembered fact and check that the next investigation reflects the change. Two small tests like these show more about a memory than any diagram of it.

SOURCES

Source: Mate Security blog: Introducing the Security Context Graph (19 February 2026) · Read 27 Sep 2026

Source: Mate Security platform · Read 27 Sep 2026

Source: Torq newsroom: SOC Brain (27 July 2026) · Read 27 Sep 2026

Source: Torq newsroom: Torq acquires Jit (18 May 2026) · Read 27 Sep 2026

Source: Conifers homepage · Read 27 Sep 2026