agent-threat-rules 2.0.16 → 2.0.17

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-threat-rules",
-  "version": "2.0.16",
+  "version": "2.0.17",
   "type": "module",
   "description": "Open detection standard -- like Sigma, but for AI agents. 311 rules for prompt injection, tool poisoning, context exfiltration, and MCP attacks. Shipped in Cisco AI Defense. 97.1% recall on NVIDIA garak.",
   "main": "./dist/index.js",

package/rules/context-exfiltration/ATR-2026-00021-api-key-exposure.yaml

@@ -65,6 +65,15 @@ compliance:
     - clause: "6.2"
       context: "Protecting credentials from exposure is an explicit AIMS information security objective under clause 6.2; detection of leakage events measures whether this objective is being achieved."
       strength: secondary
+  colorado_ai_act:
+    - section: "6-1-1703"
+      clause: "Deployer risk management for consumer-facing AI"
+      context: "Credentials leaked from a consumer-facing AI system can expose the database records, scoring model inputs, or authentication tokens that drive consequential decisions. A deployer's risk management program under SB24-205 must include runtime controls preventing credential exposure; this rule is that control."
+      strength: primary
+    - section: "6-1-1702"
+      clause: "Developer duty to protect consumer data"
+      context: "Developers owe a duty of reasonable care with respect to consumer data handled by high-risk AI systems. Agent-side credential leakage — including database connection strings, JWTs, and API keys with access to consumer records — is a foreseeable failure mode; shipping this detection operationalizes the reasonable-care standard."
+      strength: secondary
 
 tags:
   category: context-exfiltration

package/rules/excessive-autonomy/ATR-2026-00050-runaway-agent-loop.yaml

@@ -61,6 +61,11 @@ compliance:
     - clause: "9.1"
       context: "Clause 9.1 monitoring and evaluation requires measuring AI system behavior against expected norms; loop counter patterns are the measurable anomaly indicators for this rule."
       strength: secondary
+  colorado_ai_act:
+    - section: "6-1-1703"
+      clause: "Deployer ongoing monitoring of AI system performance"
+      context: "SB24-205 requires deployers to monitor high-risk AI systems for performance drift after deployment. A runaway loop is a performance-degradation event — the system is no longer behaving within its validated operational envelope. This rule gives the deployer the telemetry signal needed to fulfill the ongoing-monitoring obligation and to trigger impact reassessment if needed."
+      strength: primary
 
 tags:
   category: excessive-autonomy

package/rules/privilege-escalation/ATR-2026-00040-privilege-escalation.yaml

@@ -63,6 +63,11 @@ compliance:
     - clause: "8.6"
       context: "Clause 8.6 AI system operational control requires that agents do not exceed their authorized operational scope; privilege escalation detection enforces that operational boundary."
       strength: secondary
+  colorado_ai_act:
+    - section: "6-1-1703"
+      clause: "Deployer risk management program"
+      context: "When a high-risk AI system acquires privileges beyond its authorized scope, any consequential decision it makes afterward falls outside the risk-management program's impact assessment. SB24-205 requires deployers to keep AI systems within documented operational bounds; this rule detects the boundary violation that would invalidate the deployer's impact-assessment assumptions."
+      strength: primary
 
 tags:
   category: privilege-escalation