This Week's Highlights — issue 014, October 2, 2026
The best tooling updates that shipped this week.
The week in numbers · Sep 25–Oct 1
Changes per week, last 12 weeks · Sep 25–Oct 1
Changes we read in that week's dailies, including docs and API changes. A gap means no daily was published.
Category moves this month
Every feature release from the 1326 tools on our watchlist goes into the daily newsletter. Once a week we read the whole field side by side and grade each release from 1 to 5 on three things, weighted equally:
- Depth. How complete is the best new capability?
- Impact. How much does it change what you can do?
- Novelty. Has any other tool done this before? We check every capability against the history of every tool we track. Features most tools already have earn nothing here. Being first earns the most.
A tool is judged on everything it shipped that week, so a project that releases daily gets credit for the sum — and still only takes one slot. We would rather run a short list than a padded one.
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.
This issue came out before editions were ranked, so it shows the Standard edition in issue order.
The picks in full
Cribl is an observability pipeline platform that helps organizations collect, process, route, and transform machine data from any source to any destination.
Cribl Detect launches a full SIEM built on the data-pipeline platform — 8,000+ detection rules, detection posture management showing coverage gaps and broken rules, and in-pipeline detection that generates signals while telemetry is in motion, priced on infrastructure rather than per-GB. A pipeline vendor entering the SIEM market lets its customers consolidate detection where their data already flows.
At CriblCon 26, Cribl launched two major platform additions: Cribl Detect, a full SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. built on its pipeline, and StreamAI, an enterprise AI gateway — alongside a new agentic development environment, broader agent/integration access via MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface., automatic telemetry parsing, and a growing app marketplace.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
what's the number?
Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.
- depth0–40 what it does and how it works or what changed
- specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
- actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.
Cribl Detect is a complete SIEM built on the Cribl platform covering detection, coverage and posture management, investigation, response, and threat intelligence, available now for Cribl.Cloud customers at up to 50% less cost than incumbent SIEMsSIEMsSecurity Information and Event Management platforms that collect, normalize, and correlate log data across an infrastructure so cyber tools can detect threats and trigger alerts from a central point., priced on infrastructure rather than per-GB ingestion.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It includes Detection Posture Management that continuously shows coverage gaps, broken rules, and missing telemetry required to detect specific attacks, ships with a catalog of more than 8,000 detection rules with correlation across signals to surface multi-stage attacks, and generates detection signals directly in the data pipeline for real-time identification while telemetry is still in motion.
StreamAI is an enterprise AI gateway with a built-in model router that routes each prompt to the right model based on SecIT Bench benchmarks, offering free inference for customers using automatic routing. It enforces spending budgets and cutoffs, redacts sensitive data in both prompts and responses, and records every model call as audit-ready telemetry.
A new agentic development environment lets teams build apps, workflows, and agents using natural language, running on the same agentic runtime that powers Cribl Detect, with compute, scheduling, logging, and permissions included.
The Cribl App Framework has grown to more than 150 apps from Cribl, partners, and customers, available in the Cribl Marketplace.
Cribl opens the platform to agents via MCP and SDKs, adding 70 new integrations this year.
Cribl adds AI auto-parsing of telemetry so incoming data is structured and usable the moment it arrives.
Qualys VMDR is a cloud-based vulnerability management platform that continuously discovers, assesses, prioritizes, and remediates security vulnerabilities across IT assets.
InstaScan delivers a vulnerability finding within an hour of a vendor disclosure — closing the window where exposure is live but unassessed — and pairs it with prioritization that tests exploitability against the environment's actual firewall and EDR controls rather than theoretical CVSS. No tracked tool ships either capability.
Qualys VMDR introduced InstaScan for near-instant vulnerability detection following vendor disclosures, paired with hyper-prioritization that tests exploitability against an environment's actual security controls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
what's the number?
Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.
- depth0–40 what it does and how it works or what changed
- specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
- actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.
InstaScan is a scanless scanning capability that delivers a finding within an hour of a vendor disclosure, enabling much faster detection than traditional scan cycles.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Hyper-prioritization tests exploitability against a given environment's actual firewall and EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device. controls, rather than relying on theoretical scoring, to better prioritize remediation.
Qualys Patch Management is a cloud-based tool that automates the discovery, prioritization, and deployment of patches across IT assets to reduce vulnerabilities.
Patch Blocking Rules let you define a bad patch by QQL query and block it across every deployment job at once, and AI-Powered Patch Reliability Scoring rates each patch from real-world internet feedback plus Qualys rollback and vuln-reopen telemetry — automatically skipping low-reliability patches from zero-touch jobs so a known-bad update never reaches production.
Qualys TruRiskTruRiskA proprietary risk-scoring methodology from Qualys that translates vulnerability and asset data into a numeric business-risk score, giving cyber tools a single prioritization signal instead of raw CVSS values. Eliminate adds guardrails to automated patching: blocking rules to halt bad patches fleet-wide, AI-driven reliability scoring to keep low-confidence patches out of zero-touch jobs, and curated mitigations to cover the gap while patches are held.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
what's the number?
Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.
- depth0–40 what it does and how it works or what changed
- specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
- actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.
A new Patch Blocking Rules page under TE > Configuration > Patch Blocking Rules (Windows, Linux, and Mac support added in release 4.2) lets admins define patches to block via a QQL query (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ patch.kb: [KB5002907, KB5124008]) and block them across every deployment job simultaneously, without editing individual jobs. Scope can be restricted to up to five asset tags per rule, up to 10 rules are allowed per platform, and each rule requires a name and a blocking reason.
Combines LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. analysis of real-world internet feedback with Qualys rollback and vulnerability-reopen telemetry to rate each patch as High, Medium, Low, or Unidentified. When reliability intelligence is added to a zero-touch job's QQL in the Select Patches step, Low-reliability patches are automatically skipped from deployment while others continue.
Qualys-curated mitigations are introduced as a complementary layer to reduce exposure while a blocked or low-reliability patch is held in testing and staging.
Metasploit Pro is a commercial penetration testing framework for identifying, exploiting, and validating security vulnerabilities in systems.
Native Kerberos authentication relay lands in the framework's relay stack, including the esc8_kerberos module for AD CS Web Enrollment and IPv6/DHCPv6 DNS-takeover coercion modules to drive the chain — alongside OPC-UA enumeration and Windows AArch64 payloads across 41 new modules.
Metasploit Pro 5.1.0 ships 41 new modules headlined by native 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. authentication relay (with ESC8ESC8An Active Directory privilege escalation path where an attacker abuses the Web Enrollment interface of a Microsoft Certificate Authority to coerce NTLM authentication and relay it to obtain a certificate for a privileged account. exploitation and IPv6IPv6The current version of the Internet Protocol, standardized by the IETF, using 128-bit addresses to replace the exhausted IPv4 space. Cyber tools target it because modern networks run dual-stack or IPv6-only. DNS-takeover coercion), new OPC-UAOPC-UAAn open, platform-neutral communication protocol for industrial automation systems, maintained by the OPC Foundation, giving cyber tools a standardized way to read and monitor data from PLCs, sensors, and SCADA equipment. and WinRM scanning capabilities, Windows AArch64AArch64The 64-bit execution state of the ARM architecture, defined by Arm Ltd., offering a wider register file and cleaner instruction set than 32-bit ARM; cyber tools target it to run natively on ARM-based servers, phones, and embedded devices. and MIPS payload support, and now requires authentication on JSON RPC by default.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
what's the number?
Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.
- depth0–40 what it does and how it works or what changed
- specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
- actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.
Adds a SessionType option to auxiliary/scanner/winrm/winrm_login to create a cmd-backed shell, a PSRP-backed PowerShell session, or automatically fall back to PowerShell when cmd shell creation is denied.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
$ use auxiliary/scanner/winrm/winrm_login
set RHOSTS 192.168.1.50
set USERNAME administrator
set PASSWORD P@ssw0rd
set SessionType powershell
run
The relay stack gains native Kerberos authentication relay capabilities, including the new esc8_kerberos auxiliary module for exploiting AD CSAD CSActive Directory Certificate Services, Microsoft's PKI role for issuing and managing X.509 certificates inside a Windows domain; cyber tools target it because misconfigurations frequently allow privilege escalation or domain compromise. Web Enrollment (ESC8), auxiliary/spoof/ipv6/ipv6_ra_dns_takeover and auxiliary/spoof/dhcp/dhcpv6_dns_takeover for native IPv6 DNS-takeover coercion as part of a Kerberos relay attack chain, KerberosTicketTrace support added to auxiliary/admin/kerberos/forge_ticket, and a new shared low-level implementation Rex::Proto::Gss::KerberosToken for handling Kerberos tokens carried by GSS-API and SPNEGO.
Adds auxiliary/scanner/scada/opcua_enum, a scanner module that detects OPC-UA servers speaking the OPC-UA TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. binary transport (opc.tcp://), useful for enumerating exposed industrial control endpoints.
$ use auxiliary/scanner/scada/opcua_enum
set RHOSTS 10.10.20.0/24
run
Adds auxiliary/scanner/http/spip_annee_sqli, which exploits a blind SQL injectionSQL injectionAn attack that makes an application treat untrusted input as part of a database command. It can expose or modify data by changing what the query does. in SPIP's date column escaping logic.
Adds Windows AArch64 staged shell payloads and extends windows/smb/psexec to work with AArch64 targets.
Updates the ZoomEye search module to support the ZoomEye v2 API, adds a three-attempt retry limit, and caps results per page at 10.
JSON 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. support now requires authentication by default, either via the database with user credentials or an auth token; existing unauthenticated JSON RPC clients will be rejected on upgrade.
Adds a MIPS64 exec payload, updates the MIPSEL and MIPSBE exec payloads, and adds prepends for all three architectures.
msfconsole adds MSFLOGO=nyan-cat.txt environment variable support for selecting the nyan cat banner, a new command-line flag to print the count of modules, and improved start-up performance.
Adds a new multi-platform persistence module for Kate, and updates existing persistence modules to use create_process instead of cmd_exec.
Adds a scanner module that enumerates ports on a host to determine whether each is a Metasploit reverse handler and what kind of shell it expects, an auxiliary scanner that fingerprints Inductive Automation Ignition gateways across all major version families by probing unauthenticated info endpoints, and a Linux x64 sandbox-evasion module that performs runtime environment checks and aborts execution when a likely sandbox or VM is detected.
Adds support to the post mixin for Windows sessions to run the .writable? method.
- !JSON RPC now requires authentication by default (via database credentials or auth token); existing unauthenticated JSON RPC clients will be rejected on upgrade.
More than DSPM: Bedrock's AI and data security platform unifies data, identity, and AI context so teams see real risk — not noise — without moving data.
Agent DLP sits inline at the agent gateway via AWS AgentCore and LiteLLM hooks, inspecting every tool call in both directions to mask, redact, or block sensitive data in real time — closing the gap between declared policy and actual agent behavior, with an observe mode to validate coverage first.
Bedrock Security shipped a wave of AI governance capability: a new ArgusAI product (AI Data Bill of MaterialsBill of MaterialsA structured list of every component, library, and dependency that makes up a piece of software or hardware, used by cyber tools to track what is inside a product and surface known vulnerabilities in its parts., Guardrail Gap Analysis, natural-language policy and investigation), a graph-backed Metadata Lake with Copilot, AI Agents for DSPMDSPMData security posture management, locating sensitive data and checking how it is protected and who can reach it. It helps teams prioritize risks around their data stores. and a free Snowflake tier, an MCP ServerMCP ServerA process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. exposing 50+ metadata signals to AI agents, and inline Agent DLPDLPData Loss Prevention: a category of controls that inspect and block sensitive data from leaving an organisation via email, web, or removable media, giving cyber tools a policy enforcement layer over data in motion and at rest. runtime enforcement extended from AWS AgentCore/LiteLLM to NVIDIA OpenShell.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
what's the number?
Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.
- depth0–40 what it does and how it works or what changed
- specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
- actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.
Extends Agent DLP to NVIDIA OpenShell via OpenShell's Supervisor Middleware, evaluating each agent action against enterprise data policies and returning an allow/block decision enforced at the sandbox boundary.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Supports an observe-only mode to validate coverage before enforcing, exposes an agent's blast radius (what data its permissions can reach, what combinations it forms, where policy would be violated) at design time, and applies the same data policies across every invocation path an agent may use — MCP tools, command-line invocations, and agent-written code — from a single OpenShell control point. Restrictions travel across table writes, tool handoffs, and agent-to-agent transfers based on the Metadata Lake knowledge graphknowledge graphA representation of entities and the relationships between them. Software can follow those connections to answer questions or combine information from different sources. rather than payload pattern matching.
Adds Natural Language Policy and Investigation in ArgusAI, letting teams articulate data controls in plain English (e.g., "Only members of HR may view employment data" or "EU personal data must remain within EU regions") and have them translated into enforceable controls across connected systems. Extends the same natural-language interface to investigation over the DBOM and guardrail context, so queries like "Which models can access PHIPHIProtected Health Information: individually identifiable health data regulated under the US HIPAA law, whose strict handling requirements drive cyber tools to audit, mask, or restrict access to it. data?" or "Which identities interacted with customer PIIPIIPersonally Identifiable Information — data that can identify a specific individual, such as names, email addresses, or SSNs. Cyber tools flag or redact it to limit exposure and meet privacy regulations. through an agent?" return answers with lineage and access evidence from the Metadata Lake.
Adds Agent DLP to ArgusAI with native hooks for AWS AgentCore and LiteLLM, sitting inline at the agent gateway to inspect every tool call in both directions (outbound requests to MCP tools and inbound tool responses) without acting as a proxy. Enforces data access and regulatory policies to mask, redact, or block sensitive data exposure in real time, logs every decision with target, action, data types, and verdict (blocked, modified, redacted, or observed), and supports an observe mode for monitoring-only enforcement scenarios.
Adds an MCP (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.) Server as a standardized gateway between AI agents and Bedrock's metadata lake, exposing data sensitivity, risk, lineage, access, and usage signals via the open MCP protocol. Surfaces over 50 distinct metadata signals as queryable context for agentic AI workflows and automated governance pipelines, letting AI agents and external applications — including legal and compliance teams — query the metadata lake without custom point-to-point integrations. Builds on the existing Bedrock Metadata Lake Copilot and audits AI model interactions with enterprise data for traceability and policy alignment.
Introduces the Bedrock Metadata Lake, a graph-backed centralized repository that continuously catalogs enterprise data stores across SaaSSaaSSoftware delivered over the internet and billed by subscription, hosted and operated by the vendor so the buyer skips installation and infrastructure management., PaaS, and IaaS, capturing location, sensitivity, entitlements, lineage, usage, risk, and more than fifty additional parameters.
Launches Bedrock Free for Snowflake, a free tier delivering automated sensitive-data discovery and classification for Snowflake environments, including access to Metadata Lake Copilot, with upgrade paths to entitlement chain and usage analysis and automated policy capabilities.
Introduces Bedrock AI Agents for DSPM, which proactively analyze the metadata lake for policy violations and new risks, gather context automatically, suggest next steps, and guide users through incident-response resolution workflows.
Adds Guardrail Gap Analysis in ArgusAI, which compares policy intent against model data exposure drawn from the Metadata Lake and generates targeted remediations to suppress or mask sensitive data at the source or agent runtime.
Adds ArgusAI's AI Data Bill of Materials (DBOM), which automatically links Amazon Bedrock Custom Models, Knowledge Bases (RAGRAGRetrieval-augmented generation: looking up relevant documents and adding them to the prompt before the model answers. It grounds responses in private or current data without retraining.), and Agents to the datasets used during training and inference.
Launches Bedrock Metadata Lake Copilot, a natural-language interface for querying the metadata lake to identify sensitive assets, riskiest users, and other data-risk questions.
Exposes an API-first architecture enabling teams to implement and enforce uniform data-security policies across heterogeneous enterprise infrastructure and to integrate the metadata lake with SIEMsSIEMsSecurity Information and Event Management platforms that collect, normalize, and correlate log data across an infrastructure so cyber tools can detect threats and trigger alerts from a central point., CNAPPs, and DLPs. Also supports detection of sensitive data used in AI initiatives and plain-text secrets, and provides external sharing discovery.
Where each pick stands · Sep 25–Oct 1
Tools with changes in each pick's category over the last 12 weeks, including the pick itself.
Each pick's release rhythm · Sep 25–Oct 1
Changes per week for the last 12 weeks. The bright bar is this week; a dash marks a week with no daily.
Which categories moved · Sep 25–Oct 1
The thick bar is this week. The thin bar is the average of the four weeks before, counting only weeks with a daily.
Who shipped the most · Sep 25–Oct 1
Changes per tool this week. Volume is not a quality score.