The Cyber Toolchain — issue 075, September 15, 2026
THE CYBER TOOLCHAIN
NO. 075
Tail
THE DAILY RELEASE FIREHOSE
PUBLISHED SEPTEMBER 15, 2026 · EVERY DAY
EDITIONStail|grep|head|ls|diff|uniq
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. Zeek 9.0 can now ingest mirrored VXLANVXLANA network encapsulation protocol that wraps Layer 2 Ethernet frames inside UDP packets, extending virtual LANs across Layer 3 networks. Cyber tools use it to simulate or inspect traffic across large-scale virtualized and cloud environments./GENEVEGENEVEA network tunneling protocol that encapsulates Ethernet frames in UDP, designed to be extensible via metadata headers. Cyber tools use it to build flexible overlay networks across physical infrastructure. traffic directly, so cloud-overlay taps land in your sensors without a decap appliance. ZeroPath put a 0–100 score on findings and moved repo permissions server-side. And InsightIDR can pull Domain Controller security logs through the Insight Agent and act on ADADActive Directory, Microsoft's directory service for Windows networks, storing user accounts, credentials, and policies — tools use it to query or attack identity and access management infrastructure. accounts from the console.
detect
Get cloud-overlay and Domain Controller traffic into your sensors without extra plumbing
Zeek 9.0's UDPUDPA network protocol that sends individual messages without guaranteeing delivery or order. Applications trade built-in reliability for less overhead and can add their own recovery. packet source reads VXLAN/GENEVE mirror sessions straight off the wire, removing the decapsulation hop that cloud traffic mirroring normally forces, and adds NTP and multicast logs plus deeper TLS, DCE-RPCDCE-RPCA remote procedure call protocol standardized by the Open Group that lets a program call functions on a remote system over a network, giving cyber tools a structured way to parse or emulate Windows service communication., KerberosKerberosA network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. and 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. events. InsightIDR collects DC security logs via the Insight Agent, so the usual WEF/collector chain for the noisiest and most valuable log source on the estate goes away.
Triage application findings by rank instead of by severity bucket
ZeroPath's 0–100 priority score plus refined 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. 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. severity handling gives an ordered queue rather than a pile of Highs, and repository permissions are now enforced server-side rather than in the UI. Codex Security's $codex-security:assess-patch-risk and $codex-security:verify-fix close the other end — judging whether a proposed fix actually lands before it ships.
Contain a compromised AD account from the same console you saw the alert in
InsightIDR's Active DirectoryActive DirectoryMicrosoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments. response actions cut the hop to a domain admin console during the first minutes of an account-takeover investigation. Threat Command adds an IOCIOCAn indicator of compromise, an observable clue that may point to malicious activity, such as a suspicious file hash or domain. It is evidence to investigate, rather than proof by itself. enrichment pivot from Rapid7 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. and Automation into the Threat Intelligence database, plus a query language for alert search, so checking whether an indicator is already known stops being a copy-paste into a second tab.
sippts v4.2.1 adds 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.-based severity scoring to CVE detection results, sorting findings from most to least severe.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
CVSS scoring for CVE resultsimproved65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
The scan module now assigns CVSS scores with severity colours to detected CVEs and orders findings worst-first.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ This is backed by a 6th column added to data/cve.csv carrying the CVSS score (list version 0.5), which requires sippts 4.2.1 or newer to read.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact file, column addition, and version requirement.v4.2.1
gowitness - a golang, web screenshot utility using Chrome Headless
gowitness 3.2.0 adds support for reusing authenticated Chrome sessions during scans and a flag to disable colored log output.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Reuse authenticated Chrome sessions via user data dirnew77how completely this was documenteddepth25/40specificity22/30actionability30/3077 / 100
The new --chrome-user-data-dir flag lets you point gowitness at an existing Chrome User Directory, enabling reuse of an already-authenticated browser session (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ after manually logging into an SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. portal) across gowitness runs instead of re-authenticating each scan.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Screenshot targets while inheriting an already-authenticated Chrome profile (e.g. after manually logging into an SSO portal) to avoid re-authenticating during a scan.
$ gowitness scan single --url "https://internal.corp.example.com" --write-db--chrome-user-data-dir ~/.config/google-chrome/Default
— Named flag with clear mechanism and runnable example command.3.2.0
thinner coverage below
0200
Disable ANSI color in log outputnew45how completely this was documenteddepth10/40specificity15/30actionability20/3045 / 100
A new --no-log-color global flag disables ANSI color codes in gowitness's log output.
— Named flag but no example or further context given.3.2.0
Join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity.
GitHub Copilot's auto model selection now lets users tune the cost-quality tradeoff with new optimization tiers, rolled out across VS Code, Copilot CLI, and the GitHub Copilot app.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Configurable tiers for Copilot auto model selectionnew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Copilot auto model selection gains three optimization tiers — efficiency, balance, and intelligence — letting users control how auto weighs cost, quality, and response latency per prompt.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The tier configuration is rolled out in Visual Studio Code, Copilot CLI, and the GitHub Copilot app.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
A fully-managed, enterprise-scale solution to control, secure, and distribute software packages and containers.
Cloudsmith's latest release focuses on visibility and access control: teams can now export vulnerability findings, audit per-package changes, grant narrower read-only roles, and get richer GitHub secret-scanning alerts.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Granular billing, usage and OIDC read-only rolesnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Workspace owners can now grant members individual read-only access to billing, usage, and 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. data without assigning the Manager or Owner role, via separate toggles for Billing, Usage, and OIDC privileges under Workspace Settings > Members.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Give a finance or compliance team member visibility into billing and OIDC configuration without elevating their role to Manager or Owner.
📍In the Cloudsmith web app, go to Workspace Settings › Members, select the member, and enable the individual Billing, Usage, or OIDC read-only privilege toggles separately.
Richer GitHub secret-scanning alert emailsimproved40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
GitHub secret-scanning email notifications now list every location an exposed Cloudsmith API key was found in a GitHub repository, each with a direct link to the detection.
Invicti's scan location exports now surface HTTP method and status code data across CSV, JSON, and XML formats, making it easier to spot authentication gaps in crawl coverage.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Official documentation for Invicti AppSec Platform, Invicti Platform, and Invicti Enterprise — web application security testing, DAST, API security, and vulnerability management.
Invicti's scan location exports now surface HTTP method and status code data across CSV, JSON, and XML formats, making it easier to spot authentication gaps in crawl coverage.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
HTTP method and status code columns in scan location exportsimproved70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Scan location exports now include HTTP Methods and Status Codes fields.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The CSV (Locations) export gets these columns appended at the end of each row, and the JSON and XML scan location export formats gain matching HTTP method and HTTP response code fields.
After a scan completes, export locations in CSV to spot routes returning 401 or 403 — indicating authentication gaps in crawl coverage.
📍In the scan results, go to Scan › Locations › Export, select CSV (Locations), then open the file and filter the Status Codes column for 401 or 403 responses.
Levo shipped a synchronous CreateFinding API mode, per-application security-test configuration overrides, a beta Service Graph for visualizing API call relationships, expanded RBACRBACRole-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. permissions and audit logging, broader form-encoded body and unauthenticated-access testing, plus a new API discovery source and two new integrations.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Continuous API Security Assurance â observe, detect, and protect your APIs.
Levo shipped a synchronous CreateFinding API mode, per-application security-test configuration overrides, a beta Service Graph for visualizing API call relationships, expanded RBACRBACRole-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. permissions and audit logging, broader form-encoded body and unauthenticated-access testing, plus a new API discovery source and two new integrations.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
11 FEATURES0 OF 11 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
RBAC permissions and audit logging expansionnew80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Adds Test Runs update and delete permissions, with Owner and Admin holding them by default while other roles require explicit grants; adds Admin-wide delete permissions across the platform; grants Security Engineer the ability to delete endpoints; and adds role and permission changes to the audit log under a new Role resource type, recording the role's identifier, permission set, and user-assignment actions as distinct events.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Per-application security-test configuration overridesnew75how completely this was documenteddepth30/40specificity20/30actionability25/3075 / 100
Adds per-application security-test configuration overrides via a new Configuration tab on each application's Security Testing page, with settings marked as inherited from the environment or overridden for that application.
Override rate-limit and other security-test settings for a single high-traffic application without affecting environment-wide defaults.
📍In the Levo console, open the application, go to Security Testing › Configuration tab, locate the setting you want to change (e.g., rate limit), toggle it from Inherited to Override, and set the desired value (shown in requests per minute).
On-Prem Deployments monitoring and setupnew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Adds an Active / Stale / Down status filter on the On-Prem Deployments screen for Satellites, Taggers, Sensors, DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces. Runners, and AI Gateways alongside the existing lifecycle filter, and adds an Install Satellite action to the Taggers tab on On-Prem Deployments.
Unauthenticated-access probing in Broken User Authentication testsimproved60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Extends Broken User Authentication tests to probe for unauthenticated access even when no authenticated baseline is available, reporting genuine resource-shaped responses as Medium, low-confidence unconfirmed findings.
Consolidated component-health alert emailsimproved50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Consolidates component-health alerts for large fleets into a single email with a CSV listing components oldest-heartbeat first, instead of one email per detection wave.
GitGuardian Detection Engine scans code repositories to identify and alert on exposed secrets, credentials, and sensitive data.
GitGuardian's Detection Engine adds two new secret analyzers, sharpens entropy-based false positive filtering, and improves detection recall for n8n and HashiCorp Vault credentials.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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.
0100
Entropy secret filter for checksum variablesimproved60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Adds a generic_high_entropy_secret filter that suppresses false positives when the assigned variable name ends with checksum, with no loss of recall.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
n8n host detection for MCP and API tokensimproved60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Extends the n8n MCP Access Token and n8n API Key detectors to recognize n8n hosts given as a container service name or as a scheme-less hostname, and to reject unreachable private IP hosts.
New analyzers for Akamai and Docker Hub secretsnew45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Adds a secret analyzer for Akamai API Credentials and a new analyzer for Docker Hub personal access tokenspersonal access tokensA 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..
iLEAPP v2026.4.1 upgrades its Apple Unified Logs parser and extends OS version recognition to cover the newest iOS, macOS, tvOS, visionOS, and watchOS releases.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Unified Logs engine upgraded to v0.7.0improved57how completely this was documenteddepth25/40specificity22/30actionability10/3057 / 100
The Apple Unified Logs parsing engine is upgraded to unifiedlog_iterator v0.7.0, which fills previously empty process paths on Simpledump and Statedump rows and logs the parser version at import time.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names mechanism and affected row types but no reproduction steps.v2026.4.1
0200
New OS build recognition in build ID mapnew45how completely this was documenteddepth10/40specificity25/30actionability10/3045 / 100
Automated Malware Analysis - Development and Licensing of Automated Malware Analysis Tools to Fight Malware
Joe Security shipped Joe Reverser 2.1 Golden Eagle, expanding its agentic automated analyst for malware, phishing, malicious documents and web-based threats, with tighter integration into automated analysis workflows.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Joe Reverser 2.1 'Golden Eagle' agentic analystimproved40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
Joe Reverser 2.1, codenamed Golden Eagle, is an agentic automated analyst that covers malware, phishing campaigns, malicious documents, and web-based threats, with enhanced autonomous analysis and reverse engineering capabilities.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The release also improves integration of Joe Reverser's agentic capabilities into automated analysis workflows.
Zeek is a powerful network analysis framework that is much different from the typical IDS you may know.
Zeek 9.0 adds a UDPUDPA network protocol that sends individual messages without guaranteeing delivery or order. Applications trade built-in reliability for less overhead and can add their own recovery. packet source for VXLANVXLANA network encapsulation protocol that wraps Layer 2 Ethernet frames inside UDP packets, extending virtual LANs across Layer 3 networks. Cyber tools use it to simulate or inspect traffic across large-scale virtualized and cloud environments./GENEVEGENEVEA network tunneling protocol that encapsulates Ethernet frames in UDP, designed to be extensible via metadata headers. Cyber tools use it to build flexible overlay networks across physical infrastructure. mirroring, a Spicy-based ZIP file analyzer, new NTP and multicast logs, and expanded TLS, DCE-RPCDCE-RPCA remote procedure call protocol standardized by the Open Group that lets a program call functions on a remote system over a network, giving cyber tools a structured way to parse or emulate Windows service communication., KerberosKerberosA network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. and LDAP event coverage, while removing Broker's legacy embedded WebSocket server in favor of Cluster::listen_websocket().︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
24 FEATURES3 OF 24 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
UDP packet source for VXLAN/GENEVE mirroringnew95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Zeek adds a UDP packet source via zeek -i udp::0.0.0.0:4789:vxlan (bundled zeek-packet-source-udp plugin) to receive VXLAN or GENEVE mirror traffic over UDP without needing raw packet capturepacket captureA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic., using SO_REUSEPORT so multiple workers can kernel-load-balance the traffic.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The new policy/frameworks/conn_key/packet_source/udp/vxlan_vni policy script adds VNI-aware connection tracking when this source is used.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Receive VXLAN mirror traffic over UDP on a busy sensor where multiple Zeek workers share the load via kernel SO_REUSEPORT balancing — no raw packet capture interface needed.
$ zeek -i udp::0.0.0.0:4789:vxlan
Enable VNI-aware connection tracking so each VXLAN tenant network is tracked separately — load alongside the UDP packet source.
— Full command, plugin and mechanism given with runnable examplesv9.0.0
0200
Configurable JSON string escape policynew88how completely this was documenteddepth30/40specificity30/30actionability28/3088 / 100
Adds Log::json_string_escape_policy (type JSON::STRING_ESCAPE_POLICY_*) to make control-character and invalid UTF-8 escaping in JSON logging configurable; default remains JSON::STRING_ESCAPE_POLICY_HEX. Setting it to JSON::STRING_ESCAPE_POLICY_TSV in local.zeek switches to reversible TSVTSVA plain-text format storing tabular data with fields separated by tab characters, making it easy for cyber tools to parse and exchange structured records without a CSV parser's quoting complexity.-style encoding for round-tripping binary fields.
Switch JSON log escaping to TSV-style (reversible) encoding instead of the default hex encoding, so downstream 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. parsers can round-trip binary fields correctly.
— Exact config key, values, and runnable example givenv9.0.0
0301
Legacy Broker WebSocket server removedbreaking82how completely this was documenteddepth30/40specificity30/30actionability22/3082 / 100
Broker's legacy embedded WebSocketWebSocketA protocol that upgrades an HTTP connection into a persistent, full-duplex channel, letting a server push data to a client without repeated polling. Cyber tools use it for real-time event streaming and live command output. server is fully removed: Broker::BrokerProtocol, Broker::default_port_websocket, Broker::default_listen_address_websocket, Broker::web_socket_buffer_size, and Broker::web_socket_overflow_policy no longer exist, and the BrokerProtocol enum and the Broker manager's Listen() C++ method's optional BrokerProtocol argument have been removed. Use Cluster::listen_websocket() and the ZEEK_WEBSOCKET_* environment variables instead.
— Names every removed symbol and the migration pathv9.0.0
0400
Storage framework options for known-* scriptsimproved80how completely this was documenteddepth28/40specificity30/30actionability22/3080 / 100
Extends the known-certs, known-hosts, and known-services scripts with storage-framework options including enable_hosts_persistence, host_store_prefix, host_store_backend_type, and host_store_backend_options, using a SQLite backend under Cluster::default_store_dir by default.
— Names every option and default backend locationv9.0.0
0502
zeek::fmt() no longer safe off the main threadbreaking76how completely this was documenteddepth28/40specificity28/30actionability20/3076 / 100
Calling zeek::fmt() from non-main threads now emits a warning (and aborts in debug builds); plugins spawning threads must switch to threading::BasicThread::Fmt() or std::format().
— Names replacement APIs and build-mode behaviourv9.0.0
0600
Spicy-based ZIP file analyzernew75how completely this was documenteddepth25/40specificity28/30actionability22/3075 / 100
Adds policy/files/zip/register.zeek to map the bundled Spicy ZIP file analyzer to the application/zip MIME type; recursive ZIP depth is controlled by Spicy::max_file_depth.
— Names config script and depth control, no usage examplev9.0.0
0700
LDAP SASL payload forwarding to GSSAPI/NTLMimproved74how completely this was documenteddepth28/40specificity28/30actionability18/3074 / 100
Extends the 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. analyzer to forward SASLSASLA framework for plugging authentication mechanisms into network protocols, standardized by the IETF, so a tool can support password, Kerberos, or certificate login without rewriting auth logic per protocol. payloads from bindRequest/bindResponse to the GSSAPI and NTLMNTLMA Windows authentication protocol that proves knowledge of a password through a challenge and response. Captured authentication exchanges can be abused in relay attacks when protections are absent. parsers, enriching ntlm.log and kerberos.log.
Kerberos AP-REQ tracking improvementsimproved74how completely this was documenteddepth28/40specificity28/30actionability18/3074 / 100
Extends krb_ap_request() event with an in_kdc_padata parameter to indicate whether the AP-REQ is embedded in KDC/TGS pre-authentication data, and populates the service and cipher columns in kerberos.log AP entries, which were previously unset.
— Names event parameter and log columns, before/after givenv9.0.0
0900
New HTTP header validation weirdsnew73how completely this was documenteddepth25/40specificity30/30actionability18/3073 / 100
Extends the HTTP analyzer with nine new weirds — HTTP_bad_chunk_size, HTTP_chunked_multi, HTTP_content_length_0_and_expect_100_cont, HTTP_content_length_leading_zeros, HTTP_bad_content_length, HTTP_obsolete_line_folding, HTTP_content_length_and_chunked, HTTP_content_range_and_chunked, and HTTP_expect_not_100_continue — for unusual Content-Length, Transfer-Encoding, and Expect header usage.
New `?as` operator and expanded `as` castingimproved68how completely this was documenteddepth25/40specificity25/30actionability18/3068 / 100
Adds ?as operator to test whether a value can be safely cast to a target type at script level, and extends the as casting operator to cover all type conversions previously requiring explicit BiFs such as interval_to_double(), plus additional natural companions.
— Names both operators and an example BiF replacedv9.0.0
1200
DCE-RPC authentication eventnew65how completely this was documenteddepth25/40specificity22/30actionability18/3065 / 100
Adds dce_rpc_auth() event giving script-level access to the security provider, per-message protection, and authentication context in DCE-RPCRPCRemote Procedure Call, a protocol that lets a program execute a function on another machine as if it were local, giving cyber tools a structured way to communicate across processes or hosts without managing raw sockets. PDUs.
Multicast participants lognew63how completely this was documenteddepth20/40specificity25/30actionability18/3063 / 100
Adds policy/protocols/conn/multicast-participants.zeek, producing a new multicast_participants.log with IGMPIGMPA network-layer protocol used by IPv4 hosts and routers to manage multicast group membership, letting routers know which hosts want traffic for a given multicast address.-derived data about hosts participating in multicast connections.
— Names log and script but no field-level detailv9.0.0
1400
New TLS extension events for ECH and signature algorithmsnew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Adds ssl_extension_encrypted_client_hello, an event carrying information about the TLS encrypted_client_hello extension, and ssl_extension_signature_algorithms_cert, raised for the TLS signature_algorithms_cert extension.
— Names both events but no field-level detailv9.0.0
thinner coverage below
1500
Syslog analyzer TCP supportimproved59how completely this was documenteddepth22/40specificity22/30actionability15/3059 / 100
Extends the Syslog analyzer to support TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. via Octet Counting and Non-Transparent-Framing on port 514/tcp.
QUIC detection signatures for non-standard portsnew59how completely this was documenteddepth22/40specificity22/30actionability15/3059 / 100
Adds DPD signatures for QUICQUICA UDP-based transport protocol standardized by the IETF that bakes in TLS 1.3, multiplexed streams, and connection migration, giving tools low-latency encrypted transport without head-of-line blocking. version 1 and QUIC version 2 to attach the QUIC analyzer on non-port-443 UDP connections when a signature match occurs.
Non-final OpaqueType for plugin-defined scripting typesnew59how completely this was documenteddepth25/40specificity22/30actionability12/3059 / 100
Makes OpaqueType non-final and adds hooks for hashing, casting, and default initialization, enabling plugins to introduce new scripting types storable in sets/tables and castable to existing Zeek types (experimental).
— Explains mechanism but marked experimental, no examplev9.0.0
1800
Standalone ZeroMQ connection without cluster node eventsimproved59how completely this was documenteddepth22/40specificity22/30actionability15/3059 / 100
Splits zeromq/main.zeek options into a separate zeromq/options.zeek file to allow standalone Zeek processes to connect to the ZeroMQZeroMQA messaging library that provides socket-like abstractions for async message passing over TCP, IPC, or in-process transports, letting tools wire together distributed components without a dedicated message broker. layer without participating in cluster node events.
Case-insensitive and single-line pattern modifiers in Input Frameworkimproved57how completely this was documenteddepth20/40specificity22/30actionability15/3057 / 100
Extends the Input Framework to read pattern values with case-insensitive (/foo/i) and single-line (/bar/s) modifiers.
Multi-interface support in zeek.conf and systemd generatorimproved45how completely this was documenteddepth15/40specificity18/30actionability12/3045 / 100
Extends zeek.conf and zeek-systemd-generator to support multiple interfaces and multi-host deployments.
— Named files but no config keys or example shownv9.0.0
2400
FreeBSD moved to community-patch supportdeprecated41how completely this was documenteddepth18/40specificity15/30actionability8/3041 / 100
FreeBSD is no longer officially supported with CI testing; it moves to the same community-patch model as OpenBSD.
— States change but no timeline or migrationv9.0.0
└──▷ BREAKING ON UPGRADE
!
Broker's legacy embedded WebSocket server is fully removed: Broker::BrokerProtocol, Broker::default_port_websocket, Broker::default_listen_address_websocket, Broker::web_socket_buffer_size, and Broker::web_socket_overflow_policy no longer exist. Use Cluster::listen_websocket() and the ZEEK_WEBSOCKET_* environment variables instead.
!
The BrokerProtocol enum has been removed and the Broker manager's Listen() C++ method no longer accepts its optional BrokerProtocol argument; it always uses Broker's native protocol.
!
Calling zeek::fmt() from non-main threads now emits a warning (and aborts in debug builds); plugins spawning threads must switch to threading::BasicThread::Fmt() or std::format().
!
The ZeekJS plugin now requires std::format from C++20, dropping support for older distributions using GCC 12.x such as Debian 12.
!
FreeBSD is no longer officially supported with CI testing; it moves to the same community-patch model as OpenBSD.
Fastly is a content delivery network and edge computing platform that accelerates web content delivery and application performance globally.
Fastly's CLI gained new logging subcommands for Log Explorer and Insights, while the JavaScript SDK added an async method for cache transaction lookups.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Async cache transaction lookup in JS SDKnew60how completely this was documenteddepth15/40specificity20/30actionability25/3060 / 100
The Fastly JavaScript SDK 3.46.0 adds a CoreCache.transactionLookupAsync method for performing asynchronous cache transaction lookups.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Rapid7 InsightCloudSec's 26.9.15 release adds new Query Filters and Insights covering Azure Cache for Redis, Cosmos DB, and Database Instances (PostgreSQL, SQL Server, MySQL), backed by expanded harvesters that collect the underlying encryption, authentication, and network-access properties.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Rapid7 InsightCloudSec is a cloud security platform that provides visibility, compliance, and threat detection across multi-cloud environments.
Rapid7 InsightCloudSec's 26.9.15 release adds new Query Filters and Insights covering Azure Cache for Redis, Cosmos DB, and Database Instances (PostgreSQL, SQL Server, MySQL), backed by expanded harvesters that collect the underlying encryption, authentication, and network-access properties.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Azure Cache for Redis security visibilitynew80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds Cache Instance Encryption Type Query Filter to identify Cache Instances by encryption configuration (Customer-Managed Key vs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Provider-Managed Key), defaulting to Provider-Managed Key detection, and Cache Instance Access Key Authentication Enabled Query Filter to identify Azure Cache for Redis instances where disableAccessKeyAuthentication is set to false. Adds Insights Cache Instance Not Using Customer Managed Key and Cache Instance With Access Key Authentication Enabled (aligned with 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. Azure Database Services Benchmark v2.0.0 Control 2.9). Expands the Azure Cache for Redis harvester to collect Customer-Managed Key (CMK) encryption properties from Azure Cache for Redis Enterprise resources.
— Names filters, insights and CIS mapping but no exact UI path or API call2026-09-15-3c05e607
0200
Azure Cosmos DB Distributed Table coveragenew80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds Distributed Table Public Network Access Query Filter to identify Azure Cosmos DB accounts with public network access enabled, and Distributed Table Without Diagnostic Logging Query Filter to identify Cosmos DB accounts missing a specified diagnostic log category, defaulting to allLogs. Adds Insights Distributed Table With Public Network Access Enabled (mapped to CIS Controls v8.1.2 safeguard 4.4, CMMC L1/L2, NIST SP 800-53 Rev. 5, and Microsoft Cloud Security Benchmark v1) and Distributed Table Without Diagnostic Logging, requiring the allLogs category. Expands the Azure Diagnostic Settings harvester to collect diagnostic settings for Cosmos DB accounts (Microsoft.DocumentDb/databaseAccounts) and the Distributed Table harvester to collect the public_network_access property.
— Named filters, insights, resource type and compliance mappings, no direct API call2026-09-15-3c05e607
0300
Database Instance security checks across PostgreSQL, SQL Server, MySQLnew80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds Database Instance Entra-Only Authentication Query Filter to identify Database Instances without Microsoft Entra-only authentication configured. Adds Insights: Database Instance Without Microsoft Entra-Only Authentication (PostgreSQL); Database Instance Public Network Access Enabled (SQL Server); Database Instance Without Secure Transport Enabled (MySQL), detecting Azure Database for MySQL Flexible Servers where require_secure_transport is not enabled; and Database Instance Without Connection Log Auditing Events (MySQL), detecting instances where audit_log_events does not include CONNECTION or CONNECTION_V2, aligned with CIS Azure Database Services Benchmark v2.0.0 Control 5.6. Expands the Azure Database Instance harvester to collect Microsoft Entra-only authentication status for Azure Database for PostgreSQL flexible servers.
— Names four insights, one filter, two config fields, and CIS control mapping2026-09-15-3c05e607
Plerion is a cloud security platform that discovers and manages vulnerabilities and misconfigurations across infrastructure.
Plerion added enterprise identity and access controls this window: SCIM 2.0SCIM 2.0A standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. provisioning, syncable user groups, organization-scoped API keys, and break-glass admin accounts.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
SCIM 2.0 provisioning supportnew65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Plerion adds SCIMSCIMA standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. 2.0 provisioning so Okta, 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 any SCIM 2.0 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. can create, update, and deactivate Plerion users.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Existing users are matched by email address and adopted automatically into the SCIM-managed set.
— Names identity providers and matching logic but no exact setup steps.SCIM provisioning:
0200
Organization-scoped API keysnew60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Adds organization API keys scoped to the whole organization with read or readWrite access, intended for use by identity providersidentity providersA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. performing SCIM provisioning.
— Names concrete access levels but no endpoint or generation flow.SCIM provisioning:
thinner coverage below
0300
Break-glass admin accountsnew45how completely this was documenteddepth25/40specificity10/30actionability10/3045 / 100
Organization admins can be designated as break-glass accounts that can always sign in with a password and cannot be deactivated by an identity provider; at least one is required when SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. or SCIM is enabled.
— Describes the safeguard's rules without setup instructions.SCIM provisioning:
0400
User groups with role inheritancenew40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
New user groups grant roles to every member, and can be synced from an identity provider over SCIM or created directly within Plerion.
— Explains behavior but gives no concrete creation or config path.SCIM provisioning:
Kata Containers 4.2.0 adds TLS to the monitoring endpoint, moves block and VFIOVFIOA Linux kernel framework that lets userspace programs take direct ownership of a PCI device, bypassing kernel drivers, giving cyber tools low-latency, isolated hardware access without running in kernel space. device attachment in the QEMUQEMUAn open-source machine emulator and virtualizer that lets software run a guest OS or CPU architecture on a different host, giving cyber tools an isolated, inspectable execution environment without dedicated hardware. runtime to file-descriptor passing, and removes two unsupported runtime-rs config overrides.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Kata Containers is an open source project and community working to build a standard implementation of lightweight Virtual Machines (VMs) that feel and perform like containers, but provide the workload isolation and security advantages of VMs. https://katacontainers.io/
Kata Containers 4.2.0 adds TLS to the monitoring endpoint, moves block and VFIOVFIOA Linux kernel framework that lets userspace programs take direct ownership of a PCI device, bypassing kernel drivers, giving cyber tools low-latency, isolated hardware access without running in kernel space. device attachment in the QEMUQEMUAn open-source machine emulator and virtualizer that lets software run a guest OS or CPU architecture on a different host, giving cyber tools an isolated, inspectable execution environment without dedicated hardware. runtime to file-descriptor passing, and removes two unsupported runtime-rs config overrides.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
9 FEATURES0 OF 9 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
Removed unsupported runtime-rs config overridesbreaking70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
The disable_block_device_use option is removed from runtime-rs as it was unsupported — configs referencing it will need to be updated.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The cpu_nested_config override is removed from runtime-rs.
FD-based block and VFIO device passing in runtime-rs/QEMUnew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Passes block storage sources by file descriptor in runtime-rs/QEMU, enabling more secure and flexible block device attachment, and passes VFIO devices by file descriptor in runtime-rs/QEMU, enabling fd-based VFIO device handoff.
— Names mechanism and scope but no config flag4.2.0
thinner coverage below
0300
NVIDIA GPU guest image enhancementsnew55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Ships dcgm-exporter in the NVIDIA GPUGPUA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference. guest images and enables NFD (Node Feature Discovery) in the NVIDIA kata-deploy presets.
— Names two concrete additions, no usage steps4.2.0
0400
Cold-plug block devices with Cloud Hypervisornew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Enables cold-plug of block devices requested before boot in runtime-rs with Cloud Hypervisor.
— Names runtime and hypervisor, no config detail4.2.0
0500
virtio-rng entropy device in dragonball VMMnew45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Adds virtio-rngvirtio-rngA paravirtualized random-number-generator device defined by the virtio standard, letting a virtual machine pull entropy from its hypervisor host to seed the guest's entropy pool faster than emulated hardware allows. entropy device to the dragonball VMMVMMA Virtual Machine Monitor is software that creates and manages virtual machines, abstracting physical hardware so multiple OS instances run in isolation; cyber tools use it to sandbox execution or emulate target environments safely..
— Names the device and VMM, no further detail4.2.0
0600
Rootfs base bumped to Ubuntu 26.04improved45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Bumps rootfs base to Ubuntu 26.04 across all images.
— Names the version but no rationale or impact4.2.0
0700
TLS support for kata-monitornew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds TLS support to kata-monitor for encrypted metrics exposure.
— Names the component but no flag or config key given4.2.0
0800
Early guest console log capturenew40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Captures early guest console logs in the runtime before the agent is fully up.
Databricks is a unified analytics platform for data engineering, data science, and machine learning built on Apache Spark.
Databricks shipped a Beta snapshots API for Lakebase, session restore for debugging failed serverless jobs, an audio transcription AI function, Slack-embedded Genie visualizations, and configurable retention for system tables.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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.
0101
Lakebase snapshots APInew75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
A Beta API for Lakebase supports create, get, list, and delete operations on point-in-time snapshots of a project branch, plus restoring a snapshot by creating a new branch from it.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Session restore for serverless jobsnew75how completely this was documenteddepth35/40specificity20/30actionability20/3075 / 100
Public Preview feature that automatically captures a snapshot of Python variables and Spark session state from eligible serverless compute job runs, letting you restore them into a new interactive notebook to debug failures or explore results without rerunning the entire job.
Tenzir is a data pipeline engine for security teams that collects, transforms, enriches, and routes telemetry.
Tenzir shipped performance improvements to its pipeline engine, on-demand schema loading in the platform, and automatic SigmaSigmaAn open, vendor-neutral rule format for describing patterns in log data, maintained by the Sigma project community, giving cyber tools a shared detection language that converts into platform-specific queries. rule matching for 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.-formatted events.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
3 FEATURES1 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.
0101
Automatic Sigma matching for OCSF eventsnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Tenzir Node v6.16.0 adds automatic Sigma rule matching for OCSF-formatted events, extending detection coverage to OCSF schemas without manual mapping.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Instinct meets AI. Arctic Wolf Aurora's built-in agents operate at machine speed while human experts maintain oversight.
Arctic Wolf introduced Aurora MDRMDRManaged detection and response, an outsourced service that monitors security signals, investigates threats and helps respond to incidents. It combines specialist analysts with detection tools. Connect, a new managed detection and responsemanaged detection and responseManaged detection and response, an outsourced service that monitors security signals, investigates threats and helps respond to incidents. It combines specialist analysts with detection tools. tier built exclusively for MSPsMSPsA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs..︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE1 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.
0101
Aurora MDR Connect for MSPsnew30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
A new tier of Aurora Managed Detection and Response built exclusively for MSPs, powered by the Aurora Superintelligence Platform and the Aurora Agentic SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared..︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Censys added case-insensitive regex matching to its query language, rolled out 22 new protocol and application scanners, and added two ASMASMAttack Surface Management: the continuous practice of discovering, inventorying, and monitoring an organization's externally exposed assets so that cyber tools can flag unknown or misconfigured entry points before attackers find them. risk fingerprints for recent GitLab vulnerabilities.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Censys is a search engine for internet-connected devices and certificates, enabling security researchers to discover and analyze exposed assets.
Censys added case-insensitive regex matching to its query language, rolled out 22 new protocol and application scanners, and added two ASMASMAttack Surface Management: the continuous practice of discovering, inventorying, and monitoring an organization's externally exposed assets so that cyber tools can flag unknown or misconfigured entry points before attackers find them. risk fingerprints for recent GitLab vulnerabilities.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Case-insensitive regex in CenQLnew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds the (?i) case-insensitive regex operator to the Censys Query Language (CenQL), enabling case-insensitive value=~ pattern matching in fields such as host.services.endpoints.http.headers and other string fields.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Hunt for nginx servers advertised with non-standard casing (e.g. Nginx, NGINX) to catch assets that evade case-sensitive filters.
$ host.services.endpoints.http.headers:(key="Server" and value=~"(?i)^nginx$" and not value="nginx")
New ASM risk fingerprints for GitLab CVEsnew80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Adds two new ASM risk fingerprints queryable via risks.name: Vulnerable GitLab Server (CVE-2026-85706) covering unauthenticated arbitrary file read via the repository commits API, and Vulnerable GitLab Server (CVE-2026-87719) covering authenticated credential leak via a GraphQL subscription in GitLab EE.
Query ASM for assets flagged as vulnerable to the unauthenticated GitLab arbitrary-file-read risk to prioritize patching.
DefectDojo added inline image support to the Markdown editor for finding notes and reports, and extended the deduplication engine with configurable candidate scope, winner ordering, and dedupe pools.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Inline images in Markdown editornew63how completely this was documenteddepth25/40specificity18/30actionability20/3063 / 100
The Markdown editor used in Finding notes, descriptions, and other markdown fields now supports images via paste from clipboard, drag-and-drop, or the Insert image toolbar button.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Images are stored by DefectDojo and render inline in the notes feed and in generated reports, removing the need for an external image host.
Attach a screenshot of exploit evidence directly to a finding note so it appears inline in reports without needing an external host.
📍In a Finding, open the Notes section, then paste a screenshot from your clipboard or drag an image file onto the Markdown editor. The image is stored by DefectDojo and rendered inline in the notes feed and any generated reports.
— Names UI mechanism and toolbar button, but no config surface.product docs
thinner coverage below
0200
Configurable deduplication engine scope and poolsimproved35how completely this was documenteddepth15/40specificity12/30actionability8/3035 / 100
The deduplication engine gains injectable candidate scope and winner order configuration, along with support for dedupe pools.
— Names mechanism but no concrete config keys or examples.3.3.100
ⓘSourcesRelease page →1 release · seen 2026-09-15Notes ↗RankWhy this ranktop features scored 60/52, +15 breaking change, +6 runnable example — 77How ranking works →
Immuta's Request app now supports submitting a single access request for multiple users, while fingerprint-based masking options for Snowflake are being deprecated ahead of removal in December 2026.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Use Immuta to provision governed access to data.
Immuta's Request app now supports submitting a single access request for multiple users, while fingerprint-based masking options for Snowflake are being deprecated ahead of removal in December 2026.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Fingerprint-based masking deprecated for Snowflakedeprecated60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Fingerprint-based masking options — format-preserving masking, randomized response masking, and rounding/grouping using a data fingerprint — for Snowflake integrations are deprecated and will be removed from Immuta SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. on December 15, 2026.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Tenants without existing policies using these options can no longer create new ones.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact masking types, integration, and removal date.snapshot-20260915
thinner coverage below
0200
Multi-user access requests in Request appnew52how completely this was documenteddepth22/40specificity12/30actionability18/3052 / 100
The Immuta Request app now lets managers and admins select multiple users in a single request form and submit once instead of once per user. The form also adds an email address hover-over on user names to help distinguish between users with similar or identical names.
Request access for an entire team in one submission rather than repeating the process for each individual.
📍In the Immuta Request app, open the request form, select all relevant users from the user list, fill in the request details, and click Submit once to create a single access request covering all selected users.
— Clear behavior and UI steps given, but no config/API name.snapshot-20260915
└──▷ BREAKING ON UPGRADE
!
Fingerprint-based masking options (format-preserving masking, randomized response masking, and rounding/grouping using a data fingerprint) for Snowflake integrations are deprecated and will be removed from Immuta SaaS on December 15, 2026. Tenants without existing policies using these options can no longer create them.
The leading data and AI security platform that proactively reduces risk, enforces policies, and stops active threats with our AI-native automation.
Varonis expanded its web interface to cover core administrative workflows (dictionaries, users/roles, permissions/groups) that previously required the separate Management Console, while also adding a unified account activity view, 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. monitoring in 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., SharePoint sensitivity-label filtering, and custom link prefixes for Data Lifecycle Automation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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.
0101
Web interface administration for dictionaries, users, and permissionsnew68how completely this was documenteddepth25/40specificity28/30actionability15/3068 / 100
Consolidates administration previously requiring the Management Console into the Varonis web interface: creating and updating dictionaries alongside EDM classifiers and classification policies; creating, viewing, and managing users and roles; and managing permissions, groups, folder protection, and memberships directly from the Analytics page.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Unified account activity investigation in Account Panenew63how completely this was documenteddepth25/40specificity18/30actionability20/3063 / 100
Adds a dedicated Activity tab inside the Account Pane that combines activity trends and detailed event logs in a single view, with interactive filtering and drill-down to identify spikes and accelerate investigations.
When an alert fires on a user account, open the Account Pane and navigate to the Activity tab to see event trends and drill into specific events without leaving the pane.
📍In the Varonis console, locate the account in question and open the Account Pane › Activity tab. Use the interactive filters to narrow by time range or event type, then drill down into spikes to review detailed event logs.
Quickly triage unusual account behavior during an incident by reviewing activity trends and raw event logs without pivoting between screens.
📍In the Varonis web interface, open the Account Pane for the account under investigation, select the Activity tab, use the interactive filters to isolate the relevant time window, and drill down into event log entries showing the spike.
SharePoint site filtering by sensitivity labelnew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Enables filtering and analysis of SharePoint Online sites by sensitivity label assigned directly to the site, surfacing site-level classification for security and compliance investigations.
Custom link prefixes for Data Lifecycle Automationnew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Data Lifecycle Automation policies can now generate links with custom prefixes when content is moved, making automation-generated links distinguishable for auditing and link management.
Non-human sign-in monitoring in Entra IDnew40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
Monitors and surfaces authentication events for service principals and AI agents in Entra ID, enabling investigation of non-human identity sign-ins that were previously invisible.
ⓘSourcesBlog / feed →8 releases · 2026-09-14Blog ↗RankWhy this ranktop features scored 93/90/88, +15 breaking change, +10 product media, +6 runnable example — 121.33How 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's biggest window moves are new standalone products — Password Vault, Access Requests, the 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, and GA Access Risk Detection — layered on top of steady identity work (JumpCloud Go passwordless login, certificate-based 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., 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.SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management., forced 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./OIDC re-authentication) and device management growth across Windows, Android, and Apple MDM, Device Monitoring and Alerting, and a granular Custom Admin Roles/RBAC rework.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
51 FEATURES13 OF 51 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
AI & SaaS Management platformimproved93how completely this was documenteddepth38/40specificity30/30actionability25/3093 / 100
Introduces SaaS ManagementSaaS ManagementA category of software that tracks, governs, and optimises an organisation's portfolio of SaaS subscriptions, covering spend, access, and licence utilisation from a single control plane. with discovery, categorization, warning/blocking controls, and usage insights for shadow IT apps via the JumpCloud Go browser extension, and lets admins manually add applications for tracking, warning, and blocking before automatic discovery occurs (r2).︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Renames it to AI & SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. Management and significantly expands coverage of generative AI apps for discovery, adds the Shadow AI Dashboard for visibility into generative AI shadow IT usage, adoption by department, and most active users, and releases SaaS License Management to GA, automating license tracking for supported SaaS applications via connectors (r3).︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Adds MCP Discovery and Token & Cost Tracking options under Access > AI & SaaS Management > Settings > Enhanced Discovery Options to discover 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 track token usage and estimated cost from Cursor, Claude Code, OpenCode, Codex, and VS Code Copilot CLI on managed Windows and macOS devices, and adds an MCP Connection column in Access > AI & SaaS Management > Applications showing Discovered, Connected, or Not Available status for each app, with Add MCP Server and View actions available inline (r4).
Enable MCP server discovery and AI token cost tracking across managed devices to get visibility into AI coding tool usage in your environment.
📍In the Admin Portal, go to Access › AI & SaaS Management › Settings. Under Enhanced Discovery Options, enable MCP Discovery and Token & Cost Tracking.
Connect a discovered MCP server to AI Gateway from the same view used to manage SaaS apps, without switching tools.
📍In the Admin Portal, go to Access › AI & SaaS Management › Applications. Locate an app showing Discovered in the MCP Connection column, click the status, review the discovered MCP servers, and click Add MCP Server.
Custom Admin Roles with granular RBAC scopesbreaking90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Releases Custom Admin Roles for all direct organizations, enabling granular role creation based on specific admin responsibilities (r3). Adds CRUDCRUDThe four basic database operations — Create, Read, Update, Delete — used as shorthand for any system that manages persistent data records, giving cyber tools a standard model for interacting with stored information. operations and a No Access permission to the Identity Management and Application Management scopes; splits Identity Management and Directory and Groups Management into separate, independently assignable scopes; moves Directory Management and Group Management under a unified Directory and Groups Management category, SaaS Applications and Asset Management under SaaS and Asset Management, and RADIUS Authentication under Access Management; includes Application Templates in the Applications scope and existing User Portal APIs/operations under the Multi-Factor Authentication scope; and renames Policy Management to Access Management, System Management to Devices, and Authentication Policies to Conditional Access Policies and IP Lists (r5 preview).
API deprecations: reactivate endpoint and Dynamic Groups filter operatorsdeprecated88how completely this was documenteddepth30/40specificity30/30actionability28/3088 / 100
The GET request for api/systemusers/reactivate/{id} is deprecated and now returns a 404 error; replace it with POST https://console.jumpcloud.com/systemusers/reactivate/{id} with activation_email in the request body. Dynamic Groups API memberQuery filter operators $ge and $le are deprecated and replaced by $gte and $lte; existing API scripts using $ge or $le must be updated.
Forced re-authentication and authentication method claimsnew83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Adds forced re-authentication support: the IdPIdPA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. now honors ForceAuthn="true" in SAML and prompt=login in OIDC, prompting users for credentials even with an active session; and adds 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 both 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.).
Trigger step-up authentication for a high-privilege app by sending a SAML AuthnRequest with ForceAuthn set, ensuring the user must re-authenticate even with an active session.
Patch management for macOS and browsersnew80how completely this was documenteddepth32/40specificity28/30actionability20/3080 / 100
Adds per-device macOS software update scheduling from the Admin Portal, including timeframe control and user deferral options; adds macOS Ventura upgrade-blocking software management policies so admins can delay or prevent unwanted upgrades to macOS 13; adds a Managed Login Items policy for macOS 13 Ventura to prevent end users from disabling persistent software such as the JumpCloud Agent; adds a Universal Browser Patch Management policy for Google Chrome across macOS, Windows, and Linux from a single policy; and adds a Browser Patch Management Policy Report and an OS Patch Management Policy Report for audit evidence and compliance status.
Prevent macOS 13 Ventura from upgrading automatically on managed devices while you validate app compatibility.
📍In the Admin Portal, go to Device Management › Policies › New Policy, select the macOS Ventura delay/block software management policy, configure the deferral window, and bind it to your macOS device groups before the delta update is offered.
Password Manager storage limits and auto-lock controlsimproved78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Raises item storage limits to 13,000 items with autofill enabled, 5,000 items per shared folder, and 30,000 items when autofill is not used; introduces an auto-lock schedule with a default of 15 minutes of inactivity and a maximum of 1440 minutes (24 hours), plus an Auto Lock setting that locks the app when the device is locked.
MFA and JumpCloud Protect hardeningimproved78how completely this was documenteddepth32/40specificity26/30actionability20/3078 / 100
Enables 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. by default for all new admin accounts logging into the Admin Portal, splits WebAuthnWebAuthnA web standard that lets a browser prove possession of a passkey or hardware key to a website. It is the browser-facing part of FIDO2 sign-in. into separate Security Keys and Device credential types for enrollment, adds push bombing mitigation for JumpCloud Protect blocking more than one notification per resource within a sixty-second period (configurable in MFA Configurations), and adds lock-screen push notification approval or denial in JumpCloud Protect (long-press on iOS, expand on Android) when User Verification is not required (r1). Allows admins to enable password resets from the User Portal when MFA is enforced but the user has not yet enrolled (r2). Adds user group exclusion from JumpCloud Protect Push enforcement, allowing excluded groups to use TOTPTOTPA one-time password algorithm (RFC 6238) that generates short-lived codes from a shared secret and the current time, giving cyber tools phishing-resistant second-factor authentication without a server round-trip. only (r3).
Harden admin push notification security by reviewing the sixty-second push bombing limit and adjusting the maximum concurrent attempts for your org.
📍In the Admin Portal, go to Security › MFA Configurations, locate JumpCloud Protect push settings, and adjust the maximum concurrent attempts or disable the limit.
Multi-Tenant Portal administration featuresimproved77how completely this was documenteddepth30/40specificity25/30actionability22/3077 / 100
Adds MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. admin ability to bulk-select and export reports across all tenant organizations as JSON or CSV from the Multi-Tenant Portal homepage, and adds MSP Custom Command Templates so MSP admins can create, save, and apply command templates across tenant organisations (r0). Adds ad hoc command execution on devices directly from the Multi-Tenant Portal and Admin Portal, the ability to add new users and devices, export user and device lists, and run bulk actions directly from the Multi-Tenant Portal, and MSP billing visibility for committed user license counts and JumpCloud contract downloads (r1). Adds Account > Settings > Global MFA Requirement in the Multi-Tenant Portal to bulk-enforce MFA for all MSP admins in a tenant (r2).
Enforce MFA for every MSP admin in your tenant from the Multi-Tenant Portal without touching individual admin accounts.
📍In the MTP Admin Portal, go to Account › Settings, then enable the toggle under Global MFA Requirement.
Dynamic Groups for devices and usersnew77how completely this was documenteddepth30/40specificity25/30actionability22/3077 / 100
Adds Dynamic Groups for both devices and users, allowing admins to automate group membership via attribute-based rules with optional pre-review of membership changes; adds Vendor and Public IP Address as new attributes for dynamic device groups, and Manager as a new attribute for dynamic user groups.
Automatically maintain a device group of all macOS endpoints from a specific vendor so policies stay current as fleet changes.
📍In the Admin Portal, go to Device Groups, create or edit a group, enable Dynamic, and add a rule: Attribute = Vendor, Operator = is, Value = Apple.
Shared folder management in Password Managerimproved76how completely this was documenteddepth32/40specificity22/30actionability22/3076 / 100
Adds shared folder management for JumpCloud Password Manager from the Admin Portal, including manual per-folder sync from the desktop application (r1); admins can create and update shared folders and assign users or user groups to any shared folder, a Move All items button moves every item in a folder at once, and shared folder events sync to Directory Insights (r7).
Assign a user group to a shared folder so the whole team gets access to shared credentials without manual per-user assignment.
📍In the Password Manager desktop app, go to Shared Folders, select or create a folder, then use Assign Users or User Groups to add the relevant group.
Bulk-relocate all credentials out of a shared folder in one action when reorganizing vault structure or offboarding a team.
📍Open the shared folder in the Password Manager desktop app, then click the Move All items button to move every item in the folder at once.
JumpCloud Go passwordless authenticationimproved76how completely this was documenteddepth32/40specificity26/30actionability18/3076 / 100
Adds the JumpCloud Go browser extension enabling hardware-protected, phishing-resistant passwordless login using Apple Touch ID and Windows HelloWindows HelloA Microsoft authentication framework built into Windows 10 and later that lets users sign in via biometrics or PIN instead of passwords, giving cyber tools a phishing-resistant credential layer to build on. on managed macOS and Windows devices, and enforces it as the default MFA method for conditional access policies on SSO apps with user and device verification on every application session (r1). JumpCloud Go sessions now automatically refresh on device login or unlock, enabling seamless access to protected resources without additional MFA challenges, and a new User Portal > Security > Multi-Factor Authentication section lets users manage JumpCloud Go sessions per device (r2).
Access Risk Detection reaches general availabilitynew75how completely this was documenteddepth35/40specificity25/30actionability15/3075 / 100
Promotes Access Risk Detection to general availability, providing behavior-based detection of unusual locations, impossible travel, unfamiliar devices, dormant accounts, and abnormal login volumes, with configurable risk factors, automatic MFA-based resolution, intelligent 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./gateway suppression, and email, Slack, and webhook notifications.
Commands feature: agent-install triggers, running status, remote toolsnew74how completely this was documenteddepth28/40specificity24/30actionability22/3074 / 100
Adds a Command After Agent Install command type so admins can specify enrollment commands to run immediately after the JumpCloud agent is installed on new devices, and adds a Running column to the commands queue to distinguish commands waiting in queue from commands actively running (r0). Adds Background Tools remote command line and remote file transfer capabilities, letting admins access an end-user's device and transfer files without disrupting their work (r1).
Enroll new Windows endpoints with a hardening script that runs the moment the JumpCloud agent finishes installing, before any user logs in.
📍In the Admin Portal, go to Commands › New Command, set the command type to Command After Agent Install, paste your hardening script, and save — the command will execute automatically on every newly enrolled device.
MCP servers require SSO application association in AI Gatewaybreaking73how completely this was documenteddepth28/40specificity25/30actionability20/3073 / 100
MCP servers in AI Gateway must now be associated with an SSO application or bookmark via the App dropdown, enabling group-based access scoping; a + New App option opens the standard Add New SSO Application wizard during server setup. Previously created MCP servers without an associated application must be assigned one or access will not be scoped by User Groups.
Remote Assist remote supportnew73how completely this was documenteddepth32/40specificity26/30actionability15/3073 / 100
Introduces JumpCloud Remote Assist for unlimited remote desktop access and support on Windows and macOS — free, installed silently via JumpCloud Agent v1.61.0 or later (r0). Adds user-switching between accounts during Remote Assist sessions on Windows devices, a Ctrl+Alt+Del command shortcut from the Session Options toolbar, and support for viewing and interacting with the initial login screen on Windows servers (r1). Ships Remote Assist as two separate architecture-specific packages — ARM64ARM64The 64-bit instruction set architecture from ARM Holdings, used in modern mobile chips, Apple Silicon, and cloud server CPUs; tools target it to run natively on those platforms without emulation overhead. for Apple Silicon and x86_64 for Intel Macs (r2).
RADIUS authentication enhancementsimproved72how completely this was documenteddepth32/40specificity25/30actionability15/3072 / 100
Adds certificate (passwordless) based authentication to JumpCloud RADIUS, supporting any X.509X.509A standard defining the format of public-key certificates, maintained by the ITU-T, used by cyber tools to authenticate identities and establish encrypted connections over TLS and similar protocols. compliant certificate authority — existing certificates can be imported and used for RADIUS auth; adds RADIUS authentication with Azure AD as the 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., enabling secure RADIUS access without managing users outside Azure AD (r0). Adds faster reconnect for EAP connections by allowing recently authenticated devices to skip the full security handshake using a cached session credential (r3).
Agent Identities for AI Gatewaynew70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
Introduces Agent Identities so admins can register an AI agent with OAuth client credentials for the JumpCloud AI Gateway and scope its SSO application access via Agent Groups, keeping automated agents auditable and separate from human accounts.
Register an AI agent identity with OAuth credentials and scope its SSO application access via a group, keeping it auditable and separate from human accounts.
📍In the Admin Portal, go to Identity Management › Agents and click + Add. Enter the agent name, owner, and company email on the Details tab. On the Authentication tab, generate OAuth client credentials for the JumpCloud AI Gateway. Then go to Identity Management › Agent Groups, create a group, add the agent, and assign SSO applications.
API filter escaping for pipe characterimproved70how completely this was documenteddepth20/40specificity28/30actionability22/3070 / 100
Adds support for escaping the pipe | character with backslash \\ inside in and nin API filter operators (e.g. GET /systemusers?filter=department:$in:...), enabling pipe characters in search terms.
Admin-managed Password Manager install via command template v2.0.0improved69how completely this was documenteddepth25/40specificity22/30actionability22/3069 / 100
Admins can install and update the Password Manager desktop app using a new command template v.2.0.0 on Windows and macOS devices, removing the need for users to have admin permissions for subsequent updates.
Password Manager Desktop App platform builds expandnew68how completely this was documenteddepth28/40specificity25/30actionability15/3068 / 100
Adds a Password Manager Desktop App Linux build (Debian/Ubuntu x86) with improved security and automatic updates (r1); adds an 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. build for macOS devices with M-series silicon (M1 and above), available on the Downloads page with automatic update to the ARM build when applicable, and an RPM build for Linux (x64 Red Hat distributions such as Fedora), auto-updating and stable, alongside the existing Debian build (r7).
Asset Management enhancementsnew68how completely this was documenteddepth28/40specificity25/30actionability15/3068 / 100
Adds an Asset Manager role in the Admin Portal providing dedicated Asset Management access without broader admin permissions; adds file upload functionality (Invoice field) to asset records under Purchase Details with support for custom fields of the File Upload type; adds Disk Size to Hardware Specifications for tracking device storage capacity; adds a Local Device Accounts display on the Asset Detail page under Device Management; and adds asset cloning, automatically clearing unique fields to prevent duplicates.
Access Requests approval workflownew67how completely this was documenteddepth30/40specificity22/30actionability15/3067 / 100
Introduces JumpCloud Access Requests, enabling approval flows for access requests submittable from the JumpCloud User Portal and manageable in the admin console; adds webhook support to integrate with external ticketing systems such as JIRA, automatically creating tickets on new request submission; and tracks Access Request events in Directory Insights.
Support case portal evolves into Customer Portalimproved65how completely this was documenteddepth28/40specificity22/30actionability15/3065 / 100
Adds the JumpCloud Case Portal under the Support menu, centralising all organisation cases and ideas into a filterable list with clickable case numbers (r0). Introduces the Customer Portal for tracking and managing support cases, with sortable columns for Last Modified Date, Account, and Requester, plus attachment uploads and inline ticket editing, and adds MTP admin access to view and create support cases for all managed tenant organizations (r3).
Android MDM management: zero-touch, EMM, work profilenew65how completely this was documenteddepth28/40specificity25/30actionability12/3065 / 100
Adds Android zero-touch enrollment support for fully managed, dedicated, and company-owned Android devices with a work profile (r1); adds Android EMMEMMEnterprise Mobility Management: a category of software for enforcing policies on mobile devices, apps, and data, giving cyber tools a hook to monitor or control endpoints without managing the full OS. support for fully managed and dedicated devices with 7 new policies including Factory Reset Protection, Kiosk Mode, and System Updates, plus Android EMM work profile support for enrolling and managing company-owned and personal Android mobile devices (r1); and 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. (r2).
Apple MDM enrollment, restriction policies, and app deploymentnew65how completely this was documenteddepth28/40specificity25/30actionability12/3065 / 100
Supports BYODBYODBring Your Own Device: a policy allowing employees to use personal phones, laptops, or tablets for work, creating a network of unmanaged endpoints that cyber tools must monitor or enforce policy on. enrollment of iOS/iPadOS 18+ devices via Account-Driven User Enrollment (ADUE) in MDM, now in general availability, and adds two new MDM policies to restrict Apple Intelligence features on iOS/iPadOS 18.1 and macOS 15.1 Sequoia devices (r2). Adds Apple Business Manager as a new service discovery method for Account-driven Enrollment, and adds IPA file support to the JumpCloud Private Repository for uploading and deploying iOS and iPadOS app packages (r3).
Third-party integrations: SentinelOne, AWS Verified Access, Deel, Microsoft 365new65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds SentinelOne integration via the Commands feature to download and install the SentinelOne Agent on macOS, Windows, and Linux devices, and extends the Microsoft 365 integration to include M365/Azure AD security groups (r0). Adds integration with AWS Verified Access using JumpCloud Go, SAML, or OIDC SSO as a VPN-less remote access solution, and adds a Deel SSO Connector integration (r1).
Password Manager Desktop App usability and list managementimproved62how completely this was documenteddepth25/40specificity25/30actionability12/3062 / 100
Adds Download Logs and Keyboard Shortcuts options under Settings, and multi-select functionality with item sorting (r2); extends sorting to various criteria including nicknames, adds multi-select for bulk management, a paginated items list showing 100 items per page, a Copy button in Password History, ability to delete multiple folders at once, a What's New link on Settings > General for release updates, and archiving of items with the ability to view, delete, and restore archived items (r7).
Device Monitoring and Alertingnew62how completely this was documenteddepth28/40specificity22/30actionability12/3062 / 100
Introduces JumpCloud Device Monitoring and Alerting, supporting availability, software, uptime, disk, and battery monitoring plus directory event alerts (user addition, privilege elevation) on Windows, macOS, and Linux endpoints.
Windows MDM CSP policy and SCEP expansionnew62how completely this was documenteddepth22/40specificity28/30actionability12/3062 / 100
Adds six new Windows MDM CSP-basedCSP-basedContent Security Policy, a W3C browser standard that restricts which scripts, styles, and resources a page may load, letting cyber tools enforce or audit site defenses against injection attacks. policies: Windows Wi-Fi Configuration Policy, Windows VPN Policy, Install Certificate Policy, Bluetooth Configuration Policy, Control Policy Conflict, and Windows Notification Service, plus a new policy to configure Simple Certificate Enrollment Protocol (SCEPSCEPSimple Certificate Enrollment Protocol, an IETF-standardized protocol for automating X.509 certificate issuance and renewal over HTTP, letting cyber tools request PKI certificates from a CA without manual intervention.) for Windows devices.
MDM/SSO certificate and token expiration monitoringimproved61how completely this was documenteddepth25/40specificity24/30actionability12/3061 / 100
Adds an MDM Upcoming Certificate Expirations homepage widget covering MDM certificates, Apple VPP, and Automated Device Enrollment Certificates (r0), evolving into an MDM Certificate & Token Status Board on the Admin Portal and Multi-Tenant Portal homepages, showing expiry status for MDM, SSO, and AzureAD tokens and certificates with an aggregate MSP view (r1).
Linux platform support and hardeningnew60how completely this was documenteddepth22/40specificity20/30actionability18/3060 / 100
Adds JumpCloud agent support for Linux Fedora 37, and adds a Linux Forbidden Services policy to remove unsupported service types and reduce security risk across Linux fleets.
Block an entire Linux fleet from running unnecessary services (e.g. telnet, rsh) to reduce the attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. without touching each machine individually.
📍In the Admin Portal, go to Device Management › Policies › New Policy, select Linux Forbidden Services, choose the service types to forbid, and bind the policy to the target Linux device group.
Self-Service Account Provisioningnew57how completely this was documenteddepth25/40specificity20/30actionability12/3057 / 100
Adds Self-Service Account Provisioning so new users can bind their account to JumpCloud-managed macOS and Windows devices directly from the login window, including a new macOS login window with wireless connectivity controls.
Password Manager launch and cloud backupnew56how completely this was documenteddepth28/40specificity20/30actionability8/3056 / 100
Introduces JumpCloud Password Manager with end-to-end encrypted local storage, browser extension auto-fill, secure password sharing, and password generation; adds Cloud Backup as a secure fallback to minimize data loss.
RSS feed subscriptions for release notesnew56how completely this was documenteddepth18/40specificity18/30actionability20/3056 / 100
Adds RSS subscription options for JumpCloud Help Center updates, including separate feeds for product release notes, agent release notes, and bug fix reports via the Release Notes and Bug Fixes page.
Stay current on JumpCloud product and agent changes by subscribing to the release notes RSS feed in your reader.
📍Go to the JumpCloud Release Notes and Bug Fixes page › Click Subscribe to Release Notes and Bug Fixes RSS Feed › Add the resulting RSS URL to your RSS reader of choice.
AI Commands Builder general availabilitynew55how completely this was documenteddepth22/40specificity18/30actionability15/3055 / 100
Launches the AI Commands Builder (GA), allowing admins to generate commands for Windows, macOS, and Linux devices using natural-language prompts in the Admin Portal.
Personalization policies for Windows and macOSnew54how completely this was documenteddepth20/40specificity22/30actionability12/3054 / 100
Adds new Windows Personalization policies: Taskbar Customization, Screen Saver Configuration, and Desktop and Lock Screen Settings; and adds new functionality to existing Mac Personalization policies: Dock Settings and Items, and Lock Screen (Screen Saver).
Disk encryption device condition in Conditional Access Policiesnew54how completely this was documenteddepth20/40specificity22/30actionability12/3054 / 100
Adds disk encryption state (FileVaultFileVaultApple's full-disk encryption feature built into macOS, using XTS-AES-128 to encrypt the startup volume so that data is unreadable without the user's credentials. on macOS, system drive on Windows, root disk on Linux) as a device condition in 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.
EU region support for Password Managernew53how completely this was documenteddepth20/40specificity18/30actionability15/3053 / 100
Adds EU region support — users can select their region before activating their account, available on the activation page for the desktop app and on the pairing page for the browser extension.
User Portal login and application browsing experienceimproved52how completely this was documenteddepth22/40specificity20/30actionability10/3052 / 100
Adds Identity First Login flow for the User Portal and SSO applications, splitting login into a username/email screen followed by a password screen (r0); adds All Applications and Favorites tabs to the Applications area of the User Portal, with a starring mechanism and responsive search field (r1).
Directory Insights filter refinementimproved48how completely this was documenteddepth18/40specificity20/30actionability10/3048 / 100
Refines Directory Insights filters by splitting Application Name into Application Name, Application Display Name, and Application Display Label, and Resource Name into Resource Name, Resource Display Name, and Resource Display Label.
LDAP authentication improvementsimproved48how completely this was documenteddepth20/40specificity18/30actionability10/3048 / 100
Adds TOTP as a supported MFA factor for 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. applications, alongside JumpCloud Protect push notifications (r0); adds source IP tracking for incoming LDAP requests for enhanced security and traceability (r3).
JumpCloud MCP Server general availabilitynew47how completely this was documenteddepth22/40specificity15/30actionability10/3047 / 100
Introduces the JumpCloud MCP Server (GA), connecting compatible AI tools to JumpCloud via 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. for direct interaction with org data and admin capabilities.
Premium Support live chat moves to Admin Portalbreaking45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Adds Premium Support live chat directly in the Admin Portal, automatically recognising Premium Support status without requiring a PIN; live chat is no longer available on the JumpCloud Support site and has moved exclusively to the Admin Portal.
OIDC Single Sign-On supportnew38how completely this was documenteddepth15/40specificity15/30actionability8/3038 / 100
Adds OpenID ConnectOpenID ConnectOpenID 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. (OIDC) Single Sign-On support for OIDC-capable web applications.
Premium Support live chat is no longer available on the JumpCloud Support site — it has moved exclusively to the Admin Portal.
!
The GET request for api/systemusers/reactivate/{id} is deprecated and now returns a 404 error; replace it with POST https://console.jumpcloud.com/systemusers/reactivate/{id} with activation_email in the request body.
!
Dynamic Groups API memberQuery filter operators $ge and $le are deprecated and replaced by $gte and $lte; existing API scripts using $ge or $le must be updated.
!
MCP servers in AI Gateway now require a mandatory association with an SSO application or bookmark; previously created MCP servers without an associated application must be assigned one or access will not be scoped by User Groups.
!
The Policy Management scope is renamed to Access Management — any roles or documentation referencing the old name must be updated.
!
The System Management scope is renamed to Devices — any roles or documentation referencing the old name must be updated.
!
The Authentication Policies scope is renamed to Conditional Access Policies and IP Lists — any roles or documentation referencing the old name must be updated.
!
Identity Management no longer bundles directory and group permissions; those now live under the separate Directory and Groups Management scope — existing custom roles relying on Identity Management for directory/group access must be updated.
!
JumpCloud Protect is not included in any RBACRBACRole-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. scope — admins managing Protect have no RBAC coverage in this release.
!
The .appimage Linux build is no longer supported as of April 18, 2024; users must migrate to the RPM or Debian build.
ⓘSourcesBlog / feed →1 release · 2026-09-14Blog ↗RankWhy this ranktop features scored 65, +10 product media, +6 runnable example — 81How ranking works →
ConductorOne launched an EU data residency instance, giving organizations region-specific URLs across the whole platform, with one known gap in Microsoft Teams support.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Govern workforce access, deploy AI agents, and get work done with C1.
ConductorOne launched an EU data residency instance, giving organizations region-specific URLs across the whole platform, with one known gap in Microsoft Teams support.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE1 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.
0101
EU data residency instancenew65how completely this was documenteddepth25/40specificity22/30actionability18/3065 / 100
ConductorOne now offers an EU-hosted instance with region-specific URLs for login, API, webhooks, 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 CLI, selectable via the Hosting region option (EU) during domain registration.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Microsoft Teams as a notification and interaction surface is not yet supported on the EU data residency instance.
When registering a new ConductorOne domain for an EU-based organization, select the EU hosting region so that all tenant URLs (login, API, webhooks, MCP server, CLI) are routed to EU infrastructure.
📍In the ConductorOne domain registration flow, under Hosting region, select EU before completing registration. All tenant-specific URLs — including login, redirect URIs, API and webhook endpoints, MCP server, and CLI configuration — will reflect the EU instance from that point on.
— Names all region-specific surfaces and setup step, but limited mechanism detail.EU instance (2026-09-14)
Auth0 extended Tenant Access Control Lists with a blanket Deny All option that blocks all incoming traffic regardless of signal matching.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Secure users, AI agents, and more with Auth0, an easy-to-implement, scalable, and adaptable authentication and authorization platform.
Auth0 extended Tenant Access Control Lists with a blanket Deny All option that blocks all incoming traffic regardless of signal matching.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Deny All rule for Tenant ACLnew70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds the match_all: true attribute to Tenant Access Control List (ACLACLAn access control list, a set of rules allowing or denying operations for particular users, services or network addresses. It decides who can use a resource.) rules, enabling a Deny All rule that rejects all incoming traffic across the full tenant scope without requiring specific signal matching (such as IP or geolocation).︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Nudge Security expanded its browser extension to Safari, bringing real-time SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally./AI monitoring, identity risk detection, and in-browser nudges to company Macs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Discover every SaaS and AI asset, harden security posture, and scale identity governance.
Nudge Security expanded its browser extension to Safari, bringing real-time SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally./AI monitoring, identity risk detection, and in-browser nudges to company Macs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Safari browser extension for SaaS/AI visibilitynew71how completely this was documenteddepth32/40specificity24/30actionability15/3071 / 100
The Nudge Security extension now supports Safari, deployed silently to company Macs via Apple Business Manager and MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies..︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It monitors SaaS and AI activity in real time — including daily AI usage, logins, access patterns, and file uploads — and detects identity and access risks such as weak or reused passwords, SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. or 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. bypass attempts, shared credentials, and risky password manager use. It also delivers automated, customizable in-browser nudges to guide employees toward safer SaaS and AI behaviors.
Deploy the Nudge Security Safari extension silently to all company Macs so employees get SaaS/AI monitoring and nudges without any manual install step.
📍In Nudge Security, go to Settings › Browser Extension › Safari and follow the step-by-step deployment instructions to push the extension via Apple Business Manager and your MDM.
— Names deployment path and specific risk/monitoring categories, but no config keys.changelog-20260915-8c973857
Read docs, explore use cases, learn best practices
Ping Identity's PingOne AIC rapid channel release adds ESV-based configuration for connector server names with matching script-editor validation, alongside a batch of UI usability improvements to identity, job, and form management, plus a bulk connector version upgrade.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
ESV support for connector configuration and scriptsnew53how completely this was documenteddepth20/40specificity18/30actionability15/3053 / 100
Connector configuration can now use an ESV (environment secret/variable) for the connector server name, and the script editor now shows errors when scripts reference environment ESVs incorrectly.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Streamlined identity, job, and modal management UIimproved42how completely this was documenteddepth20/40specificity12/30actionability10/3042 / 100
Admins can create another identity immediately after creating one without closing the modal, edit a scheduled job to start sooner than its originally configured future start time, close modals with the Escape key, and see forms clearly identify fields that contain errors after submission.
Explore iDenfy documentation for identity verification (KYC), business verification (KYB), AML screening, fraud prevention, and more.
iDenfy shipped automatic branding theme import from a website domain, a new fields filter parameter on the KYBKYBKnow Your Business — a regulatory compliance process for verifying the legal identity, ownership, and legitimacy of a business entity, used by cyber tools to screen counterparties or customers against fraud and sanctions risk. company endpoint, native-script export columns in KYCKYCKnow Your Customer — a regulatory requirement that financial services verify the identity of their users before granting access, used by cyber tools handling payments or financial data to stay compliant. CSV reports, and real-time framing feedback during document capture.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
`fields` parameter on KYB company endpointnew85how completely this was documenteddepth25/40specificity30/30actionability30/3085 / 100
The KYB company endpoint now accepts a fields parameter to return only the requested data fields instead of the full response payload, reducing payload size.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Fetch only specific fields from the KYB company endpoint to reduce payload size and avoid processing unused data.
$ curl -X GET 'https://api.idenfy.com/api/v2/kyb/company?fields=name,registrationNumber,status' \
-H 'Authorization: Bearer <token>'
— Runnable curl example with exact endpoint and parameter valuessnapshot-20260915
0200
Auto-import branding from website domainnew70how completely this was documenteddepth30/40specificity20/30actionability20/3070 / 100
The verification UI theme can now be pre-filled automatically by pulling brand colors and logo from a website domain, eliminating manual palette setup. In the dashboard, go to Settings > IDV Flow & Branding, enter the website domain in the theme import field, and review the imported colors and logo before saving.
When onboarding a new client, pre-fill their verification UI theme automatically instead of entering colors manually.
📍In the dashboard, go to Settings › IDV Flow & Branding, enter your website domain in the theme import field, and review the imported colors and logo before saving.
— Names exact UI path and steps, but no technical mechanism givensnapshot-20260915
thinner coverage below
0300
Native-script data columns in KYC CSV reportsnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
KYC CSV reports gain an Original language data section that exports document field values in their native script as separate columns.
— Names the CSV section but no field names or column detailssnapshot-20260915
0400
Real-time framing feedback in document captureimproved25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Document capture now provides real-time framing feedback during the capture flow.
— Single generic sentence, no mechanism or UI detail givensnapshot-20260915
Replace your VPN with Firezone, an open-source zero trust access platform built on WireGuard®. Connect users to anything, anywhere.
Firezone's Windows client gains native support for ARM64ARM64The 64-bit instruction set architecture from ARM Holdings, used in modern mobile chips, Apple Silicon, and cloud server CPUs; tools target it to run natively on those platforms without emulation overhead. devices, shipping a dedicated installer alongside the existing x86-64 build.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Native ARM64 Windows client installernew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Firezone adds a native ARM64 (aarch64) installer for Windows 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. devices, available alongside the existing x86-64 installer.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ WinGet automatically selects the correct installer for the detected CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware. architecture.
Give feedback to the DNSFilter team so we can make more informed product decisions. Powered by Canny.
DNSFilter's biggest update this window is the general availability of its 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., letting AI assistants query DNS data and manage policies through natural language instead of the dashboard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
DNSFilter MCP Server now generally availablenew83how completely this was documenteddepth32/40specificity26/30actionability25/3083 / 100
The DNSFilter 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 integration is GA, letting AI assistants such as Claude, ChatGPT, and Codex query DNS activity and threat data, manage policies and allow/block lists, and automate reports and investigations via 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. without dashboard navigation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It's set up under Integrations → AI Connectors, where an admin opens the DNSFilter MCP Server card and copies the server URL to connect a client; the connection stays authorized for seven days before requiring reconnection.
Connect an AI assistant to DNSFilter so you can query DNS threat data and manage block lists in natural language, without touching the dashboard.
📍In the DNSFilter console, go to Integrations → AI Connectors, open the DNSFilter MCP Server card, copy the server URL, then follow the MCP Server setup guide to point your client (Claude, ChatGPT, or Codex) at that URL.
Ai-Safe2-Framework provides governance, risk, and compliance controls for securing agentic AI systems and non-human identities.
AI SAFE² CLI shipped two new evidence-intake surfaces: a provider-neutral harness evidence command and a portable agent system identity manifest with strict validation, dual hashing, and schema export commands.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Portable agent system identity manifest and evidence commandsnew98how completely this was documenteddepth38/40specificity30/30actionability30/3098 / 100
Adds safe2 evidence system SOURCE --output FILE to normalize an attributed agent-system identity declaration into a portable manifest, and safe2 evidence manifest FILE --subject-id ID --output FILE to bind that manifest into a wider hashed evidence run.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ A --strict flag on both safe2 evidence system and safe2 evidence manifest exits with status 1 when identity gaps, unknown evidence bases, missing versions, or disconnected components are detected.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ safe2 schema export system-identity-source-v1 and safe2 schema export system-identity-manifest-v1 export the provider-neutral input and normalized output contracts. The manifest models eight component categories (model, harness, tools, skills, memory, environment, policy, evaluator), a relationship graph of use, execution, policy, evaluation, memory, and delegation links, and an authority inventory of read, write, execute, network, delegate, approve, admin, or unknown classes per component. Dual hashing binds exact submitted bytes via source.sha256 while system_fingerprint_sha256 fingerprints normalized composition independent of key order, list order, and formatting; coverage recommendations surface remaining version, attribution, inventory, and topology gaps using four coverage statuses (complete, partial, missing, not-applicable) and three evidence-basis labels (observed, declared, unknown).
Provider-neutral harness evidence intakenew91how completely this was documenteddepth35/40specificity28/30actionability28/3091 / 100
safe2 evidence harness SOURCE --output FILE validates and normalizes a provider-neutral harness export into a structured AI SAFE² evidence result. It assesses coverage across seven domains (task lifecycle, tool calls, artifacts, tests, usage, environment state, and completion claims), records a 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. digest and size binding the exact export processed, preserves evidence attribution (producer, export identifier, source references, and collection basis), and produces loss-aware recommendations that surface which evidence areas remain partial or missing rather than treating gaps as success. It establishes a stable integration seam targeting Codex, Claude Code, Hermes, OpenClaw, and other agent harnessesagent harnessesThe software around an AI agent that manages its tools, execution loop, state and limits. It determines how the model's proposed actions are run and checked..