PAGES
Subscribe Get it delivered — five to ten releases we picked each morning from the tools you run, with every release in the issue on the web. Compare plans →

The Cyber Toolchain — issue 089, September 29, 2026

THE CYBER TOOLCHAIN NO. 089
Tail
THE DAILY RELEASE FIREHOSE
PUBLISHED SEPTEMBER 29, 2026 · EVERY DAY
EDITIONS tail grep head ls diff uniq

The daily firehose — everything the toolchain shipped today, already filtered.

We read every release from the 1326 tools on our watchlist at the source — GitHub and GitLab release notes, vendor release pages and changelogs, project blogs and feeds, vendor press releases, and the source code behind the tag. Bug-fix-only releases and non-product newsroom noise are dropped; what's left is summarized down to the new capability, how to try it, and any screenshots or videos the release itself published. Every entry links to the sources it was built from.

VIEW
ISSUE VIEW scroll
INFORMATION DENSITY everything
ISSUE WIDTH reading width
Do you prefer scroll?
ADDITIONAL FILTERS
$ tct list   # 48 tools matched

What stands out across today's releases, grouped by what it lets you do. Every tool named links to its entry below.

Three unrelated things stand out. Knocknoc grew just-in-time network access from a handful of enforcement points to most of the firewall and cloud estate, so ports open per-session instead of standing open. Qualys can now block a bad patch fleet-wide by rule and skip unreliable ones in zero-touch jobs. Snyk Container finally reports Go standard-library CVEs.

  • protect

    Open a port for one person for one session, on the firewall you already own

    Enforcement now reaches DigitalOcean, Cloudflare, AWS WAFAWS WAFAmazon's managed web application firewall service that inspects HTTP/S requests and blocks traffic matching configurable rules for threats like SQLi and XSS, letting cyber tools offload layer-7 filtering to AWS infrastructure. and EC2 Security GroupsEC2 Security GroupsAWS firewall rules attached to EC2 instances that control inbound and outbound traffic at the instance level; cyber tools use them to restrict exposure without managing host-based firewalls., Azure NSGAzure NSGAzure Network Security Group: a Microsoft Azure resource that filters inbound and outbound traffic to Azure resources using configurable allow/deny rules, giving cyber tools a native firewall layer without deploying separate appliances., Sophos SFOS/XGS, F5 BigIP, Fortinet, PF, Windows Firewall and Linux IPSetIPSetA Linux kernel subsystem for storing sets of IP addresses, networks, or ports in hash or bitmap structures so that firewall rules can match millions of entries in constant time instead of scanning a list. from one Integrations hub, with PostgreSQL HAPostgreSQL HAA deployment pattern for PostgreSQL databases that keeps the service available through automatic failover when the primary node fails, letting cyber tools maintain persistent storage without manual intervention during outages. behind the server. The usual blocker for JIT network access is that it only covers one chokepoint and everything else stays allow-listed by IP forever; this covers enough of the estate to actually retire those rules, and the Trust Engine ships its decisions to SIEM.

    Knocknoc

  • protect

    Stop a patch that breaks machines before it reaches the fleet

    TruRiskTruRiskA proprietary risk-scoring methodology from Qualys that translates vulnerability and asset data into a numeric business-risk score, giving cyber tools a single prioritization signal instead of raw CVSS values. Eliminate takes QQL-based rules that block specific patches environment-wide and uses reliability scoring to drop low-confidence patches out of zero-touch jobs, with curated interim mitigations for what stays unpatched. That is the missing half of automated patching: teams turn zero-touch off entirely after one bad Tuesday, and now they can exclude the offender instead. Iru adds per-device Windows update and patch compliance reporting so you can see who is actually current.

    Qualys Patch Management · Iru

  • protect

    See Go stdlib CVEs in container scans instead of missing them

    Vulnerabilities in the Go standard library are compiled into the binary and carry no manifest entry, so scanners routinely reported a clean image while the runtime itself was vulnerable. Snyk now synthesizes the stdlib as a dependency in results, which means the finding shows up in the existing triage queue rather than requiring a separate govulncheckgovulncheckA Go static-analysis command maintained by the Go team that scans a module's dependencies for known vulnerabilities, reporting only those reachable by the code's actual call graph. pass someone remembers to run.

    Snyk Container

  • identify

    Find the repos and cloud accounts your scanner never actually covered

    GitGuardian's Coverage Hub flags where integration, monitoring, scanning or ownership is missing across the monitored perimeter with one-click remediation, turning "we scan for secrets" into a list of the sources you demonstrably do not. Kubescape's multi-cluster fleet scanning rolls compliance into one report and adds scan-coverage metrics, so a clean posture score is distinguishable from a score computed over half the clusters.

    GitGuardian SaaS · kubescape

Application Security
◆  Code Security

GitHub

Sources Blog / feed → Self-hosted runner version enforcement date has moved (2026-09-28) Blog Rank Why this rank top features scored 70/60, +15 breaking change, +6 runnable example — 86 How ranking works →

GitHub shipped a REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. for tracking self-hosted runner version deprecations ahead of a tightened enforcement deadline, and made Claude Sonnet 5.5 generally available in Copilot with admin controls.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

GitHub is a web-based platform for version control and collaborative software development using Git repositories.

GitHub shipped a REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. for tracking self-hosted runner version deprecations ahead of a tightened enforcement deadline, and made Claude Sonnet 5.5 generally available in Copilot with admin controls.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 2 FEATURES 1 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
Claude Sonnet 5.5 in GitHub Copilot Not checked yet new 70

Claude Sonnet 5.5 is now generally available in GitHub Copilot across all supported clients and IDEs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Copilot Enterprise and Business admins can manage access via the model policy in Copilot settings, with new models automatically enabled under default model enablement unless the global default is off or the model is explicitly disabled.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Select Claude Sonnet 5.5 for an agentic coding task in VS Code to take advantage of its faster, lower-token execution on well-scoped feature work.
📍In GitHub Copilot (VS Code, JetBrains, or github.com), open the model picker and select Claude Sonnet 5.5, then submit your Copilot Chat or coding agent prompt as normal.
As a Copilot Enterprise or Business admin, control which users can access Claude Sonnet 5.5 before the gradual rollout reaches your org.
📍Navigate to your organization's Copilot settings › model policy, then enable or disable Claude Sonnet 5.5 under the default model enablement controls.
— Gives exact UI navigation and picker steps for use and admin control. Claude Sonnet 5.5 in GitHub Copilot (2026-09…
02 00
REST API for runner version deprecations Not checked yet breaking 60

A new REST API lets teams query registration and runtime deprecation dates for any self-hosted runner version, enabling automated alerts for fleets nearing their deadline. This accompanies a policy change: self-hosted runners below version 2.329.0 on GitHub Enterprise Cloud will not be able to register or reregister starting September 29, 2026, and existing runners below the minimum runtime version will stop executing workflow jobs even if previously registered.

— Names deadline and version threshold but no endpoint path or method. Self-hosted runner version enforcement date …
└──▷ BREAKING ON UPGRADE
  • !
    Self-hosted runners below version 2.329.0 on GitHub Enterprise Cloud will not be able to register or reregister starting September 29, 2026; existing runners below the minimum runtime version will stop executing workflow jobs even if previously registered.
Self-hosted runner version enforcement date has moved (2026-09-28) Blog LatestStable

New REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. for runner version deprecations lets you query registration and runtime deprecation dates for any self-hosted runner version.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ BREAKING ON UPGRADE
  • !Self-hosted runners below version 2.329.0 on GitHub Enterprise Cloud will not be able to register or reregister starting September 29, 2026; existing runners below the minimum runtime version will stop executing workflow jobs even if previously registered.
Claude Sonnet 5.5 in GitHub Copilot (2026-09-28) Blog Stable

Claude Sonnet 5.5 is now generally available in GitHub Copilot across all supported clients and IDEs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Select Claude Sonnet 5.5 for an agentic coding task in VS Code to take advantage of its faster, lower-token execution on well-scoped feature work.
📍In GitHub Copilot (VS Code, JetBrains, or github.com), open the model picker and select Claude Sonnet 5.5, then submit your Copilot Chat or coding agent prompt as normal.
As a Copilot Enterprise or Business admin, control which users can access Claude Sonnet 5.5 before the gradual rollout reaches your org.
📍Navigate to your organization's Copilot settings › model policy, then enable or disable Claude Sonnet 5.5 under the default model enablement controls.
  • Copilot Enterprise and Business administrators can manage access to Claude Sonnet 5.5 via the model policy in Copilot settings, with new models automatically enabled under default model enablement unless the global default is off or the model is explicitly disabled.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

1 detail in Everything

Was this useful?

GitLab

Sources Blog / feed → What's new in Git 2.56.0? (2026-09-28) Blog Rank Why this rank top features scored 88/88/80, +6 runnable example — 91.33 How ranking works →

Git 2.56.0 ships a batch of new subcommands and flags spanning history rewriting, branch cleanup, ref management, partial-clone maintenance, and object introspection.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

The intelligent orchestration platform for DevSecOps, enabling teams and agents to ship trusted software at enterprise scale.

Git 2.56.0 ships a batch of new subcommands and flags spanning history rewriting, branch cleanup, ref management, partial-clone maintenance, and object introspection.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 7 FEATURES 0 OF 7 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
New --delete-merged and --forked flags for git branch Not checked yet new 88

Adds --delete-merged flag to git-branch(1) to delete all local branches whose tips are reachable from their configured upstream, removing merged feature branches in one step.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Adds --forked flag as a listing filter to show branches whose configured upstream matches a provided ref, remote name, or branch.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Clean up all local feature branches that have already been merged into origin/main, including branches forked from it rather than merged locally.
$ git branch --delete-merged origin
— Both flags named with mechanism and a runnable example. What's new in Git 2.56.0? (2026-09-28)
02 00
Drop filtered blobs in git repack Not checked yet new 88

Adds --drop-filtered option to git-repack(1) to remove locally cached promisor blobs above the given filter threshold, recovering disk space in partial clones.

Recover disk space in a blobless partial clone by evicting large cached blobs so Git re-fetches them lazily only when needed.
$ git repack -a -d --filter=blob:limit=1k --drop-filtered
— Named flag with mechanism and a runnable example. What's new in Git 2.56.0? (2026-09-28)
03 00
New git history drop subcommand Not checked yet new 80

Adds a drop subcommand to git-history(1) to remove a commit and rebase its descendants in a single command: git history drop <commit>.

Drop a specific commit from history and automatically rebase its descendants — no interactive rebase editor needed.
$ git history drop <commit>
— Names exact command and includes a runnable example. What's new in Git 2.56.0? (2026-09-28)
04 00
Remote object metadata lookup in git cat-file Not checked yet new 78

Adds a remote-object-info command to git-cat-file(1)'s --batch-command mode to fetch object metadata (size, type) over Git protocol v2 without transferring the full object.

— Mechanism and protocol detail given, no usage example. What's new in Git 2.56.0? (2026-09-28)
05 00
New create, update, rename, delete subcommands for git refs Not checked yet new 73

Adds create, update, rename, and delete subcommands to git-refs(1), with update and delete accepting an optional expected old value for validation.

— All four subcommands named but no example given. What's new in Git 2.56.0? (2026-09-28)
06 00
Linearize flag for git replay Not checked yet new 70

Adds --linearize flag to git-replay(1) to enable rebasing commit ranges that contain merge commits by flattening the history.

— Flag and effect named, no example given. What's new in Git 2.56.0? (2026-09-28)
07 00
Path fields added to git repo info Not checked yet improved 60

Extends the git repo info subcommand with path.gitdir and path.commondir fields, each available in both absolute and relative forms.

— Fields named but no usage example provided. What's new in Git 2.56.0? (2026-09-28)
What's new in Git 2.56.0? (2026-09-28) Blog LatestStable

Git 2.56 adds git history drop, git branch --delete-merged, git refs create/update/rename/delete, git repack --drop-filtered, and more.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT
Drop a specific commit from history and automatically rebase its descendants — no interactive rebase editor needed.
$ git history drop <commit>
Clean up all local feature branches that have already been merged into origin/main, including branches forked from it rather than merged locally.
$ git branch --delete-merged origin
Recover disk space in a blobless partial clone by evicting large cached blobs so Git re-fetches them lazily only when needed.
$ git repack -a -d --filter=blob:limit=1k --drop-filtered
  • Adds drop subcommand to git-history(1) to remove a commit and rebase its descendants in a single command: git history drop <commit>.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds --delete-merged flag to git-branch(1) to delete all local branches whose tips are reachable from their configured upstream, removing merged feature branches in one step. Not checked yet
  • Adds --forked flag to git-branch(1) as a listing filter to show branches whose configured upstream matches a provided ref, remote name, or branch.
  • Adds create, update, rename, and delete subcommands to git-refs(1), with update and delete accepting an optional expected old value for validation.
  • Adds remote-object-info command to git-cat-file(1)'s --batch-command mode to fetch object metadata (size, type) over Git protocol v2 without transferring the full object.
+3 more show less
  • Adds --drop-filtered option to git-repack(1) to remove locally cached promisor blobs above the given filter threshold, recovering disk space in partial clones.
  • Extends git repo info subcommand with path.gitdir and path.commondir fields, each available in both absolute and relative forms.
  • Adds --linearize flag to git-replay(1) to enable rebasing commit ranges that contain merge commits by flattening the history.
  • Adds drop subcommand to git-history(1) to remove a commit and rebase its descendants in a single command: git history drop <commit>.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds remote-object-info command to git-cat-file(1)'s --batch-command mode to fetch object metadata (size, type) over Git protocol v2 without transferring the full object.
  • Adds --drop-filtered option to git-repack(1) to remove locally cached promisor blobs above the given filter threshold, recovering disk space in partial clones.

5 more in Everything

Was this useful?

StepSecurity

Sources Blog / feed → Dev Machine Guard v1.17.0 (2026-09-29) Blog Rank Why this rank top features scored 78/75/75, +10 product media, +6 runnable example — 92 How ranking works →

StepSecurity's Dev Machine Guard v1.17.0 extends Secure Registry package config policies to PyPI/uv and Go, adds a fleet-wide Agent Plugins inventory for Claude Code and Codex, brings Insomnia into credential scanning, and redesigns the Compliance tab.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

StepSecurity hardens CI/CD pipelines by detecting and preventing supply chain attacks through runtime security monitoring and vulnerability detection.

StepSecurity's Dev Machine Guard v1.17.0 extends Secure Registry package config policies to PyPI/uv and Go, adds a fleet-wide Agent Plugins inventory for Claude Code and Codex, brings Insomnia into credential scanning, and redesigns the Compliance tab.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 8 FEATURES 0 OF 8 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Go Secure Registry package config policy Not checked yet new 78

Adds Go package config policies that set the Secure Registry as the sole GOPROXYGOPROXYAn environment variable and protocol used by the Go toolchain to specify a module proxy server from which `go` commands fetch dependencies, enabling reproducible builds, caching, and access control over third-party packages. in the user's go/env file via the same shared ~/.netrc credential, leaving GOPRIVATE, GONOPROXY, GONOSUMDB, and GOSUMDB untouched.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Precise env vars and scope, but no CLI example given Dev Machine Guard v1.17.0 (2026-09-29)
02 00
PyPI/uv Secure Registry package config policy Not checked yet new 75

Adds PyPI package config policies that point pip and uv at your tenant's Secure Registry by setting index in pip.conf and uv.toml, storing a shared credential in ~/.netrc, and restoring the prior config when the policy is detached.

— Names exact config files and keys but no runnable command shown Dev Machine Guard v1.17.0 (2026-09-29)
03 00
Extra npm settings in package config policies Not checked yet improved 75

Adds support for an optional list of extra .npmrc settings in npm package config policies, delivered to every assigned device inside the managed block, with tokens referenced as ${ENV_NAME} from the developer's environment.

Roll out a scoped private registry for your org's npm packages alongside the Secure Registry, using an environment-variable token that StepSecurity never stores.
ini
@myorg:registry=https://npm.mycompany.internal
//npm.mycompany.internal/:_authToken=${MYORG_NPM_TOKEN}
— Includes a runnable .npmrc config example with token syntax Dev Machine Guard v1.17.0 (2026-09-29)
04 00
Agent Plugins inventory for Claude Code and Codex Not checked yet new 70

Adds a new Agent Plugins inventory page under IDE & AI Agents that tracks Claude Code and Codex plugins fleet-wide, including marketplace/repository source, publisher, installed and enabled state per device, and the skills, commands, and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers each plugin supplies.

Audit which Claude Code and Codex plugins are installed across your fleet before approving them for use in a compliance review.
📍In the StepSecurity console, go to IDE & AI Agents › Agent Plugins to view each plugin's marketplace source, publisher, enabled state per device, and the MCP servers it supplies.
— Clear UI navigation given, no API or flag Dev Machine Guard v1.17.0 (2026-09-29)
05 00
Insomnia credential scanning Not checked yet new 65

Adds Insomnia to the credential inventory under a new API clients category, covering request authentication, credential headers, environment and secret variables, OAuth tokens, request history, and account/provider stores; secret variables in Insomnia's encrypted storage are reported as Protected.

— Thorough on scope but no action path given Dev Machine Guard v1.17.0 (2026-09-29)
06 00
Redesigned Compliance tab per policy Not checked yet improved 65

Redesigns the profile Compliance tab to show a compliance card per policy, one overall status per device, a device panel with per-policy status and reason, and highlights devices whose agent is too old for a policy.

— UI path implied and behaviour detailed, no exact navigation given Dev Machine Guard v1.17.0 (2026-09-29)
07 00
New coding tool and IDE detection Not checked yet new 60

Adds detection for Grok Build, Kimi Code, Muse Code, Hermes Agent, and Oh My Pi as Coding Tools, and Kiro as an IDE, with their skills plus Kiro, Windsurf, Antigravity, and OpenClaw skills now appearing under Agent Skills.

— Many named tools but no usage or action described Dev Machine Guard v1.17.0 (2026-09-29)
thinner coverage below
08 00
Agent Skills usage tracking Not checked yet improved 45

Agent Skills now lists standalone Claude Code commands and shows a per-skill usage count drawn from Claude Code's recorded history.

— Describes what changed but no mechanism detail or path Dev Machine Guard v1.17.0 (2026-09-29)
Dev Machine Guard v1.17.0 (2026-09-29) Blog LatestStable

Dev Machine Guard v1.17.0 adds PyPI, uv, and Go Secure Registry policies plus a Claude Code/Codex Agent Plugins inventory and Insomnia credential scanning.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Audit which Claude Code and Codex plugins are installed across your fleet before approving them for use in a compliance review.
📍In the StepSecurity console, go to IDE & AI Agents › Agent Plugins to view each plugin's marketplace source, publisher, enabled state per device, and the MCP servers it supplies.
Roll out a scoped private registry for your org's npm packages alongside the Secure Registry, using an environment-variable token that StepSecurity never stores.
.npmrc
@myorg:registry=https://npm.mycompany.internal
//npm.mycompany.internal/:_authToken=${MYORG_NPM_TOKEN}
  • Adds PyPI package config policies that point pip and uv at your tenant's Secure Registry by setting index in pip.conf and uv.toml, storing a shared credential in ~/.netrc, and restoring prior config when the policy is detached.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds Go package config policies that set the Secure Registry as the sole GOPROXYGOPROXYAn environment variable and protocol used by the Go toolchain to specify a module proxy server from which `go` commands fetch dependencies, enabling reproducible builds, caching, and access control over third-party packages. in the user's go/env file via the same shared ~/.netrc credential, leaving GOPRIVATE, GONOPROXY, GONOSUMDB, and GOSUMDB untouched.
  • Adds support for an optional list of extra .npmrc settings in npm package config policies, delivered to every assigned device inside the managed block, with tokens referenced as ${ENV_NAME} from the developer's environment.
  • Adds a new Agent Plugins inventory page under IDE & AI Agents that tracks Claude Code and Codex plugins fleet-wide, including marketplace/repository source, publisher, installed and enabled state per device, and the skills, commands, and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers each plugin supplies.
  • Adds Insomnia to the credential inventory under a new API clients category, covering request authentication, credential headers, environment and secret variables, OAuth tokens, request history, and account/provider stores — secret variables in Insomnia's encrypted storage are reported as Protected.
+3 more show less
  • Adds detection for Grok Build, Kimi Code, Muse Code, Hermes Agent, Oh My Pi as Coding Tools and Kiro as an IDE, with their skills plus Kiro, Windsurf, Antigravity, and OpenClaw skills appearing under Agent Skills.
  • Agent Skills now lists standalone Claude Code commands and shows a per-skill usage count drawn from Claude Code's recorded history.
  • Redesigns the profile Compliance tab to show a compliance card per policy, one overall status per device, a device panel with per-policy status and reason, and highlights devices whose agent is too old for a policy.
  • Adds PyPI package config policies that point pip and uv at your tenant's Secure Registry by setting index in pip.conf and uv.toml, storing a shared credential in ~/.netrc, and restoring prior config when the policy is detached.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds Go package config policies that set the Secure Registry as the sole GOPROXYGOPROXYAn environment variable and protocol used by the Go toolchain to specify a module proxy server from which `go` commands fetch dependencies, enabling reproducible builds, caching, and access control over third-party packages. in the user's go/env file via the same shared ~/.netrc credential, leaving GOPRIVATE, GONOPROXY, GONOSUMDB, and GOSUMDB untouched.
  • Adds a new Agent Plugins inventory page under IDE & AI Agents that tracks Claude Code and Codex plugins fleet-wide, including marketplace/repository source, publisher, installed and enabled state per device, and the skills, commands, and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers each plugin supplies.
  • Adds Insomnia to the credential inventory under a new API clients category, covering request authentication, credential headers, environment and secret variables, OAuth tokens, request history, and account/provider stores — secret variables in Insomnia's encrypted storage are reported as Protected.

4 more in Everything

Was this useful?

Veracode

Sources Blog / feed → Training updates (2026-09-29) Blog Rank Why this rank top features scored 78/78/63, +15 breaking change — 88 How ranking works →

Veracode's September 2026 training update centers on an upgraded Get Lesson Progress API, deeper Veracode Platform IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. integration for Security Labs team management, a wave of new OWASP Top 10:2025OWASP Top 10:2025A ranked list of the ten most critical web application risk categories, maintained by the Open Worldwide Application Security Project, used by cyber tools to prioritize detection, testing, and remediation coverage. and LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. security content, and several breaking changes including a new Security Labs URL and the retirement of the eLearning REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. and dozens of legacy courses.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Veracode is a cloud-based application security platform that performs static, dynamic, and software composition analysis to identify vulnerabilities in code.

Veracode's September 2026 training update centers on an upgraded Get Lesson Progress API, deeper Veracode Platform IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. integration for Security Labs team management, a wave of new OWASP Top 10:2025OWASP Top 10:2025A ranked list of the ten most critical web application risk categories, maintained by the Open Worldwide Application Security Project, used by cyber tools to prioritize detection, testing, and remediation coverage. and LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. security content, and several breaking changes including a new Security Labs URL and the retirement of the eLearning REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. and dozens of legacy courses.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 14 FEATURES 0 OF 14 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Get Lesson Progress API enhancements Not checked yet improved 78

Adds updatedAfter parameter to support incremental loads and excludeNotStarted=true to filter out lessons that have not been started, plus new stack and updated_on fields in the response; the API now returns Not Started when both start_time and end_time are null.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Names exact API parameters and fields but no endpoint path or method. Training updates (2026-09-29)
02 00
Security Labs default URL changed Not checked yet breaking 78

The default Security Labs URL has changed from https://securitylabs.veracode.com/ to https://securitylabs.veracode.com/security-labs/; customers using SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. with a stand-alone account must update their Security Labs URL.

— Exact before/after URLs and a clear required migration step. Training updates (2026-09-29)
03 00
New Security Labs lesson content for OWASP 2025, LLM and containers Not checked yet new 63

Adds new OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Top 10:2025 Security Labs covering all 10 categories, including two new categories A03 Software Supply ChainSupply ChainThe network of vendors, dependencies, and build processes that produce and deliver software; cyber tools target it because a compromise anywhere upstream can silently backdoor every downstream consumer. Failures and A10 Mishandling of Exceptional Conditions; adds OWASP Top 10 for LLM applications lessons covering LLM01 through LLM09 in Flask; and adds Container Security in Docker lessons covering Users, Virtualization, Networking, Resources, Inventory, and Orchestration topics.

— Names all covered categories and topics but no way to start a lesson. Training updates (2026-09-29)
04 00
Deprecated eLearning courses and OWASP 2021 lessons removed Not checked yet deprecated 63

33 deprecated eLearning courses (OWASP 2017, OWASP Top 10 (2021), Secure Coding for .NET, Java, JavaScript, PHP, Python — 6 courses each, Python 3 courses) are no longer available, with certification levels updated to include newer replacement courses; the OWASP Top 10 (2021) Security Labs lessons are also no longer available.

— Enumerates the removed courses precisely but no reader action path. Training updates (2026-09-29)
thinner coverage below
05 00
Six new eLearning secure coding courses Not checked yet new 55

Adds six new eLearning secure coding courses aligned to OWASP Top 10:2025 for .NET, Java, JavaScript, PHP, Python, and Security Awareness, available with English, Spanish, French, Portuguese, and Chinese captions.

— Lists languages and topics but no access instructions. Training updates (2026-09-29)
06 00
Assessment quiz eLearning courses Not checked yet new 55

Adds assessment quiz eLearning courses for User and application setup, Static Analysis, Dynamic Analysis, Scan and fix in your IDE, and SCASCASoftware composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. agent-based scanning, available in English, Portuguese, and Spanish.

— Names all course topics and languages but no access steps. Training updates (2026-09-29)
07 00
Team and IAM management in Security Labs Not checked yet new 48

Organizations with more than 500 teams can now select which teams are available for use in Security Labs; Security Labs users and teams management is integrated with the Veracode Platform, with users authenticated through Veracode IAM; administrators and managers can also search teams within Security Labs.

— Describes what changed but not the underlying mechanism. Training updates (2026-09-29)
08 00
Extended eLearning report date range Not checked yet improved 45

Extends eLearning report date range selection to up to one year in the past.

— Gives concrete limit but no exact UI path. Training updates (2026-09-29)
09 00
CWE tagging for Security Labs lessons Not checked yet new 40

Adds CWECWECommon Weakness Enumeration, a catalog of recurring software and hardware weakness types. It describes classes of mistakes, such as injection, rather than individual vulnerability instances. tagging for Security Labs lessons, enabling admins to search lessons by CWE and learners to see lessons linked to specific CWEsCWEsA community-maintained list of software and hardware weakness types, maintained by MITRE, that gives cyber tools a standard taxonomy for classifying and communicating vulnerability root causes..

— Explains function but no search syntax or UI path. Training updates (2026-09-29)
10 00
Security Labs terminology renamed Not checked yet breaking 40

In Security Labs, Teams are now called Organizations and Roles are now called Teams; any documentation or automation referencing the old terminology must be updated.

— Names the terminology swap but no specifics on where it appears. Training updates (2026-09-29)
11 00
Veracode eLearning REST API end of support Not checked yet deprecated 30

The Veracode eLearning REST API has reached end of support and will no longer receive updates or technical support.

— States EOL status only, no migration path given. Training updates (2026-09-29)
12 00
Security Labs community edition deprecated Not checked yet deprecated 30

The Security Labs community edition is deprecated as of July 31, 2026.

— Gives a firm date but no replacement or migration guidance. Training updates (2026-09-29)
13 00
Code syntax highlighting in lessons Not checked yet new 25

Adds code syntax highlighting in Security Labs lessons tailored to programming languages.

— Single-line description with no further detail. Training updates (2026-09-29)
14 00
In-app guidance for campaigns and reporting Not checked yet new 20

Security Labs adds in-app guidance for creating campaigns and using reporting.

— Bare description with no mechanism or navigation detail. Training updates (2026-09-29)
└──▷ BREAKING ON UPGRADE
  • !
    The default Security Labs URL has changed from https://securitylabs.veracode.com/ to https://securitylabs.veracode.com/security-labs/; customers using SSO with a stand-alone account must update their Security Labs URL.
  • !
    In Security Labs, Teams are now called Organizations and Roles are now called Teams; any documentation or automation referencing the old terminology must be updated.
  • !
    The Veracode eLearning REST API has reached end of support and will no longer receive updates or technical support.
  • !
    33 deprecated eLearning courses (OWASP 2017, OWASP Top 10 (2021), Secure Coding for .NET, Java, JavaScript, PHP, Python — 6 courses each, Python 3 courses) are no longer available; certification levels have been updated to include newer replacement courses.
  • !
    The OWASP Top 10 (2021) Security Labs lessons are no longer available.
  • !
    The Security Labs community edition is deprecated as of July 31, 2026.
Training updates (2026-09-29) Blog LatestStable

Veracode Security Labs gains team selection for large orgs, Veracode Platform IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. integration, and updated Get Lesson Progress API with new parameters.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds updatedAfter parameter to the Get Lesson Progress API to support incremental loads.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds excludeNotStarted=true parameter to the Get Lesson Progress API to filter out lessons that have not been started. Not checked yet
  • Adds stack field and updated_on field to the Get Lesson Progress API response; shows Not Started when both start_time and end_time are null.
  • Enables organizations with more than 500 teams to select which teams are available for use in Security Labs.
  • Integrates Security Labs users and teams management with the Veracode Platform, authenticating Security Labs users through Veracode IAM (Identity and Access Management).
+10 more show less
  • Allows Security Labs administrators and managers to search teams within Security Labs.
  • Adds in-app guidance for creating campaigns and using reporting in Security Labs. Not checked yet
  • Adds new OWASP Top 10:2025OWASP Top 10:2025A ranked list of the ten most critical web application risk categories, maintained by the Open Worldwide Application Security Project, used by cyber tools to prioritize detection, testing, and remediation coverage. Security Labs covering all 10 categories, including two new categories: A03 Software Supply ChainSupply ChainThe network of vendors, dependencies, and build processes that produce and deliver software; cyber tools target it because a compromise anywhere upstream can silently backdoor every downstream consumer. Failures and A10 Mishandling of Exceptional Conditions.
  • Adds new OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Top 10 for LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. applications Security Labs lessons covering LLM01 through LLM09 in Flask.
  • Adds Container Security in Docker Security Labs lessons covering Users, Virtualization, Networking, Resources, Inventory, and Orchestration topics.
  • Adds six new eLearning secure coding courses aligned to OWASP Top 10:2025 for .NET, Java, JavaScript, PHP, Python, and Security Awareness, available with English, Spanish, French, Portuguese, and Chinese captions.
  • Adds CWECWECommon Weakness Enumeration, a catalog of recurring software and hardware weakness types. It describes classes of mistakes, such as injection, rather than individual vulnerability instances. tagging for Security Labs lessons, enabling admins to search lessons by CWE and learners to see lessons linked to specific CWEsCWEsA community-maintained list of software and hardware weakness types, maintained by MITRE, that gives cyber tools a standard taxonomy for classifying and communicating vulnerability root causes..
  • Adds code syntax highlighting in Security Labs lessons tailored to programming languages.
  • Extends eLearning report date range selection to up to one year in the past. Not checked yet
  • Adds assessment quiz eLearning courses for User and application setup, Static Analysis, Dynamic Analysis, Scan and fix in your IDE, and SCASCASoftware composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. agent-based scanning, available in English, Portuguese, and Spanish.
  • Adds updatedAfter parameter to the Get Lesson Progress API to support incremental loads.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Enables organizations with more than 500 teams to select which teams are available for use in Security Labs.
  • Integrates Security Labs users and teams management with the Veracode Platform, authenticating Security Labs users through Veracode IAM (Identity and Access Management).
  • Allows Security Labs administrators and managers to search teams within Security Labs.
  • Adds in-app guidance for creating campaigns and using reporting in Security Labs. Not checked yet
+7 more show less
  • Adds new OWASP Top 10:2025OWASP Top 10:2025A ranked list of the ten most critical web application risk categories, maintained by the Open Worldwide Application Security Project, used by cyber tools to prioritize detection, testing, and remediation coverage. Security Labs covering all 10 categories, including two new categories: A03 Software Supply ChainSupply ChainThe network of vendors, dependencies, and build processes that produce and deliver software; cyber tools target it because a compromise anywhere upstream can silently backdoor every downstream consumer. Failures and A10 Mishandling of Exceptional Conditions.
  • Adds new OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Top 10 for LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. applications Security Labs lessons covering LLM01 through LLM09 in Flask.
  • Adds Container Security in Docker Security Labs lessons covering Users, Virtualization, Networking, Resources, Inventory, and Orchestration topics.
  • Adds six new eLearning secure coding courses aligned to OWASP Top 10:2025 for .NET, Java, JavaScript, PHP, Python, and Security Awareness, available with English, Spanish, French, Portuguese, and Chinese captions.
  • Adds CWECWECommon Weakness Enumeration, a catalog of recurring software and hardware weakness types. It describes classes of mistakes, such as injection, rather than individual vulnerability instances. tagging for Security Labs lessons, enabling admins to search lessons by CWE and learners to see lessons linked to specific CWEsCWEsA community-maintained list of software and hardware weakness types, maintained by MITRE, that gives cyber tools a standard taxonomy for classifying and communicating vulnerability root causes..
  • Adds code syntax highlighting in Security Labs lessons tailored to programming languages.
  • Adds assessment quiz eLearning courses for User and application setup, Static Analysis, Dynamic Analysis, Scan and fix in your IDE, and SCASCASoftware composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. agent-based scanning, available in English, Portuguese, and Spanish.

3 more in Everything

└──▷ BREAKING ON UPGRADE
  • !The default Security Labs URL has changed from https://securitylabs.veracode.com/ to https://securitylabs.veracode.com/security-labs/; customers using SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. with a stand-alone account must update their Security Labs URL.
  • !In Security Labs, Teams are now called Organizations and Roles are now called Teams; any documentation or automation referencing the old terminology must be updated.
  • !The Veracode eLearning REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. has reached end of support and will no longer receive updates or technical support.
  • !33 deprecated eLearning courses (OWASP 2017, OWASP Top 10 (2021), Secure Coding for .NET, Java, JavaScript, PHP, Python — 6 courses each, Python 3 courses) are no longer available; certification levels have been updated to include newer replacement courses.
  • !The OWASP Top 10 (2021) Security Labs lessons are no longer available.
  • !The Security Labs community edition is deprecated as of July 31, 2026.
Was this useful?
◆  Secrets Detection & Management

GitGuardian SaaS

Sources Blog / feed → Spot your uncovered assets. Close your blindspot in one click! (2026-09-28) Blog Rank Why this rank top features scored 88/80/75, +15 breaking change, +10 product media, +6 runnable example — 112 How ranking works →

GitGuardian SaaS is a cloud-based security platform that detects and prevents secrets leakage in git repositories and source code.

GitGuardian's biggest addition this window is the Coverage Hub on the Monitored Perimeter page, which surfaces integration, monitoring, scanning and ownership gaps with one-click remediation; the perimeter page also gained saved views, column customization, team-ownership tracking, improved bulk actions, and automatic team-perimeter eviction rules for deleted, archived or unmonitored sources, alongside a breaking replacement of the Health filter with Has open incidents.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 5 FEATURES 0 OF 5 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Coverage Hub on the perimeter page Not checked yet new 88

Adds the Coverage Hub to the Monitored Perimeter page: four summary cards (Integrations, Real time monitoring, Historical scans, Team ownership) quantify coverage gaps — installed integrations, share of sources monitored in real time, share scanned successfully, and share owned by a team — and link directly to filtered source lists.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Card actions filter the sources table to sources needing action (unmonitored, unscanned, or unassigned) in one click, and a red badge counts sources GitGuardian cannot reach, with a Show more details view listing integrations and flagging unreachable ones.

Surface integrations with unreachable sources so you can restore monitoring coverage before secrets go undetected.
📍In the perimeter page, look for the red badge on the Coverage Hub, then click Show more details to see which integrations have unreachable sources and click the card action to filter the table to those sources.
Identify all sources not yet assigned to a team and bulk-assign them to close ownership gaps.
📍In the perimeter page, click the Owned by a team card action to filter the sources table to unassigned sources, select all, then choose a bulk action to assign them. Alternatively, use the Team filter and select No team assigned to reach the same view.
— Names all four cards and gives exact click-through steps. Spot your uncovered assets. Close your blind…
02 00
Bulk actions on perimeter sources Not checked yet improved 80

Adds a bulk actions bar for acting on many perimeter sources at once — Monitor, Unmonitor, and Launch historical scan — requiring confirmation when selecting more than 30 sources or when some sources will be skipped. Later grays out inapplicable actions with explanatory tooltips and lists skipped sources with reasons when monitoring, unmonitoring, or scanning more than 30 sources.

Kick off historical scans for every source that has never been scanned, confirming the batch when GitGuardian prompts on selections over 30 sources.
📍In the Monitored Perimeter page, click See unscanned sources in the Historical scans card, use 'Select all N sources that match filters', choose the Launch historical scan bulk action, and confirm the dialog.
— Names each bulk action and a worked example with the 30-source threshold. Spot your uncovered assets. Close your blind…
03 00
Automatic team-perimeter eviction rules Not checked yet new 75

Adds configurable automatic team-perimeter eviction rules — Deleted sources, Archived sources, and Unmonitored sources — so members lose access to a source and its incidents as soon as it leaves the team perimeter under one of these statuses. Managers toggle the team perimeter setting per status to keep or remove unmonitored and archived/deleted sources from team perimeters.

Automatically remove unmonitored sources from a team perimeter so stale sources do not clutter a team's incident view — while keeping manager access intact.
📍In the GitGuardian console, go to Workspace Settings › Team perimeter and enable the Unmonitored sources setting so that sources which are no longer monitored are automatically removed from all team perimeters.
— Names each status toggle and the console path to enable it. product docs
04 00
Saved views and column customization on perimeter page Not checked yet new 70

Adds saved views to the perimeter page, including built-in non-editable views Monitored, Critical sources, With open secret incidents, Scanning issues, and Without honeytoken; a Columns control to show, hide, or reorder perimeter table columns; a Teams column (shown by default in the Monitored view) with a No team assigned filter value to identify unowned sources; and a Last scan column with a Skipped badge and hover explanation for scans that did not run.

— Enumerates every named view and column but no runnable step. Spot your uncovered assets. Close your blind…
thinner coverage below
05 00
Health filter replaced by Has open incidents Not checked yet breaking 50

Replaces the Health filter with Has open incidents on the perimeter page, with saved views using the old filter migrated automatically; the sources table is now sorted by open incidents by default, prioritising sources at risk.

— States the before/after but gives no migration steps. Spot your uncovered assets. Close your blind…
└──▷ BREAKING ON UPGRADE
  • !
    The Health filter on the perimeter page is replaced by Has open incidents; saved views using the old filter are migrated automatically.
Spot your uncovered assets. Close your blindspot in one click! (2026-09-28) Blog Stable

GitGuardian's new Coverage Hub surfaces unmonitored, unscanned, and unowned sources on the perimeter page with one-click remediation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Identify all sources not yet assigned to a team and bulk-assign them to close ownership gaps.
📍In the perimeter page, click the Owned by a team card action to filter the sources table to unassigned sources, select all, then choose a bulk action to assign them. Alternatively, use the Team filter and select No team assigned to reach the same view.
Surface integrations with unreachable sources so you can restore monitoring coverage before secrets go undetected.
📍In the perimeter page, look for the red badge on the Coverage Hub, then click Show more details to see which integrations have unreachable sources and click the card action to filter the table to those sources.
  • Adds the Coverage Hub to the perimeter page: four cards show installed integrations, share of sources monitored in real time, share scanned successfully, and share owned by a team.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds card actions that filter the sources table to sources needing action — unmonitored, unscanned, or unassigned — in one click.
  • Adds a red badge on the Coverage Hub to count sources GitGuardian cannot reach, with a Show more details view listing integrations and flagging unreachable ones.
  • Adds a Teams column to the perimeter sources table showing the teams assigned to each source.
  • Adds a No team assigned option to the Team filter to surface sources without an owner.
+3 more show less
  • Replaces the Health filter with Has open incidents on the perimeter page, with saved views migrated automatically.
  • Sorts the perimeter sources table by open incidents by default, prioritising sources at risk.
  • Improves bulk actions on perimeter sources: grays out inapplicable actions with explanatory tooltips, and lists skipped sources with reasons when monitoring, unmonitoring, or scanning more than 30 sources.
  • Adds the Coverage Hub to the perimeter page: four cards show installed integrations, share of sources monitored in real time, share scanned successfully, and share owned by a team.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds card actions that filter the sources table to sources needing action — unmonitored, unscanned, or unassigned — in one click.
  • Adds a red badge on the Coverage Hub to count sources GitGuardian cannot reach, with a Show more details view listing integrations and flagging unreachable ones.
  • Adds a Teams column to the perimeter sources table showing the teams assigned to each source.

4 more in Everything

└──▷ BREAKING ON UPGRADE
  • !The Health filter on the perimeter page is replaced by Has open incidents; saved views using the old filter are migrated automatically.
Was this useful?
Reverse Engineering, Malware & Forensics
◆  Digital Forensics & Incident Response

iLEAPP

Sources Release notes →Source code → v2026.4.3 Notes Code Rank Why this rank top features scored 90/80/60, +15 breaking change, +6 runnable example — 97.67 How ranking works →

iOS Logs, Events, And Plist Parser

iLEAPP v2026.4.3 unifies GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands. and CLI into a single ileapp binary, greatly expands the forensic image formats it can parse directly, and adds nine new iOS app parsers plus several new artifact types.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 11 FEATURES 0 OF 11 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Raw image and filesystem support in `-t raw` Not checked yet improved 90

Extends -t raw to parse E01E01A forensic disk image format that stores a drive's contents in segmented files with built-in checksums and metadata, widely used in digital forensics because it supports compression and chain-of-custody verification. and Ex01, SMART, AFFAFFAdvanced Forensic Format, an open disk-image container standard maintained by Simson Garfinkel, designed to store forensic evidence with built-in compression, metadata, and cryptographic hashing. and AFD forensic images, Apple disk images (.dmg, .sparseimage, sparse bundles and segmented sets), encrypted Apple disk images, FTK Imager AD-encrypted images, and encrypted APFSAPFSApple's proprietary filesystem introduced in 2017, replacing HFS+, designed for SSDs with native encryption, snapshots, and space sharing — giving cyber tools reliable forensic primitives on modern Apple devices. volumes opened with a supplied password, without mounting or admin rights.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Also adds NTFSNTFSThe default file system format for Windows, developed by Microsoft, storing files with rich metadata and access controls; cyber tools target it to parse artifacts like timestamps, alternate data streams, and the MFT. alternate data stream reading under -t raw.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Parse an EnCase E01 acquisition directly — no mounting or admin rights needed — useful when working from a forensic image on a case workstation.
$ ileapp -t raw -i /evidence/acquisition.E01 -o /cases/output/
— Lists every supported format and includes a runnable command v2026.4.3
02 00
Unified `ileapp` binary across platforms Not checked yet breaking 80

iLEAPP now ships as a single ileapp binary for both GUI and CLI on all platforms — running without arguments launches the GUI, running with arguments runs the CLI — replacing the separate ileappGUI binary. Windows downloads are -windows-x64-setup.exe / -windows-x64-portable.zip and -windows-arm64-setup.exe / -windows-arm64-portable.zip; macOS gets signed and notarised -macos-arm64.dmg / -macos-x64.dmg; Linux gets -linux-x64.AppImage / -linux-arm64.AppImage. Automated tooling that invoked ileappGUI or the old file-naming scheme must be updated.

— Names exact new download files but no migration command v2026.4.3
03 00
Nine new iOS app parsers Not checked yet new 60

Adds iOS artifact parsers for Roblox, KakaoTalk (with message, attachment and phone field decryption and inline media), WeChat, Telekom Mail, BOTIM, VK Messenger, Odnoklassniki, and SimpleX Chat (SQLCipher database decrypted with the keychain key).

— Names every app but no usage detail beyond that v2026.4.3
thinner coverage below
04 00
GUI support for .tar.xz archives Not checked yet improved 50

Adds GUI support for accepting .tar.xz archives, matching the existing CLI support via -t tar.

— Names format and flag but no full command shown v2026.4.3
05 00
Sysdiagnose Process tree artifact Not checked yet new 45

Adds a Sysdiagnose Process tree artifact built from ps.txt.

— Names the source file but no usage instructions v2026.4.3
06 00
Intelligence Platform artifact family for iOS Not checked yet new 35

Adds a new Intelligence Platform artifact family for iOS covering the knowledge graphknowledge graphA representation of entities and the relationships between them. Software can follow those connections to answer questions or combine information from different sources., expired interactions, behaviors timeline, and event locations.

— Names the four sub-artifacts but no mechanism v2026.4.3
07 00
Snapchatter Records rename and friends-list parsing Not checked yet improved 35

Renames the Snapchat Friends artifact to Snapchatter Records and adds parsing of the friends list.

— Clear rename and addition, no further mechanism given v2026.4.3
08 00
Call History columns for iOS 26 Not checked yet new 30

Adds Call History columns for iOS 26.

— Bare mention of new columns, no specifics v2026.4.3
09 00
qnxprobe dependency updated to 1.51 Not checked yet improved 30

Updates the bundled qnxprobe tool to version 1.51.

— Version bump only, no behaviour change described v2026.4.3
10 00
iOS Health walking and running distance artifact Not checked yet new 25

Adds an iOS Health artifact for walking and running distance.

— Thin one-line addition with no further detail v2026.4.3
11 00
Biome sync merged events artifact Not checked yet new 25

Adds a Biome sync merged events artifact.

— Thin one-line addition with no further detail v2026.4.3
└──▷ BREAKING ON UPGRADE
  • !
    The separate ileappGUI binary no longer exists; both GUI and CLI are now the single ileapp binary (GUI when run without arguments, CLI when run with arguments). Automated tooling that invokes ileappGUI must be updated.
  • !
    Download file names changed: the previous naming scheme (e.g. ileappGUI-v*-Windows_x86_64.zip) is replaced by new names such as -windows-x64-setup.exe, -windows-x64-portable.zip, -macos-arm64.dmg, -linux-x64.AppImage, etc.
v2026.4.3 Notes Code LatestStable

iLEAPP v2026.4.3 adds unified ileapp binary for all platforms, E01E01A forensic disk image format that stores a drive's contents in segmented files with built-in checksums and metadata, widely used in digital forensics because it supports compression and chain-of-custody verification./AFD/APFSAPFSApple's proprietary filesystem introduced in 2017, replacing HFS+, designed for SSDs with native encryption, snapshots, and space sharing — giving cyber tools reliable forensic primitives on modern Apple devices. image support via -t raw, and nine new iOS app parsers.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v2026.4.3 https://github.com/abrignoni/iLEAPP.git
# already have the repo? check out this version:
$ git checkout v2026.4.3
└──▷ TRY IT
Parse an EnCase E01 acquisition directly — no mounting or admin rights needed — useful when working from a forensic image on a case workstation.
$ ileapp -t raw -i /evidence/acquisition.E01 -o /cases/output/
  • Extends -t raw to support E01 and Ex01, SMART, AFFAFFAdvanced Forensic Format, an open disk-image container standard maintained by Simson Garfinkel, designed to store forensic evidence with built-in compression, metadata, and cryptographic hashing. and AFD images, Apple disk images (.dmg, .sparseimage, sparse bundles and segmented sets), encrypted Apple disk images, FTK Imager AD-encrypted images, and encrypted APFS volumes (opened with a supplied password).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds NTFSNTFSThe default file system format for Windows, developed by Microsoft, storing files with rich metadata and access controls; cyber tools target it to parse artifacts like timestamps, alternate data streams, and the MFT. alternate data stream reading under -t raw.
  • Adds iOS artifact support for Roblox, KakaoTalk (with message/attachment/phone field decryption and inline media), WeChat, Telekom Mail, BOTIM, VK Messenger, Odnoklassniki, and SimpleX Chat (SQLCipher, keychain key).
  • Adds iOS Health walking and running distance artifact.
  • Adds Intelligence Platform artifact family for iOS: knowledge graphknowledge graphA representation of entities and the relationships between them. Software can follow those connections to answer questions or combine information from different sources., expired interactions, behaviors timeline, and event locations.
+7 more show less
  • Adds Biome sync merged events artifact.
  • Renames Snapchat Friends to Snapchatter Records and adds friends-list parsing.
  • Adds Call History columns for iOS 26.
  • Adds Sysdiagnose Process tree built from ps.txt.
  • Unifies all platform downloads into a single ileapp binary: Windows gets -windows-x64-setup.exe / -windows-x64-portable.zip and -windows-arm64-setup.exe / -windows-arm64-portable.zip; macOS gets signed and notarised -macos-arm64.dmg / -macos-x64.dmg; Linux gets -linux-x64.AppImage / -linux-arm64.AppImage.
  • Accepts .tar.xz archives in the GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands. (already supported on the CLI via -t tar).
  • Updates qnxprobe to version 1.51. Not checked yet
  • Extends -t raw to support E01 and Ex01, SMART, AFFAFFAdvanced Forensic Format, an open disk-image container standard maintained by Simson Garfinkel, designed to store forensic evidence with built-in compression, metadata, and cryptographic hashing. and AFD images, Apple disk images (.dmg, .sparseimage, sparse bundles and segmented sets), encrypted Apple disk images, FTK Imager AD-encrypted images, and encrypted APFS volumes (opened with a supplied password).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds NTFSNTFSThe default file system format for Windows, developed by Microsoft, storing files with rich metadata and access controls; cyber tools target it to parse artifacts like timestamps, alternate data streams, and the MFT. alternate data stream reading under -t raw.
  • Adds iOS artifact support for Roblox, KakaoTalk (with message/attachment/phone field decryption and inline media), WeChat, Telekom Mail, BOTIM, VK Messenger, Odnoklassniki, and SimpleX Chat (SQLCipher, keychain key).
  • Adds iOS Health walking and running distance artifact.
  • Adds Intelligence Platform artifact family for iOS: knowledge graphknowledge graphA representation of entities and the relationships between them. Software can follow those connections to answer questions or combine information from different sources., expired interactions, behaviors timeline, and event locations.
+1 more show less
  • Adds Biome sync merged events artifact.

6 more in Everything

└──▷ BREAKING ON UPGRADE
  • !The separate ileappGUI binary no longer exists; both GUI and CLI are now the single ileapp binary (GUI when run without arguments, CLI when run with arguments). Automated tooling that invokes ileappGUI must be updated.
  • !Download file names changed: the previous naming scheme (e.g. ileappGUI-v*-Windows_x86_64.zip) is replaced by new names such as -windows-x64-setup.exe, -windows-x64-portable.zip, -macos-arm64.dmg, -linux-x64.AppImage, etc.
Was this useful?

Mobile Verification Toolkit

Sources Release notes →Source code → v2026.9.28 Notes Code Rank Why this rank top features scored 65/65 — 65 How ranking works →

MVT (Mobile Verification Toolkit) helps with conducting forensics of mobile devices in order to find signs of a potential compromise.

MVT improved its bugreport forensics pipeline by making check-bugreport recover data from nested OEM archives and fixing a parsing bug that dropped system properties, and it added a new alert for suspicious accessibility service counts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Bugreport archive handling improvements Not checked yet improved 65

check-bugreport now descends into OEM wrapper .zip archives when the outer archive lacks a dumpstate entry point, automatically finding and using the nested bugreport.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ A separate fix corrects cases where a section timing line was misidentified as a section boundary, restoring full SYSTEM PROPERTIES output on affected archives.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Names the subcommand and fixed output section, no exact CLI flags given v2026.9.28
02 00
Accessibility service count alert in dumpsys analysis Not checked yet new 65

Dumpsys accessibility analysis now surfaces accessibility service counts (installedServiceCount=N) per user, raising a LOW alert when the number of services listed in the count does not match the number actually named in the dump.

— Names the field and alert severity but no example output shown v2026.9.28
v2026.9.28 Notes Code LatestStable

MVT's check-bugreport now descends into OEM wrapper archives and recovers previously truncated dumpstate sections⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v2026.9.28 https://github.com/mvt-project/mvt.git
# already have the repo? check out this version:
$ git checkout v2026.9.28
  • Extends check-bugreport to descend into OEM wrapper .zip archives when the outer archive lacks a dumpstate entry point, automatically finding and using the nested bugreport.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Recovers properties lost when a section timing line was misidentified as a section boundary in bugreport parsing, restoring full SYSTEM PROPERTIES output on affected archives.
  • Surfaces accessibility service counts (installedServiceCount=N) per user in dumpsys accessibility analysis, raising a LOW alert when services are listed in the count but not named in the dump.
  • Extends check-bugreport to descend into OEM wrapper .zip archives when the outer archive lacks a dumpstate entry point, automatically finding and using the nested bugreport.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

2 more in Everything

Was this useful?

macos-unifiedlogs

Sources Release notes → v0.7.0 Notes Rank Why this rank top features scored 40/30/25 — 31.67 How ranking works →

A cross platform parser for Apple UnifiedLogs!

Adds lzbitmap decompression and richer Simpledump/Statedump field extraction.

└──▷ GET THIS VERSION
$ git clone --branch v0.7.0 https://github.com/mandiant/macos-UnifiedLogs.git
# already have the repo? check out this version:
$ git checkout v0.7.0
  • Adds lzbitmap decompression support for parsing log entries compressed with that algorithm. Not checked yet
  • Includes additional details extracted from Simpledump and Statedump log entries.

2 details in Everything

Was this useful?

cortex-analyzers

Sources Release notes → 3.10.0 Notes Rank Why this rank top features scored 45 — 45 How ranking works →

Cortex Analyzers Repository

v3.10.0 adds a ThreatFox analyzer, an Elastic Security alert-sync responder, and CheckPoint Harmony Email & Collaboration responders.

└──▷ GET THIS VERSION
$ git clone --branch 3.10.0 https://github.com/TheHive-Project/Cortex-Analyzers.git
# already have the repo? check out this version:
$ git checkout 3.10.0
  • New integrationAdds a new ThreatFox analyzer for querying the Abuse.ch ThreatFox threat intelligence platform. Not checked yet
  • New integrationAdds an Elastic Security responder to sync alert statuses between Cortex and Elastic Security.
  • New integrationAdds CheckPoint Harmony Email & Collaboration responders for incident response actions against that platform.

3 details in Everything

Was this useful?
◆  Reverse Engineering

Finite State Platform

Sources Blog / feed → September 28, 2026 - Project name checks, Finding VEX retention, and faster Component replace (2026-09-28) Blog Rank Why this rank top features scored 90/50/50, +6 runnable example — 69.33 How ranking works →

Finite State Platform is a software supply chain security tool that analyzes firmware and software composition to identify vulnerabilities and compliance risks.

Finite State Platform's latest release adds an audit trail for user deletions, speeds up Component replace/revert on large Versions, preserves VEXVEXA machine-readable statement from a vendor saying whether a CVE in a component actually affects their product. It is how a scanner is told to stop flagging a vulnerability that is not reachable. and triage data through reassessment, and cleans up Findings CSV export headers.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 4 FEATURES 0 OF 4 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
USER_DELETED audit event on user deletion Not checked yet new 90

When DELETE /public/v0/users/{id} succeeds, the platform now logs a USER_DELETED event to GET /public/v0/audit including the deleted user's id and email, and terminates that user's active sessions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Verify that deleting a user produces an audit trail — confirm the USER_DELETED event and the user's id and email appear in the audit log.
$ curl -X DELETE 'https://platform.finitestate.io/public/v0/users/{id}' -H 'Authorization: Bearer <token>'

curl 'https://platform.finitestate.io/public/v0/audit' -H 'Authorization: Bearer <token>'
— Named endpoints, event type, and fields with a runnable verification example September 28, 2026 - Project name checks, Fi…
thinner coverage below
02 00
Faster Component replace and revert on large Versions Not checked yet improved 50

Component replace and revert operations on large Versions are now faster because license Policy is evaluated once per Component rather than once per finding.

— Explains mechanism but gives no command or config to act on September 28, 2026 - Project name checks, Fi…
03 00
VEX and comment retention through reassessment Not checked yet improved 50

Findings that carry a VEX status or a comment — including SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue.-supplied VEX and triage — are now preserved through reassessment triggered by exclude, include, replace, or revert operations.

— Clear behavior described but no interface or command to trigger it September 28, 2026 - Project name checks, Fi…
04 00
Consistent column headers in Findings CSV exports Not checked yet improved 35

Filtered, searched, and row-selected Findings CSV exports now use the same column header labels as the unfiltered export, instead of raw internal key names.

— States before/after but no export path or command given September 28, 2026 - Project name checks, Fi…
September 28, 2026 - Project name checks, Finding VEX retention, and faster Component replace (2026-09-28) Blog LatestStable

Finite State Platform now logs USER_DELETED audit events, retains VEXVEXA machine-readable statement from a vendor saying whether a CVE in a component actually affects their product. It is how a scanner is told to stop flagging a vulnerability that is not reachable./comments through reassessment, and speeds up Component replace on large Versions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT
Verify that deleting a user produces an audit trail — confirm the USER_DELETED event and the user's id and email appear in the audit log.
$ curl -X DELETE 'https://platform.finitestate.io/public/v0/users/{id}' -H 'Authorization: Bearer <token>'

curl 'https://platform.finitestate.io/public/v0/audit' -H 'Authorization: Bearer <token>'
  • Adds USER_DELETED audit event to GET /public/v0/audit — including the deleted user's id and email — when DELETE /public/v0/users/{id} succeeds, and terminates the deleted user's active sessions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Speeds up Component replace and revert on large Versions by evaluating license Policy once per Component rather than per finding.
  • Preserves Findings that carry a VEX status or a comment (including SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue.-supplied VEX and triage) through reassessment after exclude, include, replace, or revert operations.
  • Filtered, searched, and row-selected Findings CSV exports now use the same column header labels as the unfiltered export instead of raw internal key names.
  • Adds USER_DELETED audit event to GET /public/v0/audit — including the deleted user's id and email — when DELETE /public/v0/users/{id} succeeds, and terminates the deleted user's active sessions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

3 more in Everything

Was this useful?
◆  Malware Analysis

YARA-X

Sources Release notes → v1.21.0 Notes Rank Why this rank top features scored 57/53/48 — 52.67 How ranking works →

A rewrite of YARA in Rust.

Adds Scanner.set_module_output to Python bindings, a new debug command for atoms, and stdin-based scan list support.

└──▷ GET THIS VERSION
$ git clone --branch v1.21.0 https://github.com/VirusTotal/yara-x.git
# already have the repo? check out this version:
$ git checkout v1.21.0
  • Adds Scanner.set_module_output method to the Python bindings for controlling module output during scans. Not checked yet
  • Adds debug command for showing atoms extracted from YARA-X rules.
  • Supports reading scan target lists from stdin, enabling pipeline-driven scanning workflows.

3 details in Everything

Was this useful?
Network Security
◆  Network Analysis & Monitoring

SO-CRATES

Sources Release notes → v4.3.0 Notes Rank Why this rank top features scored 80/65/55, +6 runnable example — 72.67 How ranking works →

SO-CRATES: Security Onion Containerized Rapid Analysis of Threats, Evil, and Sus!

SO-CRATES v4.3.0 bundles a fully offline CyberChef instance directly into the container and wires it into the UI at multiple entry points — stream payloads, SuricataSuricataAn open-source network threat detection engine maintained by the OISF that performs IDS, IPS, and network security monitoring; cyber tools build on it for high-speed packet inspection and rule-based alerting.-extracted files, and ad-hoc transcript selections — for air-gapped decode-and-pivot workflows.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 4 FEATURES 0 OF 4 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Send stream payload bytes to CyberChef Not checked yet new 80

Adds a Send to CyberChef action in a stream's Payload panel that sends the exact bytes in Both directions, or just the Source or Dest side, preserving XOR keys, compressed data, and shellcode intact for analysis in the bundled CyberChef.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Analyse a full bidirectional TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. payload — shellcode, compressed data, XOR-keyed content — in an air-gapped CyberChef without it appearing in browser history.
📍In the stream detail view, open the Payload panel, then click Send to CyberChef and choose Both, Source, or Dest to load the exact bytes into the bundled CyberChef instance.
— Names exact panel, direction options, and byte-level guarantees with a runnable UI flow v4.3.0
02 00
Pivot-menu text selection with auto Magic decode Not checked yet improved 65

Selecting any text in an ASCII transcript — base64 blobs, headers, or partial values — now surfaces a pivot menu with CyberChef (and other lookups) access. CyberChef's Magic operation is applied automatically to small payloads sent this way, including values sent from the pivot menu, to suggest decodings.

Decode a suspicious base64 blob or header value spotted in an ASCII transcript without leaving the SO-CRATES UI.
📍Select the text (e.g. a base64 blob) in the ASCII transcript, then choose CyberChef from the pivot menu that appears — CyberChef opens with the selected text and, for small values, applies the Magic operation automatically.
— Describes trigger and auto-decode mechanism with a concrete usage walkthrough v4.3.0
thinner coverage below
03 00
Bundled, air-gapped CyberChef instance Not checked yet new 55

CyberChef is now bundled into the container image (~48 MB added) so pivot-menu CyberChef lookups work with no internet access. The bundled instance also syncs its light/dark theme to match the user's chosen SO-CRATES theme unless a CyberChef theme has been set manually.

— Explains size and offline mechanism but no config surface to act on v4.3.0
04 00
Send to CyberChef for Suricata-extracted files Not checked yet new 50

Adds a Send to CyberChef button in the File Info panel for files Suricata extracted from traffic, loading the file's bytes directly into the bundled CyberChef instance for offline triage.

Inspect a file Suricata carved from traffic — PE, archive, document — directly in CyberChef for offline triage.
📍Navigate to the alert or flow's File Info panel and click the Send to CyberChef button next to the extracted file to load its bytes into the bundled CyberChef instance.
— Names the panel and button but describes little beyond the single action v4.3.0
v4.3.0 Notes LatestStable

SO-CRATES v4.3.0 ships a bundled, air-gapped CyberChef with full-payload pivoting, bidirectional stream support, and Suricata-extracted file analysis.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v4.3.0 https://github.com/dougburks/so-crates.git
# already have the repo? check out this version:
$ git checkout v4.3.0
└──▷ HOW TO FIND IT
Analyse a full bidirectional TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. payload — shellcode, compressed data, XOR-keyed content — in an air-gapped CyberChef without it appearing in browser history.
📍In the stream detail view, open the Payload panel, then click Send to CyberChef and choose Both, Source, or Dest to load the exact bytes into the bundled CyberChef instance.
Decode a suspicious base64 blob or header value spotted in an ASCII transcript without leaving the SO-CRATES UI.
📍Select the text (e.g. a base64 blob) in the ASCII transcript, then choose CyberChef from the pivot menu that appears — CyberChef opens with the selected text and, for small values, applies the Magic operation automatically.
Inspect a file Suricata carved from traffic — PE, archive, document — directly in CyberChef for offline triage.
📍Navigate to the alert or flow's File Info panel and click the Send to CyberChef button next to the extracted file to load its bytes into the bundled CyberChef instance.
  • Bundles CyberChef (~48 MB added to container image) so the pivot menu's CyberChef lookup works with no internet access.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds Send to CyberChef from a stream's Payload panel, sending exact bytes in Both directions, or just the Source or Dest side — XOR keys, compressed data, and shellcode arrive intact.
  • Adds a Send to CyberChef button in File Info for files Suricata extracted from traffic.
  • Enables pivot-menu access to CyberChef (and other lookups) by selecting any text in an ASCII transcript — base64 blobs, headers, or partial values.
  • Applies CyberChef's Magic operation automatically to small payloads, now including values sent from the pivot menu, to suggest decodings.
+1 more show less
  • Syncs CyberChef's light/dark theme to match the user's chosen SO-CRATES theme unless a CyberChef theme has been set manually.
  • Bundles CyberChef (~48 MB added to container image) so the pivot menu's CyberChef lookup works with no internet access.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds Send to CyberChef from a stream's Payload panel, sending exact bytes in Both directions, or just the Source or Dest side — XOR keys, compressed data, and shellcode arrive intact.
  • Adds a Send to CyberChef button in File Info for files Suricata extracted from traffic.
  • Enables pivot-menu access to CyberChef (and other lookups) by selecting any text in an ASCII transcript — base64 blobs, headers, or partial values.
  • Syncs CyberChef's light/dark theme to match the user's chosen SO-CRATES theme unless a CyberChef theme has been set manually.

1 more in Everything

Was this useful?
◆  Firewalls & Network Defense

Fastly

Sources Blog / feed → Add AI Firewall metrics to Historical Stats and Real-Time Analytics APIs (2026-09-23) Blog Rank Why this rank top features scored 95/55/40, +15 breaking change, +6 runnable example — 84.33 How ranking works →

Fastly expanded its analytics APIs with new AI Firewall and Content Guard/PATPATA personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. metrics, and overhauled Next-Gen WAFWAFA reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. event logging to capture changes from every management surface while deprecating the old event-type taxonomy.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Fastly's edge cloud platform delivers faster, safer, and more scalable sites and apps to customers. Elevate your edge CDN, video delivery, security, and more.

Fastly expanded its analytics APIs with new AI Firewall and Content Guard/PATPATA personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. metrics, and overhauled Next-Gen WAFWAFA reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. event logging to capture changes from every management surface while deprecating the old event-type taxonomy.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 3 FEATURES 3 OF 3 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
Next-Gen WAF changes recorded across all surfaces in event log Not checked yet breaking 95

The Event logs API now records Next-Gen WAF configuration changes made through any surface — the Next-Gen WAF API, the Fastly control panel, the Next-Gen WAF control panel, or Terraform — not just changes made through Fastly.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ The list events API gains filter[event_type] support for all ngwaf.* event types, covering workspaces, rules, lists, custom signals, redactions, virtual patches, thresholds, workspace alerts, header links, rate limited sources, custom dashboards, request reports, and agent keys.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ The legacy security.workspace.create, security.workspace.update, security.workspace.delete, security.redaction.create, security.redaction.update, security.redaction.delete, security.rule.create, security.rule.update, security.rule.delete, security.virtual_patch.create, security.virtual_patch.update, security.virtual_patch.delete, and security.event.update event types are deprecated and no longer recorded — use the ngwaf.* equivalents (e.g. ngwaf.rule.create in place of security.rule.create); existing log entries keep their original event type.

Audit all Next-Gen WAF rule changes across every management surface — API, control panels, and Terraform — by filtering the event log for ngwaf.rule events.
$ curl -s -X GET 'https://api.fastly.com/events?filter[event_type]=ngwaf.rule.create' -H 'Fastly-Key: <your_api_token>'
Review all Next-Gen WAF workspace deletions to detect unauthorised removal of workspaces regardless of which panel or tool made the change.
$ curl -s -X GET 'https://api.fastly.com/events?filter[event_type]=ngwaf.workspace.delete' -H 'Fastly-Key: <your_api_token>'
— Exact endpoint, filter syntax, full deprecated-type list, runnable curl examples. Next-Gen WAF configuration changes now recor…
thinner coverage below
02 02
AI Firewall metrics in analytics APIs Not checked yet new 55

The Historical Stats API and Real-Time Analytics API gain two new metrics, arc_ai_firewall_requests and arc_ai_firewall_blocked, tracking AI Firewall activity within AI Runtime Control.

— Names exact metrics but gives no query example or endpoint. Add AI Firewall metrics to Historical Stats …
03 03
Content Guard and PAT metrics in analytics APIs Not checked yet new 40

Adds ten new metrics to the Historical Stats API and Real-Time Analytics API covering Content Guard challenge and token creation, validation outcomes, and Private Access Token (PAT) challenges issued during rule enforcement.

— Describes scope but omits the actual metric names. Add Content Guard challenge metrics to Histo…
└──▷ BREAKING ON UPGRADE
  • !
    The event types security.workspace.create, security.workspace.update, security.workspace.delete, security.redaction.create, security.redaction.update, security.redaction.delete, security.rule.create, security.rule.update, security.rule.delete, security.virtual_patch.create, security.virtual_patch.update, security.virtual_patch.delete, and security.event.update are deprecated and no longer recorded — use the ngwaf.* equivalents (e.g. ngwaf.rule.create in place of security.rule.create); existing log entries keep their original event type.
Add AI Firewall metrics to Historical Stats and Real-Time Analytics APIs (2026-09-23) Blog Stable

Fastly Historical Stats and Real-Time Analytics APIs gain two new AI Firewall metrics for AI Runtime Control.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Next-Gen WAF configuration changes now recorded in the event log (2026-09-08) Blog Stable

Event logs API now captures Next-Gen WAFWAFA reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. config changes from all sources — API, Fastly panel, NG WAF panel, and Terraform.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT
Audit all Next-Gen WAF rule changes across every management surface — API, control panels, and Terraform — by filtering the event log for ngwaf.rule events.
$ curl -s -X GET 'https://api.fastly.com/events?filter[event_type]=ngwaf.rule.create' -H 'Fastly-Key: <your_api_token>'
Review all Next-Gen WAF workspace deletions to detect unauthorised removal of workspaces regardless of which panel or tool made the change.
$ curl -s -X GET 'https://api.fastly.com/events?filter[event_type]=ngwaf.workspace.delete' -H 'Fastly-Key: <your_api_token>'
  • Adds filter[event_type] support on the list events API for all ngwaf.* event types, covering workspaces, rules, lists, custom signals, redactions, virtual patches, thresholds, workspace alerts, header links, rate limited sources, custom dashboards, request reports, and agent keys.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Not checked yet
  • Extends the Event logs API to record Next-Gen WAF configuration changes made through any surface — the Next-Gen WAF API, the Fastly control panel, the Next-Gen WAF control panel, or Terraform — not just changes made through Fastly.
  • Adds filter[event_type] support on the list events API for all ngwaf.* event types, covering workspaces, rules, lists, custom signals, redactions, virtual patches, thresholds, workspace alerts, header links, rate limited sources, custom dashboards, request reports, and agent keys.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Not checked yet

1 more in Everything

└──▷ BREAKING ON UPGRADE
  • !The event types security.workspace.create, security.workspace.update, security.workspace.delete, security.redaction.create, security.redaction.update, security.redaction.delete, security.rule.create, security.rule.update, security.rule.delete, security.virtual_patch.create, security.virtual_patch.update, security.virtual_patch.delete, and security.event.update are deprecated and no longer recorded — use the ngwaf.* equivalents (e.g. ngwaf.rule.create in place of security.rule.create); existing log entries keep their original event type.
Was this useful?
Cloud & Container Security
◆  CNAPP

Rapid7 InsightCloudSec

Sources Blog / feed →Product docs → changelog · Sep 29, 2026 Docs Blog Rank Why this rank top features scored 75/65/65, +6 runnable example — 74.33 How ranking works →

InsightCloudSec's September 2026 release adds CSV export for container vulnerability findings, two new CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline. database compliance packs for AWS and Azure, two new RDS misconfiguration detections, and small improvements to Layered Context and OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. harvesting.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Rapid7 InsightCloudSec is a cloud security platform that provides visibility, compliance monitoring, and vulnerability management across cloud infrastructures.

InsightCloudSec's September 2026 release adds CSV export for container vulnerability findings, two new CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline. database compliance packs for AWS and Azure, two new RDS misconfiguration detections, and small improvements to Layered Context and OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. harvesting.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 5 FEATURES 0 OF 5 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
CIS database compliance packs for AWS and Azure Not checked yet new 75

Adds CIS AWS Database Services Benchmark v1.0.0 compliance pack covering 22 controls across Aurora, RDS, DynamoDB, ElastiCache, Redshift, DocumentDB, Neptune, and Timestream.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Adds CIS Microsoft Azure Database Services Benchmark v2.0.0 compliance pack covering 47 controls across Azure Cache for Redis, Azure Cosmos DB, Azure Data Factory, Azure Database for MySQL, Azure Database for PostgreSQL, and Azure SQL Database — available for Azure, Azure Gov, and Azure China.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Names both packs, control counts, and covered services 2026-09-29-023b1562
02 00
Container vulnerability CVE CSV export Not checked yet new 65

Exports container vulnerability findings from the Layered Context list view as a CSV file, with one row per container, CVE, and affected package.

Pull a per-container, per-CVE, per-package CSV of all container vulnerability findings for offline triage or ticket import.
📍In InsightCloudSec, open Layered Context, filter to the desired container resources, then select Export › CSV to download one row per container, CVE, and affected package.
— Names export format and row structure, gives UI steps 2026-09-29-023b1562
03 00
Database transit encryption and backup detections Not checked yet new 65

Adds Database Instance Not Enforcing Transit Encryption (AWS) detection identifying Amazon RDS instances that do not enforce SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination./TLS encryption in transit, excluding DocumentDB and Neptune, and Database Instance Without Automatic Backups (AWS) detection identifying Amazon RDS instances with backup retention period of 0, excluding DocumentDB and Neptune.

— Names exact detection conditions and exclusions 2026-09-29-023b1562
thinner coverage below
04 00
Reduced OCI Identity Domains API calls Not checked yet improved 45

Reduces OCI Identity Domains API calls during cloud user harvesting for Oracle Cloud Infrastructure, lowering the risk of rate-limit errors on large tenancies.

— Explains benefit but no user-facing action 2026-09-29-023b1562
05 00
Resource lifecycle state in Layered Context Not checked yet improved 40

Shows each resource's lifecycle state as reported by the cloud provider, along with last harvest time, in Layered Context.

— Brief description, no mechanism beyond display 2026-09-29-023b1562
changelog · Sep 29, 2026 Docs Blog LatestStable

InsightCloudSec 26.9.29 adds CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline. database compliance packs, container CVE CSV export, and richer Layered Context resource state.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Pull a per-container, per-CVE, per-package CSV of all container vulnerability findings for offline triage or ticket import.
📍In InsightCloudSec, open Layered Context, filter to the desired container resources, then select Export › CSV to download one row per container, CVE, and affected package.
  • Exports container vulnerability findings from the Layered Context list view as a CSV file, with one row per container, CVE, and affected package.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds CIS AWS Database Services Benchmark v1.0.0 compliance pack covering 22 controls across Aurora, RDS, DynamoDB, ElastiCache, Redshift, DocumentDB, Neptune, and Timestream.
  • Adds CIS Microsoft Azure Database Services Benchmark v2.0.0 compliance pack covering 47 controls across Azure Cache for Redis, Azure Cosmos DB, Azure Data Factory, Azure Database for MySQL, Azure Database for PostgreSQL, and Azure SQL Database — available for Azure, Azure Gov, and Azure China.
  • Adds Database Instance Not Enforcing Transit Encryption (AWS) detection identifying Amazon RDS instances that do not enforce SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination./TLS encryption in transit, excluding DocumentDB and Neptune.
  • Adds Database Instance Without Automatic Backups (AWS) detection identifying Amazon RDS instances with backup retention period of 0, excluding DocumentDB and Neptune.
+2 more show less
  • Shows each resource's lifecycle state as reported by the cloud provider, along with last harvest time, in Layered Context.
  • Reduces OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. Identity Domains API calls during cloud user harvesting for Oracle Cloud Infrastructure, lowering the risk of rate-limit errors on large tenancies.
  • Exports container vulnerability findings from the Layered Context list view as a CSV file, with one row per container, CVE, and affected package.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds CIS AWS Database Services Benchmark v1.0.0 compliance pack covering 22 controls across Aurora, RDS, DynamoDB, ElastiCache, Redshift, DocumentDB, Neptune, and Timestream.
  • Adds CIS Microsoft Azure Database Services Benchmark v2.0.0 compliance pack covering 47 controls across Azure Cache for Redis, Azure Cosmos DB, Azure Data Factory, Azure Database for MySQL, Azure Database for PostgreSQL, and Azure SQL Database — available for Azure, Azure Gov, and Azure China.
  • Adds Database Instance Not Enforcing Transit Encryption (AWS) detection identifying Amazon RDS instances that do not enforce SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination./TLS encryption in transit, excluding DocumentDB and Neptune.
  • Adds Database Instance Without Automatic Backups (AWS) detection identifying Amazon RDS instances with backup retention period of 0, excluding DocumentDB and Neptune.

2 more in Everything

Was this useful?
◆  Container & Image Security

kubescape

Sources Release notes → v4.0.15 Notes Rank Why this rank top features scored 90/60/60, +6 runnable example — 76 How ranking works →

Kubescape v4.0.15 adds multi-cluster fleet scanning with a combined report and compliance rollup, expands image scanning to Quay and Azure ACR credential chains, adds scan-coverage metrics to report outputs, and speeds up large-cluster processing with a new partition and spill store engine.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Kubescape is an open-source Kubernetes security platform for your IDE, CI/CD pipelines, and clusters. It includes risk analysis, security, compliance, and misconfiguration scanning, saving Kubernetes users and administrators precious time, effort, and resources.

Kubescape v4.0.15 adds multi-cluster fleet scanning with a combined report and compliance rollup, expands image scanning to Quay and Azure ACR credential chains, adds scan-coverage metrics to report outputs, and speeds up large-cluster processing with a new partition and spill store engine.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 11 FEATURES 0 OF 11 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Multi-cluster fleet scanning Not checked yet new 90

The --fleet-report flag on kubescape scan, combined with --kube-contexts to name multiple clusters, writes one unified report across all of them.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ The fleet report includes a compliance rollup, a fleet summary printed after the scan, and reporting of which controls clusters disagree on.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Scan multiple Kubernetes clusters in one pass and write a unified fleet report — useful in multi-tenant or multi-region environments.
$ kubescape scan --kube-contexts prod-us,prod-eu,staging --fleet-report fleet-results.json
— Exact flags plus a runnable multi-cluster command v4.0.15
02 00
Show-evidence fix-path line resolution Not checked yet improved 60

The --show-evidence output now resolves fix-path line numbers for delete and review paths.

— Names the flag and behaviour, no example given v4.0.15
03 00
Config command key filtering and deletion Not checked yet new 60

kubescape config view supports filtering configurations by key, and kubescape config now supports deleting specific configuration keys.

— Two named subcommand capabilities, no usage shown v4.0.15
04 00
Scan coverage metrics and degraded-coverage reporting Not checked yet new 60

Adds scan coverage metrics to Markdown, HTML, and CSV report outputs, and reports degraded scan coverage and skipped controls in printer output.

— Names three report formats but no command shown v4.0.15
05 00
Large-cluster performance improvements Not checked yet improved 60

Introduces a partition and spill store engine for handling large-cluster resources, and uses mmap and fastjson for manifest parsing to improve performance on large manifest sets.

— Names the mechanisms but no benchmark or command v4.0.15
thinner coverage below
06 00
VAP Agent Runtime policy set Not checked yet new 55

kubescape vap gains a complete Agent Runtime policy set.

— Names exact subcommand, scope of policy set unclear v4.0.15
07 00
Key-signed image support without transparency log Not checked yet new 55

Control C-0236 now supports key-signed images that lack a transparency log entry.

— Names exact control ID, no further mechanism detail v4.0.15
08 00
Output-dir support for file-based reports Not checked yet improved 45

The --output-dir flag is now honoured for file-based reports.

— Bare one-line addition naming an exact flag v4.0.15
09 00
Quay and Azure ACR image scanning support Not checked yet new 45

Image scanning now supports Quay vulnerability scanning, and full Azure credential chain support for ACR image pulls.

— Names two registries, no mechanism or flags given v4.0.15
10 00
Namespace filter hot-reload Not checked yet improved 40

Namespace filters in the HTTP handler now hot-reload without requiring a restart.

— Explains behaviour but no config or endpoint named v4.0.15
11 00
OPA whole-cluster execution policies Not checked yet new 40

Adds execution policies for whole-cluster controls in the OPAOPAOpen Policy Agent, a CNCF-graduated policy engine that evaluates rules written in the Rego language against JSON-structured data, letting tools enforce authorization and compliance decisions without hardcoding logic. processor.

— Brief mention of processor change, scope unclear v4.0.15
v4.0.15 Notes LatestStable

Kubescape v4.0.15 adds multi-cluster fleet scanning, Quay image scanning, namespace-filter hot-reload, and scan-coverage metrics in reports.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v4.0.15 https://github.com/kubescape/kubescape.git
# already have the repo? check out this version:
$ git checkout v4.0.15
└──▷ TRY IT
Scan multiple Kubernetes clusters in one pass and write a unified fleet report — useful in multi-tenant or multi-region environments.
$ kubescape scan --kube-contexts prod-us,prod-eu,staging --fleet-report fleet-results.json
  • Adds --fleet-report flag to kubescape scan to write one combined report across multiple clusters specified with --kube-contexts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds --show-evidence output that now resolves fix-path line numbers for delete and review paths.
  • Adds kubescape config view support for filtering configurations by key.
  • Adds support for deleting specific configuration keys via kubescape config.
  • Adds --output-dir support honoured for file-based reports.
+13 more show less
  • Adds Quay vulnerability scanning support for image scans.
  • Adds full Azure credential chain support for ACR image pulls in image scanning.
  • Adds scan coverage metrics to Markdown, HTML, and CSV report outputs.
  • Adds reporting of degraded scan coverage and skipped controls in printer output.
  • Adds compliance rollup to the fleet report.
  • Adds a fleet summary printed after a multi-context scan.
  • Adds reporting of controls that clusters disagree on in fleet scans.
  • Adds hot-reload of namespace filters in the HTTP handler without requiring a restart.
  • Adds complete Agent Runtime policy set to VAP (kubescape vap).
  • Introduces partition and spill store engine for large-cluster resource handling.
  • Uses mmap and fastjson for manifest parsing, improving performance on large manifest sets.
  • Adds support for key-signed images without a transparency log entry in control C-0236.
  • Adds execution policies for whole-cluster controls in the OPAOPAOpen Policy Agent, a CNCF-graduated policy engine that evaluates rules written in the Rego language against JSON-structured data, letting tools enforce authorization and compliance decisions without hardcoding logic. processor.
  • Adds --fleet-report flag to kubescape scan to write one combined report across multiple clusters specified with --kube-contexts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds Quay vulnerability scanning support for image scans.
  • Introduces partition and spill store engine for large-cluster resource handling.
  • Adds execution policies for whole-cluster controls in the OPAOPAOpen Policy Agent, a CNCF-graduated policy engine that evaluates rules written in the Rego language against JSON-structured data, letting tools enforce authorization and compliance decisions without hardcoding logic. processor.

14 more in Everything

Was this useful?

Chainguard

Sources Release page → Week of 2026-09-28 Notes Rank Why this rank top features scored 95/85/60, +15 breaking change, +6 runnable example — 101 How ranking works →

Chainguard provides trusted open source artifacts for every layer of your modern software stack—containers, language libraries, and VM images.

Chainguard shipped a FIPS 140-3FIPS 140-3A US federal standard, maintained by NIST, that defines requirements for cryptographic modules used in government systems. Cyber tools target it to satisfy procurement mandates requiring validated crypto. validated OpenSSL provider with post-quantum key exchangepost-quantum key exchangeA cryptographic handshake algorithm designed to resist attacks from quantum computers, using math problems like lattices that quantum algorithms cannot efficiently solve, letting tools stay secure against future quantum-capable adversaries., opened an invite-only beta for Chainguard Libraries covering Go and .NET, added 19 new container images, and expanded the Agent Skills CLI with new publishing, install and lifecycle flags.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 4 FEATURES 2 OF 4 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Agent Skills CLI flags and lifecycle handling Not checked yet improved 95

The chainctl skills CLI adds --dry-run to the publish command to build and validate an artifact without publishing it; --tag (repeatable, e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ --tag v1.0.0 --tag latest) to publish under one or more explicit tags, warning when omitted that no version was pinned; --copy on the install command to give each agent its own copy of a skill instead of the default shared symlink under .agents/skills/; --yes to non-interactively accept the Agent Skills Terms of Service and Data Privacy Agreement in CI environments; and --parent on entitlements subcommands plus --group on other skills subcommands to target a specific organization. Deleting a skill's last remaining version now also removes the empty skill entry to prevent stale listing output, and skill uninstall accepts a tag-less reference (e.g. "$HARDENED_REPO") only when no versions remain, otherwise an explicit tag is required. Requires chainctl v0.2.364 or later.

Validate a skill artifact locally before publishing — useful in PR CI to catch build errors without creating a registry entry.
$ chainctl skills publish --tag v1.0.0 --dry-run
Publish the same skill artifact under both a pinned version tag and latest so consumers can reference either.
$ chainctl skills publish --tag v1.0.0 --tag latest
— Names every flag with runnable example commands product docs
02 01
FIPS 140-3 validated OpenSSL provider with post-quantum support Not checked yet new 85

Chainguard FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. Provider for OpenSSL v3.6 is FIPS 140-3 validated (Certificate #5523), adding hybrid post-quantumpost-quantumCryptography designed to stay secure against a large quantum computer, which could break today's RSA and elliptic-curve keys. NIST standardized the first algorithms in 2024 as ML-KEM, ML-DSA and SLH-DSA. TLS key exchange via ML-KEMML-KEMNIST's post-quantum key-exchange standard (FIPS 203), formerly Kyber. Two parties use it to agree on a shared secret, usually alongside X25519 in a hybrid TLS handshake. paired with classical algorithms, plus standalone ML-KEM, ML-DSAML-DSANIST's main post-quantum digital signature standard (FIPS 204), formerly Dilithium. It is the planned replacement for RSA and ECDSA signatures on certificates and code., and SLH-DSASLH-DSANIST's hash-based post-quantum signature standard (FIPS 205), formerly SPHINCS+. Its security rests only on hash functions, so it is slower and larger than ML-DSA but a conservative backup. support alongside AES, SHA-2, SHA-3, ECDSA, and RSA. Opt-in is available for Chainguard FIPS container images starting October 1, 2026; note that SHA-1 is not an approved algorithm in the v3.6 FIPS module, so workloads relying on SHA-1 will break if they opt in on or after that date.

— Names cert number and algorithms but no opt-in command shown Week of 2026-09-28
03 00
19 new container images added Not checked yet new 60

Adds 19 new container images this week, including chainguard-server-hypervisor-gcp, kured (+fips), conftest (+fips), foundry, keepalived (+fips), mcp-grafana-fips, nix, ray, vault-secrets-webhook (+fips), argocd-agent, kates (+fips), kubernetes-pause-fips, and victoriatraces (+fips).

— Full image list named but no usage detail beyond naming Week of 2026-09-28
thinner coverage below
04 02
Chainguard Libraries beta for Go and .NET Not checked yet new 45

Chainguard Libraries launches for Go and .NET ecosystems in an invite-only beta, letting accepted organizations pull Go and .NET packages from Chainguard Libraries into existing development workflows.

— Invite-only beta described with no usage steps Week of 2026-09-28
└──▷ BREAKING ON UPGRADE
  • !
    SHA-1SHA-1A cryptographic hash function standardized by NIST that produces a 160-bit digest; tools use it for file integrity checks, though it is now considered cryptographically broken and unsuitable for collision-resistant applications. is not an approved algorithm in the OpenSSL v3.6 FIPS module — workloads relying on SHA-1 will break if they opt in to the v3.6 module on or after October 1, 2026.
Week of 2026-09-28 Notes Stable

Chainguard gains FIPS 140-3FIPS 140-3A US federal standard, maintained by NIST, that defines requirements for cryptographic modules used in government systems. Cyber tools target it to satisfy procurement mandates requiring validated crypto. validation with post-quantumpost-quantumCryptography designed to stay secure against a large quantum computer, which could break today's RSA and elliptic-curve keys. NIST standardized the first algorithms in 2024 as ML-KEM, ML-DSA and SLH-DSA. algorithms, Libraries beta for Go and .NET, and 19 new container images.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. 140-3 validated Chainguard FIPS Provider for OpenSSL v3.6 (Certificate #5523), including hybrid post-quantum TLS key exchange via ML-KEMML-KEMNIST's post-quantum key-exchange standard (FIPS 203), formerly Kyber. Two parties use it to agree on a shared secret, usually alongside X25519 in a hybrid TLS handshake. paired with classical algorithms, plus standalone ML-KEM, ML-DSAML-DSANIST's main post-quantum digital signature standard (FIPS 204), formerly Dilithium. It is the planned replacement for RSA and ECDSA signatures on certificates and code., and SLH-DSASLH-DSANIST's hash-based post-quantum signature standard (FIPS 205), formerly SPHINCS+. Its security rests only on hash functions, so it is slower and larger than ML-DSA but a conservative backup. support alongside AESAESA symmetric block cipher standardized by NIST that encrypts data in 128-bit blocks using 128-, 192-, or 256-bit keys; tools use it because hardware acceleration makes it fast enough for bulk encryption., SHA-2, SHA-3, ECDSA, and RSA; opt-in available for Chainguard FIPS container images starting October 1, 2026.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Launches Chainguard Libraries for Go and .NET ecosystems in an invite-only beta, letting accepted organizations pull Go and .NET packages from Chainguard Libraries into existing development workflows.
  • Adds 19 new container images this week, including chainguard-server-hypervisor-gcp, kured (+fips), conftest (+fips), foundry, keepalived (+fips), mcp-grafana-fips, nix, ray, vault-secrets-webhook (+fips), argocd-agent, kates (+fips), kubernetes-pause-fips, and victoriatraces (+fips).

3 details in Everything

└──▷ BREAKING ON UPGRADE
  • !SHA-1SHA-1A cryptographic hash function standardized by NIST that produces a 160-bit digest; tools use it for file integrity checks, though it is now considered cryptographically broken and unsuitable for collision-resistant applications. is not an approved algorithm in the OpenSSL v3.6 FIPS module — workloads relying on SHA-1 will break if they opt in to the v3.6 module on or after October 1, 2026.
Was this useful?

Anchore

Sources Blog / feed → FedRAMP & CMMC in 2026: what actually changed for your Authority to Operate (ATO) (2026-09-22) Blog Rank Why this rank top features scored 87/52/49, +6 runnable example — 68.67 How ranking works →

Anchore's software supply chain solutions automate vulnerability scanning, strengthen container security, and support compliance with NIST, FedRAMP & more.

Anchore's policy bundle v2026.1 adds a CISA KEVCISA KEVA catalog maintained by the US Cybersecurity and Infrastructure Security Agency listing vulnerabilities confirmed to be actively exploited in the wild, giving cyber tools a vetted, authoritative prioritization signal.-mapped STOP gate with per-control failure detail, folds KEV and EPSSEPSSExploit Prediction Scoring System, an estimate of the probability that a published vulnerability will be exploited in the next 30 days. It helps prioritize investigation and patching. scoring into risk-based prioritization, adds POA&MPOA&MA Plan of Action and Milestones: a US federal government document that tracks known security weaknesses in a system, the remediation steps planned, and the deadlines for completing them, required under FISMA compliance.-style time-bound allowlisting, and extends policy enforcement from build time into live Kubernetes clusters.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 4 FEATURES 1 OF 4 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
STOP gate for CISA KEV vulnerabilities with per-control detail Not checked yet new 87

Policy bundle v2026.1 adds a dedicated STOP gate for CISA KEVKEVCISA's Known Exploited Vulnerabilities catalog, a list of vulnerabilities with evidence of exploitation in real attacks. It helps teams prioritize fixes for problems attackers already use.-listed vulnerabilities mapped to NIST 800-53NIST 800-53A catalog of security and privacy controls for U.S. federal information systems, published by NIST. Cyber tools cite it to map their findings or features to a recognized compliance framework. SI-2.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Running anchorectl image check <image> --detail -f surfaces per-control failure detail, returning the specific control and finding that failed rather than a pass/fail count, so assessors can trace results back to a named requirement.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Fail a CI/CD build immediately on any CISA KEV-listed vulnerability and get the specific NIST control and finding — not just a pass/fail — so the result is directly traceable for an ATO assessor.
$ anchorectl image check <image> --detail -f
— Names the gate, control mapping, and exact command with flags FedRAMP & CMMC in 2026: what actually change…
thinner coverage below
02 00
Runtime policy enforcement in Kubernetes via admission controller Not checked yet new 52

Extends policy enforcement from build time into live Kubernetes clusters via a runtime inventory and admission controller that blocks non-compliant workloads before scheduling.

— States mechanism and scope but no setup steps given FedRAMP & CMMC in 2026: what actually change…
03 00
POA&M enforcement with time-bound allowlists Not checked yet new 49

Supports POA&M enforcement through policies, gates, and time-bound allowlists, letting a non-compliant finding be allowlisted with an explicit remediation date rather than silently ignored or blocking all builds.

— Describes mechanism but no concrete config key or command FedRAMP & CMMC in 2026: what actually change…
04 00
KEV and EPSS scoring in policy engine Not checked yet new 46

Incorporates CISA's Known Exploited VulnerabilitiesKnown Exploited VulnerabilitiesCISA's Known Exploited Vulnerabilities catalog, a list of vulnerabilities with evidence of exploitation in real attacks. It helps teams prioritize fixes for problems attackers already use. (KEV) list and EPSS exploit prediction scores alongside CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. in the policy engine, enabling risk-based vulnerability prioritization.

— Names data sources but no config or command shown FedRAMP & CMMC in 2026: what actually change…
FedRAMP & CMMC in 2026: what actually changed for your Authority to Operate (ATO) (2026-09-22) Blog LatestStable

Anchore Enterprise policy bundle v2026.1 adds a dedicated STOP gate for CISA KEVCISA KEVA catalog maintained by the US Cybersecurity and Infrastructure Security Agency listing vulnerabilities confirmed to be actively exploited in the wild, giving cyber tools a vetted, authoritative prioritization signal.-listed vulnerabilities mapped to NIST 800-53NIST 800-53A catalog of security and privacy controls for U.S. federal information systems, published by NIST. Cyber tools cite it to map their findings or features to a recognized compliance framework. SI-2.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT
Fail a CI/CD build immediately on any CISA KEVKEVCISA's Known Exploited Vulnerabilities catalog, a list of vulnerabilities with evidence of exploitation in real attacks. It helps teams prioritize fixes for problems attackers already use.-listed vulnerability and get the specific NIST control and finding — not just a pass/fail — so the result is directly traceable for an ATO assessor.
$ anchorectl image check <image> --detail -f
  • Surfaces per-control failure detail via anchorectl image check <image> --detail -f, returning the specific control and finding that failed rather than a pass/fail count, enabling assessors to trace results to a named requirement.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Incorporates CISA's Known Exploited VulnerabilitiesKnown Exploited VulnerabilitiesCISA's Known Exploited Vulnerabilities catalog, a list of vulnerabilities with evidence of exploitation in real attacks. It helps teams prioritize fixes for problems attackers already use. (KEV) list and EPSSEPSSExploit Prediction Scoring System, an estimate of the probability that a published vulnerability will be exploited in the next 30 days. It helps prioritize investigation and patching. exploit prediction scores alongside CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. in the policy engine for risk-based vulnerability prioritization. Not checked yet
  • Supports POA&MPOA&MA Plan of Action and Milestones: a US federal government document that tracks known security weaknesses in a system, the remediation steps planned, and the deadlines for completing them, required under FISMA compliance. enforcement through policies, gates, and time-bound allowlists, letting a non-compliant finding be allowlisted with an explicit remediation date rather than silently ignored or blocking all builds.
  • Extends policy enforcement from build time into live Kubernetes clusters via a runtime inventory and admission controller that blocks non-compliant workloads before scheduling.
  • Surfaces per-control failure detail via anchorectl image check <image> --detail -f, returning the specific control and finding that failed rather than a pass/fail count, enabling assessors to trace results to a named requirement.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Supports POA&MPOA&MA Plan of Action and Milestones: a US federal government document that tracks known security weaknesses in a system, the remediation steps planned, and the deadlines for completing them, required under FISMA compliance. enforcement through policies, gates, and time-bound allowlists, letting a non-compliant finding be allowlisted with an explicit remediation date rather than silently ignored or blocking all builds.
  • Extends policy enforcement from build time into live Kubernetes clusters via a runtime inventory and admission controller that blocks non-compliant workloads before scheduling.

1 more in Everything

Was this useful?

Snyk Container

Sources Blog / feed → changelog · Sep 16, 2026 Blog Rank Why this rank top features scored 78, +15 breaking change — 93 How ranking works →

Snyk Container now detects and reports vulnerabilities in the Go standard library itself, automatically surfacing them as a new dependency in scan results.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Snyk Container scans Docker images and container registries for vulnerabilities, misconfigurations, and malware to secure containerized applications.

Snyk Container now detects and reports vulnerabilities in the Go standard library itself, automatically surfacing them as a new dependency in scan results.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 1 FEATURE 0 OF 1 FEATURE most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Go standard library vulnerability reporting Not checked yet new 78

Snyk Container scans now identify the Go standard library version a binary was compiled with and surface known CVEs against it, shown as a stdlib@<version> dependency (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ stdlib@1.25.10) in the dependency graph.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ It works across standard, stripped, and CGo builds, is enabled automatically for all organizations with no configuration required, and CLI-based container scans require Snyk CLI v1.1303.2 or later. As a result, vulnerability counts will increase for container image projects built from Go binaries on or after October 7, 2026, except those built with Go 1.25.13+ or Go 1.26.6+.

— Names format, versions, CLI requirement, and rollout impact date. 2026-09-16-523bbbee
└──▷ BREAKING ON UPGRADE
  • !
    Vulnerability counts will increase for all container image projects built from Go binaries on or after October 7, 2026: each affected project gains new findings determined by the Go version the binary was compiled with. Images built with Go 1.25.13+ or Go 1.26.6+ report no new findings from this change.
changelog · Sep 16, 2026 Blog LatestStable

Snyk Container now reports Go standard library vulnerabilities in container images, shown as a stdlib@<version> dependency.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds Go standard library vulnerability reporting for container images: scans identify the stdlib version the binary was compiled with and surface known CVEs against it, shown as stdlib@<version> (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ stdlib@1.25.10) in the dependency graph — enabled automatically for all organizations with no configuration required. Not checked yet
  • Supports Go standard library detection across standard, stripped, and CGo builds. Not checked yet
  • Requires Snyk CLI v1.1303.2 or later for standard library reporting in CLI-based container scans. Not checked yet
  • Adds Go standard library vulnerability reporting for container images: scans identify the stdlib version the binary was compiled with and surface known CVEs against it, shown as stdlib@<version> (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ stdlib@1.25.10) in the dependency graph — enabled automatically for all organizations with no configuration required. Not checked yet
  • Supports Go standard library detection across standard, stripped, and CGo builds. Not checked yet

1 more in Everything

└──▷ BREAKING ON UPGRADE
  • !Vulnerability counts will increase for all container image projects built from Go binaries on or after October 7, 2026: each affected project gains new findings determined by the Go version the binary was compiled with. Images built with Go 1.25.13+ or Go 1.26.6+ report no new findings from this change.
Was this useful?
◆  Cloud Security Posture

Prowler

Sources Release notes →Source code → 5.44.0 Notes Code Rank Why this rank top features scored 95/80/75, +6 runnable example — 89.33 How ranking works →

Prowler 5.44.0 adds targeted partial re-scans of specific resources across the API, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tools and UI, plus S3-compatibleS3-compatibleAn object-storage API that mirrors Amazon S3's HTTP interface, so any client or cyber tool written for AWS S3 works unchanged against any compliant storage backend. output storage and configurable AWS retry behavior.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Prowler is the world’s most widely used open-source cloud security platform that automates security and compliance across any cloud environment.

Prowler 5.44.0 adds targeted partial re-scans of specific resources across the API, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tools and UI, plus S3-compatibleS3-compatibleAn object-storage API that mirrors Amazon S3's HTTP interface, so any client or cyber tool written for AWS S3 works unchanged against any compliant storage backend. output storage and configurable AWS retry behavior.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 5 FEATURES 0 OF 5 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Partial resource re-checks via API, MCP and UI Not checked yet new 95

Adds POST /api/v1/scans support for resource_uids (up to 10 resources) to launch partial scans, with is_partial exposed on scan objects and a filter[is_partial] query parameter on scan list endpoints.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ The same capability is exposed through the prowler_trigger_scan MCP tool's resource_uids argument, with is_partial shown on prowler_list_scans and prowler_get_scan and an is_partial filter on prowler_list_scans. A new Re-check resource action in the Findings page actions menu and resource detail drawer launches a partial scan that re-runs only the checks that last reported on that resource.

Immediately re-check up to 10 specific resources after a remediation, without waiting for the next full scan.
$ curl -X POST https://<your-prowler-api>/api/v1/scans \
  -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' \
  -d '{"resource_uids": ["arn:aws:s3:::my-bucket", "arn:aws:ec2:us-east-1:123456789012:instance/i-0abc123"]}'
— Names endpoint, fields, filter, MCP tool and UI action verbatim. 5.44.0
02 00
S3-compatible storage for scan output Not checked yet new 80

Adds DJANGO_OUTPUT_S3_AWS_ENDPOINT_URL environment variable to direct scan output uploads and downloads at S3-compatible object storage such as MinIO, without polluting process-wide AWS environment variables.

Point a self-hosted Prowler deployment at MinIO (or another S3-compatible store) for scan report storage without affecting AWS provider role assumptions.
ini
DJANGO_OUTPUT_S3_AWS_ENDPOINT_URL=http://minio.internal:9000
— Exact env var and config example given. 5.44.0
03 00
Configurable Boto3 retry attempts for AWS provider Not checked yet new 75

Adds PROWLER_AWS_BOTO3_RETRIES_MAX_ATTEMPTS environment variable to control Boto3Boto3The official AWS SDK for Python, maintained by Amazon, that gives tools programmatic access to AWS services like S3, EC2, and IAM through a clean Python API. retry attempts for the AWS provider; set to 0 to disable retries entirely.

Cap Boto3 retries for the AWS provider in environments where unreachable partition endpoints cause long delays during connection tests.
ini
PROWLER_AWS_BOTO3_RETRIES_MAX_ATTEMPTS=3
— Exact env var, default behavior and disable value named. 5.44.0
thinner coverage below
04 00
Simplified AWS account connection wizard Not checked yet improved 55

Connects AWS accounts in a single wizard step: the account ID is read from the role ARN (or typed for static access keys), the role is assumed, and credentials are stored and tested in one submit.

— Describes flow mechanism but no exact UI path or endpoint. 5.44.0
05 00
Unified latest-scan resolution across endpoints Not checked yet improved 35

Unifies latest-scan resolution across all endpoints so findings, compliance, and mute rules always read from the same scan for a given provider.

— No named endpoints or config; thin prose description. 5.44.0
5.44.0 Notes Code LatestStable

Prowler 5.44.0 adds partial resource re-checks, S3-compatibleS3-compatibleAn object-storage API that mirrors Amazon S3's HTTP interface, so any client or cyber tool written for AWS S3 works unchanged against any compliant storage backend. storage via DJANGO_OUTPUT_S3_AWS_ENDPOINT_URL, and PROWLER_AWS_BOTO3_RETRIES_MAX_ATTEMPTS for retry control.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch 5.44.0 https://github.com/prowler-cloud/prowler.git
# already have the repo? check out this version:
$ git checkout 5.44.0
└──▷ TRY IT
Immediately re-check up to 10 specific resources after a remediation, without waiting for the next full scan.
$ curl -X POST https://<your-prowler-api>/api/v1/scans \
  -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' \
  -d '{"resource_uids": ["arn:aws:s3:::my-bucket", "arn:aws:ec2:us-east-1:123456789012:instance/i-0abc123"]}'
Point a self-hosted Prowler deployment at MinIO (or another S3-compatible store) for scan report storage without affecting AWS provider role assumptions.
.env
DJANGO_OUTPUT_S3_AWS_ENDPOINT_URL=http://minio.internal:9000
Cap Boto3Boto3The official AWS SDK for Python, maintained by Amazon, that gives tools programmatic access to AWS services like S3, EC2, and IAM through a clean Python API. retries for the AWS provider in environments where unreachable partition endpoints cause long delays during connection tests.
.env
PROWLER_AWS_BOTO3_RETRIES_MAX_ATTEMPTS=3
  • Adds POST /api/v1/scans support for resource_uids (up to 10 resources) to launch partial scans, with is_partial exposed on scan objects and a filter[is_partial] query parameter on scan list endpoints.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds DJANGO_OUTPUT_S3_AWS_ENDPOINT_URL environment variable to direct scan output uploads and downloads at S3-compatible object storage such as MinIO, without polluting process-wide AWS environment variables.
  • Adds PROWLER_AWS_BOTO3_RETRIES_MAX_ATTEMPTS environment variable to control Boto3 retry attempts for the AWS provider; set to 0 to disable retries entirely.
  • Adds prowler_trigger_scan MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tool support for a resource_uids argument to launch partial scans, and exposes is_partial on prowler_list_scans and prowler_get_scan with an is_partial filter on prowler_list_scans.
  • Adds a Re-check resource action in the Findings page actions menu and resource detail drawer, launching a partial scan that re-runs only the checks that last reported on that resource.
+2 more show less
  • Connects AWS accounts in a single wizard step: the account ID is read from the role ARN (or typed for static access keys), the role is assumed, and credentials are stored and tested in one submit.
  • Unifies latest-scan resolution across all endpoints so findings, compliance, and mute rules always read from the same scan for a given provider.
  • Adds POST /api/v1/scans support for resource_uids (up to 10 resources) to launch partial scans, with is_partial exposed on scan objects and a filter[is_partial] query parameter on scan list endpoints.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds DJANGO_OUTPUT_S3_AWS_ENDPOINT_URL environment variable to direct scan output uploads and downloads at S3-compatible object storage such as MinIO, without polluting process-wide AWS environment variables.
  • Adds PROWLER_AWS_BOTO3_RETRIES_MAX_ATTEMPTS environment variable to control Boto3 retry attempts for the AWS provider; set to 0 to disable retries entirely.
  • Adds a Re-check resource action in the Findings page actions menu and resource detail drawer, launching a partial scan that re-runs only the checks that last reported on that resource.

3 more in Everything

Was this useful?
Detection & Response
◆  SIEM

Sumo Logic

Sources Blog / feed → Amazon Security Lake (Apps) (2026-09-29) Blog Rank Why this rank top features scored 45 — 45 How ranking works →

Sumo Logic is a cloud-based platform for log management, monitoring, and security analytics of applications and infrastructure.

Sumo Logic added a new app for Amazon Security Lake, giving unified AWS security visibility through OCSFOCSFAn open schema standard, maintained by the OCSF community under CISA and industry backing, that defines a common event format so cyber tools can share and ingest log data without per-source normalization work.-normalized events and pre-built dashboards.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 1 FEATURE 0 OF 1 FEATURE most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Amazon Security Lake app Not checked yet new 45

A new Sumo Logic app for Amazon Security Lake provides unified visibility into AWS security activity across accounts and regions using OCSF-normalized events, with pre-built dashboards covering network, identity, application, and host activity to detect threats, investigate anomalies, and assess AWS security posture.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Describes scope and dashboards but no setup steps or config details. Amazon Security Lake (Apps) (2026-09-29)
Amazon Security Lake (Apps) (2026-09-29) Blog LatestStable

New Sumo Logic app for Amazon Security Lake delivers unified AWS security visibility via OCSFOCSFAn open schema standard, maintained by the OCSF community under CISA and industry backing, that defines a common event format so cyber tools can share and ingest log data without per-source normalization work.-normalized events and pre-built dashboards.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds a new Sumo Logic app for Amazon Security Lake that provides unified visibility into AWS security activity across accounts and regions using OCSF-normalized events.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Includes pre-built dashboards covering network, identity, application, and host activity to detect threats, investigate anomalies, and assess AWS security posture. Not checked yet

2 details in Everything

Was this useful?

Databricks

Sources Blog / feed → 1Password Event Logs connector (Beta) (2026-09-28) Blog Stable Rank Why this rank top features scored 70/65/55, +6 runnable example — 69.33 How ranking works →

Databricks is a unified analytics platform for data engineering, data science, and machine learning built on Apache Spark.

Lakeflow Connect gains a 1Password Event Logs connector Beta; workspace admins control access via the Previews page.

  • New integrationAdds a 1Password Event Logs connector in Lakeflow Connect Beta, ingesting audit events, item usages, and sign-in attempts from the 1Password Events API into Databricks using an Events Reporting bearer tokenbearer tokenA credential that grants access to whoever presents it, without a separate proof of possession. Protecting the token matters because a stolen copy can be used by someone else.. Not checked yet
  • Workspace admins can enable or disable the 1Password Event Logs connector from the Previews page. Not checked yet

2 details in Everything

4 more releases in this issue · 2026-09-24 → 2026-09-28
Microsoft 365 Unified Audit Logs connector is available in Beta (2026-09-28) Blog Stable

Databricks Lakeflow Connect adds a managed Microsoft 365 Unified Audit Logs connector Beta using OAuth machine-to-machine auth with incremental ingestion.

Workday Activity Logging connector (Beta) (2026-09-28) Blog LatestStable

Databricks Lakeflow Connect introduces a Beta Workday Activity Logging connector that incrementally ingests Workday user activity log events using OAuth refresh tokensrefresh tokensA credential used to obtain a new access token without signing in again. It is sent to the authorization service rather than used directly to call the protected API..

Usage tracking adds session metadata and token details (Public Preview) (2026-09-27) Blog Stable

system.ai_gateway.usage gains coding-agent session metadata, invocation source, prompt-cache token fields, and search counts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds token-detail fields to system.ai_gateway.usage capturing tokens written to the 5-minute and 1-hour prompt caches, plus file and web search counts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

1 detail in Everything

ai_search can search Lakebase synced tables (Beta) (2026-09-24) Blog Stable

ai_search now supports Lakebase synced tables via a new lakebase_search knowledge source, combinable with vector_search in one call Beta.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Was this useful?
◆  Endpoint Security (EDR/XDR)

Eclypsium

Sources Blog / feed → Safe AI Agents Start With Trusted AI Infrastructure (2026-09-28) Blog Rank Why this rank top features scored 60/55, +10 product media — 67.5 How ranking works →

Eclypsium’s infrastructure assurance platform protects mission critical hardware and detects compromised devices in enterprises and government agencies.

Eclypsium launched AI Infrastructure Assurance, joining NVIDIA's Open Agent Safety Platform to extend hardware and firmware integrity monitoring to the GPUsGPUsA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference., DPUsDPUsData Processing Units are purpose-built network processors that offload packet parsing, encryption, and telemetry from the host CPU, letting cyber tools run inspection pipelines at wire speed without taxing application cores., BMCs and other components underpinning AI agent workloads.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
NVIDIA Open Agent Safety Platform integration Not checked yet new 60

Integrates with NVIDIA's Open Agent Safety Platform to extend Eclypsium's firmware integrity verification and vulnerability identification to the infrastructure underpinning NVIDIA OpenShell and NVIDIA Sentry enforcement boundaries.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Continuously monitors AI infrastructure components for integrity drift, unauthorized firmware modifications, and persistent compromise throughout the device lifecycle, and provides component-level evidence — including known-good baseline comparisons and supply-chain risk — to inform decisions about when agent workloads are permitted to run.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Explains mechanism and lifecycle but no concrete config or command Safe AI Agents Start With Trusted AI Infrast…
thinner coverage below
02 00
AI Infrastructure Assurance coverage for AI hardware Not checked yet new 55

Adds AI Infrastructure Assurance coverage that inventories hardware, firmware, and OS code across AI-specific components — GPUs, DPUs (including NVIDIA BlueField-4), TPUs, BMCs, NICsNICsA network interface card or adapter, the hardware that connects a computer to a network. It sends and receives packets over the link., HBM, SSDs, TPMs, and accelerators.

— Names many components but no command or UI path Safe AI Agents Start With Trusted AI Infrast…
Safe AI Agents Start With Trusted AI Infrastructure (2026-09-28) Blog LatestStable

Eclypsium joins NVIDIA's Open Agent Safety Platform to extend hardware/firmware assurance to AI agent infrastructure including GPUsGPUsA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference., DPUsDPUsData Processing Units are purpose-built network processors that offload packet parsing, encryption, and telemetry from the host CPU, letting cyber tools run inspection pipelines at wire speed without taxing application cores., and BMCs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds AI Infrastructure Assurance coverage for AI-specific components — GPUs, DPUs (including NVIDIA BlueField-4), TPUs, BMCs, NICsNICsA network interface card or adapter, the hardware that connects a computer to a network. It sends and receives packets over the link., HBM, SSDs, TPMs, and accelerators — inventorying hardware, firmware, and OS code across all of them.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Integrates with NVIDIA Open Agent Safety Platform to extend Eclypsium's firmware integrity verification and vulnerability identification to the infrastructure underpinning NVIDIA OpenShell and NVIDIA Sentry enforcement boundaries.
  • Continuously monitors AI infrastructure components for integrity drift, unauthorized firmware modifications, and persistent compromise throughout the device lifecycle — not just at deployment time.
  • Provides component-level evidence of device and firmware posture — including known-good baseline comparisons and supply-chain risk — to inform decisions about when agent workloads are permitted to run. Not checked yet
  • Adds AI Infrastructure Assurance coverage for AI-specific components — GPUs, DPUs (including NVIDIA BlueField-4), TPUs, BMCs, NICsNICsA network interface card or adapter, the hardware that connects a computer to a network. It sends and receives packets over the link., HBM, SSDs, TPMs, and accelerators — inventorying hardware, firmware, and OS code across all of them.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Integrates with NVIDIA Open Agent Safety Platform to extend Eclypsium's firmware integrity verification and vulnerability identification to the infrastructure underpinning NVIDIA OpenShell and NVIDIA Sentry enforcement boundaries.

2 more in Everything

Was this useful?

Trend Vision One

Sources Blog / feed → Scan streaming, cookie-authenticated, and plain-text custom AI endpoints in AI Scanner (2026-09-28) Blog Rank Why this rank top features scored 95/75/65, +6 runnable example — 84.33 How ranking works →

Trend Vision One expanded AI Scanner to handle streaming, cookie-authenticated, and plain-text custom AI endpoints, rolled out ZTSAZTSAZero Trust Security Architecture: a network access model where no user or device is trusted by default, requiring continuous verification before granting access, letting cyber tools enforce least-privilege policies across any environment. module improvements for Android/ChromeOS, and moved Agentless Vulnerability & Threat Detection on Azure to the Flex Consumption Plan while adding China region coverage and tighter transport security.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Trend Vision One is Trend Micro's cloud-based XDR platform providing unified security visibility and threat detection across endpoints, networks, and cloud environments.

Trend Vision One expanded AI Scanner to handle streaming, cookie-authenticated, and plain-text custom AI endpoints, rolled out ZTSAZTSAZero Trust Security Architecture: a network access model where no user or device is trusted by default, requiring continuous verification before granting access, letting cyber tools enforce least-privilege policies across any environment. module improvements for Android/ChromeOS, and moved Agentless Vulnerability & Threat Detection on Azure to the Flex Consumption Plan while adding China region coverage and tighter transport security.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 6 FEATURES 1 OF 6 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
Streaming, cookie auth, and plain-text support for custom AI endpoints Not checked yet new 95

AI Scanner adds a stream option for custom targets so it can scan endpoints returning incremental responses (SSESSEServer-Sent Events, a browser API and HTTP-based protocol where a server pushes a stream of text events to a client over a single long-lived connection, giving tools a lightweight alternative to WebSockets for one-way real-time updates. or streamed text chunks); in JSON streaming mode it applies the response template to each frame as a delta path (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ choices[0].delta.content) and concatenates content in arrival order, while text streaming mode reads and joins raw bytes until the stream ends.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ It also adds cookie as a supported auth_type value, reading credentials from api_key_env and sending them in the cookie header, and adds text as a supported response_format value that treats the whole response body as raw text (requiring the {{response}} marker in the response template); plain-text handling works with both buffered and streaming endpoints and can be combined with cookie auth or streaming.

Scan a cookie-authenticated, streaming chat endpoint that returns plain-text chunks — combining all three new capabilities in one custom target config.
yaml
auth_type: cookie
api_key_env: SESSION_COOKIE
stream: true
response_format: text
response_template: '{{response}}'
Scan a streaming JSON endpoint (e.g. an OpenAI-compatible API) by enabling the stream option and pointing the delta path at the incremental content field.
yaml
stream: true
response_format: json
response_template: 'choices[0].delta.content'
— Names exact config keys, values and runnable example configs Scan streaming, cookie-authenticated, and pl…
02 00
China region support for Agentless V&TD Not checked yet new 75

Adds China East 2, China North 2, and China North 3 region support for Agentless Vulnerability & Threat Detection and VNetVNetA private, isolated network hosted inside Microsoft Azure that lets virtual machines and services communicate with each other and with the internet under user-defined IP ranges and routing rules. Flow Logs, including vulnerability and malware scanning for Azure Virtual Machines, Disks, Azure Container Registry images, and Azure Function Apps, plus VNet Flow Logs collection and forwarding to TrendAI Vision One.

— Names exact regions and covered Azure resource types Agentless Vulnerability & Threat Detection v…
03 00
Azure Flex Consumption Plan migration for Agentless V&TD Not checked yet improved 65

Agentless Vulnerability & Threat Detection and VNet Flow Logs are migrated from the Y1 Consumption Plan to the Flex Consumption Plan for non-China Azure regions, ahead of the Y1 plan's retirement on September 30, 2028.

— Clear before/after and deadline, but no user action required Agentless Vulnerability & Threat Detection v…
thinner coverage below
04 00
HTTPS-only enforcement for Agentless V&TD Function Apps Not checked yet breaking 50

Enforces https_only on Azure Agentless Vulnerability & Threat Detection and VNet Flow Logs Function Apps to strengthen transport security.

— Names the exact config flag but not migration steps Agentless Vulnerability & Threat Detection v…
05 00
ZTSA module updates for Android/ChromeOS Not checked yet improved 45

The Zero Trust Secure Access Module for Android/ChromeOS (v2.0.0.1651) adds support for using an MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.-provided phone number as fallback device information, adds policy support for managing notification and storage permissions on devices, and improves ZTNAZTNAZero Trust Network Access, a framework that grants users access to specific applications only after continuously verifying identity and device posture, replacing broad VPN-style network access with least-privilege connections. session stability/connection resilience along with PACPACA Proxy Auto-Configuration file, a JavaScript snippet a browser or OS fetches to decide which proxy server to route each request through, letting cyber tools intercept or redirect traffic without per-app configuration. and SWGSWGA Secure Web Gateway is a network proxy that inspects outbound web traffic, enforcing policy by blocking malicious sites, filtering content, and decrypting TLS — giving cyber tools a choke point for all user HTTP/S sessions. traffic routing.

— Lists what changed but no config, flag, or metric given Zero Trust Secure Access Module for Android/…
06 00
Expanded Azure region coverage for Agentless V&TD Not checked yet new 15

Expands region support for Agentless Vulnerability & Threat Detection and VNet Flow Logs on Azure subscriptions beyond the newly added China regions.

— No specific regions or scope named Agentless Vulnerability & Threat Detection v…
Scan streaming, cookie-authenticated, and plain-text custom AI endpoints in AI Scanner (2026-09-28) Blog Stable

AI Scanner adds streaming, session-cookie auth, and plain-text response support for custom AI endpoints⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ USE IT
Scan a cookie-authenticated, streaming chat endpoint that returns plain-text chunks — combining all three new capabilities in one custom target config.
yaml
auth_type: cookie
api_key_env: SESSION_COOKIE
stream: true
response_format: text
response_template: '{{response}}'
Scan a streaming JSON endpoint (e.g. an OpenAI-compatible API) by enabling the stream option and pointing the delta path at the incremental content field.
yaml
stream: true
response_format: json
response_template: 'choices[0].delta.content'
  • Adds stream option for custom AI Scanner targets to scan endpoints that return incremental responses (SSESSEServer-Sent Events, a browser API and HTTP-based protocol where a server pushes a stream of text events to a client over a single long-lived connection, giving tools a lightweight alternative to WebSockets for one-way real-time updates. or streamed text chunks), enabling coverage of chat-style APIs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • In JSON streaming mode, AI Scanner applies an existing response template to each SSE/streamed frame as a delta path (e.g. choices[0].delta.content) and concatenates extracted content in arrival order.
  • In text streaming mode, AI Scanner reads raw response bytes and joins them until the stream ends.
  • Adds cookie as a supported value for auth_type, allowing AI Scanner to authenticate against endpoints that require a browser or application session; credentials are read from api_key_env and sent in the cookie request header.
  • Adds text as a supported value for response_format, causing AI Scanner to treat the entire response body as raw text; response templates must include the {{response}} marker to insert the returned text into the response envelope.
+1 more show less
  • Plain-text response handling works with both buffered and streaming endpoints, and can be combined with cookie auth or the stream option.
  • Adds stream option for custom AI Scanner targets to scan endpoints that return incremental responses (SSESSEServer-Sent Events, a browser API and HTTP-based protocol where a server pushes a stream of text events to a client over a single long-lived connection, giving tools a lightweight alternative to WebSockets for one-way real-time updates. or streamed text chunks), enabling coverage of chat-style APIs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • In text streaming mode, AI Scanner reads raw response bytes and joins them until the stream ends.
  • Adds cookie as a supported value for auth_type, allowing AI Scanner to authenticate against endpoints that require a browser or application session; credentials are read from api_key_env and sent in the cookie request header.
  • Adds text as a supported value for response_format, causing AI Scanner to treat the entire response body as raw text; response templates must include the {{response}} marker to insert the returned text into the response envelope.

2 more in Everything

Zero Trust Secure Access Module for Android/ChromeOS version 2.0.0.1651 (2026-09-28) Blog LatestStable

ZTSAZTSAZero Trust Security Architecture: a network access model where no user or device is trusted by default, requiring continuous verification before granting access, letting cyber tools enforce least-privilege policies across any environment. Module for Android/ChromeOS 2.0.0.1651 adds MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. phone-number fallback and new permission policy controls.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds support for using an MDM-provided phone number as fallback device information.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds policy support for managing notification and storage permissions on Android/ChromeOS devices.
  • Improves ZTNAZTNAZero Trust Network Access, a framework that grants users access to specific applications only after continuously verifying identity and device posture, replacing broad VPN-style network access with least-privilege connections. session stability and connection resilience.
  • Improves PACPACA Proxy Auto-Configuration file, a JavaScript snippet a browser or OS fetches to decide which proxy server to route each request through, letting cyber tools intercept or redirect traffic without per-app configuration. and SWGSWGA Secure Web Gateway is a network proxy that inspects outbound web traffic, enforcing policy by blocking malicious sites, filtering content, and decrypting TLS — giving cyber tools a choke point for all user HTTP/S sessions. traffic routing.
  • Adds support for using an MDM-provided phone number as fallback device information.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds policy support for managing notification and storage permissions on Android/ChromeOS devices.

2 more in Everything

Agentless Vulnerability & Threat Detection version 1.206.09221355 (2026-09-25) Blog Stable

Agentless V&TD for Azure gains Flex Consumption Plan migration, China region support, and expanded regional coverage.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Migrates Agentless Vulnerability & Threat Detection and VNetVNetA private, isolated network hosted inside Microsoft Azure that lets virtual machines and services communicate with each other and with the internet under user-defined IP ranges and routing rules. Flow Logs from the Y1 Consumption Plan to the Flex Consumption Plan for non-China Azure regions, ahead of the Y1 plan retirement on September 30, 2028.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Not checked yet
  • Adds China region support (China East 2, China North 2, China North 3) for Agentless Vulnerability & Threat Detection and VNet Flow Logs, including vulnerability and malware scanning for Azure Virtual Machines, Disks, Azure Container Registry images, and Azure Function Apps, plus VNet Flow Logs collection and forwarding to TrendAI Vision One. Not checked yet
  • Expands region support for Agentless Vulnerability & Threat Detection and VNet Flow Logs on Azure subscriptions. Not checked yet
  • Enforces https_only on Azure Agentless Vulnerability & Threat Detection and VNet Flow Logs Function Apps to strengthen transport security. Not checked yet
  • Migrates Agentless Vulnerability & Threat Detection and VNetVNetA private, isolated network hosted inside Microsoft Azure that lets virtual machines and services communicate with each other and with the internet under user-defined IP ranges and routing rules. Flow Logs from the Y1 Consumption Plan to the Flex Consumption Plan for non-China Azure regions, ahead of the Y1 plan retirement on September 30, 2028.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Not checked yet
  • Adds China region support (China East 2, China North 2, China North 3) for Agentless Vulnerability & Threat Detection and VNet Flow Logs, including vulnerability and malware scanning for Azure Virtual Machines, Disks, Azure Container Registry images, and Azure Function Apps, plus VNet Flow Logs collection and forwarding to TrendAI Vision One. Not checked yet

2 more in Everything

Was this useful?

Iru

Sources Release page → What's New in Iru | September 25th Notes Stable Rank Why this rank top features scored 88/75/70, +10 product media — 87.67 How ranking works →

Iru is a device-centric platform that unifies security, IT, and compliance around devices and everything they touch.

Iru adds MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. Billing, LAPSLAPSA Microsoft feature that automatically generates, rotates, and stores unique local administrator passwords for each Windows machine in Active Directory, eliminating shared static credentials across a fleet. for Mac, compliance evidence enhancements, and macOS 27 support.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds MSP Billing with itemized billing to increase visibility into MSP margins.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds LAPS for Mac as a Library Item. Not checked yet
  • Enhances Iru Compliance evidence collection.
  • Adds MSP Billing with itemized billing to increase visibility into MSP margins.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds LAPS for Mac as a Library Item. Not checked yet

1 more in Everything

4 more releases in this issue · 2026-09-18 → 2026-09-25
Recommended privacy permissions for iPhone and iPad Notes Stable

Iru's Privacy Library Item gains a Recommended privacy permissions area for iPhone and iPad, letting admins bundle app and Safari permission prompts into a single consent scr⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Introducing MSP Billing Notes Stable

Iru adds MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. Billing with daily per-tenant spend visibility and self-serve setup in the Partner Portal.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

What's New in Iru | September 18th Notes Stable

Iru adds Windows Vulnerability Management, OS update status visibility, and enrollment invite email routing for Identity.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds Vulnerability Management and Response deployment support for Windows devices.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds OS update status visibility per Windows device, showing clear update state across your fleet. Not checked yet
  • Enables control over which email address enrollment invites are sent to in Iru Identity. Not checked yet
  • Adds Vulnerability Management and Response deployment support for Windows devices.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds OS update status visibility per Windows device, showing clear update state across your fleet. Not checked yet

1 more in Everything

Windows Managed OS patch compliance Notes Stable

Windows Managed OS Library Items now surface per-device patch compliance with Pass/Update past due/Error status and build-level enforcement date detail.

Was this useful?
◆  Threat Intelligence

OpenCTI

Sources Release notes → 7.260928.0 Notes Rank Why this rank top features scored 90/83/40, +15 breaking change, +6 runnable example — 92 How ranking works →

OpenCTI ships XTM One-based Enterprise Edition licensing with a new Filigran Experience settings page, alongside SSVCSSVCA decision-support framework for vulnerability prioritization, maintained by CISA and Carnegie Mellon's CERT/CC, that uses stakeholder-specific decision trees to guide patch and remediation timing instead of relying on numeric scores alone. vulnerability prioritization aligned to CISA BOD 26-04CISA BOD 26-04A Binding Operational Directive issued by CISA that legally compels US federal civilian agencies to meet specific cybersecurity requirements within set deadlines, giving cyber tools a compliance mandate to build workflows around., Indicator-to-Security-Platform sightings, always-on ingestion logs, investigation duplication, and per-node Redis TLS validation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Open Cyber Threat Intelligence Platform

OpenCTI ships XTM One-based Enterprise Edition licensing with a new Filigran Experience settings page, alongside SSVCSSVCA decision-support framework for vulnerability prioritization, maintained by CISA and Carnegie Mellon's CERT/CC, that uses stakeholder-specific decision trees to guide patch and remediation timing instead of relying on numeric scores alone. vulnerability prioritization aligned to CISA BOD 26-04CISA BOD 26-04A Binding Operational Directive issued by CISA that legally compels US federal civilian agencies to meet specific cybersecurity requirements within set deadlines, giving cyber tools a compliance mandate to build workflows around., Indicator-to-Security-Platform sightings, always-on ingestion logs, investigation duplication, and per-node Redis TLS validation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 7 FEATURES 0 OF 7 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
XTM One Enterprise Edition licensing Not checked yet new 90

Adds xtm:xtm_one_url (env XTM__XTM_ONE_URL, default https://common.xtm1.filigran.io) and xtm:xtm_one_token (env XTM__XTM_ONE_TOKEN) config keys so OpenCTI registers with XTM One every 5 minutes and receives a Filigran-signed Enterprise Edition license; OpenCTI now verifies that signed license and grants EE access from it.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ A new Settings > Filigran Experience page shows the license source (OpenCTI or XTM One), customer, type, and validity dates, rechecked every 5 minutes, with a 90-day grace period for expired licenses (no grace for trial or ci types).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Requires XTM One release #3831 or later — against an older XTM One the license grants nothing and OpenCTI logs a warning.

Enable XTM One-based Enterprise Edition licensing so OpenCTI automatically receives and renews its EE license from the XTM One server every 5 minutes.
yaml
xtm:
  xtm_one_url: "https://common.xtm1.filigran.io"
  xtm_one_token: "<your-xtm-one-registration-token>"
— names config keys, env vars, defaults, UI path across two releases 7.260928.0
02 00
Per-node Redis TLS validation Not checked yet new 83

Adds redis:tls_cluster_node_mode (env REDIS__TLS_CLUSTER_NODE_MODE) config key that, when set, validates each Redis cluster node certificate individually rather than globally.

Enforce individual TLS certificate validation for each Redis cluster node instead of a single shared check.
yaml
redis:
  tls_cluster_node_mode: true
— exact config key, env var, and runnable example given product docs
thinner coverage below
03 00
SSVC vulnerability prioritization Not checked yet new 40

Adds SSVC risk-based prioritization metrics aligned to CISA BOD 26-04BOD 26-04A Binding Operational Directive issued by CISA requiring U.S. federal civilian agencies to take specific cybersecurity actions; tools cite it to show their output maps to mandatory federal compliance requirements. for vulnerability objects.

— names the standard but not scoring mechanism or UI 7.260928.0
04 00
Observed Data occurrence counters Not checked yet new 40

Adds number_seen and max_distinct_count counters to the Observed Data data model.

— names the fields but not how they populate or display 7.260928.0
05 00
Ingestion logs for all ingestion types Not checked yet improved 40

Adds ingestion logs across all ingestion types; the previous feature flag has been removed so logging is now always active.

— notes flag removal but not log location or format 7.260928.0
06 00
Indicator-to-Security-Platform sightings Not checked yet new 35

Supports sighting relationships between an Indicator and a Security Platform entity.

— names entity types but no workflow detail 7.260928.0
07 00
Investigation duplication Not checked yet new 20

Supports duplicating an investigation.

— bare feature name with no mechanism or UI path 7.260928.0
└──▷ BREAKING ON UPGRADE
  • !
    XTM One-based Enterprise Edition licensing requires XTM One release #3831 or later; against an older XTM One the XTM license grants nothing and OpenCTI logs a warning — upgrade XTM One before OpenCTI.
7.260928.0 Notes LatestStable

OpenCTI 7.260928.0 adds SSVCSSVCA decision-support framework for vulnerability prioritization, maintained by CISA and Carnegie Mellon's CERT/CC, that uses stakeholder-specific decision trees to guide patch and remediation timing instead of relying on numeric scores alone. vulnerability prioritization, Indicator-to-Security-Platform sightings, ingestion logs, and investigation duplication.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch 7.260928.0 https://github.com/OpenCTI-Platform/opencti.git
# already have the repo? check out this version:
$ git checkout 7.260928.0
  • Adds number_seen and max_distinct_count counters to the Observed Data data model.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds ingestion logs across all ingestion types (feature flag removed, now always active).
  • Adds SSVC risk-based prioritization metrics aligned to CISA BOD 26-04CISA BOD 26-04A Binding Operational Directive issued by CISA that legally compels US federal civilian agencies to meet specific cybersecurity requirements within set deadlines, giving cyber tools a compliance mandate to build workflows around. for vulnerability objects.
  • Supports sighting relationships between an Indicator and a Security Platform entity.
  • Supports duplicating an investigation.
+1 more show less
  • Verifies Filigran-signed XTM licenses returned by XTM One registration and grants Enterprise Edition from the verified license.
  • Adds number_seen and max_distinct_count counters to the Observed Data data model.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds SSVC risk-based prioritization metrics aligned to CISA BOD 26-04CISA BOD 26-04A Binding Operational Directive issued by CISA that legally compels US federal civilian agencies to meet specific cybersecurity requirements within set deadlines, giving cyber tools a compliance mandate to build workflows around. for vulnerability objects.
  • Supports sighting relationships between an Indicator and a Security Platform entity.
  • Supports duplicating an investigation.
  • Verifies Filigran-signed XTM licenses returned by XTM One registration and grants Enterprise Edition from the verified license.

1 more in Everything

Was this useful?

MISP

Sources Release notes → v2.5.48 Notes Rank Why this rank top features scored 88/62, +10 product media, +6 runnable example — 91 How ranking works →

MISP v2.5.48 adds XLSX as a native export format across events, attributes and sightings, and lets enrichment/import modules remove tags from existing attributes instead of only adding new ones.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

MISP (core software) - Open Source Threat Intelligence and Sharing Platform

MISP v2.5.48 adds XLSX as a native export format across events, attributes and sightings, and lets enrichment/import modules remove tags from existing attributes instead of only adding new ones.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
XLSX export for events, attributes, sightings Not checked yet new 88

MISP adds XLSX export for events, attributes, and sightings via restSearch and the per-event and mass export pickers.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ A new escape_formulas_literal:1 parameter switches formula-safe cells to literal apostrophe form instead of using quotePrefix cell styling, avoiding Excel formula-injection warnings.

Export all attributes matching a network indicator search as an Excel workbook for analyst review — avoiding CSV formula-injection warnings in Excel.
$ curl -s -H 'Authorization: <api-key>' -H 'Accept: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet' 'https://<misp-host>/attributes/restSearch/returnFormat:xlsx/type:ip-dst' -o results.xlsx
Export attributes as XLSX with formula cells written as literal apostrophe-prefixed strings, for workflows that re-export the workbook back to CSV without preserving quotePrefix styling.
$ curl -s -H 'Authorization: <api-key>' -H 'Accept: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet' 'https://<misp-host>/attributes/restSearch/returnFormat:xlsx/escape_formulas_literal:1' -o results_literal.xlsx
— Names endpoint params and exact flag with runnable curl examples v2.5.48
02 00
Tag removal from module results Not checked yet new 62

Enrichment and import modules can now include a remove_tags list in result rows, letting modules strip tags from existing attributes instead of creating duplicates. Removed tags are surfaced in the resolution screen and in EventShell enrichment output.

— Names config field and output surface but no runnable example v2.5.48
v2.5.48 Notes LatestStable

MISP v2.5.48 adds XLSX export for events/attributes/sightings and tag removal from misp-module enrichment results.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v2.5.48 https://github.com/MISP/MISP.git
# already have the repo? check out this version:
$ git checkout v2.5.48
└──▷ TRY IT
Export all attributes matching a network indicator search as an Excel workbook for analyst review — avoiding CSV formula-injection warnings in Excel.
$ curl -s -H 'Authorization: <api-key>' -H 'Accept: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet' 'https://<misp-host>/attributes/restSearch/returnFormat:xlsx/type:ip-dst' -o results.xlsx
Export attributes as XLSX with formula cells written as literal apostrophe-prefixed strings, for workflows that re-export the workbook back to CSV without preserving quotePrefix styling.
$ curl -s -H 'Authorization: <api-key>' -H 'Accept: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet' 'https://<misp-host>/attributes/restSearch/returnFormat:xlsx/escape_formulas_literal:1' -o results_literal.xlsx
  • Adds XLSX export for events, attributes, and sightings via restSearch and the per-event and mass export pickers, with escape_formulas_literal:1 to switch formula-safe cells to literal apostrophe form instead of quotePrefix cell style.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds remove_tags list support in enrichment and import module result rows, letting modules strip tags from existing attributes instead of creating duplicates, with removed tags surfaced in the resolution screen and EventShell enrichment output.

2 details in Everything

Was this useful?

Recorded Future

Sources Blog post → announced · Sep 28, 2026 Blog Rank Why this rank top features scored 90/50/45, +10 product media, +6 runnable example — 77.67 How ranking works →

Recorded Future launched its MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. (Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.) gateway to general availability, giving OAuth-authenticated AI agents access to 80+ intelligence tools, write-back capability, and direct Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express. traversal.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Get started with the Recorded Future API. Covers authentication, base URLs, API key setup, and how to integrate threat intelligence into your security workflows.

Recorded Future launched its MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. (Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.) gateway to general availability, giving OAuth-authenticated AI agents access to 80+ intelligence tools, write-back capability, and direct Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express. traversal.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 3 FEATURES 1 OF 3 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
Recorded Future MCP gateway reaches GA Not checked yet new 90

Recorded Future MCP is a Model Context Protocol gateway exposing 80+ intelligence tools — including threat actor profiles, Risk Scores, ransomware metadata, malware sandbox data, and dark web intelligence — to AI agents via OAuth 2.0OAuth 2.0An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. (Client ID/Secret).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ It is accessible as a tile in the Integration Center, supports both OAuth 2.0 Client ID/Secret (for integration users) and portal user-based authentication (SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management.), and is compatible with Claude, ChatGPT Enterprise, Copilot, Cursor, Gemini CLI, and any other OAuth-capable MCP client.

Activate Recorded Future MCP from within the platform so your AI agents gain authenticated access to the full intelligence tool catalog.
📍In the Recorded Future Platform, go to Integration Center › find the Recorded Future MCP tile › click to activate › configure an integration user with Client ID/Secret (OAuth 2.0) for persistent agent access.
— Names auth method, activation path, and client compatibility with exact steps. launch-20260928-306293b1
thinner coverage below
02 00
Intelligence Graph traversal for MCP agents Not checked yet new 50

MCP supports direct graph traversal of the Intelligence Graph, letting agents find related entities and context in fewer calls, reducing token cost and latency at agentic scale.

— Explains the benefit and mechanism but no concrete usage example. launch-20260928-306293b1
03 00
Agent write-back to Watch Lists and Analyst Notes Not checked yet new 45

MCP-connected agents can now write back to the Recorded Future Platform, updating Watch Lists and authoring Platform Analyst Notes directly rather than only reading intelligence.

— States the capability but no mechanism or steps to invoke it. launch-20260928-306293b1
announced · Sep 28, 2026 Blog

Recorded Future MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. is now GA, giving AI agents OAuth-authenticated access to 80+ intelligence tools including write-back to Watch Lists and Analyst Notes.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Activate Recorded Future MCP from within the platform so your AI agents gain authenticated access to the full intelligence tool catalog.
📍In the Recorded Future Platform, go to Integration Center › find the Recorded Future MCP tile › click to activate › configure an integration user with Client ID/Secret (OAuth 2.0) for persistent agent access.
  • Adds Recorded Future MCP, a Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. gateway exposing 80+ intelligence tools — including threat actor profiles, Risk Scores, ransomware metadata, malware sandbox data, and dark web intelligence — to AI agents via OAuth 2.0OAuth 2.0An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. (Client ID/Secret).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Enables write-back from agents to Recorded Future Platform: agents can update Watch Lists and author Platform Analyst Notes directly, not just read intelligence.
  • Accessible as a tile in the Integration Center for activation alongside existing integrations; supports both OAuth 2OAuth 2An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs..0 Client ID/Secret (for integration users) and portal user-based authentication (SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management.).
  • Supports direct graph traversal of the Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express., letting agents find related entities and context in fewer calls to reduce token cost and latency at agentic scale.
  • Compatible with Claude, ChatGPT Enterprise, Copilot, Cursor, Gemini CLI, and any other OAuth-capable MCP client — no custom agent required.

5 details in Everything

Was this useful?
◆  SOAR

Shuffle

Sources Release notes → v2.3.0 Notes Rank Why this rank top features scored 85/60/50, +6 runnable example — 71 How ranking works →

Shuffle: A general purpose security automation platform. Our focus is on collaboration and resource sharing.

Shuffle v2.3.0 focuses on self-hosted and air-gapped deployments, adding on-prem/hybrid AI Agents, private-registry and air-gapped app builds, and automatic recovery of stuck workflow executions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 6 FEATURES 0 OF 6 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Air-gapped and private-registry app builds Not checked yet new 85

Adds SHUFFLE_BASE_IMAGE_REGISTRY and SHUFFLE_BASE_IMAGE_NAME config settings for consistent custom/private registry behavior across all deployment types, and supports a custom App SDK image for building apps in disconnected or air-gapped environments on self-hosted installations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Point a self-hosted Shuffle deployment at a private container registry so all app builds pull from your internal mirror instead of Docker Hub.
ini
SHUFFLE_BASE_IMAGE_REGISTRY=registry.internal.corp
SHUFFLE_BASE_IMAGE_NAME=shuffle/shuffle-app-sdk
— Names two env vars with a runnable config example v2.3.0
02 00
On-prem and hybrid AI Agents Not checked yet new 60

AI Agents can now run in on-premises and hybrid setups, picking the correct backend address and tool timeouts, recovering late-arriving results, and using local AI credentials or Shuffle AI synced from the cloud.

— Explains mechanism but no config surface given v2.3.0
thinner coverage below
03 00
Shuffle Security in Compose and Helm deployments Not checked yet new 50

Includes Shuffle Security in both the Docker Compose configuration and Kubernetes Helm chart for easier self-hosted deployment.

— Names deployment files but no exact keys given v2.3.0
04 00
Automatic rerun of stuck executions in Orborus Not checked yet new 45

Adds an automatic rerun system within Orborus that detects and restarts stuck workflow executions, reducing the need for manual intervention.

— Explains behavior, no flag or config named v2.3.0
05 00
Live workflow update streaming improvements Not checked yet improved 45

Improves live workflow update streaming, including AI-generated edits, with more reliable change history and reconnection handling, and reduces background polling when only one person is viewing a workflow.

— Behavior described, no named surface or metric v2.3.0
06 00
AI Agent and MCP action name matching refinement Not checked yet improved 45

Refines AI Agent and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. action app/tool name matching by searching workflows to find the correct action, with added execution and permission checks on agent-initiated runs.

— Describes mechanism, no named endpoint or flag v2.3.0
v2.3.0 Notes LatestStable

Shuffle v2.3.0 brings on-prem/hybrid AI Agents, air-gapped app builds, and automatic stuck-execution reruns via Orborus.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v2.3.0 https://github.com/Shuffle/Shuffle.git
# already have the repo? check out this version:
$ git checkout v2.3.0
└──▷ USE IT
Point a self-hosted Shuffle deployment at a private container registry so all app builds pull from your internal mirror instead of Docker Hub.
.env
SHUFFLE_BASE_IMAGE_REGISTRY=registry.internal.corp
SHUFFLE_BASE_IMAGE_NAME=shuffle/shuffle-app-sdk
  • Adds SHUFFLE_BASE_IMAGE_REGISTRY and SHUFFLE_BASE_IMAGE_NAME config settings for consistent custom/private registry behavior across all deployment types.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Enables AI Agents to run in on-premises and hybrid setups, picking the correct backend address and tool timeouts, recovering late-arriving results, and using local AI credentials or Shuffle AI synced from the cloud.
  • Adds automatic rerun system within Orborus to detect and restart stuck workflow executions, reducing the need for manual intervention.
  • Supports a custom App SDK image for building apps in disconnected or air-gapped environments on self-hosted installations.
  • Improves live workflow update streaming, including AI-generated edits, with more reliable change history and reconnection handling, and reduces background polling when only one person is viewing a workflow.
+2 more show less
  • Includes Shuffle Security in both the Docker Compose configuration and Kubernetes Helm chart for easier self-hosted deployment.
  • Refines AI Agent and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. action app/tool name matching by searching workflows to find the correct action, with added execution and permission checks on agent-initiated runs.
  • Adds SHUFFLE_BASE_IMAGE_REGISTRY and SHUFFLE_BASE_IMAGE_NAME config settings for consistent custom/private registry behavior across all deployment types.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds automatic rerun system within Orborus to detect and restart stuck workflow executions, reducing the need for manual intervention.
  • Supports a custom App SDK image for building apps in disconnected or air-gapped environments on self-hosted installations.
  • Includes Shuffle Security in both the Docker Compose configuration and Kubernetes Helm chart for easier self-hosted deployment.

3 more in Everything

Was this useful?
◆  Security Data Pipeline

Cribl

Sources Blog / feed →Product docs → changelog · Sep 29, 2026 Docs Blog Rank Why this rank top features scored 83/65/48, +6 runnable example — 71.33 How ranking works →

Cribl is built for IT and Security data and provides a unified data management platform for exploring, collecting, processing, and accessing that data at scale.

Cribl launched two major new products at CriblCon 26 — Cribl Detect, a full SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. with 8,000+ detection rules and posture management, and StreamAI, an enterprise AI gateway with model routing and spend/redaction controls — alongside a new agentic development environment, expanded MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface./SDK agent access, AI auto-parsing, and a growing App Framework marketplace.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 6 FEATURES 3 OF 6 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
Cribl Detect SIEM launch Not checked yet new 83

Cribl Detect is a full SIEM built on the Cribl platform, combining detection, Detection Posture Management (continuously showing coverage gaps, broken rules, and missing telemetry required to detect specific attacks), investigation, response, and threat intelligence.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ It ships with a catalog of more than 8,000 detection rules with correlation across signals to surface multi-stage attacks, and generates detection signals directly in the data pipeline for real-time threat identification while telemetry is still in motion. It is available now for Cribl.Cloud customers at up to 50% less cost than incumbent SIEMsSIEMsSecurity Information and Event Management platforms that collect, normalize, and correlate log data across an infrastructure so cyber tools can detect threats and trigger alerts from a central point., priced on infrastructure rather than per-GB ingestion.

Get started with Cribl Detect on Cribl.Cloud to immediately access SIEM detection, posture management, and 8,000+ detection rules without migrating existing telemetry pipelines.
📍In Cribl.Cloud, log in to your organization, navigate to the Cribl Detect tile, and select Get Started to activate detection on your existing telemetry streams.
— Mechanism, coverage and pricing detailed; only a UI-path example given 2026-09-29-1d8f4bc7
02 02
StreamAI enterprise AI gateway with model routing Not checked yet new 65

StreamAI is an enterprise AI gateway with a built-in model router that routes each prompt to the right model based on SecIT Bench benchmarks, offering free inference for customers using automatic routing. It enforces spending budgets and cutoffs, redacts sensitive data in both prompts and responses, and records every model call as audit-ready telemetry.

— Names controls and benchmark but no config keys or endpoints 2026-09-29-1d8f4bc7
thinner coverage below
03 03
Agentic development environment for apps and workflows Not checked yet new 48

A new agentic development environment lets teams build apps, workflows, and agents using natural language, running on the same agentic runtime that powers Cribl Detect, with compute, scheduling, logging, and permissions included.

— Describes runtime components but no concrete usage path 2026-09-29-1d8f4bc7
04 00
Cribl App Framework grows to 150+ apps Not checked yet improved 40

The Cribl App Framework grows to more than 150 apps from Cribl, partners, and customers, available in the Cribl Marketplace.

— States count and location but no usage instructions 2026-09-29-1d8f4bc7
05 00
Agent access via MCP and SDKs Not checked yet new 35

Cribl opens the platform to agents via MCP and SDKs, adding 70 new integrations this year.

— Names MCP/SDK surfaces but gives no usage specifics 2026-09-29-1d8f4bc7
06 00
AI auto-parsing of incoming telemetry Not checked yet new 28

Adds AI auto-parsing of telemetry so incoming data is structured and usable the moment it arrives.

— Bare description with no mechanism or config detail 2026-09-29-1d8f4bc7
changelog · Sep 29, 2026 Docs Blog LatestStable

Cribl launches StreamAI (AI gateway with model routing) and Cribl Detect (full SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. with 8,000+ detection rules) at CriblCon 26.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Get started with Cribl Detect on Cribl.Cloud to immediately access SIEM detection, posture management, and 8,000+ detection rules without migrating existing telemetry pipelines.
📍In Cribl.Cloud, log in to your organization, navigate to the Cribl Detect tile, and select Get Started to activate detection on your existing telemetry streams.
  • Adds Cribl Detect, a complete SIEM built on the Cribl platform with detection, coverage and posture management, investigation, response, and threat intelligence — available now for Cribl.Cloud customers at up to 50% less cost than incumbent SIEMsSIEMsSecurity Information and Event Management platforms that collect, normalize, and correlate log data across an infrastructure so cyber tools can detect threats and trigger alerts from a central point., priced on infrastructure rather than per-GB ingestion.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds StreamAI, an enterprise AI gateway with a built-in model router that routes each prompt to the right model based on SecIT Bench benchmarks, with free inference for customers using automatic routing.
  • StreamAI enforces spending budgets and cutoffs, redacts sensitive data in both prompts and responses, and records every model call as audit-ready telemetry.
  • Cribl Detect includes Detection Posture Management, continuously showing coverage gaps, broken rules, and missing telemetry required to detect specific attacks.
  • Cribl Detect ships with a catalog of more than 8,000 detection rules covering a broad range of threats, with correlation across signals to surface multi-stage attacks.
+5 more show less
  • Cribl Detect generates detection signals directly in the data pipeline, enabling real-time threat identification while telemetry is still in motion.
  • Adds an agentic development environment that lets teams build apps, workflows, and agents using natural language, running on the same agentic runtime that powers Cribl Detect with compute, scheduling, logging, and permissions included.
  • Opens the platform to agents via MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. and SDKs, adding 70 new integrations this year.
  • Adds AI auto-parsing of telemetry so incoming data is structured and usable the moment it arrives.
  • Grows the Cribl App Framework to 150+ apps from Cribl, partners, and customers, available in the Cribl Marketplace.
  • Adds Cribl Detect, a complete SIEM built on the Cribl platform with detection, coverage and posture management, investigation, response, and threat intelligence — available now for Cribl.Cloud customers at up to 50% less cost than incumbent SIEMsSIEMsSecurity Information and Event Management platforms that collect, normalize, and correlate log data across an infrastructure so cyber tools can detect threats and trigger alerts from a central point., priced on infrastructure rather than per-GB ingestion.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds StreamAI, an enterprise AI gateway with a built-in model router that routes each prompt to the right model based on SecIT Bench benchmarks, with free inference for customers using automatic routing.
  • StreamAI enforces spending budgets and cutoffs, redacts sensitive data in both prompts and responses, and records every model call as audit-ready telemetry.
  • Cribl Detect includes Detection Posture Management, continuously showing coverage gaps, broken rules, and missing telemetry required to detect specific attacks.
  • Cribl Detect ships with a catalog of more than 8,000 detection rules covering a broad range of threats, with correlation across signals to surface multi-stage attacks.
+4 more show less
  • Cribl Detect generates detection signals directly in the data pipeline, enabling real-time threat identification while telemetry is still in motion.
  • Adds an agentic development environment that lets teams build apps, workflows, and agents using natural language, running on the same agentic runtime that powers Cribl Detect with compute, scheduling, logging, and permissions included.
  • Opens the platform to agents via MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. and SDKs, adding 70 new integrations this year.
  • Adds AI auto-parsing of telemetry so incoming data is structured and usable the moment it arrives.

1 more in Everything

Was this useful?
Exposure & Vulnerability Management
◆  Vulnerability & Exposure Management

Rapid7 InsightVM

Sources Blog / feed →Product docs → changelog · Sep 29, 2026 Docs Blog Rank Why this rank top features scored 55/48 — 51.5 How ranking works →

Rapid7 InsightVM is a vulnerability management platform that discovers, prioritizes, and remediates security risks across IT infrastructure.

The Rapid7 Agent's Windows filesystem walk tool is improved to reduce assessment failures on large filesystems and remove prior file search scope limits.

Was this useful?

Future Architect Vuls

Sources Release notes →Source code → v0.41.0-rc.2 Notes Code Rank Why this rank top features scored 35 — 35 How ranking works →

Agent-less vulnerability scanner for Linux, FreeBSD, Container, WordPress, Programming language libraries, Network devices

Vuls v0.41.0-rc.2 expands vulnerability detection coverage through its vuls2 engine, adding support for Oracle Solaris, Apple security releases, and OpenSSH advisories.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 0 FEATURES1 FEATURE 0 OF 1 FEATURE most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
vuls2 detection engine adds Solaris, Apple, and OpenSSH coverage Not checked yet new 35

The vuls2 detection engine now detects vulnerabilities in the Oracle Solaris family, Apple security releases, and OpenSSH security advisories.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Names three new detection targets but no flags, commands, or mechanism detail. v0.41.0-rc.2
v0.41.0-rc.2 Notes Code Pre-release

Vuls v0.41.0-rc.2 adds Oracle Solaris, Apple security releases, and OpenSSH advisory detection via vuls2⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v0.41.0-rc.2 https://github.com/future-architect/vuls.git
# already have the repo? check out this version:
$ git checkout v0.41.0-rc.2
  • Detects vulnerabilities in the Oracle Solaris family through the vuls2 detection engine.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Detects Apple security releases through the vuls2 detection engine.
  • Detects OpenSSH security advisories through the vuls2 detection engine.

3 details in Everything

Was this useful?

Qualys Patch Management

Sources Blog / feed → changelog · Sep 29, 2026 Blog Rank Why this rank top features scored 95/70/22, +10 product media, +6 runnable example — 78.33 How ranking works →

Qualys TruRiskTruRiskA proprietary risk-scoring methodology from Qualys that translates vulnerability and asset data into a numeric business-risk score, giving cyber tools a single prioritization signal instead of raw CVSS values. Eliminate now lets teams block risky patches environment-wide via QQL-based rules and automatically skip low-reliability patches in zero-touch jobs using AI-driven reliability scoring, backed by curated interim mitigations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Qualys Patch Management is a cloud-based vulnerability management tool that identifies, prioritizes, and automates the deployment of security patches across IT infrastructure.

Qualys TruRiskTruRiskA proprietary risk-scoring methodology from Qualys that translates vulnerability and asset data into a numeric business-risk score, giving cyber tools a single prioritization signal instead of raw CVSS values. Eliminate now lets teams block risky patches environment-wide via QQL-based rules and automatically skip low-reliability patches in zero-touch jobs using AI-driven reliability scoring, backed by curated interim mitigations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 3 FEATURES 0 OF 3 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Patch Blocking Rules in TruRisk Eliminate Not checked yet new 95

Adds Patch Blocking Rules under TE > Configuration > Patch Blocking Rules, available for Windows, Linux, and Mac in release 4.2, letting admins define patches to block via a QQL query (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ patch.kb: [KB5002907, KB5124008, KB5124012, KB5123099]) so they are excluded across every deployment job at once without editing individual jobs. Scope is controlled by up to five asset tags per rule, with up to 10 rules allowed per platform, and each rule requires a name and a blocking reason.

Immediately stop a vendor-paused or known-bad Windows patch from deploying across your entire environment without touching individual patch jobs.
📍In TruRisk Eliminate, go to TE › Configuration › Patch Blocking Rules, select Windows, click Create Rule. Enter a name (e.g. Block paused Sep-2026 updates) and a blocking reason. Under Criteria (QQL), enter: patch.kb: [KB5002907, KB5124008, KB5124012, KB5123099] and click Preview to confirm the match. Leave asset tags empty to cover all assets, then save.
Protect production assets while a test group validates a new patch by scoping a blocking rule to production asset tags.
📍In TruRisk Eliminate, go to TE › Configuration › Patch Blocking Rules, select Windows, click Create Rule. Enter a name (e.g. Hold KB5002907 from prod during validation) and a blocking reason. Under Criteria (QQL), enter: patch.kb: [KB5002907] and click Preview. Under asset scope, add up to five production asset tags to restrict the block to production only, then save.
— Names exact UI path, QQL syntax, and rule limits. 2026-09-29-7aca09ff
02 00
AI-Powered Patch Reliability Scoring Not checked yet new 70

Adds AI-Powered Patch Reliability Scoring, which combines LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. analysis of real-world internet feedback with Qualys rollback and vulnerability-reopen telemetry to rate each patch High, Medium, Low, or Unidentified. Adding reliability intelligence to a zero-touch job's Select Patches step QQL automatically skips Low-reliability patches from deployment while other patches continue as scheduled.

Keep zero-touch patch jobs running while automatically skipping low-reliability patches by adding reliability intelligence to the job's patch-selection query.
📍In the zero-touch patch job's Select Patches step, update the QQL to include reliability criteria alongside your existing filters so that Low-reliability patches — such as those currently rated Low by AI-Powered Patch Reliability Scoring — are excluded from automatic deployment while all other patches continue to deploy.
— Explains rating mechanism but omits exact QQL field syntax. 2026-09-29-7aca09ff
thinner coverage below
03 00
Curated mitigations for held patches Not checked yet new 22

Introduces Qualys-curated mitigations as a complementary layer to reduce exposure while a blocked or low-reliability patch is held in testing and staging.

— Single-sentence description with no named surface or steps. 2026-09-29-7aca09ff
└──▷ ALSO FROM THESE RELEASES
changelog · Sep 29, 2026 Blog LatestStable

Qualys TruRiskTruRiskA proprietary risk-scoring methodology from Qualys that translates vulnerability and asset data into a numeric business-risk score, giving cyber tools a single prioritization signal instead of raw CVSS values. Eliminate adds Patch Blocking Rules and AI-Powered Patch Reliability Scoring to keep bad patches out of automation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Immediately stop a vendor-paused or known-bad Windows patch from deploying across your entire environment without touching individual patch jobs.
📍In TruRisk Eliminate, go to TE › Configuration › Patch Blocking Rules, select Windows, click Create Rule. Enter a name (e.g. Block paused Sep-2026 updates) and a blocking reason. Under Criteria (QQL), enter: patch.kb: [KB5002907, KB5124008, KB5124012, KB5123099] and click Preview to confirm the match. Leave asset tags empty to cover all assets, then save.
Protect production assets while a test group validates a new patch by scoping a blocking rule to production asset tags.
📍In TruRisk Eliminate, go to TE › Configuration › Patch Blocking Rules, select Windows, click Create Rule. Enter a name (e.g. Hold KB5002907 from prod during validation) and a blocking reason. Under Criteria (QQL), enter: patch.kb: [KB5002907] and click Preview. Under asset scope, add up to five production asset tags to restrict the block to production only, then save.
Keep zero-touch patch jobs running while automatically skipping low-reliability patches by adding reliability intelligence to the job's patch-selection query.
📍In the zero-touch patch job's Select Patches step, update the QQL to include reliability criteria alongside your existing filters so that Low-reliability patches — such as those currently rated Low by AI-Powered Patch Reliability Scoring — are excluded from automatic deployment while all other patches continue to deploy.
  • Adds Patch Blocking Rules in TE > Configuration > Patch Blocking Rules (available for Windows, Linux, and Mac in release 4.2), letting you define patches via a QQL query and block them across every deployment job at once without editing individual jobs; scope is controlled by up to five asset tags per rule, with up to 10 rules per platform, and each rule requires a name and blocking reason.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds AI-Powered Patch Reliability Scoring that combines LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. analysis of real-world internet feedback with Qualys rollback and vulnerability-reopen telemetry to rate each patch High, Medium, Low, or Unidentified — automatically skipping Low-reliability patches from zero-touch jobs when reliability intelligence is added to the job's QQL in the Select Patches step.
  • Introduces Qualys-curated mitigations as a complementary layer to reduce exposure while a blocked or low-reliability patch is held in testing and staging.

3 details in Everything

Was this useful?
◆  Vulnerability & Exposure Management

Censys

Sources Blog / feed → September 28, 2026 (2026-09-28) Blog Rank Why this rank top features scored 75/60/45, +6 runnable example — 66 How ranking works →

Censys is a search engine for internet-connected devices that indexes certificates, websites, and network services for security research and reconnaissance.

Censys shipped an AI Skills plugin that lets Claude agents drive cencli directly, raised the Adversary Investigation batch limit sixfold, and added two new Kiteworks fingerprints to the Platform.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 3 FEATURES 0 OF 3 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
AI Skills plugin for cencli agents Not checked yet new 75

Adds the censys-ai-skills repo, a Claude plugin that exposes cencli commands to AI agents for asset lookups, investigations, and CensEye job execution.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ It can be installed as a Claude plugin and prompted to run asset lookups and investigations autonomously.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Wire cencli into a Claude agent so it can autonomously look up assets and run investigations without leaving the AI workflow.
📍Install the censys-ai-skills repo as a Claude plugin, then prompt your agent: 'Use cencli to look up all assets tagged Kiteworks PCN and run an investigation on the top 100 indicators.'
— Named repo and commands plus install/usage steps September 28, 2026 (2026-09-28)
02 00
Adversary Investigation batch limit raised to 100 Not checked yet improved 60

Raises the Adversary Investigation AI investigator batch limit from 35 to 100 indicators per submission.

— Exact before/after numbers but no usage command September 28, 2026 (2026-09-28)
thinner coverage below
03 00
New Platform fingerprints for Kiteworks Not checked yet new 45

Adds two new fingerprints to the Platform: software Kiteworks PCN and software Kiteworks Secure MFT Server.

— Named fingerprints but no usage guidance given September 28, 2026 (2026-09-28)
September 28, 2026 (2026-09-28) Blog LatestStable

Censys adds AI Skills plugin for cencli-powered agents and raises AI investigator batch limit to 100 indicators.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Wire cencli into a Claude agent so it can autonomously look up assets and run investigations without leaving the AI workflow.
📍Install the censys-ai-skills repo as a Claude plugin, then prompt your agent: 'Use cencli to look up all assets tagged Kiteworks PCN and run an investigation on the top 100 indicators.'
  • Adds the censys-ai-skills repo, a Claude plugin that exposes cencli commands to AI agents for asset lookups, investigations, and CensEye job execution.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Raises the Adversary Investigation AI investigator batch limit from 35 to 100 indicators per submission.
  • Adds two new fingerprints to the Platform: software Kiteworks PCN and software Kiteworks Secure MFT Server.
  • Adds the censys-ai-skills repo, a Claude plugin that exposes cencli commands to AI agents for asset lookups, investigations, and CensEye job execution.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

2 more in Everything

Was this useful?
Identity, Access & Data Protection
◆  Identity & Access Management

iDenfy

Sources Release page → updated · Sep 29, 2026 Notes Rank Why this rank top features scored 48 — 48 How ranking works →

Explore iDenfy documentation for identity verification (KYC), business verification (KYB), AML screening, fraud prevention, and more.

iDenfy's mobile SDK update focuses on the Android SDK, adding landscape support, improved document selection guidance, glare/blur detection for older devices, and deeper UI customization.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 1 FEATURE 0 OF 1 FEATURE most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Android SDK capture and UI improvements Not checked yet new 48

The Android SDK gains landscape mode support, a recommended document badge in the document selection UI to guide users toward the right document type, blur and glare detection for older Android devices to improve capture quality, and color scheme customization with XML fallbacks for theming the SDK's UI.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Names four concrete SDK additions but no APIs or config keys. snapshot-20260929
updated · Sep 29, 2026 Notes LatestStable

iDenfy mobile SDKs gain landscape mode, recommended document badge, blur/glare detection, and Smart-ID refresh state.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds landscape mode support to the Android SDK.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds a recommended document badge in the Android SDK document selection UI.
  • Adds blur and glare detection for older Android devices.
  • Adds color scheme customization with XML fallbacks for the Android SDK.
  • Adds landscape mode support to the Android SDK.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds a recommended document badge in the Android SDK document selection UI.
  • Adds blur and glare detection for older Android devices.

1 more in Everything

Was this useful?

JumpCloud

Sources Blog / feed → Release Notes 2022 (2026-09-29) Blog Rank Why this rank top features scored 95/90/80, +15 breaking change, +10 product media, +6 runnable example — 119.33 How ranking works →

JumpCloud makes it simple to manage Windows, Apple, Linux, and Android devices and to deliver secure access with SSO, MFA, Zero Trust, RADIUS, and more.

JumpCloud shipped a large slate of updates spanning identity, device management, patch management and password security — headlined by a Password Vault in the User Portal, a unified Patch Management dashboard, Access Requests approval workflows, and step-up authentication with AMR claimsAMR claimsAssertions made by a CPU about its own current operating mode and privilege level, used by attestation systems to verify that code is running in a trusted execution environment. — alongside breaking changes that restrict LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. TLS cipher suites and retire legacy API endpoints and filter operators.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 25 FEATURES 12 OF 25 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
Unified Patch Management dashboard Not checked yet new 95

Adds a unified Patch Management dashboard under Device Management > Patch Management with Overview, Apple, and Windows tabs, severity filters, KB search, CVE detail review, CSV/JSON export of the KB list, and bulk remediation; admins can immediately remediate critical missing patches by applying the Critical severity filter, selecting affected devices, and choosing Install missing critical patches.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Immediately remediate critical missing patches across non-compliant Windows devices without waiting for the next policy window.
📍In the Admin Portal, go to Device Management › Patch Management › Windows, apply the Critical severity filter, then select affected devices and choose Install missing critical patches to trigger immediate remediation.
— Names tabs, filters, export formats and a runnable remediation path Release Notes 2026 (2026-09-29)
02 02
User reactivation endpoint replaces deprecated GET call Not checked yet breaking 90

Adds POST https://console.jumpcloud.com/systemusers/reactivate/{id} to replace the deprecated GET api/systemusers/reactivate/{id}, which now returns a 404 error; requests must include an activation_email field in the JSON body.

Reactivate a user account using the new POST endpoint after removing the deprecated GET call from scripts or automations.
$ curl -s -X POST 'https://console.jumpcloud.com/systemusers/reactivate/<user_id>' -H 'x-api-key: <your-api-key>' -H 'Content-Type: application/json' -d '{"activation_email": "user@example.com"}'
— Exact endpoints, method and required field with a runnable example Release Notes 2024 (2026-09-29)
03 03
Access Requests approval workflow Not checked yet new 80

Adds Access Requests, letting admins configure an approval flow so users must request and receive admin approval before gaining access to a sensitive application; supports assigning approvers and automatic JIRA ticket creation via a configured webhook URL.

Configure an Access Request approval flow so users must request and receive admin approval before gaining access to a sensitive application, with automatic JIRA ticket creation.
📍In the JumpCloud Admin Portal, go to Access Requests › Create Approval Flow, assign approvers, enable webhook integration, and enter your JIRA webhook URL so tickets are created automatically on each new request submission.
— Exact UI path and JIRA webhook integration described Release Notes 2025 (2026-09-29)
04 00
Step-up authentication and audit signals for SSO Not checked yet new 80

Adds a sso_auth event to logs for forced re-authentication events, giving audit visibility for compliance and security reviews. Adds ForceAuthn='true' (SAMLSAMLA standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider.) and prompt=login (OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user.) support so applications can trigger step-up authentication without ending the user's existing session, and includes Authentication Methods References (AMRAMRAutonomous Mobile Robot — a self-navigating wheeled platform that maps its environment and plans its own path; cyber tools might target AMR firmware or fleet-management APIs in OT/ICS assessments.) claims in SAML assertions and OIDC ID tokens, tagging logins with proof of factors used (e.g., password + OTPOTPOne-time password: a short-lived numeric or alphanumeric code valid for a single authentication attempt, generated via TOTP or HOTP standards, giving cyber tools phishing-resistant second-factor verification without stored shared secrets.).

— Names exact SAML/OIDC parameters and log event but no exact API call Release Notes 2025 (2026-09-29)
05 04
LDAP TLS restricted to strong cipher suites Not checked yet breaking 80

Restricts LDAP TLS connections to five strong cipher suites: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, and TLS_RSA_WITH_AES_128_GCM_SHA256, removing weak CBC-mode and SHA-1SHA-1A cryptographic hash function standardized by NIST that produces a 160-bit digest; tools use it for file integrity checks, though it is now considered cryptographically broken and unsuitable for collision-resistant applications./SHA-256SHA-256A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data. suites; older suites (including RSARSAThe oldest widely used public-key algorithm, for both encryption and signatures, with security resting on factoring large numbers. A large quantum computer would break it. or ECDHE key exchange) are no longer accepted.

— Exact cipher suite names but no migration command Release Notes 2025 (2026-09-29)
06 05
Password Vault in User Portal Not checked yet new 75

Adds a Password Vault in the User Portal, accessible from the left navigation after login, supporting credential creation, sharing, personal and shared folders, and bulk import via CSV or Excel file.

— Names UI location and import formats but no field-level detail Release Notes 2026 (2026-09-29)
07 00
macOS Ventura upgrade delay/block policies Not checked yet new 75

Adds new macOS software management policies to delay or block upgrades to macOS 13 Ventura on managed devices; configured in Admin Portal under Device Management > Policies > New Policy by selecting the Ventura delay/block software management policy and binding it to a device group.

Block macOS 13 Ventura upgrades on managed devices while your team validates app compatibility.
📍In the Admin Portal, go to Device Management › Policies › New Policy, select macOS and choose the Ventura delay/block software management policy, then bind it to the relevant device group.
— Exact UI navigation given for applying the policy Release Notes 2022 (2026-09-29)
08 00
Global MFA Requirement for MSP admins Not checked yet new 70

Adds a Global MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. Requirement setting (Account > Settings) that enforces MFA for all MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. admins across the tenant, closing gaps where individual admin accounts had MFA disabled.

Enforce MFA for all MSP admins across the tenant from the Multi-Tenant Portal to close gaps where individual admin accounts had MFA disabled.
📍In the Admin Portal, go to Account › Settings, then locate Global MFA Requirement and enable the setting.
— Exact settings path given for enforcement Release Notes 2024 (2026-09-29)
09 00
Dynamic Device Groups by attribute Not checked yet improved 70

Supports automating device group membership via Dynamic Groups, using attribute rules such as OS = Linux and Vendor = Dell so matching devices are added automatically without manual intervention.

Automate device group membership so newly enrolled Linux endpoints are added without manual intervention.
📍In the Admin Portal, go to Device Groups › (select or create a group) › Group Details › Set as Dynamic, then add attribute rules such as OS = Linux and Vendor = Dell to automatically include matching devices.
— Exact attribute example given but unclear if newly added Release Notes 2023 (2026-09-29)
10 06
Password Manager Cloud Backup Not checked yet new 70

Adds a Cloud Backup toggle for the Password Manager (Password Manager > Settings), giving users a secure recovery path if their local vault is lost.

Enable Cloud Backup for the Password Manager to give users a secure recovery path if their local vault is lost.
📍In the Admin Portal, go to Password Manager › Settings and enable the Cloud Backup toggle for your organization.
— Exact settings path given, mechanism is a simple toggle Release Notes 2023 (2026-09-29)
11 07
EU region selection for Password Manager Not checked yet new 70

Supports selecting the EU region at first launch so credentials are stored and activated within the EU region; choose EU on the desktop app activation page before entering the activation code, or on the browser extension pairing page before pairing.

Configure the EU region at first launch so that credentials are stored and activated within the EU region.
📍On the Password Manager desktop app activation page, select EU from the region selector before entering your activation code; for the browser extension, select EU on the pairing page before pairing.
— Exact selection steps given for desktop and browser extension What’s New: Password Manager Desktop App (20…
12 08
Dynamic Groups filter operators renamed Not checked yet breaking 65

Deprecates the $le and $ge filter operators in Dynamic Groups memberQuery API filters; replace with $lte and $gte respectively in all API requests.

— Exact operator names but no endpoint or example call Release Notes 2024 (2026-09-29)
13 00
Agent deployment via Commands Not checked yet improved 65

Supports deploying agents such as the SentinelOne Agent across a fleet from the JumpCloud Admin Portal's Commands feature, by creating a new command targeting an OS (macOS, Windows, or Linux), pasting the install script, and running it against a device group.

Deploy the SentinelOne Agent across your Linux fleet from the JumpCloud Admin Portal using the Commands feature — no manual distribution needed.
📍In the Admin Portal, go to Commands › New Command, select the target OS (macOS, Windows, or Linux), paste the SentinelOne Agent installation script, and run it against your device group.
— Exact steps given but unclear if newly introduced Release Notes 2022 (2026-09-29)
14 00
Dormant Application Access detection refinement Not checked yet improved 60

Improves Dormant Application Access detection in Access Risk > Configuration to trigger only on re-access after inactivity (not first-time access), reducing noise from newly provisioned apps.

— Names the config location and behavior change precisely Release Notes 2026 (2026-09-29)
thinner coverage below
15 00
Android 15 and Windows 11 25H2 support in MDM Not checked yet new 40

Adds full Android 15 support in MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. and Windows 11 25H2 support for JumpCloud Windows management components.

— Names both OS versions but no rollout or configuration detail Release Notes 2024 (2026-09-29)Release Notes 2025 (2026-09-29)
16 09
MFA frequency controls in Conditional Access (Preview) Not checked yet new 40

Adds MFA Frequency Controls to Conditional AccessConditional AccessA policy enforcement framework, most commonly Microsoft's in Entra ID, that grants or blocks resource access based on signals like user identity, device state, and location — letting cyber tools trigger step-up auth or deny risky sessions. Policies Preview, letting admins define how often users must re-authenticate with MFA.

— No UI steps or config values given, still in preview product docs
17 00
Mac Personalization policy updates for Dock and Lock Screen Not checked yet improved 35

Extends Mac Personalization policies with updates to Dock Settings and Items and Lock Screen (Screen Saver) policies.

— Names the policy areas but no fields or steps Release Notes 2025 (2026-09-29)
18 00
Multiple IP addresses in RADIUS server configuration Not checked yet improved 30

Adds multiple IP address support to RADIUSRADIUSA networking protocol for centralised authentication, authorisation, and accounting of users connecting to a network, maintained under IETF standards. Cyber tools use it to integrate with existing enterprise identity infrastructure. server configuration.

— Bare description, no config keys or limits given Release Notes 2024 (2026-09-29)
19 10
Custom banned password lists Not checked yet new 30

Adds Custom Banned Password List support, enabling organizations to block organization-specific weak or prohibited passwords.

— Names the capability but no config path or limits product docs
20 00
Microsoft 365 security group integration Not checked yet new 30

Adds Microsoft 365 integration support for M365/Azure AD security groups.

— Only a one-line description, no setup steps Release Notes 2022 (2026-09-29)
21 00
Workflows with templates Not checked yet new 30

Adds a Workflows feature with a builder UI, including support for templates, as shown across the release's Workflows UI screens.

— Only illustrated via screenshots; no written mechanism given Release Notes 2026 (2026-09-29)
22 00
Password Manager Desktop item sorting by nickname Not checked yet new 25

Adds item sorting by nicknames in the Password Manager Desktop App.

— Bare mention with no further mechanism What’s New: Password Manager Desktop App (20…
23 00
Trial recap summary Not checked yet new 15

Adds a trial recap feature summarizing feature usage during a JumpCloud trial.

— Bare description with no mechanism or location Release Notes 2022 (2026-09-29)
24 11
MCP Server Not checked yet new 10

Adds an MCP ServerMCP ServerA process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. as part of JumpCloud's 2025 platform additions.

— Named only in summary, no further detail given Release Notes 2025 (2026-09-29)
25 12
AI Commands Builder Not checked yet new 10

Adds an AI Commands Builder as part of JumpCloud's 2025 platform additions.

— Named only in summary, no further detail given Release Notes 2025 (2026-09-29)
└──▷ ALSO FROM THESE RELEASES
Subscribe to JumpCloud product and agent release note feeds so your RSS reader automatically surfaces new capability announcements.
📍1. Go to the Release Notes and Bug Fixes page in the JumpCloud Help Center. 2. Click Subscribe to Release Notes and Bug Fixes RSS Feed to receive product release notes, agent release notes, and bug fix reports. 3. (Optional) Click Subscribe to Agent Release Notes RSS Feed for agent-only updates. 4. Open your RSS reader and add the feed URL to begin receiving updates automatically.
└──▷ BREAKING ON UPGRADE
  • !
    The GET api/systemusers/reactivate/{id} endpoint is deprecated and now returns a 404 error; replace all usages with POST https://console.jumpcloud.com/systemusers/reactivate/{id} with activation_email in the request body.
  • !
    The $le and $ge filter operators in Dynamic Groups memberQuery API filters are deprecated; replace with $lte and $gte respectively in all API requests.
  • !
    LDAP TLS connections that used CBC-mode or SHA-1/SHA-256 cipher suites (including those with RSA or ECDHE key exchange) are no longer accepted; only TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, and TLS_RSA_WITH_AES_128_GCM_SHA256 are permitted.
  • !
    The .appimage Linux build is no longer supported as of April 18, 2024 (v. 2.2.197); switch to the RPM or Debian build.
Release Notes 2022 (2026-09-29) Blog Stable

JumpCloud: Adds new macOS software management policies to delay or block upgrades to macOS 13 Ventura on managed devices.

└──▷ HOW TO FIND IT
Deploy the SentinelOne Agent across your Linux fleet from the JumpCloud Admin Portal using the Commands feature — no manual distribution needed.
📍In the Admin Portal, go to Commands › New Command, select the target OS (macOS, Windows, or Linux), paste the SentinelOne Agent installation script, and run it against your device group.
Block macOS 13 Ventura upgrades on managed devices while your team validates app compatibility.
📍In the Admin Portal, go to Device Management › Policies › New Policy, select macOS and choose the Ventura delay/block software management policy, then bind it to the relevant device group.
Enforce disk-encryption-based Conditional AccessConditional AccessA policy enforcement framework, most commonly Microsoft's in Entra ID, that grants or blocks resource access based on signals like user identity, device state, and location — letting cyber tools trigger step-up auth or deny risky sessions. to protect sensitive SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. resources on unencrypted endpoints.
📍In the Admin Portal, go to Security › Conditional Access › New Policy, add a Device Condition for Disk Encryption set to Enabled, and apply the policy to the target SSO application.
  • Adds Microsoft 365 integration support for M365/Azure AD security groups. Not checked yet
  • Adds MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. Upcoming Certificate Expirations widget to the JumpCloud Homepage (single-org view).
  • Adds trial recap feature summarizing feature usage during a JumpCloud trial.
  • Adds MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. Upcoming Certificate Expirations widget to the JumpCloud Homepage (single-org view).
  • Adds trial recap feature summarizing feature usage during a JumpCloud trial.

1 more in Everything

Release Notes 2024 (2026-09-29) Blog Stable

JumpCloud: Adds POST https://console.jumpcloud.com/systemusers/reactivate/{id} endpoint to replace the deprecated GET api/systemusers/reactivate/{id}.

└──▷ TRY IT
Reactivate a user account using the new POST endpoint after removing the deprecated GET call from scripts or automations.
$ curl -s -X POST 'https://console.jumpcloud.com/systemusers/reactivate/<user_id>' -H 'x-api-key: <your-api-key>' -H 'Content-Type: application/json' -d '{"activation_email": "user@example.com"}'
Enforce MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. for all MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. admins across the tenant from the Multi-Tenant Portal to close gaps where individual admin accounts had MFA disabled.
📍In the Admin Portal, go to Account › Settings, then locate Global MFA Requirement and enable the setting.
  • Adds full Android 15 support in MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.. Not checked yet
  • Adds multiple IP address support to RADIUSRADIUSA networking protocol for centralised authentication, authorisation, and accounting of users connecting to a network, maintained under IETF standards. Cyber tools use it to integrate with existing enterprise identity infrastructure. server configuration. Not checked yet

2 more in Everything

└──▷ BREAKING ON UPGRADE
  • !The GET api/systemusers/reactivate/{id} endpoint is deprecated and now returns a 404 error; replace all usages with POST https://console.jumpcloud.com/systemusers/reactivate/{id} with activation_email in the request body.
  • !The $le and $ge filter operators in Dynamic Groups memberQuery API filters are deprecated; replace with $lte and $gte respectively in all API requests.
Release Notes 2025 (2026-09-29) Blog Stable

JumpCloud adds Access Requests, MCP ServerMCP ServerA process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface., AI Commands Builder, Shadow AI Dashboard, Custom Admin Roles, and major SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management./MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. enhancements in 2025.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Configure an Access Request approval flow so users must request and receive admin approval before gaining access to a sensitive application, with automatic JIRA ticket creation.
📍In the JumpCloud Admin Portal, go to Access Requests › Create Approval Flow, assign approvers, enable webhook integration, and enter your JIRA webhook URL so tickets are created automatically on each new request submission.
  • Adds sso_auth event to logs for forced re-authentication events, providing audit visibility for compliance and security reviews.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Not checked yet
  • Adds ForceAuthn='true' (SAMLSAMLA standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider.) and prompt=login (OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user.) support so applications can trigger step-up authentication without ending the user's existing session. Not checked yet
  • Includes Authentication Methods References (AMRAMRAutonomous Mobile Robot — a self-navigating wheeled platform that maps its environment and plans its own path; cyber tools might target AMR firmware or fleet-management APIs in OT/ICS assessments.) claims in SAML assertions and OIDC ID tokens, tagging logins with proof of factors used (e.g., password + OTPOTPOne-time password: a short-lived numeric or alphanumeric code valid for a single authentication attempt, generated via TOTP or HOTP standards, giving cyber tools phishing-resistant second-factor verification without stored shared secrets.). Not checked yet
  • Extends Mac Personalization policies with updates to Dock Settings and Items and Lock Screen (Screen Saver) policies.
  • Adds Windows 11 25H2 support for JumpCloud Windows management components.
+1 more show less
  • Restricts LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. TLS connections to five strong cipher suites: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, and TLS_RSA_WITH_AES_128_GCM_SHA256, removing weak CBC-mode and SHA-1SHA-1A cryptographic hash function standardized by NIST that produces a 160-bit digest; tools use it for file integrity checks, though it is now considered cryptographically broken and unsuitable for collision-resistant applications./SHA-256SHA-256A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data. suites.
  • Adds sso_auth event to logs for forced re-authentication events, providing audit visibility for compliance and security reviews.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Not checked yet
  • Adds ForceAuthn='true' (SAMLSAMLA standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider.) and prompt=login (OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user.) support so applications can trigger step-up authentication without ending the user's existing session. Not checked yet
  • Includes Authentication Methods References (AMRAMRAutonomous Mobile Robot — a self-navigating wheeled platform that maps its environment and plans its own path; cyber tools might target AMR firmware or fleet-management APIs in OT/ICS assessments.) claims in SAML assertions and OIDC ID tokens, tagging logins with proof of factors used (e.g., password + OTPOTPOne-time password: a short-lived numeric or alphanumeric code valid for a single authentication attempt, generated via TOTP or HOTP standards, giving cyber tools phishing-resistant second-factor verification without stored shared secrets.). Not checked yet

3 more in Everything

└──▷ BREAKING ON UPGRADE
  • !LDAP TLS connections that used CBC-mode or SHA-1/SHA-256 cipher suites (including those with RSARSAThe oldest widely used public-key algorithm, for both encryption and signatures, with security resting on factoring large numbers. A large quantum computer would break it. or ECDHE key exchange) are no longer accepted; only TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, and TLS_RSA_WITH_AES_128_GCM_SHA256 are permitted.
Release Notes 2026 (2026-09-29) Blog Stable

JumpCloud: Adds Password Vault in the User Portal (accessible from left navigation after login), supporting credential creation, sharing, personal and shared folders, and bulk import via CSV or Excel file.

└──▷ HOW TO FIND IT
Upload an internal runbook to the AI Assistant knowledge base so the assistant can answer org-specific process questions.
📍In the Admin Portal, navigate to AI Assistant › Knowledge Base, click Upload, select a PDF, TXT, DOCX, or MD file (up to 10 MB), and confirm. Repeat for up to 25 files per org.
Configure an AI agent to authenticate with Amazon Bedrock AgentCore, which requires credentials in the request body rather than the header.
📍In the Admin Portal, open the agent, go to the Authentication tab, and set the client authentication type to Client secret post so the client ID and secret are sent in the request body when requesting a token.
Immediately remediate critical missing patches across non-compliant Windows devices without waiting for the next policy window.
📍In the Admin Portal, go to Device Management › Patch Management › Windows, apply the Critical severity filter, then select affected devices and choose Install missing critical patches to trigger immediate remediation.
  • Adds a unified Patch Management dashboard under Device Management > Patch Management with Overview, Apple, and Windows tabs, severity filters, KB search, CVE detail review, CSV/JSON export of KB list, and bulk remediation.
  • Improves Dormant Application Access detection in Access Risk > Configuration to trigger only on re-access after inactivity (not first-time access), reducing noise from newly provisioned apps.
  • Adds a unified Patch Management dashboard under Device Management > Patch Management with Overview, Apple, and Windows tabs, severity filters, KB search, CVE detail review, CSV/JSON export of KB list, and bulk remediation.

1 more in Everything

Was this useful?

Ping Identity

Sources Blog / feed → 28 Sep 2026 (2026-09-29) Blog Rank Why this rank top features scored 85/80/80, +15 breaking change, +10 product media, +6 runnable example — 112.67 How ranking works →

Read docs, explore use cases, learn best practices

Ping Identity's Authorize gateway now fails closed instead of continuing to run unhealthy when it can't retrieve policy, while the Advanced Identity Cloud admin console picks up a broad set of additions spanning SAMLSAMLA standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. metadata import, email provider configuration, telephone user properties, node designer, navigation profiles and journey canvas UX.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 11 FEATURES 0 OF 11 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Navigation profiles for hosted account pages Not checked yet new 85

Enables customization of the hosted account pages navigation menu for different user groups using navigation profiles, configured via Hosted Pages > Navigation Profiles by creating a profile, defining menu items, and assigning it to a target group.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Serve tailored navigation menus to different user groups on hosted account pages by assigning navigation profiles per group.
📍In the Advanced Identity Cloud admin console, go to Hosted Pages › Navigation Profiles, create a profile for a user group, define the menu items, then assign the profile to the target group.
— Full UI path and steps make this immediately actionable. 28 Sep 2026 (2026-09-29)
02 00
Skip XML signature check on SAML metadata import Not checked yet new 80

Adds ability to skip XML signature verification when importing remote SAML 2.0SAML 2.0A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. provider metadata by enabling Skip XML signature verification during import, avoiding failures when a partner's metadata lacks a valid signature.

Skip signature validation when federating with a partner whose SAML 2.0 metadata lacks a valid XML signature, avoiding import failures.
📍In the admin console, go to Federation › Entity Providers › Import Remote Provider, upload the metadata file, and enable Skip XML signature verification before saving.
— Exact UI navigation and toggle name make this directly usable. 28 Sep 2026 (2026-09-29)
03 00
Entra ID and SMTP email provider configuration Not checked yet new 80

Enables configuration of Microsoft Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. or custom SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure. email providers and test-email sending from the Advanced Identity Cloud admin console, via Settings > Email Provider, selecting Microsoft Entra ID or Custom SMTP, entering connection details, and sending a test email to confirm delivery.

Configure a Microsoft Entra ID or custom SMTP email provider and verify delivery with a test email before rolling out to users.
📍In the Advanced Identity Cloud admin console, go to Settings › Email Provider, select Microsoft Entra ID or Custom SMTP, fill in the connection details, then click Send Test Email to confirm.
— Exact console path and steps to configure and verify delivery. 28 Sep 2026 (2026-09-29)
04 00
Authorize gateway fails closed on policy retrieval failure Not checked yet breaking 75

Authorize gateway 1.2.2 now logs an error and shuts down when it cannot retrieve the latest authorization policy version from PingOne or the locally stored deployment configuration, replacing the previous behavior of remaining alive but unable to serve decision requests. Any monitoring or restart logic that assumed a running-but-unhealthy gateway process must be updated.

— Clear before/after behavior described, but no config key or command to act on. product docs
05 00
Telephone number as user property format Not checked yet new 60

Supports telephone number as a user property format, with optional server-side validation and separate country code and phone number fields in journeys.

— Mechanism described but no exact configuration path given. 28 Sep 2026 (2026-09-29)
06 00
LexisNexis DDP Profiler script injection location Not checked yet new 60

Allows configuring the LexisNexis DDP Profiler node to inject scripts in the head element or in an iframe.

— Names the concrete injection targets but no config steps. 28 Sep 2026 (2026-09-29)
thinner coverage below
07 00
Target phase selection for reconciliations Not checked yet new 50

Adds runTargetPhase selection in the Advanced Identity Cloud admin console when running reconciliations.

— Names the property but gives no navigation path or example. 28 Sep 2026 (2026-09-29)
08 00
Journey canvas panning and multi-node selection Not checked yet improved 50

Enables panning journey canvases by holding the space bar and dragging with the left mouse button, and enables selecting multiple journey nodes by holding Shift and clicking each node.

— Exact key and mouse combinations given, directly usable. 28 Sep 2026 (2026-09-29)
09 00
Multi-value custom node properties Not checked yet new 45

Allows selection of multiple values from predefined options when configuring custom node properties in the node designer.

— States the capability but no steps or example to follow. 28 Sep 2026 (2026-09-29)
10 00
Next-generation scripting engine now default Not checked yet improved 40

Makes the next-generation scripting engine the default and recommended option when creating scripts in the Advanced Identity Cloud admin console.

— Describes the change but no detail on what differs in the engine. 28 Sep 2026 (2026-09-29)
11 00
Search and sort for AI agent identities Not checked yet new 25

Adds search and sort capabilities for the list of AI agent identities.

— Bare mention with no mechanism or navigation detail. 28 Sep 2026 (2026-09-29)
└──▷ ALSO FROM THESE RELEASES
└──▷ BREAKING ON UPGRADE
  • !
    Authorize gateway 1.2.2 will shut down (instead of staying alive) when it cannot reach PingOne or load its local deployment configuration — any monitoring or restart logic that assumed a running-but-unhealthy gateway process must be updated.
  • !
    Authorize gateway instances that previously stayed alive in an unhealthy state when policy retrieval failed will now shut down on upgrade to 1.2.2 — any automation or health-check logic that relied on the instance remaining running in that scenario will need to be updated.
28 Sep 2026 (2026-09-29) Blog LatestStable

Ping Identity adds multi-value node properties, telephone format, Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments./SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure. email config, SAMLSAMLA standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. signature skip, and more in Sep 2026 release.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Skip signature validation when federating with a partner whose SAML 2.0SAML 2.0A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. metadata lacks a valid XML signature, avoiding import failures.
📍In the admin console, go to Federation › Entity Providers › Import Remote Provider, upload the metadata file, and enable Skip XML signature verification before saving.
Configure a Microsoft Entra ID or custom SMTP email provider and verify delivery with a test email before rolling out to users.
📍In the Advanced Identity Cloud admin console, go to Settings › Email Provider, select Microsoft Entra ID or Custom SMTP, fill in the connection details, then click Send Test Email to confirm.
Serve tailored navigation menus to different user groups on hosted account pages by assigning navigation profiles per group.
📍In the Advanced Identity Cloud admin console, go to Hosted Pages › Navigation Profiles, create a profile for a user group, define the menu items, then assign the profile to the target group.
  • Adds runTargetPhase selection in the Advanced Identity Cloud admin console when running reconciliations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds ability to skip XML signature verification when importing remote SAML 2.0 provider metadata.
  • Enables configuration of Microsoft Entra ID or custom SMTP email providers and test-email sending from the Advanced Identity Cloud admin console.
  • Supports telephone number as a user property format, with optional server-side validation and separate country code and phone number fields in journeys.
  • Allows selection of multiple values from predefined options when configuring custom node properties in the node designer.
+6 more show less
  • Enables customization of the hosted account pages navigation menu for different user groups using navigation profiles.
  • Adds search and sort capabilities for the list of AI agent identities.
  • Makes the next-generation scripting engine the default and recommended option when creating scripts in the Advanced Identity Cloud admin console.
  • Allows configuring the LexisNexis DDP Profiler node to inject scripts in the head element or in an iframe.
  • Enables panning journey canvases by holding the space bar and dragging with the left mouse button. Not checked yet
  • Enables selecting multiple journey nodes by holding Shift and clicking each node.
  • Adds runTargetPhase selection in the Advanced Identity Cloud admin console when running reconciliations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds ability to skip XML signature verification when importing remote SAML 2.0 provider metadata.
  • Enables configuration of Microsoft Entra ID or custom SMTP email providers and test-email sending from the Advanced Identity Cloud admin console.
  • Enables customization of the hosted account pages navigation menu for different user groups using navigation profiles.

7 more in Everything

Was this useful?

ConductorOne

Sources Blog post → announced · Sep 29, 2026 Blog Rank Why this rank top features scored 70/65/65, +10 product media — 76.67 How ranking works →

ConductorOne is an identity governance platform that automates workforce access management and deploys AI agents to streamline access reviews and provisioning.

ConductorOne now handles OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. sign-in, AuthZENAuthZENAn OpenID Foundation working group specification that standardises the API between policy enforcement points and policy decision points, letting cyber tools swap authorization engines without rewriting integration code. real-time authorization, and governed access requests for AI-built apps, eliminating local user tables and stale permission snapshots.

  • New integrationActs as a standard OIDC provider for AI-built applications, federating authentication to the company's existing identity provideridentity providerA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. without requiring a separate user table or login page.
  • New integrationAdds an OpenID AuthZENOpenID AuthZENAn emerging standard from the OpenID Foundation that defines a common API for querying authorization engines, letting cyber tools swap policy decision points without rewriting integration code. authorization endpoint so AI-built apps can query ConductorOne for real-time, per-request access decisions instead of relying on stale local role snapshots. Not checked yet
  • Surfaces access-denied events as governable access requests: employees can submit a request from within the application, owners review it with context, and time-bound access is granted or denied without a code change or redeploy.
  • Makes AI-built application access a ConductorOne entitlement, bringing it into existing request, approval, access-review, certification, and revocation workflows alongside all other governed systems.

4 details in Everything

1 more release in this issue · 2026-09-28 → 2026-09-29
announced · Sep 28, 2026 Blog

ConductorOne launches C1 AppHub, a self-hosted internal app platform connecting AI-built apps to identity, authz, credentials, and model access.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Introduces C1 AppHub, a self-hosted internal application platform that wires each new app to ConductorOne identity, authorization, credential/token vending, network access, and model access without per-app custom integrations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • AppHub apps are added to C1.ai's identity graph alongside every other connected system, each with an assigned owner, enabling inclusion in access reviews and offboarding workflows.
  • Supports a skills file that teaches coding agents the company's approved development pattern — directing them to use C1.ai for sign-in, authorization, credential and token vending, network access, and model access as the app is built.
  • Available as a public repository so teams can inspect the architecture, run it in their own environment, and adapt the integration pattern to their needs.

4 details in Everything

Was this useful?

Auth0

Sources Blog post → announced · Sep 28, 2026 Blog Rank Why this rank top features scored 65, +10 product media, +6 runnable example — 81 How ranking works →

Secure users, AI agents, and more with Auth0, an easy-to-implement, scalable, and adaptable authentication and authorization platform.

Auth0 launches a ChatGPT plugin that provisions tenants, generates real SDK code, and queries tenant state via plain-language prompts.

  • New integrationNew Auth0 plugin for ChatGPT connects to a real Auth0 tenant to create applications, configure connections, and adjust settings by plain-language prompt. Not checked yet
  • Generates tenant-matched SDK integration code instead of generic boilerplate. Not checked yet
  • Enables querying and managing tenant state — applications, users, and connections — from within a ChatGPT session. Not checked yet
  • Surfaces Auth0 documentation answers directly inside the ChatGPT conversation.

4 details in Everything

Was this useful?

Material Security

Sources Blog post → announced · Sep 1, 2026 Blog Rank Why this rank top features scored 70/45 — 57.5 How ranking works →

Material Security is an email security platform that uses AI to detect and prevent advanced threats like phishing, malware, and data exfiltration.

Material Security significantly widened programmatic access to its detection platform, extending the Issues API and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server across nearly all resource types, and overhauled how analysts see why a detection fired.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Issues API and MCP server resource expansion Not checked yet improved 70

The Issues API now covers Issues, Messages, Accounts, Groups, Roles, OAuth Apps, and Trusted Entities as addressable resources for programmatic access.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ MCP server tools were broadened to work across issues, messages, accounts, and OAuth apps, including updating Trusted Entities (allowlist management) without touching the UI.

— Names all resource types but no endpoint paths or exact tool calls launch-20260901-8b2dcaca
thinner coverage below
02 00
Detection explanation overhaul on Issue Details page Not checked yet improved 45

The detection explanation experience on the Issue Details page was overhauled to give analysts specific technical evidence for why a detection fired.

— Describes intent but not the actual evidence shown launch-20260901-8b2dcaca
announced · Sep 1, 2026 Blog

Material Security expands its Issues API and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server to cover Issues, Messages, Accounts, Groups, Roles, OAuth Apps, and Trusted Entities.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Expands the Issues API to cover Issues, Messages, Accounts, Groups, Roles, OAuth Apps, and Trusted Entities as addressable resources for programmatic access.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Broadens MCP server tools to work across issues, messages, accounts, and OAuth apps — including updating Trusted Entities (allowlist management) without touching the UI.
  • Overhauled the detection explanation experience on the Issue Details page to give analysts specific technical evidence for why a detection fired.
  • Expands the Issues API to cover Issues, Messages, Accounts, Groups, Roles, OAuth Apps, and Trusted Entities as addressable resources for programmatic access.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

2 more in Everything

Was this useful?
◆  Secure Access (VPN / SASE / ZTNA)

DNSFilter

Sources Blog / feed → 09/29 September 29 – Web Application and API Update (2026-09-29) Blog Rank Why this rank top features scored 55/50 — 52.5 How ranking works →

Give feedback to the DNSFilter team so we can make more informed product decisions. Powered by Canny.

DNSFilter widened access to the Branding settings page for MSPsMSPsA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. and enriched the Unblock Requests grid with category data even for non-category blocks.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Branding settings for MSPs without custom domain Not checked yet improved 55

The Branding settings page is now extended to MSPs that do not have a custom domain configured, replacing the legacy Whitelabel form; existing logos are carried over automatically.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Names the surface and migration behavior but no exact UI path 09/29 September 29 – Web Application and API…
02 00
Category data in Unblock Requests grid Not checked yet improved 50

The Category column in the Unblock Requests grid now shows domain category information even when a domain was blocked for a non-category reason, such as Block List, AppAware, or Security block.

— Describes exact grid and block reasons but no config or command 09/29 September 29 – Web Application and API…
09/29 September 29 – Web Application and API Update (2026-09-29) Blog LatestStable

DNSFilter expands Branding settings to more MSPsMSPsA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. and adds richer category data to Unblock Requests reviews.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Extends the Branding settings page to MSPs without a custom domain configured, replacing the legacy Whitelabel form, with existing logos carried over automatically.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds domain category information to the Category column in the Unblock Requests grid even when a domain was blocked for a non-category reason (Block List, AppAware, or Security block).
  • Extends the Branding settings page to MSPs without a custom domain configured, replacing the legacy Whitelabel form, with existing logos carried over automatically.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

1 more in Everything

Was this useful?

Firezone

Sources Blog post → announced · Sep 24, 2026 Blog Rank Why this rank top features scored 90/35, +6 runnable example — 68.5 How ranking works →

Replace your VPN with Firezone, an open-source zero trust access platform built on WireGuard®. Connect users to anything, anywhere.

Firezone shipped a new firezone CLI for its desktop clients, adding tunnel management, Resource visibility, and a headless sign-in path for service accounts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
firezone CLI for tunnel control and unattended sign-in Not checked yet new 90

Firezone desktop clients on macOS (v1.5.21+), Windows, and Linux (v1.5.18+) now ship with a firezone CLI for managing tunnel state, viewing Resources, and enabling or disabling the Internet Resource.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ A new firezone connect command reads a service-account token from stdin or the FIREZONE_TOKEN environment variable, enabling unattended/headless tunnel connections that were not officially supported before.

Authenticate a headless server or CI runner with a service-account token without interactive prompts.
$ echo "$SERVICE_ACCOUNT_TOKEN" | firezone connect
# or
export FIREZONE_TOKEN="$SERVICE_ACCOUNT_TOKEN"
firezone connect
— Names exact command, env var, platform versions, and a runnable example. launch-20260924-1573d61e
thinner coverage below
02 00
macOS subcommand for system extension management Not checked yet new 35

The firezone CLI exposes a macOS-only subcommand for managing the system extension.

— Mentions the subcommand exists but no flags or usage detail given. launch-20260924-1573d61e
announced · Sep 24, 2026 Blog

Firezone desktop clients (macOS, Windows, Linux) now ship with a firezone CLI for tunnel control and unattended service-account sign-in.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ TRY IT
Authenticate a headless server or CI runner with a service-account token without interactive prompts.
$ echo "$SERVICE_ACCOUNT_TOKEN" | firezone connect
# or
export FIREZONE_TOKEN="$SERVICE_ACCOUNT_TOKEN"
firezone connect
  • Adds firezone connect command that reads a service-account token from stdin or the FIREZONE_TOKEN environment variable, enabling unattended/headless tunnel connections that were not officially supported before.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Not checked yet
  • Adds the firezone CLI to macOS (v1.5.21+), Windows, and Linux (v1.5.18+) desktop clients for managing tunnel state, viewing Resources, and enabling or disabling the Internet Resource. Not checked yet
  • Exposes a macOS-only firezone subcommand for managing the system extension. Not checked yet

3 details in Everything

Was this useful?
◆  Public Key Infrastructure (PKI)

DigiCert CertCentral

Sources Blog post → announced · Sep 27, 2026 Blog Rank Why this rank top features scored 55/53/50 — 52.67 How ranking works →

DigiCert CertCentral is a centralized platform for managing SSL/TLS certificates, automating issuance, renewal, and deployment across organizations.

DigiCert extended AI Trust Manager to bring cryptographic AI Passports to agents, models, and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers running inside NVIDIA's OpenShell sandbox, adding AIBOMAIBOMAn inventory of every AI model, dataset, and dependency used in a system, analogous to a software bill of materials, giving cyber tools a structured way to audit AI supply-chain risk.-based signing and scanning, a signed audit trail anchored to its AI Root of Trust, and a policy-based kill switch.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 4 FEATURES 4 OF 4 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
AI Passport identity for OpenShell agents Not checked yet new 55

DigiCert AI Trust Manager now issues AI Passports for every agent, model, and MCP server running inside an NVIDIA OpenShell sandbox, giving each a cryptographic PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets.-rooted identity that OpenShell policy can act on instead of a name in a config file.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Explains mechanism (PKI-rooted identity) but no setup steps given. launch-20260927-44f983f0
02 02
Signed audit trail for OpenShell allow/deny decisions Not checked yet new 53

Adds signed, auditable records anchored to the DigiCert AI Root of Trust for every OpenShell allow/deny decision, with confidential-compute attestation attached where applicable.

— Names the anchoring trust root and attestation but not access steps. launch-20260927-44f983f0
03 03
Policy-based kill switch for agents Not checked yet new 50

Adds a policy-based, automated, enforceable kill switch, powered by AI Passport identity, that lets customers stop any agent for any reason across organizational boundaries.

— Describes behaviour and scope but no invocation mechanism. launch-20260927-44f983f0
04 04
AIBOM signing and scanning before launch Not checked yet new 48

Adds signing and scanning of agents, models, and MCP servers with an AI Bill of MaterialsBill of MaterialsA structured list of every component, library, and dependency that makes up a piece of software or hardware, used by cyber tools to track what is inside a product and surface known vulnerabilities in its parts. (AIBOM) before a sandbox launches them.

— Names the AIBOM format but no workflow or command detail. launch-20260927-44f983f0
announced · Sep 27, 2026 Blog

DigiCert AI Trust Manager now issues AI Passports for agents running in NVIDIA OpenShell, adding cryptographic identity and a kill switch.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds AI Passport issuance for every agent, model, and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server running inside an NVIDIA OpenShell sandbox, providing cryptographic PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets.-rooted identity that OpenShell policy can act on instead of a name in a config file.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds signing and scanning of agents, models, and MCP servers with an AI Bill of MaterialsBill of MaterialsA structured list of every component, library, and dependency that makes up a piece of software or hardware, used by cyber tools to track what is inside a product and surface known vulnerabilities in its parts. (AIBOMAIBOMAn inventory of every AI model, dataset, and dependency used in a system, analogous to a software bill of materials, giving cyber tools a structured way to audit AI supply-chain risk.) before a sandbox launches them.
  • Adds signed, auditable records anchored to the DigiCert AI Root of Trust for every OpenShell allow/deny decision, with confidential-compute attestation attached where applicable.
  • Adds a policy-based, automated, enforceable kill switch — powered by AI Passport identity — that lets customers stop any agent for any reason across organizational boundaries.

4 details in Everything

Was this useful?
Governance, Risk & Compliance
◆  Continuous Control Monitoring (CCM)

RegScale

Sources Blog / feed → CLI 6.49.5 (2026-09-28) Blog LatestStable Rank Why this rank top features scored 70/50/45, +6 runnable example — 61 How ranking works →

RegScale is a compliance and security governance platform that automates regulatory assessment, documentation, and continuous monitoring across organizations.

Adds an about command to the Axonius v2 integration to display connected instance details.

1 more release in this issue · 2026-09-28
CLI 6.49.0 (2026-09-28) Blog Stable

RegScale CLI 6.49.0 enriches Wiz STIGSTIGA configuration standard published by DISA that specifies hardening requirements for a given OS, application, or device, giving cyber tools a concrete checklist to audit or enforce against./CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline. findings with per-criteria observations and expands Ports & Protocols coverage to VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. and cross-account paths.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Wiz STIG and CIS benchmark results now record, in each control test's observations, which configuration criteria produced the pass or fail result and what Wiz found on the host.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Wiz Ports and Protocols records now include ports reachable over VPN and from another cloud account.
  • Wiz STIG and CIS benchmark results now record, in each control test's observations, which configuration criteria produced the pass or fail result and what Wiz found on the host.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

1 more in Everything

Was this useful?
Agent
◆  MCP Servers & Tooling

Runlayer

Sources Blog / feed → 1.28.869 (2026-09-29) Blog Rank Why this rank top features scored 93/91/80, +15 breaking change, +6 runnable example — 109 How ranking works →

Runlayer is an MCP gateway that enforces identity-mapped permissions and detects threats across the agents and MCP servers employees use.

Runlayer's Terraform ECSECSElastic Common Schema, an open specification maintained by Elastic that defines a standard field naming convention for log and event data, letting cyber tools share and correlate records without per-source field mapping. module gained a standalone session-search indexer and an identity-aware sandbox egress proxy for AgentCore, while the product added Claude Sonnet 5.5 and Bedrock-backed Slack monitor support, expanded AI Watch Detect's browser inventory to 32 Chromium-based AI browsers, and restricted Shadow AI Scan key creation to the MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. wizard alongside a breaking change to flow-metric collection defaults.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 20 FEATURES 0 OF 20 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Identity-aware sandbox egress proxy for AgentCore Not checked yet new 93

Adds sandbox_egress_mode (values direct, proxy, proxy_only; default direct) to control how AgentCore sandboxes reach the internet, with proxy and proxy_only requiring runlayer_agentcore_network_mode = VPC; sandbox_egress_proxy_image_uri to override the proxy container image (must include an explicit tag or digest); sandbox_egress_proxy_dns_servers (default ["1.1.1.1", "8.8.8.8"]) for upstream DNS resolution; sandbox_egress_proxy_platform_allow_hosts for additional allowed host patterns (host, *.host, optional :port); and sandbox_egress_proxy_egress_ports (default [443]) for extra TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. ports the proxy's security group may open.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ A FF_ENABLE flag sandbox-egress-proxy, set via additional_backend_env_vars, must be enabled per organization and rolled out before switching to sandbox_egress_mode = "proxy_only" — doing so without the flag enabled first leaves organizations without sandbox internet access for several minutes.

Enable the identity-aware egress proxy for agent sandboxes so outbound traffic is filtered by organization policy rather than allowed directly through NAT.
hcl
sandbox_egress_mode                  = "proxy"
runlayer_agentcore_network_mode      = "VPC"
sandbox_egress_proxy_dns_servers     = ["1.1.1.1", "8.8.8.8"]
sandbox_egress_proxy_egress_ports    = [443, 8080]
sandbox_egress_proxy_platform_allow_hosts = ["*.mycompany.internal"]
Enable the sandbox egress proxy for all organizations before cutting over to proxy-only mode to avoid a gap in sandbox internet access.
hcl
additional_backend_env_vars = { FF_ENABLE = "<flags already forced>,sandbox-egress-proxy" }
After the backend rollout completes, enforce proxy-only egress so no sandbox run bypasses the proxy.
hcl
sandbox_egress_mode = "proxy_only"
— Every config key, default, and rollout sequencing named with examples. product docs
02 00
Standalone session-search indexer for ECS deployments Not checked yet new 91

Adds enable_session_search_indexer to deploy a standalone Kinesis consumer that extracts searchable text, entities, and findings from hook events and writes the session-search index tables in Postgres (opt-in, requires enable_hook_events_pipeline = true). session_search_indexer_config sets ECS cpu (minimum 256) and memory (minimum 1024); session_search_index_mode (off, shadow, write) controls whether the service only parses (shadow), writes real indexes and enables the coverage-gap alarm (write), or scales to 0 while preserving checkpoint state (off); and session_search_indexer_extra_env allows passthrough env vars prefixed SESSIONS_SEARCH_ or FF_ENABLE/FF_DISABLE, such as SESSIONS_SEARCH_FLUSH_SECONDS and SESSIONS_SEARCH_MAX_ROWS_PER_SECOND.

Enable the session-search indexer in soak mode first so you can validate extraction metrics before committing real index writes.
hcl
enable_session_search_indexer     = true
enable_hook_events_pipeline       = true
session_search_index_mode         = "shadow"
session_search_indexer_config     = {
  cpu    = 512
  memory = 2048
}
Promote to write mode and tune flush frequency without changing the module, using the FF_ENABLE flag to bypass per-org feature gates in staging.
hcl
session_search_index_mode = "write"
session_search_indexer_extra_env = {
  SESSIONS_SEARCH_FLUSH_SECONDS = "5"
  FF_ENABLE                     = "session-search-ingest"
}
— Full mechanism, all config keys, and runnable HCL examples. product docs
03 00
Standalone Kinesis consumer services for SIEM export and analytics Not checked yet new 80

Adds audit_log_siem_export_kinesis_consumer_config to run a standalone service exporting enriched SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. objects from the audit-log Kinesis stream (cpu >= 256, memory >= 512, desired_count >= 1); session_materializer_config for a Kinesis consumer that reads the hook-events stream and performs segment compaction (cpu >= 256, memory >= 3072, desired_count >= 0); cold_analyzers_consumer_config for a consumer reading the hook-events stream (cpu >= 256, memory >= 2048, desired_count >= 0); and session_siem_export_kinesis_consumer_config for a service writing gzipped NDJSONNDJSONA text format where each line is a self-contained JSON object, making it easy to stream, append, and parse large datasets record-by-record without loading the whole file into memory. to a managed or external S3 bucket (cpu >= 256, memory >= 2048, desired_count >= 1).

Ship audit-log SIEM data to a downstream system by enabling the standalone Kinesis consumer ECS service with enough capacity for production-volume audit records.
hcl
audit_log_siem_export_kinesis_consumer_config = {
  enabled       = true
  cpu           = 512
  memory        = 1024
  desired_count = 2
}
— Four named services with exact resource minimums and one example. product docs
04 00
OTLP Telemetry organization API key permission Not checked yet new 78

Adds a new write-only OTLP Telemetry organization API key permission for OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. ingestion (logs, metrics, traces) from AI clients such as Claude Code, Claude Cowork, and Glean; created from the Organization API keys page and must be the key's only permission — it cannot also use the AI Watch scan or hook endpoints.

Set up OTLPOTLPOpenTelemetry Protocol, a standard way to send traces, metrics and logs between applications, collectors and monitoring systems. It lets telemetry move across compatible tools. telemetry ingestion from Claude Code into Runlayer by creating a write-only OTLP Telemetry API key scoped to OpenTelemetry only.
📍In the Runlayer console, go to Organization API keys → Create key, select the OTLP Telemetry permission (must be the only permission), then configure your Claude Code exporter to send logs, metrics, and traces to your Runlayer OTLP endpoint using the generated key.
— Named permission, named clients, and exact setup steps. 1.28.845 (2026-09-28)
05 00
Flow-metric collection now defaults on with observability export Not checked yet breaking 75

With observability OTLP export on and tooling export off, backend flow-metric collection now defaults on; operators must explicitly set flow_metrics_collection_enabled = false in their Terraform ECS inputs to opt out of the newly-automatic collection.

Opt out of automatic flow-metric collection when running obs-only OTLP export without tooling export, to avoid unexpected data ingestion.
hcl
flow_metrics_collection_enabled = false
— Clear before/after default change with an exact opt-out command. 1.28.869 (2026-09-29)
06 00
Pi and Oh My Pi agent integration Not checked yet new 75

Adds a Pi integration guide enabling agents built on Pi to route MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tools through Runlayer, enforce policy on local tools like bash, and record activity in Sessions; adds an Oh My Pi (omp) tab in the connector setup guide with a one-line /mcp add command that signs in and saves the connector.

Connect an Oh My Pi agent to Runlayer governance in one step, routing its MCP tools through Runlayer policy enforcement.
$ /mcp add
— Names the integration, policy scope, and a runnable command. 1.28.845 (2026-09-28)
07 00
VPC/PrivateLink network mode for AgentCore Not checked yet new 74

Adds runlayer_agentcore_network_mode Terraform input requiring PUBLIC or VPCVPCA logically isolated virtual network inside a public cloud provider's infrastructure, letting tools deploy resources with private addressing, controlled routing, and firewall rules without managing physical hardware.; VPC mode requires enable_privatelink = true and either runlayer_agentcore_consumer_vpc_id with runlayer_agentcore_consumer_private_subnet_ids, or runlayer_agentcore_consumer_vpc_cidr_block with matching private and public subnet CIDRCIDRA notation for a block of IP addresses, such as 10.0.0.0/24. The number after the slash says how many leading address bits identify the network. lists.

— Exact input and dependency chain, no runnable example given. product docs
08 00
Bedrock-backed Claude access for Slack monitors Not checked yet new 74

Adds BEDROCK_ENABLED support to the agent-event-trigger consumer, granting nonstreaming bedrock:InvokeModel access to Claude foundation models and deployment-account Claude inference profiles for legacy platform fallback, plus sts:AssumeRole grants scoped to arn:aws:iam::*:role/runlayer-bedrock-* and arn:aws:iam::*:role/RunlayerBedrock* so the ECS task role can assume saved Bedrock provider roles for Slack monitors. Updating the consumer image alone does not install the new IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. permission — the Terraform module must also be upgraded and applied.

— Named env var and IAM ARN patterns with an upgrade caveat. product docs
09 00
Flow-trace collection controls decoupled from export Not checked yet new 69

Adds FLOW_TRACE_COLLECTION_ENABLED to enable or disable backend flow-metric generation independently of export transport (defaults to runlayer_central_otel_enabled || runlayer_obs_otel_enabled), and FLOW_TRACE_ADAPTIVE_SAMPLING_ENABLED as an independent cost lever that sheds local step-recording work even when remote export is off.

Decouple flow-trace collection from OTelOTelAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. export and enable adaptive sampling to reduce cost on high-throughput paths.
hcl
FLOW_TRACE_COLLECTION_ENABLED          = true
FLOW_TRACE_ADAPTIVE_SAMPLING_ENABLED   = true
— Names both env vars and default logic with a config example. product docs
10 00
Extra SNS topics for critical alert fan-out Not checked yet new 62

Adds critical_alerts_extra_sns_topic_arns to fan out critical alarms to extra SNSSNSAmazon Simple Notification Service, a managed pub/sub messaging service from AWS that lets tools fan out alerts or events to multiple subscribers — queues, email, HTTP endpoints, or Lambda functions — without managing broker infrastructure. topics (e.g. an internal Slack relay), capped at 3 extra topics when ToolGuard alarms are enabled (4 when enable_monitoring or critical_alerts_enabled is off).

Route critical CloudWatch alarms to an internal Slack relay SNS topic alongside the default alerting path.
hcl
critical_alerts_extra_sns_topic_arns = [
  "arn:aws:sns:us-east-1:123456789012:slack-critical-relay"
]
— Named key, cap logic, and a runnable example. product docs
thinner coverage below
11 00
AI Watch Detect browser inventory expanded to 32 browsers Not checked yet improved 56

AI Watch Detect now inventories 32 standalone AI browsers built on Chromium — including Perplexity Comet, Dia, Opera Neon, ChatGPT Atlas, Norton Neo, BrowserOS, Fellou, Strawberry Browser, Kahana Oasis, and kweo — on macOS, Windows, and Linux, counting a browser as installed only when its own installation is found.

— Names many browsers and detection logic but no user action. 1.28.869 (2026-09-29)
12 00
Shadow AI Scan keys restricted to MDM wizard Not checked yet breaking 55

Restricts Shadow AI Scan key creation to the MDM configuration wizard only; the Organization API keys page no longer offers the Shadow AI Scan role, and the API rejects hand-created keys with it, ensuring every key links devices and scan data to a configuration card.

— Clear restriction and rejection behavior, navigation only implied. 1.28.845 (2026-09-28)
13 00
AWS workload-identity option for secret stores Not checked yet new 52

Adds secret_stores_allow_aws_workload_identity input to allow AWS secret stores without a role ARN to use the backend ECS task role; intended for single-org self-hosted deployments only.

— Named key and scope note, no example given. product docs
14 00
Connector event triggers open to all workspaces Not checked yet improved 50

Connector event triggers — such as a new Gmail label, Linear issue, or Google Drive file — are now available for agents in every workspace without requiring an access request.

— Names trigger examples and the access-gate removal, no exact path. 1.28.869 (2026-09-29)
15 00
Redirect URI approval guidance Not checked yet new 48

Adds redirect URI approval guidance — the approval screen now shows the path Settings → General → OAuth redirect URIs and lets members copy a shareable link for their admin.

— Exact navigation path named, thin beyond that. 1.28.845 (2026-09-28)
16 00
Faster AI Watch scans via batching and skip logic Not checked yet improved 45

Speeds up AI Watch scans by batching artifact reporting in requests of up to 25 artifacts instead of one request per artifact, reducing traffic against the Runlayer deployment; also skips unchanged plugins already held by the server for the same window as skills, cutting repeat uploads on every scheduled scan tick.

— Explains mechanism and numbers but no user-facing action. 1.28.845 (2026-09-28)
17 00
Claude Sonnet 5.5 for agents Not checked yet new 41

Agents can now run on Claude Sonnet 5.5 via the Anthropic API or AWS Bedrock, with adaptive thinking effort settings.

— Names the model and two access paths but no setup steps. 1.28.869 (2026-09-29)
18 00
Generated chat titles in agent chat list Not checked yet new 40

Adds generated chat titles to an agent's chat list, replacing the first prompt, with rename available from the ⋯ menu.

— Describes the UI behavior and rename path, nothing deeper. 1.28.845 (2026-09-28)
19 00
Fetch deployments button for Azure Foundry provider Not checked yet new 39

Adds a Fetch deployments button when adding or editing an Azure Foundry AI provider, automatically listing models served by the endpoint and populating deployment names.

— Names the UI control and its effect, thin description. 1.28.869 (2026-09-29)
20 00
Availability-zone selection documented for ECS deployment Not checked yet new 32

Documents availability-zone selection for the main VPC, RDS, and the AgentCore consumer VPC, with the plan failing if a listed AZ is not supported in AgentCore.

— Documentation only, no config key or example. product docs
└──▷ BREAKING ON UPGRADE
  • !
    With observability OTLP export on and tooling export off, backend flow-metric collection now defaults on — operators who did not previously collect flow metrics in this configuration must explicitly set flow_metrics_collection_enabled = false in their Terraform ECS inputs to opt out.
  • !
    Updating the consumer image alone does not install the new bedrock:InvokeModel IAM permission — the Terraform module must also be upgraded and applied, or the permission will be missing after rollout.
  • !
    Setting sandbox_egress_mode = "proxy_only" without first enabling the sandbox-egress-proxy feature flag (via additional_backend_env_vars / FF_ENABLE) and waiting for the backend rollout will leave organizations without the flag without sandbox internet access for several minutes.
  • !
    The Organization API keys page no longer offers the Shadow AI Scan role, and the API rejects hand-created keys with that role; Shadow AI Scan keys must now be minted through the MDM configuration wizard.
1.28.869 (2026-09-29) Blog LatestStable

Runlayer 1.28.869 adds AI browser inventory, obs-only flow metrics opt-out, Claude Sonnet 5.5 for agents, and connector event triggers for all workspaces.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ USE IT
Opt out of automatic flow-metric collection when running obs-only OTLPOTLPOpenTelemetry Protocol, a standard way to send traces, metrics and logs between applications, collectors and monitoring systems. It lets telemetry move across compatible tools. export without tooling export, to avoid unexpected data ingestion.
hcl
flow_metrics_collection_enabled = false
  • Adds flow_metrics_collection_enabled = false Terraform ECSECSElastic Common Schema, an open specification maintained by Elastic that defines a standard field naming convention for log and event data, letting cyber tools share and correlate records without per-source field mapping. config key to opt out of backend flow-metric collection when observability OTLP export is on and tooling export is off (collection now defaults on in that mode).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • AI Watch Detect now inventories 16 standalone AI browsers built on Chromium — including Perplexity Comet, Dia, Opera Neon, ChatGPT Atlas, Norton Neo, and BrowserOS — on macOS, Windows, and Linux, counting a browser as installed only when its own installation is found.
  • AI Watch Detect inventories 16 more standalone AI browsers — including Fellou, Strawberry Browser, Kahana Oasis, and kweo — on macOS, Windows, and Linux.
  • Agents can now run on Claude Sonnet 5.5 via the Anthropic API or AWS Bedrock, with adaptive thinking effort settings.
  • Connector event triggers — such as a new Gmail label, Linear issue, or Google Drive file — are now available for agents in every workspace without requiring an access request.
+1 more show less
  • Adds a Fetch deployments button when adding or editing an Azure Foundry AI provider, automatically listing models served by the endpoint and populating deployment names.
  • Adds flow_metrics_collection_enabled = false Terraform ECSECSElastic Common Schema, an open specification maintained by Elastic that defines a standard field naming convention for log and event data, letting cyber tools share and correlate records without per-source field mapping. config key to opt out of backend flow-metric collection when observability OTLP export is on and tooling export is off (collection now defaults on in that mode).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • AI Watch Detect now inventories 16 standalone AI browsers built on Chromium — including Perplexity Comet, Dia, Opera Neon, ChatGPT Atlas, Norton Neo, and BrowserOS — on macOS, Windows, and Linux, counting a browser as installed only when its own installation is found.

4 more in Everything

└──▷ BREAKING ON UPGRADE
  • !With observability OTLP export on and tooling export off, backend flow-metric collection now defaults on — operators who did not previously collect flow metrics in this configuration must explicitly set flow_metrics_collection_enabled = false in their Terraform ECS inputs to opt out.
1.28.845 (2026-09-28) Blog Stable

Runlayer 1.28.845 adds OTLPOTLPOpenTelemetry Protocol, a standard way to send traces, metrics and logs between applications, collectors and monitoring systems. It lets telemetry move across compatible tools. API key ingestion for AI clients, Pi integration, and MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.-only Shadow AI Scan key minting.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Set up OTLP telemetry ingestion from Claude Code into Runlayer by creating a write-only OTLP Telemetry API key scoped to OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. only.
📍In the Runlayer console, go to Organization API keys → Create key, select the OTLP Telemetry permission (must be the only permission), then configure your Claude Code exporter to send logs, metrics, and traces to your Runlayer OTLP endpoint using the generated key.
Connect an Oh My Pi agent to Runlayer governance in one step, routing its MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tools through Runlayer policy enforcement.
$ /mcp add
  • Adds a new write-only OTLP Telemetry organization API key permission for OpenTelemetry ingestion (logs, metrics, traces) from AI clients such as Claude Code, Claude Cowork, and Glean; created from the Organization API keys page and must be the key's only permission — cannot use the AI Watch scan or hook endpoints.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Restricts Shadow AI Scan key creation to the MDM configuration wizard only; the Organization API keys page no longer offers the Shadow AI Scan role, and the API rejects hand-created keys with it, ensuring every key links devices and scan data to a configuration card.
  • Adds a Pi integration guide enabling agents built on Pi to route MCP tools through Runlayer, enforce policy on local tools like bash, and record activity in Sessions.
  • Adds an Oh My Pi (omp) tab in the connector setup guide with a one-line /mcp add command that signs in and saves the connector.
  • Adds generated chat titles to an agent's chat list, replacing the first prompt, with rename available from the ⋯ menu. Not checked yet
+3 more show less
  • Adds redirect URI approval guidance — the approval screen now shows the path Settings → General → OAuth redirect URIs and lets members copy a shareable link for their admin.
  • Speeds up AI Watch scans by batching artifact reporting in requests of up to 25 artifacts instead of one request per artifact, reducing traffic against the Runlayer deployment.
  • Skips unchanged plugins already held by the server for the same window as skills, cutting repeat uploads on every scheduled scan tick.
  • Adds a new write-only OTLP Telemetry organization API key permission for OpenTelemetry ingestion (logs, metrics, traces) from AI clients such as Claude Code, Claude Cowork, and Glean; created from the Organization API keys page and must be the key's only permission — cannot use the AI Watch scan or hook endpoints.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds a Pi integration guide enabling agents built on Pi to route MCP tools through Runlayer, enforce policy on local tools like bash, and record activity in Sessions.
  • Adds an Oh My Pi (omp) tab in the connector setup guide with a one-line /mcp add command that signs in and saves the connector.
  • Adds generated chat titles to an agent's chat list, replacing the first prompt, with rename available from the ⋯ menu. Not checked yet

4 more in Everything

└──▷ BREAKING ON UPGRADE
  • !The Organization API keys page no longer offers the Shadow AI Scan role, and the API rejects hand-created keys with that role; Shadow AI Scan keys must now be minted through the MDM configuration wizard.
Was this useful?
Govern
◆  Model & Agent Protection

Docker Sandboxes

Sources Release notes → v0.46.0 Notes Rank Why this rank top features scored 90/90/85, +15 breaking change, +6 runnable example — 109.33 How ranking works →

Docker Sandboxes isolates applications in lightweight containers, providing secure, reproducible environments for development and deployment.

Docker Sandboxes' v0.46.0 release adds kit-arg parameterization for cloud kit mixins, auto-restart on sandbox timeout, upgraded diagnostics and kit reliability, plus a breaking change to where secret commands execute from; docs additions cover a new sbx daemon restart command for reloading model provider settings.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 10 FEATURES 0 OF 10 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Parameterized kit mixins via --kit-arg Not checked yet new 90

sbx --cloud create gains --kit-arg and --kit-args-file flags to pass named arguments (in name=value form) to v2 kit mixins at sandbox creation time, or load them from a file for repeatable CI use.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Parameterize a v2 kit mixin inline when creating a cloud sandbox — useful when you need to pin a specific version of a bundled CLI tool.
$ sbx --cloud create --name cloud-tools claude --kit docker.io/<NAMESPACE>/company-cli:1.0.0 --kit-arg company-cli.version=1.2
Load kit arguments from a file to keep sandbox creation commands tidy and repeatable across CI pipelines.
$ sbx --cloud create --name cloud-tools claude --kit docker.io/<NAMESPACE>/company-cli:1.0.0 --kit-args-file kit-args.txt
Pass kit-specific configuration values when creating a cloud sandbox, so the kit can customize its behaviour at launch.
$ sbx --cloud create --kit my-agent-kit --kit-arg model=gpt-4o --kit-arg max_steps=50
— Runnable commands with exact flag syntax shown v0.46.0
02 00
Secret commands now run from a temporary directory Not checked yet breaking 90

Secret commands configured with sbx secret set --command, sbx secret set-custom --command, or secrets.<name>.command in an environment file now execute from a fresh temporary directory on the host, so relative paths such as ./credential-helper no longer resolve from the project directory or the directory where sbx was run. Existing environments with secret commands will be prompted to approve a one-time plan change for the working directory on the next sbx env run; the execution change takes effect immediately after upgrading and restarting the daemon, even before that plan is approved.

— Exact keys and migration path named, no runnable example v0.46.0
03 00
Daemon restart for model provider changes Not checked yet new 85

sbx daemon restart reloads the Docker Sandboxes daemon after setting or changing a model provider API key or adding llama-server to the host PATH, without requiring a full restart. The daemon manages a persistent model service that starts at daemon startup, survives individual sandbox or CLI exits, and lets sandboxes share a common model store and loaded models.

— Exact command with clear mechanism described product docs
04 00
Diagnostics upload status and socket-limit reporting Not checked yet improved 85

sbx diagnose --upload now returns a non-zero exit status on failed diagnostics uploads, enabling reliable script-level failure detection. sbx diagnose output also gains a runtime_socket_limit_bytes field reporting the socket-path length limit used by the container runtime.

Fail a CI step immediately if a diagnostics upload is unsuccessful, rather than silently succeeding.
$ sbx diagnose --upload || echo 'Diagnostics upload failed — check connectivity and retry'
— Named field and flag with a runnable example v0.46.0
05 00
Auto-restart cloud sandboxes on timeout Not checked yet new 75

sbx --cloud create --on-timeout restart makes a sandbox that hits its time limit stop and immediately restart instead of remaining stopped.

Keep a long-running cloud sandbox alive indefinitely by auto-restarting it the moment it hits its time limit.
$ sbx --cloud create --on-timeout restart --kit my-agent-kit
— Exact flag and runnable command, minimal further detail v0.46.0
06 00
Kit management reliability and skills directory support Not checked yet improved 60

Kits can now install files in the agent's skills directory even when shared skills are read-only, without triggering a read-only filesystem error. Kits added through the runtime API retain their network rules and applicable agent instructions when another kit addition recreates the sandbox container. sbx kit add now warns if it cannot save the updated sandbox record, explaining which kit settings could be lost and the conditions that would cause the loss.

— Names sbx kit add but no example command v0.46.0
07 00
WSL2 clipboard image paste fallback Not checked yet improved 60

Image paste in WSL2WSL2A Microsoft-maintained compatibility layer in Windows 10/11 that runs a real Linux kernel inside a lightweight VM, letting cyber tools built for Linux execute natively on Windows without dual-booting or a full VM. falls back to the Windows clipboard when Linux clipboard tools return no image, requiring clipboard.imagePaste to be enabled.

— Names config key, no example given v0.46.0
thinner coverage below
08 00
Precise error locations for sbx env Not checked yet improved 55

sbx env reports unrecognized environment-file keys with the file, line, and column where they were declared, including across merged files.

— Names command but no example or config key v0.46.0
09 00
Playwright browser downloads under balanced network policy Not checked yet improved 55

Sandboxes created with the balanced network policy preset can now download Playwright browser binaries from cdn.playwright.dev over HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate..

— Names preset and domain, no command shown v0.46.0
10 00
Bulk secret removal revokes running credentials Not checked yet improved 45

Removing secrets in bulk now revokes credentials from running sandboxes, with failed revocations retryable even after the stored secrets have been deleted.

— Describes behavior, no command or endpoint named v0.46.0
└──▷ BREAKING ON UPGRADE
  • !
    Secret commands configured with sbx secret set --command, sbx secret set-custom --command, or secrets.<name>.command in an environment file now execute from a fresh temporary directory on the host. Relative paths such as ./credential-helper no longer resolve from the project directory or the directory where you ran sbx. Existing environments that declare secret commands will be prompted to approve a one-time plan change for the working directory on the next sbx env run. The execution change takes effect immediately after upgrading and restarting the daemon, even before that plan is approved.
v0.46.0 Notes LatestStable

Docker Sandboxes v0.46.0 adds restart-on-timeout for cloud sandboxes, kit-arg passthrough, and richer CLI diagnostics.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v0.46.0 https://github.com/docker/sbx-releases.git
# already have the repo? check out this version:
$ git checkout v0.46.0
└──▷ TRY IT
Keep a long-running cloud sandbox alive indefinitely by auto-restarting it the moment it hits its time limit.
$ sbx --cloud create --on-timeout restart --kit my-agent-kit
Pass kit-specific configuration values when creating a cloud sandbox, so the kit can customize its behaviour at launch.
$ sbx --cloud create --kit my-agent-kit --kit-arg model=gpt-4o --kit-arg max_steps=50
Fail a CI step immediately if a diagnostics upload is unsuccessful, rather than silently succeeding.
$ sbx diagnose --upload || echo 'Diagnostics upload failed — check connectivity and retry'
  • Adds --on-timeout restart to sbx --cloud create so a sandbox that hits its time limit stops and immediately restarts instead of remaining stopped.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds --kit-arg and --kit-args-file flags to sbx --cloud create for passing values to kits supplied with --kit.
  • Adds sbx diagnose --upload returning a non-zero exit status on failed diagnostics uploads, enabling reliable script-level failure detection.
  • Adds runtime_socket_limit_bytes field to sbx diagnose output, reporting the socket-path length limit used by the container runtime.
  • sbx env reports unrecognized environment-file keys with the file, line, and column where they were declared, including across merged files.
+6 more show less
  • Kits can now install files in the agent's skills directory when shared skills are read-only, without triggering a read-only filesystem error.
  • Kits added through the runtime API retain their network rules and applicable agent instructions when another kit addition recreates the sandbox container.
  • sbx kit add warns if it cannot save the updated sandbox record, explaining which kit settings could be lost and the conditions that would cause the loss.
  • Image paste in WSL2WSL2A Microsoft-maintained compatibility layer in Windows 10/11 that runs a real Linux kernel inside a lightweight VM, letting cyber tools built for Linux execute natively on Windows without dual-booting or a full VM. falls back to the Windows clipboard when Linux clipboard tools return no image, requiring clipboard.imagePaste to be enabled.
  • Sandboxes created with the balanced network policy preset can now download Playwright browser binaries from cdn.playwright.dev over HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate..
  • Removing secrets in bulk now revokes credentials from running sandboxes, with failed revocations retryable even after stored secrets have been deleted.
  • Adds --on-timeout restart to sbx --cloud create so a sandbox that hits its time limit stops and immediately restarts instead of remaining stopped.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds --kit-arg and --kit-args-file flags to sbx --cloud create for passing values to kits supplied with --kit.

9 more in Everything

└──▷ BREAKING ON UPGRADE
  • !Secret commands configured with sbx secret set --command, sbx secret set-custom --command, or secrets.<name>.command in an environment file now execute from a fresh temporary directory on the host. Relative paths such as ./credential-helper no longer resolve from the project directory or the directory where you ran sbx. Existing environments that declare secret commands will be prompted to approve a one-time plan change for the working directory on the next sbx env run. The execution change takes effect immediately after upgrading and restarting the daemon, even before that plan is approved.
Was this useful?

Straiker

Sources Blog / feed → Straiker’s Technology & Channel Partnerships for AI Agent Security (2026-09-03) Blog Rank Why this rank top features scored 80/55/55 — 63.33 How ranking works →

Straiker discovers and inventories enterprise AI agents, tests them with automated red teaming and protects them with runtime guardrails.

Straiker launched a formal Partner Collective with AWS Marketplace availability and OpenAI Select Partner status, introduced three named AI-agent-security products (Discover, Ascend, and Defend AI), and unveiled Heimdall, a cyber-hardened sandbox for evaluating and training high-risk agents under an assumed-breach model.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 5 FEATURES 5 OF 5 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
Heimdall cyber-hardened AI agent sandbox Not checked yet new 80

Heimdall is a dedicated AI agent sandbox built on an assumed-breach premise, treating every workload and reachable component as potentially compromised.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ It provides dedicated Apple Silicon runner hardware supporting native macOS, Linux, and Windows evaluation environments, each starting from a fresh VM, storage volume, network identity, and credentials per attempt.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Egress is enforced via an independently managed network enforcement point outside the runner, applying default-deny across IPv4, IPv6IPv6The current version of the Internet Protocol, standardized by the IETF, using 128-bit addresses to replace the exhausted IPv4 space. Cyber tools target it because modern networks run dual-stack or IPv6-only., DNS, local subnets, management networks, overlays, redirects, proxies, and caches. It issues resource-scoped, time-bounded credentials per run — including GitHub App installation tokens scoped to approved repositories with a one-hour maximum expiration — via a control-plane broker that never exposes the private key to the runner or evaluation environment. It collects tamper-resistant, off-guest telemetry (host, network, credential, policy, and lifecycle evidence) following OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. security guidance, with each record carrying run identifier, producer identity, and sequence data to detect gaps, reordering, or substitution, and performs verified teardown confirming destruction of the VM, ephemeral volumes, routes, tokens, jobs, callbacks, service state, and external artifacts before the runner can return to an admissible state.

— Rich mechanism and named controls but no direct command or config a reader can run Heimdall: Cyber-Hardened AI Sandbox for High…
thinner coverage below
02 02
Partner Collective ecosystem and marketplace availability Not checked yet new 55

Launches the Straiker Partner Collective, a formal ecosystem bringing cloud providers, resellers, systems integrators, and ISVs together to deliver AI agent security. Makes Straiker available on AWS Marketplace, enabling procurement via private offers and committed cloud spend drawdown, and designates Straiker an OpenAI Select Partner for building, deploying, and scaling agents on OpenAI models. Also offers a co-brandable AI risk assessment powered by Discover AI and Ascend AI, plus APIs for embeddingembeddingLists of numbers a model produces to represent the meaning of text, images or code, so similar items sit close together. They power semantic search and RAG. Straiker into partner-owned services and a multi-tenant deployment model for partner-delivered engagements.

— Names AWS Marketplace, OpenAI status, APIs but no mechanism or usage path Straiker’s Technology & Channel Partnerships…
03 03
Defend AI runtime threat detection and blocking Not checked yet new 55

Defend AI delivers runtime threat detection and blocking, reporting 98.1% threat detection accuracy against injection attempts, data exfiltrationdata exfiltrationMoving data out of a system or organization without authorization. It can happen through network transfers, removable media or other channels., and off-policy behavior.

— Includes a concrete accuracy metric but no deployment mechanics Straiker’s Technology & Channel Partnerships…
04 04
Ascend AI continuous agentic red-teaming Not checked yet new 50

Ascend AI provides continuous red-teaming of AI agents using real-world agentic attack datasets, covering prompt injectionprompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools., goal hijacking, and tool misuse.

— Names attack categories but not how testing runs Straiker’s Technology & Channel Partnerships…
05 05
Discover AI agent and MCP server inventory Not checked yet new 35

Discover AI performs AI agent discovery and posture management, mapping every AI agent, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server, and agentic workflow in a customer environment.

— States what it maps but no mechanism or setup detail Straiker’s Technology & Channel Partnerships…
Straiker’s Technology & Channel Partnerships for AI Agent Security (2026-09-03) Blog LatestStable

Straiker launches the Partner Collective, adding AWS Marketplace availability and an OpenAI Select Partner designation for AI agent security.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Launches the Straiker Partner Collective, a formal ecosystem bringing cloud providers, resellers, systems integrators, and ISVs together to deliver AI agent security.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Not checked yet
  • Makes Straiker available on AWS Marketplace, enabling procurement via private offers and committed cloud spend drawdown.
  • Designates Straiker as an OpenAI Select Partner, providing enterprises a validated security path for building, deploying, and scaling agents on OpenAI models. Not checked yet
  • Introduces Straiker Discover AI for AI agent discovery and posture management, mapping every AI agent, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server, and agentic workflow in a customer environment.
  • Introduces Straiker Ascend AI for continuous red-teaming of AI agents using real-world agentic attack datasets, covering prompt injectionprompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools., goal hijacking, and tool misuse.
+3 more show less
  • Introduces Straiker Defend AI for runtime threat detection and blocking, reporting 98.1% threat detection accuracy against injection attempts, data exfiltrationdata exfiltrationMoving data out of a system or organization without authorization. It can happen through network transfers, removable media or other channels., and off-policy behavior.
  • Offers a co-brandable AI risk assessment offering that partners can take to market, powered by Discover AI and Ascend AI.
  • Provides APIs for embeddingembeddingLists of numbers a model produces to represent the meaning of text, images or code, so similar items sit close together. They power semantic search and RAG. Straiker into partner-owned services and a multi-tenant deployment model for partner-delivered engagements.

8 details in Everything

Heimdall: Cyber-Hardened AI Sandbox for High-Risk Agents | Straiker (2026-09-02) Blog Stable

Straiker launches Heimdall, a cyber-hardened AI sandbox with independent isolation, egress enforcement, tamper-resistant telemetry, and external kill-switch controls for high⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Introduces Heimdall, a dedicated AI agent sandbox built on an assumed-breach premise, treating every workload and reachable component as potentially compromised.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Provides dedicated Apple Silicon runner hardware supporting native macOS, Linux, and Windows evaluation environments, each starting from a fresh VM, storage volume, network identity, and credentials per attempt.
  • Enforces egress via an independently managed network enforcement point outside the runner, applying default-deny across IPv4, IPv6IPv6The current version of the Internet Protocol, standardized by the IETF, using 128-bit addresses to replace the exhausted IPv4 space. Cyber tools target it because modern networks run dual-stack or IPv6-only., DNS, local subnets, management networks, overlays, redirects, proxies, and caches.
  • Issues resource-scoped, time-bounded credentials per run — including GitHub App installation tokens scoped to approved repositories with a one-hour maximum expiration — via a control-plane broker that never exposes the private key to the runner or evaluation environment.
  • Collects tamper-resistant, off-guest telemetry (host, network, credential, policy, and lifecycle evidence) following OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. security guidance, with each record carrying run identifier, producer identity, and sequence data to detect gaps, reordering, or substitution.
+1 more show less
  • Performs verified teardown that confirms destruction of VM, ephemeral volumes, routes, tokens, jobs, callbacks, service state, and external artifacts against the systems that created them, blocking the runner from returning to an admissible state until all checks pass.

6 details in Everything

Was this useful?

Lasso Security

Sources Blog post → announced · Sep 29, 2026 Blog Rank Why this rank top features scored 80 — 80 How ranking works →

Lasso Security launched a Claude Enterprise integration built on Claude's Compliance API, bringing user activity, conversation content, and policy violations from Claude into its AI discovery and monitoring inventory.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Lasso Security protects employee GenAI use, LLM applications and AI agents with runtime guardrails, data-leak prevention and CPU-only guardrail models.

Lasso Security launched a Claude Enterprise integration built on Claude's Compliance API, bringing user activity, conversation content, and policy violations from Claude into its AI discovery and monitoring inventory.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 1 FEATURE 0 OF 1 FEATURE most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Claude Enterprise integration via Compliance API Not checked yet new 80

Lasso adds support for connecting a Claude Compliance API key, pulling from the Compliance API's activities endpoint to ingest Claude Enterprise and Claude Platform user activity into Lasso's inventory.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ For Claude Enterprise organizations, it also ingests message content for each chat once a Compliance Access Key minted by the primary owner is added, enabling conversation-level inspection for sensitive data, secrets, and policy violations. Each Claude user is surfaced in Lasso's AI discovery inventory alongside existing agents and AI applications, with a per-user timeline of MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers connected and skills invoked; Claude policy violations are routed to a connected SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. or SOARSOARSecurity orchestration, automation and response, coordinating incident workflows across tools. Playbooks can gather evidence, assign work or carry out approved response actions. platform for triage alongside alerts from other AI platforms, and a durable audit trail of org-level Claude events is stored for SOC 2SOC 2An auditing framework from the American Institute of CPAs that certifies a service organization's controls around security, availability, and data handling, giving buyers assurance that a vendor meets baseline trust criteria., ISOISOA widely adopted international standards body that publishes technical specifications; cyber tools cite ISO standards to signal compliance with recognized benchmarks for quality, security, or interoperability., and GDPR evidence.

— Names endpoint and access-key mechanism but no exact setup command. launch-20260929-9fec8c91
announced · Sep 29, 2026 Blog

Lasso adds a Claude Enterprise integration via Claude's Compliance API to surface user activity, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers, and conversation content.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Adds support for connecting a Claude Compliance API key to Lasso, pulling from the Compliance API's activities endpoint to ingest Claude Enterprise and Claude Platform user activity into Lasso's inventory.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • For Claude Enterprise organizations, ingests message content for each chat when a Compliance Access Key minted by the primary owner is added to Lasso, enabling conversation-level inspection for sensitive data, secrets, and policy violations.
  • Surfaces each Claude user in Lasso's AI discovery inventory alongside existing agents and AI applications, with a per-user timeline of MCP servers connected and skills invoked.
  • Routes Claude policy violations to a connected SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. or SOARSOARSecurity orchestration, automation and response, coordinating incident workflows across tools. Playbooks can gather evidence, assign work or carry out approved response actions. platform for triage alongside alerts from other AI platforms.
  • Builds a durable audit trail of org-level Claude events and user activity, stored alongside the rest of the AI environment for SOC 2SOC 2An auditing framework from the American Institute of CPAs that certifies a service organization's controls around security, availability, and data handling, giving buyers assurance that a vendor meets baseline trust criteria., ISOISOA widely adopted international standards body that publishes technical specifications; cyber tools cite ISO standards to signal compliance with recognized benchmarks for quality, security, or interoperability., and GDPRGDPREU regulation enacted in 2018 that governs how organizations collect, store, and process personal data of EU residents, giving cyber tools legal obligations around data handling and breach notification. evidence.
  • Adds support for connecting a Claude Compliance API key to Lasso, pulling from the Compliance API's activities endpoint to ingest Claude Enterprise and Claude Platform user activity into Lasso's inventory.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • For Claude Enterprise organizations, ingests message content for each chat when a Compliance Access Key minted by the primary owner is added to Lasso, enabling conversation-level inspection for sensitive data, secrets, and policy violations.

3 more in Everything

Was this useful?

Noma Security

Sources Blog post → announced · Sep 28, 2026 Blog Rank Why this rank top features scored 60/60/50 — 56.67 How ranking works →

Noma Security discovers an enterprise's AI applications and agents, manages their posture and protects them at runtime with compliance reporting.

Noma extends its agent security platform from cloud/app environments to employee endpoints, adding endpoint discovery, a governed approval registry, identity-aware access controls, and expanded AI-DR runtime threat detection for coding and productivity agents.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 8 FEATURES 6 OF 8 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
Identity-aware, tool-level Access Control policies Not checked yet new 60

Adds identity-aware Access Control policies that attribute each endpoint agent to the human behind it, linking to IdPIdPA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. users and groups for per-user, per-group, or org-wide enforcement.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Also adds tool- and action-level granularity, allowing read access to be broadly permitted while create, update, or delete operations are restricted to specific groups.

— Names IdP linkage and CRUD-level restriction scope launch-20260928-380132fb
02 02
AI-DR runtime threat protection for endpoint agents Not checked yet new 60

Adds AI-DR runtime threat protection for endpoint agents, detecting prompt injectionprompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools. (including encoded, obfuscated, and indirect injection via tool responses), sensitive data leakage (PIIPIIPersonally Identifiable Information — data that can identify a specific individual, such as names, email addresses, or SSNs. Cyber tools flag or redact it to limit exposure and meet privacy regulations., PCIPCIA hardware bus standard that connects peripheral devices to a computer's motherboard; cyber tools targeting hardware-level forensics or memory analysis use it to access device registers and DMA regions directly., secrets), malicious intent, tool poisoning, scope violations, and behavioral drift.

— Lists many named threat classes but no config/API surface launch-20260928-380132fb
thinner coverage below
03 03
Endpoint agent discovery via EDR/MDM Not checked yet new 50

Extends Noma's agent inventory to employee endpoints, using existing EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device. or MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. deployments to discover agents, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers, skills, connectors, and active processes on managed devices.

— Names EDR/MDM mechanism but no exact commands or UI path launch-20260928-380132fb
04 00
Contextual Policies for multi-step attack correlation Not checked yet new 50

Adds Contextual Policies within AI-DR that correlate prompts, tool calls, tool responses, and reasoning across full sessions to surface multi-step attacks such as indirect prompt injectionindirect prompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools. followed by secret exfiltration.

— Explains mechanism and example attack but no interface detail launch-20260928-380132fb
05 04
Open Enforcement extended to endpoints Not checked yet new 50

Extends Open Enforcement to the endpoint, enabling the same Access Control, Agent Boundaries, and AI-DR policies to be enforced through agent hooks, AI and MCP gateways, SDKs, direct APIs, and existing EDR/MDM infrastructure.

— Names enforcement surfaces but no specific config or endpoint launch-20260928-380132fb
06 05
Governed registry for discovered agents Not checked yet new 40

Adds a governed registry that automatically assigns every discovered agent, MCP server, and skill a status of approved, needs review, or blocked.

— Describes states but not how review/blocking is triggered launch-20260928-380132fb
07 06
Adaptive Context Retrieval for detector tuning Not checked yet new 40

Adds Adaptive Context Retrieval, which learns an application's traffic patterns to distinguish reusable context (system prompts, session history, RAGRAGRetrieval-augmented generation: looking up relevant documents and adding them to the prompt before the model answers. It grounds responses in private or current data without retraining. context) from user-controlled input, improving detector signal and reducing false positives.

— Explains purpose but no tunable settings named launch-20260928-380132fb
08 00
Coverage for coding and productivity agents Not checked yet new 40

Adds coverage for coding and productivity agents including Claude Code, Claude Cowork, Cursor, Codex, Windsurf, Kiro, Antigravity, and OpenClaw.

— Names all supported agents but no mechanism detail launch-20260928-380132fb
announced · Sep 28, 2026 Blog

Noma extends its agent control plane to employee endpoints, discovering coding and productivity agents via existing EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device./MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. infrastructure.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

  • Extends Noma's agent inventory to employee endpoints, using existing EDR or MDM deployments to discover agents, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers, skills, connectors, and active processes on managed devices.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds a governed registry that automatically assigns every discovered agent, MCP server, and skill a status of approved, needs review, or blocked.
  • Adds identity-aware Access Control policies that attribute each endpoint agent to the human behind it, linking to IdPIdPA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. users and groups for per-user, per-group, or org-wide enforcement.
  • Adds tool- and action-level Access Control granularity, allowing read access to be broadly permitted while create, update, or delete operations are restricted to specific groups.
  • Adds AI-DR runtime threat protection for endpoint agents, detecting prompt injectionprompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools. (including encoded, obfuscated, and indirect injection via tool responses), sensitive data leakage (PIIPIIPersonally Identifiable Information — data that can identify a specific individual, such as names, email addresses, or SSNs. Cyber tools flag or redact it to limit exposure and meet privacy regulations., PCIPCIA hardware bus standard that connects peripheral devices to a computer's motherboard; cyber tools targeting hardware-level forensics or memory analysis use it to access device registers and DMA regions directly., secrets), malicious intent, tool poisoning, scope violations, and behavioral drift.
+4 more show less
  • Adds Contextual Policies within AI-DR that correlate prompts, tool calls, tool responses, and reasoning across full sessions to surface multi-step attacks such as indirect prompt injectionindirect prompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools. followed by secret exfiltration.
  • Adds Adaptive Context Retrieval, which learns an application's traffic patterns to distinguish reusable context (system prompts, session history, RAGRAGRetrieval-augmented generation: looking up relevant documents and adding them to the prompt before the model answers. It grounds responses in private or current data without retraining. context) from user-controlled input, improving detector signal and reducing false positives.
  • Extends Open Enforcement to the endpoint, enabling the same Access Control, Agent Boundaries, and AI-DR policies to be enforced through agent hooks, AI and MCP gateways, SDKs, direct APIs, and existing EDR/MDM infrastructure.
  • Adds coverage for coding and productivity agents including Claude Code, Claude Cowork, Cursor, Codex, Windsurf, Kiro, Antigravity, and OpenClaw.
  • Extends Noma's agent inventory to employee endpoints, using existing EDR or MDM deployments to discover agents, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers, skills, connectors, and active processes on managed devices.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds a governed registry that automatically assigns every discovered agent, MCP server, and skill a status of approved, needs review, or blocked.
  • Adds Contextual Policies within AI-DR that correlate prompts, tool calls, tool responses, and reasoning across full sessions to surface multi-step attacks such as indirect prompt injectionindirect prompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools. followed by secret exfiltration.
  • Adds Adaptive Context Retrieval, which learns an application's traffic patterns to distinguish reusable context (system prompts, session history, RAGRAGRetrieval-augmented generation: looking up relevant documents and adding them to the prompt before the model answers. It grounds responses in private or current data without retraining. context) from user-controlled input, improving detector signal and reducing false positives.

5 more in Everything

Was this useful?
Saved in this browser. Sign in to sync your tools.