The daily firehose — everything the toolchain shipped today, already filtered.
We read every release from the 1309 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.
READ AS
Focus:What features shipped and what problems they solve, plus launches, packaging and where the market is moving.
Leaves out:Command-line flags, API-only deltas, usage examples, and releases that are only refinements.
Focus:New security controls, new APIs, and product improvements you can put to work, plus anything an upgrade breaks.
Leaves out:Launch and marketing news, governance, pricing, and documentation changes with no operational effect.
Focus:Dashboards, reporting, and anything you can quantify: metrics, coverage, risk scores, compliance impact, vendor moves.
Leaves out:Settings, flags, API and command-line detail, library bumps, and minor releases with no reporting or posture angle.
Focus:API, SDK and MCP changes, new libraries, breaking changes in what you import, and cyber tooling.
Leaves out:Governance, SOC operations, and vendor launches with no developer surface.
AMOUNT
DETAIL
ORDER
This issue came out before editions were ranked, so it shows the Standard edition in issue order.
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. Aikido Security now walks an external perimeter from one domain and chains CVEs and exposed secrets into working exploit paths, no pentest engagement needed. FOSSA runs impact analysis on dependency-bump PRs before merge, so upgrades stop breaking builds. Salt Security lets API threat workflows revoke and block on their own instead of filing a ticket.
protect
See your internet-facing attack surface the way an attacker chains it, from one domain
Aikido's agents enumerate the perimeter, attack what they find with known CVEs, misconfigurations and exposed secrets, and join findings into full exploit paths — the chaining is the part a vulnerability list never gives you. Censys's move to flat one-credit search, daily free searches and credit rollover makes exploratory external recon something you do on a hunch rather than budget against.
Stop a dependency upgrade from breaking the build before you merge it
FOSSA's fossabot runs application impact analysis on upgrade PRs — including PRs raised by existing auto-PR bots — so the merge decision carries evidence instead of hope, which is the main reason dependency bots get muted. Mend 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. now parses both Bun lockfile formats with reachability and workspace support, closing a blind spot for teams that moved off npm; Endor Labs packages a fully automated SCA Remediation agent grounded in its own reachability and policy data.
Let an API threat workflow contain itself instead of paging someone
Autonomous Defense gives Salt Workflows the authority to block, revoke and remediate against connected controls directly, with a visual builder and 200+ prebuilt connectors to reach gateways and IdPsIdPsIdentity Providers: services that authenticate users and issue tokens or assertions so other applications can trust who someone is without managing credentials themselves.. The gap it closes is the one between Salt detecting a live API abuse and a human logging into another console to shut off the key.
Hunter launched an official 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, letting AI assistants call its contact-finding, verification and CRM tools directly, with one-click OAuth setup on every plan including Free.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Official MCP server for AI assistantsnew86how completely this was documenteddepth30/40specificity28/30actionability28/3086 / 100
Hunter now offers an MCP server at https://mcp.hunter.io/mcp, exposing over 100 tools covering email finding, verification, enrichment, sequences, saved searches, company lists, and CRM sync to any MCP-compatible AI client.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It works with Claude, ChatGPT, Gemini, Perplexity, Claude Code, Cursor, Codex, and other MCP-compatible clients, and is included on every Hunter plan including Free. Connection uses a one-click OAuth flow that passes the Hunter API key in an X-API-Key header, so no manual API key configuration is required.
Register the Hunter MCP server in a Claude or compatible client config so your AI assistant can call Hunter tools directly.
humble 1.68 adds Markdown export, a version-lag check for the CLI, and 16 new insecure header detections.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
A humble and fast security-oriented HTTP headers analyzer.
humble 1.68 adds Markdown export, a version-lag check for the CLI, and 16 new insecure header detections.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
3 FEATURES0 OF 3 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Markdown export format for analysis resultsnew60how completely this was documenteddepth15/40specificity20/30actionability25/3060 / 100
Analysis results can now be exported to Markdown using -o md.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact flag but no further mechanism detail1.68
0200
Version lag check via -v flagnew60how completely this was documenteddepth15/40specificity20/30actionability25/3060 / 100
Running -v now shows how many days behind the latest release the installed version of humble is, e.g. python humble.py -v.
Check whether your installed copy of humble is behind the latest release and by how many days.
$ python humble.py -v
— Exact flag and runnable example given, mechanism simple1.68
thinner coverage below
0300
16 new insecure header checksnew25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds 16 new insecure header checks across multiple categories.
— No specific header names or categories listed1.68
Skylos v5.3.0 adds an opt-in AI review step that runs automatically when scan results are uploaded for the default branch.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Open source local-first PR scanner that finds dead code, security bugs, secrets, quality regressions, and AI-code mistakes before merge. For first timers refer to https://duriantaco.github.io/skylos/repo-map/
Skylos v5.3.0 adds an opt-in AI review step that runs automatically when scan results are uploaded for the default branch.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
AI review on default-branch cloud uploadsnew50how completely this was documenteddepth15/40specificity15/30actionability20/3050 / 100
Running skylos cloud to upload results for the default branch now triggers an AI review step as part of that process.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names the exact command but not what the AI review checks or outputsv5.3.0
Mend SCA adds full support for Bun-managed JavaScript and TypeScript projects, including both lockfile formats, reachability analysis, workspaces and private registries.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Mend sca is a traditional application security misses AI risk. Standalone AI security tools miss your code.
Mend SCA adds full support for Bun-managed JavaScript and TypeScript projects, including both lockfile formats, reachability analysis, workspaces and private registries.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Bun project scanning with reachability analysisnew77how completely this was documenteddepth30/40specificity27/30actionability20/3077 / 100
Mend SCA now scans Bun-managed JavaScript and TypeScript projects by reading bun.lock (the text format, default since Bun 1.2) with no Bun installation required in the scan environment, and also supports the legacy binary bun.lockb format when Bun is installed in the scan environment.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Reachability analysis is supported for Bun projects in the Mend CLI and all repository integrations, marking each dependency vulnerability as reachable or unreachable for both JavaScript and TypeScript sources. Bun workspaces and private registries are supported with no extra configuration, and any folder containing a package.json alongside a bun.lock or bun.lockb file is automatically detected and scanned as a Bun project.
FOSSA secures the software supply chain with automated SBOM generation, software composition analysis, license compliance, and vulnerability management.
FOSSA launched Context-Aware Remediation, a fossabot-powered workflow that runs application impact analysis on dependency-upgrade PRs before merge, extending to existing auto-PR tools and multiple language ecosystems.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Context-Aware Remediation for dependency upgrade PRsnew80how completely this was documenteddepth32/40specificity24/30actionability24/3080 / 100
Clicking Create PR on a security issue in FOSSA opens a pull request and runs an application impact analysis drawing on your test suites, interfaces, and CI signals, powered by fossabot.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The same breaking-change analysis now also runs on PRs opened by Dependabot, Renovate, or Snyk, making those existing auto-PR workflows context-aware without replacing them. It supports JS/TS, Python, and Java ecosystems via Quick Import from GitHub, with additional ecosystems planned. If a build fails after an upgrade, commenting @fossabot fix on the PR has fossabot read the CI failure output, generate a fix, and commit it to the PR branch.
When a security issue appears in FOSSA and the upgrade breaks the build, comment directly on the PR to have fossabot diagnose the CI failure and push a corrective commit.
📍Steps:
1. Open the pull request that fossabot created for the security issue.
2. Review the impact-analysis comment fossabot posted, which lists what it checked.
3. If the build is red, comment @fossabot fix on the PR.
4. fossabot reads the CI failure output, generates a fix, and commits it to the PR branch.
— Explains mechanism and exact trigger comment, but limited ecosystem/numeric detaillaunch-20261029-fcd14dea
Aikido Security is a developer-focused application security platform that scans code, dependencies, containers, and cloud infrastructure to detect and help fix vulnerabilities.
Aikido Security launched external network pentesting, where AI agents map an organization's entire internet-facing perimeter from a single domain, attack discovered hosts using known CVEs, misconfigurations and exposed secrets, and chain findings into full exploit paths.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES1 OF 5 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0101
External network pentesting from a single domainnew78how completely this was documenteddepth32/40specificity26/30actionability20/3078 / 100
Aikido now runs external network pentests starting from a single domain, where AI agents discover subdomains and internet-facing hosts — websites, APIs, 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. gateways, mail servers, self-hosted tools — and attack each one using known CVEs, misconfigurations, and exposed secrets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Launched via Pentesting > External Network, where you enter a root domain, verify ownership, review the auto-generated asset list, and confirm a quote before agents begin mapping and attacking discovered hosts.
Start an external network pentest when you want to see everything attackers can reach under your domain before they do.
📍In the Aikido product, go to Pentesting › External Network, enter your root domain, verify ownership, review the auto-generated asset list (remove any hosts you do not want tested), confirm the quote, and launch the pentest. Agents begin mapping subdomains and attacking each discovered host immediately.
Fix suggestions with retest agentnew57how completely this was documenteddepth25/40specificity20/30actionability12/3057 / 100
Each finding includes a fix suggestion and a retest agent that checks whether the fix resolved the issue and whether it opened a new weakness elsewhere; retests are available for up to six months.
Multi-step exploit chaining across findingsnew56how completely this was documenteddepth28/40specificity20/30actionability8/3056 / 100
Agents chain multi-step findings — for example, an exposed .git folder leading to SSH credentials leading to Azure admin access — and include the full exploit chain in the report so teams can see what an attacker could actually reach.
Continuous external perimeter pentesting modenew44how completely this was documenteddepth22/40specificity14/30actionability8/3044 / 100
A continuous pentesting mode re-maps the perimeter on every run and starts testing newly discovered hosts shortly after they go live, rather than waiting for a scheduled engagement.
Unified pentest platform and audit-ready reportingimproved37how completely this was documenteddepth18/40specificity14/30actionability5/3037 / 100
External network pentesting runs inside the same product as Aikido's existing web app and mobile pentests, with a shared findings and retest interface and the same proof-of-exploit standard across all pentest types. Every pentest produces an audit-ready report with validated findings, proof of exploit, and remediation guidance suitable for compliance and auditor review.
Endor Labs shipped a one-click plugin that brings 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. server into Google Antigravity, plus a suite of pre-built AURI Agents — including a fully automated 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. Remediation agent — that let teams hand security backlog work off to agents grounded in Endor Labs' reachability and policy data.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Endor Labs is an application security platform built for AI-generated and human-written code, helping teams prioritize and fix real risk across the SDLC.
Endor Labs shipped a one-click plugin that brings 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. server into Google Antigravity, plus a suite of pre-built AURI Agents — including a fully automated 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. Remediation agent — that let teams hand security backlog work off to agents grounded in Endor Labs' reachability and policy data.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES0 OF 2 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
One-click Endor Labs plugin for Google Antigravitynew65how completely this was documenteddepth22/40specificity18/30actionability25/3065 / 100
Endor Labs ships a one-click plugin in the Google Antigravity marketplace that installs the Endor Labs MCP server inside Antigravity, letting agents check packages for vulnerabilities, malware, or exposed secrets before a pull request is opened.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ After installing the plugin, a user can prompt the Antigravity agent to scan the project, check dependencies, and flag exposed secrets.
Trigger a full security review of your project inside an Antigravity session immediately after installing the plugin.
📍Install the Endor Labs plugin from the Plugin marketplace in Antigravity, then prompt the Antigravity agent: 'Scan my project for security flaws, check all dependencies for vulnerabilities or malware, and flag any exposed secrets.'
— Names the marketplace and MCP server with an install-and-prompt example.launch-20261029-a71d5f2e
thinner coverage below
0200
AURI Agents available inside Antigravitynew46how completely this was documenteddepth18/40specificity20/30actionability8/3046 / 100
Four pre-built AURI Agents — SCA Remediation, AI SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. Triage, Dependency Decision Helper, and Vulnerability Explainer — are now available inside Antigravity, letting teams hand off backlog security work to agents grounded in Endor Labs reachability, upgrade-impact, findings, and policy data.
— Names all four agents but gives no individual mechanism for three of them.launch-20261029-a71d5f2e
Salt Security launched Autonomous Defense, letting Salt Workflows automatically block, revoke, and remediate active threats across connected controls, alongside a new visual workflow builder with 200+ prebuilt connectors.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Salt Security is the only holistic AI security solution for the entire agentic AI lifecycle, from API discovery to posture management to threat protection.
Salt Security launched Autonomous Defense, letting Salt Workflows automatically block, revoke, and remediate active threats across connected controls, alongside a new visual workflow builder with 200+ prebuilt connectors.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES1 OF 2 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0101
Autonomous Defense actions via Salt Workflowsnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Salt Workflows can now trigger automated remediation when Salt detects risk: blocking active attacks at connected WAFs, API gateways, and other enforcement points during exploitation; revoking 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. tool access by disabling unauthorized MCP connections, quarantining shadow tools, or removing excess privilege; and enforcing AI and data protections at runtime by updating connected guardrail policies, blocking unsafe AI requests, or redacting sensitive data through connected gateways.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Drag-and-drop workflow builder with 200+ connectorsnew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Salt adds a visual drag-and-drop workflow builder directly into the Agentic Security Platform, shipping with 200+ out-of-the-box connectors and a marketplace of integrations spanning security, infrastructure, IT, and collaboration systems.
Lacework FortiCNAPP is a cloud-native application protection platform from Fortinet that secures cloud workloads, containers, and infrastructure through vulnerability scanning, misconfiguration detection, and runtime threat monitoring.
Lacework FortiCNAPP's intrusion graph now shows why entities in a composite alert are connected; Linux Agent 8.5.0 released October 22, 2026.
Lacework FortiCNAPP's intrusion graph now shows why entities in a composite alert are connected.
Linux Agent 8.5.0 is now available (released October 22, 2026).
Plerion is a cloud security platform that detects misconfigurations, vulnerabilities, and threats across cloud environments and provides remediation guidance.
Databricks introduced a Beta managed warehouse for MLflow traces, removing the need to manually select a SQL warehouse to view Unity Catalog traces.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Databricks is a cloud-based data lakehouse platform for data engineering, analytics, machine learning, and AI workloads, built on Apache Spark.
Databricks introduced a Beta managed warehouse for MLflow traces, removing the need to manually select a SQL warehouse to view Unity Catalog traces.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Managed warehouse for MLflow traces (Beta)new65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Enabling Managed Warehouse for MLflow on the Previews page lets users query Unity Catalog traces in the MLflow UI without manually selecting a SQL warehouse; MLflow automatically provisions its own warehouse or falls back to serverless compute.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Workspace admins enabling managed warehouse so analysts can view MLflow traces without configuring a SQL warehouse
📍In the Databricks console, go to Settings › Previews and enable Managed Warehouse for MLflow.
Trend Vision One's File Security Storage Google Cloud template (v2.5.0) adds scanning of dual- and multi-region Cloud Storage buckets, location-specific destination buckets, configurable Cloud RunCloud RunGoogle's managed container runtime that executes stateless workloads on demand, scaling to zero when idle, so tools can deploy without managing servers or paying for idle capacity. scaling, and failure reporting for scans that exceed the retry limit.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Trend Vision One is Trend Micro's unified cybersecurity platform that consolidates threat detection, response, and risk management across endpoints, cloud, email, and networks.
Trend Vision One's File Security Storage Google Cloud template (v2.5.0) adds scanning of dual- and multi-region Cloud Storage buckets, location-specific destination buckets, configurable Cloud RunCloud RunGoogle's managed container runtime that executes stateless workloads on demand, scaling to zero when idle, so tools can deploy without managing servers or paying for idle capacity. scaling, and failure reporting for scans that exceed the retry limit.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
4 FEATURES0 OF 4 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Cloud Run scaling and CPU allocation for scan servicesnew75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
The Google Cloud template lets you configure Cloud Run scaling and CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware. allocation for the Scanner and Post-Scan Action services, with scale-to-zero and request-based billing enabled by default.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Dual-region and multi-region bucket scanningnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
File Security Storage can now scan dual-region and multi-region Cloud Storage buckets in the Google Cloud template, provided the File Security Storage service has a matching update and a scanner is deployed in an eligible region.
SentinelOne shipped Singularity Agentic Detection and Response to discover, monitor and contain AI agents across the enterprise, and added Anthropic's Claude Mythos 5.1 model to its Wayfinder Frontier AI Services for exploitability-validated vulnerability assessment.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
SentinelOne's Singularity platform protects endpoints, cloud, identity and data with AI-driven detection, Purple AI and an agentic SOC layer.
SentinelOne shipped Singularity Agentic Detection and Response to discover, monitor and contain AI agents across the enterprise, and added Anthropic's Claude Mythos 5.1 model to its Wayfinder Frontier AI Services for exploitability-validated vulnerability assessment.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES1 OF 2 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0101
Agentic Detection and Response for AI agentsnew75how completely this was documenteddepth34/40specificity27/30actionability14/3075 / 100
Singularity Agentic Detection and Response (ADR) builds an inventory of AI agents, tools, connectors, and 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. (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 along with their permissions and associated users, supporting agents built on Salesforce Agentforce, Microsoft Copilot Studio, OpenAI ChatGPT workspace agents, and Anthropic Claude managed agents.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It monitors agent activity through event traces that link AI-driven actions to subsequent system processes to detect deviation from an agent's assigned task, and it detects and blocks threats including 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. and credential exfiltration before agent actions execute. Security teams can set controls governing which agents are allowed to operate and which resources they can access, contain an individual agent without stopping the wider workflow, and agent activity is integrated into the Singularity Platform's existing investigation and response workflows so teams can examine agent actions and automate responses within customer-defined boundaries.
— Clear mechanism and named integrations but no exact UI path or API givenlaunch-20261030-2d04f863
thinner coverage below
0200
Claude Mythos 5.1 added to Wayfinder Frontier AI Servicesnew48how completely this was documenteddepth22/40specificity18/30actionability8/3048 / 100
Wayfinder Frontier AI Services now includes Anthropic Claude Mythos 5.1, a restricted-access model, alongside existing OpenAI and Anthropic models to improve vulnerability discovery and exploitability confirmation. Findings are filtered through exploitability testing so customers receive validated results and prioritised remediation guidance rather than raw vulnerability lists.
Cloudmersive's Cloud Virus API gained additional custom policy features in version v11-11-11.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Cloudmersive is a developer API platform offering cloud-based services for file scanning and malware detection, document conversion, image processing, and data validation.
Cloudmersive's Cloud Virus API gained additional custom policy features in version v11-11-11.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Custom policy features in Cloud Virus APIimproved35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
Cloud Virus API v11-11-11 now supports additional custom policy features, though the specific policies added are not detailed.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Iru shipped Remote Shell for macOS detections, letting admins open a terminal to a managed Mac even under partial isolation, and expanded its Windows Auto App catalog with six new applications.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Iru is a device-centric platform that unifies security, IT, and compliance around devices and everything they touch.
Iru shipped Remote Shell for macOS detections, letting admins open a terminal to a managed Mac even under partial isolation, and expanded its Windows Auto App catalog with six new applications.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES0 OF 2 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Remote Shell for managed Macs in EDRnew76how completely this was documenteddepth32/40specificity22/30actionability22/3076 / 100
A Launch Remote Shell button inside the detection window opens a secure terminal tunnel to a managed Mac without leaving the investigation context.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The connection stays alive through partial device isolation, so containment and investigation can happen simultaneously, and Remote Shell is also available as an add-on for customers running Iru Endpoint Management without the EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device. package.
Contain a suspicious Mac and investigate without losing detection context or pivoting between tabs.
📍In the Iru console, open the firing detection, apply partial isolation to the device, then click Launch Remote Shell to open a terminal beside the detection details and device posture — the shell stays reachable even while the device is isolated.
Censys overhauled its pricing model with flat one-credit search pricing, new Starter subscription tiers, daily free searches for all users, and credit rollover.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Censys is a internet-wide scanning and search platform that discovers and monitors hosts, services, and certificates to help security teams assess their exposure.
Censys overhauled its pricing model with flat one-credit search pricing, new Starter subscription tiers, daily free searches for all users, and credit rollover.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
4 FEATURES1 OF 4 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0101
Starter and Starter Pro subscription tiersnew70how completely this was documenteddepth30/40specificity30/30actionability10/3070 / 100
Censys adds a Starter plan at $79/month with 500 credits, 2 Collections, and 10 asset tags, and a Starter Pro plan at $599/month with 4,000 credits, 4 Collections, and 25 asset tags.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Concrete prices and limits for both new plans, but no signup flow detail.launch-20261030-2157fb23
0200
Flat one-credit pricing for all search actionsimproved65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Censys now prices every search action — lookups, standard searches, and advanced regex queries — at one credit each, replacing the previous 1/5/8-credit tiered model.
Clerk is an authentication and user-management platform that provides pre-built UI components, APIs, and SDKs for adding sign-up, sign-in, and identity features to applications.
Clerk's biggest addition this window is passkeyspasskeysPhishing-resistant sign-in credentials built on FIDO2/WebAuthn: the device holds a private key and proves possession instead of the user typing a password. They sync across a user's devices. as a full second 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. factor, alongside a new Backend API logs endpoint, an 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.-based agent feedback tool, Clerk Protect rules against bulk sign-ups, and an early-beta Agent Auth offering — plus a breaking change to test-mode email delivery.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES1 OF 5 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Backend API audit logs endpointnew85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Query audit logs programmatically with the GET /v1/logs Backend API endpoint, filtering on the same event types available in the Dashboard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Requests over the rate limit return too_many_requests.
Agent feedback collection via MCPnew65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Collect agent feedback through your MCP server by adding the submit_feedback tool from @clerk/mcp-tools, so agents can report friction — missing tools, unexpected errors, or blocked tasks — as they encounter it.
Bulk sign-up protection rules in Clerk Protectnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Two new Clerk Protect rules limit bulk account creation on the Business plan: Limit sign-ups per email domain caps sign-ups from one domain per hour, and Limit sign-ups from shared infrastructure caps bursts from the same infrastructure.
Test-mode emails stop reaching +clerk_test addressesbreaking60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Test email addresses using the +clerk_test subaddress no longer receive any emails while Test mode is on. Test suites that read sign-in links or invitation emails from a real inbox must switch those addresses to ones without +clerk_test.
Clerk for Agent Auth private betanew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Clerk for Agent Auth, built on open OAuth standards and the Personal Agent Protocol, is now in private beta, enabling agents to discover your application and authenticate through Clerk.
Test email addresses (+clerk_test subaddress) no longer receive any emails while Test mode is on — test suites that read sign-in links or invitation emails from a real inbox must switch those addresses to ones without +clerk_test.
ConductorOne is an identity governance platform that automates workforce access management and deploys AI agents to streamline access reviews and provisioning.
ConductorOne shipped Role Mining Suggestions for surfacing group-based access profiles, 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. gateway visibility and admin controls, richer access-review campaign filtering and C1 group management, plus a wide set of breaking API, logging, and permission changes including a 16-rule policy limit and removal of the email capabilitiesgRPCgRPCAn open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. method.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
16 FEATURES5 OF 16 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Compliance framework and app annotation approval routingnew80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Policies, approver steps, entitlement routing rules, account provisioning, and forms can now check compliance frameworks and app annotations to route approvals — for example, routing SOX-tagged access requests through a dedicated approval step via a Compliance framework condition in the policy editor.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Route SOX-tagged access requests through a dedicated approval step using the new compliance framework condition in a policy.
📍In the Policy editor, add an approver step, open its conditions, select Compliance framework as the attribute, choose SOX, and assign the dedicated SOX approver group.
MCP gateway visibility and error reportingimproved75how completely this was documenteddepth30/40specificity30/30actionability15/3075 / 100
AI agents connected through the MCP gateway now see every MCP server available to them, with access status and toolsets listed per server. MCP gateway error responses report whether a rejected token expired, was revoked, or is malformed, returning error code -32010 when a server credential requires reauthorization.
invalid_client replaces invalid_grant for failed token requestsbreaking75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Failed client credentials token requests now always return invalid_client instead of a specific reason — scripts or 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. matching on invalid_grant to detect deleted, disabled, or expired credentials must match invalid_client instead.
email capabilities gRPC method removedbreaking75how completely this was documenteddepth20/40specificity30/30actionability25/3075 / 100
The email capabilities gRPC method on the provider service is removed — clients must move to the capabilities service (GET /api/v1/settings/email-capabilities is unchanged).
Campaign filtering and entitlement exclusion controlsimproved70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Access review campaigns can now be filtered using custom selectors on resource attributes and entitlement annotations, combinable with app, resource type, risk level, and compliance framework filters, and grant usage filters can be set to Used in the last [timeframe] or Unused in the last [timeframe]. Admins can also exclude specific entitlements, or everything matching a custom selector, from campaigns and templates.
MCP server tool access presets and manual connectionnew70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Admins can assign automatic tool access per MCP server by choosing a preset (Read tools, All tools) or creating a named toolset, and can connect external MCP servers manually by selecting Configure manually to supply custom OAuth client credentials or use a public client.
C1 groups membership review and creationnew65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
C1 groups, including automated groups, can now be reviewed for membership inside access review campaigns, and admins can create a C1 group from an existing group or entitlement, with C1 proposing a membership rule, inclusion and exclusion lists, and flagging anyone who cannot be adopted.
System log and MCP denial logging accuracybreaking65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
System log entries for failed token requests now record the real failure reason, and MCP tool calls refused by authorization are recorded as denied instead of a generic failure with code 500 — 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. rules or alerts matching the old status details must be updated.
Remediate with AI for unowned NHI findingsnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Admins can get AI-suggested owners for unowned non-human identitynon-human identityA non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. findings via Remediate with AI, which shows up to three candidates with confidence levels.
Administrative permission tighteningbreaking60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Application Administrators who do not own an app can no longer change an entitlement's owners, automations, or manual membership unless they are also Super Administrators; Basic Users can no longer list or download app population reports; and only Super Administrators and Read-Only Administrators can read email provider settings and email activity.
New request sidebar buttonnew55how completely this was documenteddepth20/40specificity15/30actionability20/3055 / 100
Users can start an access request from anywhere in ConductorOne using the new sidebar New request button, which opens a right-side panel without leaving the current view.
Deleted service principal credential API behavior changebreaking55how completely this was documenteddepth20/40specificity15/30actionability20/3055 / 100
Reading, updating, or creating a credential for a deleted service principal now returns not found instead of succeeding — scripts or Terraform relying on the old behavior must be updated.
Personal API key field update validationbreaking50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Updating a personal API key's roles or allowed source IPs through the API now returns an error for fields that cannot be changed, instead of silently ignoring them.
Failed client credentials token requests now always return invalid_client instead of a specific reason — scripts or SIEMs matching on invalid_grant to detect deleted, disabled, or expired credentials must match invalid_client instead.
!
Reading, updating, or creating a credential for a deleted service principal now returns not found instead of succeeding — update any scripts or Terraform that relied on the old behavior.
!
Updating a personal API key's roles or allowed source IPs through the API now returns an error for fields that cannot be changed, instead of silently ignoring them.
!
System log entries for failed token requests now record the real failure reason, and MCP tool calls refused by authorization are recorded as denied instead of a generic failure with code 500 — update SIEM rules or alerts that matched the old status details.
!
The email capabilities gRPC method on the provider service is removed — clients must move to the capabilities service (GET /api/v1/settings/email-capabilities is unchanged).
!
Application Administrators who do not own an app can no longer change an entitlement's owners, automations, or manual membership unless they are also Super Administrators; Basic Users can no longer list or download app population reports; only Super Administrators and Read-Only Administrators can read email provider settings and email activity.
!
Policies are now limited to 16 conditional rules — existing policies above the limit remain editable but cannot grow beyond their current size.
Zscaler is a cloud-based security platform that protects users and data by routing internet and private application traffic through policy-enforced zero trust gateways.
Zscaler's October 2026 GovCloud update brings Real User Monitoring to ZDX, ships Client Connector 5.0 for Windows with new network, TLS, resiliency and DLPDLPData Loss Prevention: a category of controls that inspect and block sensitive data from leaving an organisation via email, web, or removable media, giving cyber tools a policy enforcement layer over data in motion and at rest. capabilities, adds appliance terminal access to Zero Trust Branch, and extends Cloud Connector with AWS account tagging and VDIVDIVirtual Desktop Infrastructure: a model where desktop operating systems run as VMs on a central server and stream to thin clients, giving cyber tools a single managed environment to monitor or scan. provisioning roles.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES1 OF 5 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Client Connector 5.0 for Windows feature setnew80how completely this was documenteddepth32/40specificity28/30actionability20/3080 / 100
Client Connector 5.0 for Windows adds Wi-Fi Name (SSID) as a trusted network criterion, TLS 1.3 support with automatic fallback to TLS 1.2, and machine tunnels in Business Continuity mode to keep devices connected to Private Access apps when the Zscaler cloud is unreachable (requires Windows 11 24H2 build 26100 or later; Limited Availability).︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It also adds Endpoint DLP on ARMARMA family of RISC processor architectures designed by Arm Holdings and licensed to chip makers worldwide; tools target it to run natively on mobile, embedded, and increasingly server and desktop hardware.-based Windows machines (requires ZDP Module 26.08 or later).
— Names exact requirements and versions but no config path2026-10-30-146f5364
0200
AWS account tagging and VDI provisioning roles in Cloud Connectornew71how completely this was documenteddepth25/40specificity28/30actionability18/3071 / 100
Cloud Connector now supports AWS account tagging across cross-account deployments with workload communications for multi-account environment organization (FedRAMP ModerateFedRAMP ModerateA US government authorization tier requiring cloud services to meet a defined set of NIST 800-53 controls before federal agencies can use them, giving cyber tools a pre-vetted compliance baseline for government contracts.; Limited Availability), and adds a VDI Provisioning permission when adding admin roles, with Full, View Only, or None options for role-based access controlrole-based access controlRole-based access control, where permissions are assigned to roles such as reader or administrator and users receive those roles. It makes access easier to manage than individual permission lists. over virtual desktop infrastructure (FedRAMP Moderate and High).
Appliance Admin Console in Zero Trust Branchnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Zero Trust Branch 8.2.1-P1 adds an Appliance Admin Console page giving administrators terminal access to appliances for troubleshooting (FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one. Moderate and High; Limited Availability).
Real User Monitoring in ZDXnew47how completely this was documenteddepth22/40specificity15/30actionability10/3047 / 100
Zscaler Digital Experience (ZDX) now includes Real User Monitoring, capturing and analyzing browser-level user interactions with applications to give visibility into performance bottlenecks (FedRAMP Moderate).
This release centers on Endpoint DLPDLPData Loss Prevention: a category of controls that inspect and block sensitive data from leaving an organisation via email, web, or removable media, giving cyber tools a policy enforcement layer over data in motion and at rest. 26.08, broadening device control, indexing and OCROCROptical character recognition, converting text in an image or scanned document into machine-readable characters. It lets software search or process text that was stored as pixels. capabilities, and adds new Zoom AI transcript scanning that requires existing tenants to reauthorize their integration.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Zscaler Internet Access is a cloud-based secure web gateway that routes user traffic through a zero-trust proxy to enforce security policies, block threats, and control access to the internet and SaaS applications.
This release centers on Endpoint DLPDLPData Loss Prevention: a category of controls that inspect and block sensitive data from leaving an organisation via email, web, or removable media, giving cyber tools a policy enforcement layer over data in motion and at rest. 26.08, broadening device control, indexing and OCROCROptical character recognition, converting text in an image or scanned document into machine-readable characters. It lets software search or process text that was stored as pixels. capabilities, and adds new Zoom AI transcript scanning that requires existing tenants to reauthorize their integration.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
7 FEATURES1 OF 7 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0101
Zoom AI transcript and meeting summary scanningbreaking65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Zoom tenants using Data at Rest Scanning DLP and Malware can now scan AI transcripts and AI meeting summaries generated by Zoom AI Companion.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Existing Zoom tenants onboarding this capability must add additional scopes, webhook subscriptions, and reauthorize their Zoom integration.
— Names required reauthorization steps, actionable for admins2026-10-30-f0dbe129
thinner coverage below
0200
Device Control extended to portable devices and removable medianew55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Endpoint DLP 26.08 now extends Device Control to portable devices (smartphones and cameras), CD/DVD, and floppy disk channels (floppy disk is Windows only).
— Names exact device channels but no policy config details2026-10-30-f0dbe129
0300
IDM indexing removes 20-file folder limitimproved50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Endpoint DLP 26.08 now lets IDM index all files in a folder, removing the previous 20-file limit.
Existing Zoom tenants onboarding AI transcript and AI meeting summary scanning must add additional scopes, webhook subscriptions, and reauthorize their Zoom integration.
Zscaler Private Access rolled out two FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one.-limited-availability additions to Application Segments: usage reporting and AI-powered segment recommendations.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Zscaler Private Access is a zero-trust network access service that securely connects users to internal applications without exposing the corporate network to the internet.
Zscaler Private Access rolled out two FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one.-limited-availability additions to Application Segments: usage reporting and AI-powered segment recommendations.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Application Segments usage reporting and AI recommendationsnew69how completely this was documenteddepth25/40specificity22/30actionability22/3069 / 100
Admins can view or download Application Segments Usage reports from the Zscaler Admin Console (navigate to Application Segments > Usage, then View or Download) to see which segments are active and which user groups are accessing them; this requires the Segmentation add-on and is available for FedRAMP ModerateFedRAMP ModerateA US government authorization tier requiring cloud services to meet a defined set of NIST 800-53 controls before federal agencies can use them, giving cyber tools a pre-vetted compliance baseline for government contracts. and High.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Also added are AI-powered recommendations that analyze user logs and suggest application segments based on application similarity or user behavior, helping discover new segments and find missing applications for existing ones, also for FedRAMP Moderate and High.
Identify unused application segments and audit which user groups are accessing active ones — useful for access hygiene reviews.
📍In the Zscaler Admin Console, go to Application Segments › Usage, then select View or Download to export the Application Segments Usage report.
— Names exact UI path and add-on requirement, but lacks AI mechanism details.2026-10-30-959152fa
Veeam Kasten is a Kubernetes-native platform for backing up, restoring, and migrating containerized applications and their persistent data.
Kasten K10 9.0.10 adds a restore-side blueprint hook for pre-restore lifecycle control and a Presets filter on the Policies page, alongside several breaking changes around OpenShift support, STSSTSAWS Security Token Service, an Amazon Web Services API that issues short-lived credentials for IAM roles, letting cyber tools authenticate to AWS without storing long-term secrets. endpoints, and immutability protection.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES2 OF 5 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
restorePrehook blueprint actionnew93how completely this was documenteddepth35/40specificity28/30actionability30/3093 / 100
Adds the restorePrehook blueprint action, the restore-side counterpart to backupPrehook, assignable via a BlueprintBinding or the kanister.kasten.io/blueprint annotation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It is called once before each matched resource is restored to quiesce operator-managed applications, remove finalizers, or delete conflicting resources, and aborts the restore if it fails.
Quiesce an operator-managed application before restore by wiring a restorePrehook action to matching resources via an annotation on the workload.
— Names exact action, binding mechanism, and failure behavior with runnable example.9.0.10
0201
Regional STS endpoint for VDC Vault AWS profilesbreaking70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
VDC Vault AWS location profiles using the Registration authentication method now request credentials from the regional STS endpoint (e.g. sts.eu-south-1.amazonaws.com) instead of the global sts.amazonaws.com; environments that restrict outbound traffic must allow access to these regional endpoints.
— Names exact endpoint pattern and the network change required.9.0.10
0300
Immutability protection applied across shared location profilesbreaking65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
If two location profiles point at the same object store location and only one has an immutability protection period, Kasten K10 now applies that protection period to backups using the other profile too; if that profile's credentials lack immutable-backup permissions, its backups will fail until those permissions are added.
— Explains mechanism and failure condition but no config surface to act on directly.9.0.10
0402
OpenShift 4.16/4.17 support removedbreaking60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Support for Red Hat OpenShift 4.16 and 4.17 has been removed; users must upgrade to OpenShift 4.18 or later before upgrading Veeam Kasten.
— Clear version numbers and required migration action.9.0.10
thinner coverage below
0500
Presets filter on Policies pagenew50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Adds a Presets filter to the Policies page, letting users filter policies by one or more presets, by any preset, or by no preset.
— Describes the filter options but only a UI path, no further mechanism.9.0.10
└──▷ BREAKING ON UPGRADE
!
Support for Red Hat OpenShift 4.16 and 4.17 has been removed; upgrade to OpenShift 4.18 or later before upgrading Veeam Kasten.
!
VDC Vault AWS location profiles using the Registration authentication method now request credentials from the regional STS endpoint (e.g. sts.eu-south-1.amazonaws.com) instead of sts.amazonaws.com; environments that restrict outbound traffic must allow access to these regional endpoints.
!
If two location profiles point at the same object store location and only one has an immutability protection period, Kasten K10 now applies that protection period to backups using the other profile too; if that profile's credentials lack immutable-backup permissions, its backups will fail until those permissions are added.
CISO Assistant's v4.2.0 release adds six new compliance frameworks, expands EBIOS RMEBIOS RMA French risk-management method published by ANSSI for analysing cyber threats and selecting countermeasures; tools use it to structure risk assessments that satisfy French and EU regulatory expectations. exports with Workshop 5 data, enforces evidence attachments on questionnaire responses, and extends localization and TPRMTPRMAssessing and monitoring the security risk an organization takes on through its vendors, suppliers and service providers. It covers the questionnaires, evidence and continuous checks behind letting a third party hold your data. capabilities.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
CISO Assistant is a one-stop-shop GRC platform for Risk Management, AppSec, Compliance & Audit, TPRM, BIA, Privacy, and Reporting. It supports 200+ global frameworks with automatic control mapping, including ISO 27001, NIST CSF, SOC 2, CIS, PCI DSS, NIS2, DORA, GDPR, HIPAA, CMMC, and more.
CISO Assistant's v4.2.0 release adds six new compliance frameworks, expands EBIOS RMEBIOS RMA French risk-management method published by ANSSI for analysing cyber threats and selecting countermeasures; tools use it to structure risk assessments that satisfy French and EU regulatory expectations. exports with Workshop 5 data, enforces evidence attachments on questionnaire responses, and extends localization and TPRMTPRMAssessing and monitoring the security risk an organization takes on through its vendors, suppliers and service providers. It covers the questionnaires, evidence and continuous checks behind letting a third party hold your data. capabilities.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
10 FEATURES0 OF 10 FEATURESmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Folders API filter by ref_idimproved70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Filter folders by ref_id via the folders API to narrow folder lookups programmatically.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact API parameter, immediately usablev4.2.0
0200
Six new compliance frameworks added to librarynew65how completely this was documenteddepth20/40specificity30/30actionability15/3065 / 100
Add the Czech Decree 409/2025 framework and ZoKB risk matrix, the PIPEDA framework (Schedule 1, verbatim official text), the MonServiceSécurisé framework, the NCA DCC-1:2022 (Data Cybersecurity Controls) framework, the NCA CSCC-1:2019 (Critical Systems Cybersecurity Controls) framework, and OWASP Top 10 Web (2025) to the library.
— Names every framework added, but no detail on mapping mechanicsv4.2.0
thinner coverage below
0300
UI localization for Norwegian, Italian and Turkishnew55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Add Norwegian Bokmål (nb) UI localization, including forms, tables, and dynamic strings; add Italian translations for vendor evaluation quick forms and DPIADPIAA Data Protection Impact Assessment — a structured process, required under GDPR, for identifying and mitigating privacy risks before deploying a system that processes personal data at scale. workflows; and complete Turkish localization.
— Names languages and covered areas but no usage mechanismv4.2.0
0400
TPRM module gains custom fields and vendor visualsnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Add custom fields and labels on entity assessments, plus vendor posture visuals with tier-based display, in the TPRM module.
— Names module and two additions, lacks configuration detailv4.2.0
0500
Per-audit PDF report template overridenew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Override the PDF audit report template (Typst-based) per audit in the Pro edition.
— Names mechanism (Typst) and edition scope, no exact stepsv4.2.0
0600
Evidence required on questionnaire responsesnew50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Require evidence attachments on questionnaire responses before submission.
— Clear behaviour change, no config key or toggle namedv4.2.0
0700
EBIOS RM export includes Workshop 5improved40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Expand EBIOS RM exports to now include Workshop 5 data.
— States what changed but not export format or access pathv4.2.0
0800
Libraries moved under Catalog in sidebarbreaking40how completely this was documenteddepth10/40specificity15/30actionability15/3040 / 100
The Libraries navigation entry is now located under Catalog in the sidebar.
— Exact navigation change, no further rationale givenv4.2.0
0900
Portals editor supports documentsimproved35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Improve the portals editor with support for documents.
microsandbox v0.7.12 adds support for running nested virtualization inside sandboxes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
easy, fast, programmable and local-first microVM runtime and library
microsandbox v0.7.12 adds support for running nested virtualization inside sandboxes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat'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–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough 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.
0100
Nested virtualization in sandboxesnew30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Sandboxes can now run with nested virtualization enabled, allowing guest VMs to host their own hypervisor workloads.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Describes capability but no config flag or setup steps givenv0.7.12
Arcade is the actions runtime for enterprise AI agents â one control point to enforce, execute, and govern every action, every time.
Arcade adds 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. Apps, rendering interactive editors for Gmail, Slack, and Outlook Mail inside the chat, with file upload/download support and policy-enforced UI controls.
Arcade now supports MCP Apps, an extension to the 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. that renders interactive interfaces (forms, editors, dashboards) inside the chat client instead of requiring tab-switching.
New integrationFile uploads and downloads now work inside MCP Apps by running the app code locally, opening the native file picker and writing large files straight to disk — already available in the Slack, Gmail, and Outlook Mail apps.
Authorization and governance rules are enforced at the point when the MCP App interface is built and again at the point of action, so UI controls (such as a Send button) are only shown when the user's permissions allow the underlying tool call.