Secure Autonomous
FeedbackGet alertsCheck a deployment
Signals › SIG-2026-10-29-017

NIST, NSA and CISA: Key Practices for Incident Readiness and Response in Super Intelligence Training and Evaluation (October 2026)

The National Institute of Standards and Technology's Center for Advancing Innovation and Standards for Super Intelligence (NIST CAISSI), the National Security Agency's Super Intelligence Security Center (NSA SISC) and the Cybersecurity and Infrastructure Security Agency (CISA) published ten voluntary key practices for incident readiness and response in super intelligence training and evaluation, grouped under preparation, detection, response, recovery and reporting.

GuidanceSoftware agents · Enterprise work agentsRecord published 2026-10-16Posted 2026-10-29
SIG-2026-10-29-017NIST publication ↗

The record

Kind
Guidance
Source record
NIST CAISSI, NSA and CISA: Key Practices for Incident Readiness and Response in Super Intelligence Training and Evaluation (16 October 2026) (NIST publication)
Record published
2026-10-16
Posted here
2026-10-29
World
Software agents · Enterprise work agents
Controls concerned
Hard domain restriction C-E2; Independent audit log C-V1; Kill switch faster than the actor C-X2
Checked
Checked against its record on 2026-10-29 by a reader who did not draft it; report verification/reports/SIG-2026-10-29-017-2026-10-29.md.

A signal's controls are the ones its record points at, the exposure; a case's controls are the ones its records show were absent or failed, so the two can differ.

What a signal is. A signal records what a primary record says; it assigns no fault. It is lighter than a case: one dated item from one record, tagged with the world, sector and controls it touches. It becomes a case when it meets the bar for one.

New signals like this, once a week. A short email when a case, signal or rule touches software agents. Free; unsubscribe in one click.

Get the weekly email

Newer: Meta: automated protections wrongly took the No Kings Instagram account offline
Older: CVE-2026-77474: destructive_command_guard (dcg)

Is this wrong? Dispute it with the record that shows otherwise. All signals · RSS feed.

Help shape the Register

A person reads every answer; changes it leads to are logged in the methodology. To dispute a claim or reply for a named company, use Respond, dispute, or submit.

Did this page help with what you came to do?