Release history
Every entry is one real change already in production: added, changed or fixed, dated, and linked to the track it affects. The same convention any software changelog uses, so what we say about this platform can be checked against what actually shipped.
Full detail on this is covered under our non-disclosure agreement. Request access and we send it as part of that process.
No agreement needed for /training or the public Portal Kombat case file.
Request accessA new grid shows which families of the detection taxonomy our detectors have actually hit, per actor -- including the gaps.
A new webhook feeds search-term volume disruption alerts straight into the triage queue.
Visitors now pick a track from the home page, and the product status behind each one is public, with no login required.
Access now requires an electronic non-disclosure agreement, signed and recorded on an append-only trail.
The source registry became editable by an analyst, with every change written to an audit trail.
An analyst can now sign in with a Google account, alongside the existing passwordless email link.
The public site began explaining the product to a visitor, with access requested through a form instead of a shared login.
An AI colleague you can mention in a comment thread began correlating evidence with fully citable, read-only tools.
Saved filters, a review board, and quick navigation were added to the daily review workflow.
Threat actors became their own entity, with a command hierarchy and aggregated technique tags.