Skip to content

Changelog

Tags: NEW (new capability), IMPROVED (enhancement).

26h4d (November 2026)

Available on AWS Marketplace.

  • NEW — Configuration and posture history. Every configuration save, plus a daily snapshot, keeps the full configuration in the tamper-evident audit store for your audit-retention period, alongside a daily snapshot of the Compliance Posture view, so you can show exactly what was in force, and how posture trended, on any day.
  • IMPROVED — Richer audit records. Triage actions now record the threat's severity, MITRE tactic, and fired rules, and whether a closed threat was reopened. Bulk actions share one id, and any item they could not apply is recorded with the reason. AI playbook requests record the model used and the outcome, including ones that finished in the background.
  • IMPROVED — Precise exclusion history. Each added or removed exclusion and trusted IP is recorded individually, so the audit trail shows exactly what was silenced.
  • IMPROVED — Wider audit-failure alerting. You're now alerted if any part of AI SIEM fails to record an audit entry, including analyst actions, configuration saves, and integrity checks.
  • IMPROVED — More to query in the audit trail. Audit records in Athena now include threat context, configuration integrity results, cleanup summaries, and AI playbook details.
  • IMPROVED — Compliance counts scale with your deployment. The Compliance Posture view counts every open finding, however large the threat table grows.
  • IMPROVED — Claude Haiku 5.5 is the default AI model. New and upgraded deployments use Claude Haiku 5.5 for playbooks and reports, and Settings → AI recommends it, replacing Claude Haiku 4.5, which is past its AWS end-of-life floor. Action required on upgrade: enable Bedrock model access to Claude Haiku 5.5 in your account (access to 4.5 does not carry over), then click Test this model in Settings → AI; until then AI playbooks use the built-in template. Haiku 4.5 is still selectable, and a model you already chose in Settings is kept.
  • IMPROVED — Every denied action is audited. Any action a role is not permitted to take is now recorded, with the endpoint, target, and required role, including configuration saves and threat updates.
  • IMPROVED — Sign-in sessions and access reviews. Sign-in and sign-out records are paired by session, and a user's first appearance and role changes are recorded, so access can be reviewed straight from the audit trail.
  • IMPROVED — Clearer detection source. Audit records now say whether a rule fired or which source raised the threat, and daily snapshots are attributed to the system rather than the last person who saved.
  • IMPROVED — Exclusions in posture history. The daily posture snapshot records how many exclusions narrow each control.
  • IMPROVED — Alert delivery on the dashboard. System Health now shows whether threat alert emails have a confirmed recipient and whether any failed to deliver.
  • IMPROVED — Richer threat history in Athena. Threat history now records the affected resources, the finding title, and the AWS Config rule and result, including every resource a Security Hub finding lists.
  • IMPROVED — Every archived threat is listed. Each archive run now keeps a tamper-evident list of every threat it removes, with its type, how it was detected and why it was removed, and records how many were actually removed.
  • IMPROVED — Open threats are no longer archived by age. The hard age cap now only removes handled threats; open threats stay until someone triages them. The high-water mark still keeps the live list bounded, and if it ever has to remove open threats you're told by email and on the dashboard. Turn off Keep open threats past the age cap in Settings → Threat Retention & Archive to restore the previous behavior.
  • NEW — Retention at a glance. A Retention box on the dashboard shows open threats about to be archived, how close the live list is to its high-water mark, and any open threats the last archive run removed. Each line links to the threats or setting behind it, and a new Expiring soon view in Threats lists open threats in age order, oldest first.
  • NEW — Response times by severity. The dashboard shows how long threats wait to be acknowledged and resolved, per severity, over the last 30 days. Optionally set your own targets under Settings → Response Targets to see the share met, an Overdue view in Threats, a banner when anything is late, and an optional daily email. Each measured time is also recorded in the audit trail.
  • NEW — Turn on AWS Config with one script. scripts\enable-config.cmd (and .sh) turns on AWS Config recording in an account and Region: full records everything Security Hub needs (its Config.1 control passes) while recording the usually costly network interfaces daily; minimal records S3 and IAM only. status shows what is recorded and whether Config.1 can pass, and stop halts recording and its charges. Getting Started now explains why Security Hub depends on Config.
  • IMPROVED — Discovery contract v2 for suite integrations. AI SIEM now also publishes its tier, the names of its Athena audit and threats tables, where its configuration, snapshots and archive manifests are stored, how its evidence is encrypted, and where its configuration integrity seal is kept, so other Perfware products in the account can find them. Existing discovery keys are unchanged.
  • NEW — CIS and NIST coverage in Compliance posture. Compliance posture now includes CIS AWS Foundations Benchmark v5.0.0 (section 4 monitoring controls 4.3, 4.8 and 4.9) and NIST SP 800-53 Rev 5 controls in the FedRAMP baseline (AU-2, AU-6, AU-9, AU-12, AC-2, AC-6(9), SI-4). Controls that AI SIEM only partly monitors are labeled "Partial coverage" with a note on what isn't watched. This shows which events AI SIEM monitors for each control. It is not a certification or a FedRAMP authorization.
  • IMPROVED — Compliance scores measure coverage. A control counts as covered when the data sources and detection rules that monitor it are on. Open threats no longer lower the score. Each control shows how many open threats it has to review, counting each threat once, and the count links to them.
  • IMPROVED — Choose your compliance frameworks, and see the threats behind a control. Turn frameworks on or off under Settings → Compliance Frameworks; a framework you turn off is left out of Compliance Posture and its daily snapshot, not shown as passing. A control's open threats link to Threats, filtered to the ones that count against it.
  • IMPROVED — Blocked archive runs are recorded. When the archive safety limit stops a run, the audit trail now records a blocked entry with the reason and the fraction it would have removed. Nothing is deleted. Runs stopped by the continuation cap now say so too. Each run's start record also notes how close the threat table was to its limit, how many open threats it was about to remove, and whether the keep-open-threats setting came from your configuration or the default.
  • IMPROVED — Config event times. AWS Config compliance changes are timestamped when Config evaluated them.
  • IMPROVED — Clearer outside-change notices. When the configuration is changed outside the editor, the editor says so and links to the Config Tampering threat.
  • IMPROVED — Cleaner configuration history. Only your own edits are recorded as changes; defaults the editor fills in are not.
  • IMPROVED — Large archive runs finish the same day. A run with more to remove than fits in one pass continues until done.

26h4c (November 2026)

Available on AWS Marketplace.

  • IMPROVED — Threat cleanup on every deployment size. Routine automatic cleanup of old, handled threats runs on small and quiet deployments as well as large ones.
  • IMPROVED — Self-clearing health alarms. Archive monitoring alarms return to normal on their own once a transient issue passes.
  • IMPROVED — Smoother re-sign-in. When your editor session expires, signing back in returns you straight to the app, and brief network blips don't lock the screen.

26h4b (October 2026)

Available on AWS Marketplace.

  • NEW — Choose your AI model. An admin can select the Amazon Bedrock model used for playbooks and report summaries under Settings → AI — pick from a recommended list (each shows its relative cost), click Test this model to confirm it produces a usable playbook, then Apply and save, or revert to the deployment default. The change applies with no stack update. Apply unlocks only after a successful Test, so an untested model can never go live.
  • NEW — Works in every region. The AI model is now invoked through the inference profile matching your deployment's region (US, Europe, Asia-Pacific), so playbook and report AI work correctly outside us-east-1. Enter a base model id and AI SIEM applies the right regional form automatically.
  • NEW — Model-retirement warnings. When the model in use nears its AWS retirement date, the FAQ panel shows an advance warning so you can switch to a successor before it stops working. If a model is ever unavailable, AI SIEM falls back to a built-in deterministic playbook and explains why.
  • NEW — Notification bell for background playbooks. A slower model can take longer than a request should wait; when that happens, playbook generation continues in the background and a notification bell lights with a link to the threat the moment it's ready — no more watching a spinner.
  • IMPROVED — Reliable playbooks on any model. AI SIEM now adapts to how each Bedrock model formats and paces its output, so playbooks generate dependably whether you run a fast model (Claude Haiku) or a slower, more detailed one (Claude Sonnet). It automatically handles longer responses, gives a slower model more time when it needs it, and remembers what works for each model so later playbooks are quick — and if a model still can't produce usable steps, you always get a built-in playbook rather than an empty result. The model that generated each playbook is now shown on the playbook and on the dashboard.
  • IMPROVED — Faster configuration saves. Saving no longer runs a live model check, so changes save immediately; the "does this model work" guarantee moved to the Test this model button in Settings → AI.
  • IMPROVED — Clearer AI failure messages. Playbook and report AI failures now name the likely cause and the one action that fixes it — enable model access, choose a faster model, or (for a brand-new model your account isn't yet entitled to) contact AWS — instead of a generic error.
  • IMPROVED — Report preview shows a loading state. Opening a report preview now shows "Loading preview…" while it fetches, instead of a blank panel.
  • IMPROVED — Reliable AI on reasoning models. Newer "thinking" models (e.g. Claude Haiku 5.5) spend part of their budget reasoning before they answer, which could leave an AI rule assessment or suggestion cut off and unusable. AI SIEM now detects a response that ran out of room and automatically retries with more, so AI rule assessment, rule drafting, and tuning suggestions work dependably across models — and still fall back to a safe result if the model can't finish.
  • IMPROVED — Steadier processing under bursts. The ingestion and threat-detection queues now hold a message in flight longer than the processing Lambda can run, so a long-running batch can't have its work re-delivered and duplicated. The AI Monitor anomaly read also retries briefly on a slow response, smoothing over momentary load on low-traffic deployments.
  • IMPROVED — Home icon on the title. A ⌂ home icon now marks the AI SIEM title in the header; click it (or the title) to return to the dashboard from anywhere.

26h4a — General Availability (October 2026)

Now available on AWS Marketplace.

  • NEW — Generally available. First GA release of AI SIEM: AI-powered Security Information and Event Management for AWS, deployed into your own account via AWS Marketplace.
  • NEW — Unified threat detection & timeline. Correlates CloudTrail, VPC Flow Logs, GuardDuty, Security Hub, and AWS Config into a chronological threat timeline per actor, with ML behavioral baselines per IAM principal and MITRE ATT&CK mapping.
  • NEW — Guided incident response. On-demand, AI-generated response playbooks (Amazon Bedrock) with identifier de-identification before the model, and optional delegated remediation through buyer-owned AWS Systems Manager Automation runbooks.
  • NEW — Multi-account & multi-environment. A single deployment can centralize logs, metrics, and threats across your AWS organization; run separate dev/staging/prod instances side by side.
  • IMPROVED — Dashboard clarity. The "By severity" view now reflects open (needs-attention) threats, so handled items don't inflate the picture.
  • IMPROVED — Security & reliability hardening. Browser security headers/CSP on the editor, flat-cost Athena-first flow-log analysis, and resiliency/DR validation ahead of GA.

Release history

Condensed summary of pre-GA development milestones.

  • 26h4 (Oct 2026) — AI Monitor metric anomalies can raise standalone threats; at-a-glance threat lifecycle trail; Athena-first flat-cost flow-log analysis; editor security response headers/CSP; bulk-action and Data Sources UX improvements; detection-noise and compliance-tally fixes.
  • 26h3 (Sep 2026) — Delegated remediation via buyer-owned SSM Automation (replacing self-privileged auto-remediation), with staged approval, scheduling, and an SLA/stalled watchdog; dedicated VPC Flow panel; point-and-click Investigations over the long-retention archive; Bedrock privacy mode (identifier redaction, encrypted mapping); per-VPC flow thresholds.
  • 26h2 (Aug–Sep 2026) — Initial build: CloudTrail / VPC Flow / GuardDuty / Security Hub ingestion; ML behavioral baselines per IAM principal; unified threat timeline with cross-signal correlation; MITRE ATT&CK mapping; AI playbooks; editor UI with dashboard, triage, bulk assignment, per-detection email alerts, autosave/recovery; real-time dashboard totals, server-side filtering/pagination, and automatic threat retention/archive; AI Monitor & Log Processor correlation; 5-tier Marketplace entitlement.

Full, granular per-change history is retained internally and available on request.