The Cyber Toolchain — issue 142, November 17, 2026
THE CYBER TOOLCHAIN
NO. 142
Tail
THE DAILY RELEASE FIREHOSE
PUBLISHED NOVEMBER 17, 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 1325 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. Twingate's Identity Firewall brokers Kubernetes, SSH and web app sessions through an open-source Gateway instead of standing credentials. Tenzir v7.0.0-rc.3 pushes queries down into ClickHouse, Splunk, Defender and SentinelOne, so detection content runs where the data already sits. Skylos turns scan findings into a planned, test-verified cleanup queue.
protect
Grant a Kubernetes or SSH session without issuing a standing credential
Twingate's Identity Firewall puts privileged access to Kubernetes, SSH and web apps behind the open-source Twingate Gateway with Layer 7Layer 7The application layer of the OSI model, where protocols like HTTP, DNS, and TLS operate; cyber tools targeting it can inspect or manipulate traffic by meaning, not just packets. controls, which is the difference between a user holding a kubeconfigkubeconfigA YAML file that stores cluster addresses, credentials, and context settings for kubectl and other Kubernetes clients, letting a tool authenticate to and switch between clusters without extra configuration. forever and getting one brokered session. Arcade's project API keys now carry scope and can be deactivated, and OAuth connections get named profiles, so a leaked integration key no longer means every tool it touched.
Run detection queries against data you never ingested
Query pushdown to ClickHouse, Splunk, Defender (KQLKQLKusto Query Language, Microsoft's read-only query language for Azure Data Explorer and Microsoft Sentinel, used by cyber tools to filter, aggregate, and correlate large volumes of log and telemetry data at speed.), SentinelOne, SQL Server, MySQL and DuckDB means a hunt can execute inside the source system rather than copying everything into a central lake first — the usual tax on cross-tool detection. The reworked 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. functions (ocsf_derive, ocsf_cast, ocsf_compact, ocsf_trim) handle the normalization that makes results from those sources comparable.
Skylos's cleanup workflow plans a fix, has an 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. review it, and verifies it against tests before it lands — the step that usually sits in a human's queue for a quarter. Sonatype adds in-UI triage for quarantined components, so a blocked build gets resolved where the block happened rather than in a side channel.
Restore a pod and have it come back configured correctly
Restore Hooks run init containers and exec commands against restored pods, and storage-class and image-repository remapping ConfigMaps let a restore target a different cluster shape than the one it was taken from. That is the gap between having a backup and having a recovery that actually boots in your DR environment.
Three unrelated things stand out today: skylos can turn queued findings into test-verified fixes; Twingate moved privileged Kubernetes, SSH and web access behind an identity-aware broker; Velero restores can now run hooks and remap storage or images instead of needing post-restore surgery.
protect
Turn vulnerability queues into reviewed fixes
skylos added a cleanup workflow that plans remediation, routes it through 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. review, and verifies fixes with tests; OX Security added GitHub Issues routing, monorepo segmentation, inline suppressions, and VEXVEXA machine-readable statement from a vendor saying whether a CVE in a component actually affects their product. It is how a scanner is told to stop flagging a vulnerability that is not reachable. Status filtering. Together, they reduce the handoff tax between finding, assigning, suppressing, and proving a vulnerability fix.
Broker privileged access instead of handing out standing paths
Twingate’s Identity Firewall puts privileged Kubernetes, SSH, and web app access behind its open-source Gateway. Teams can move sensitive admin sessions through an identity-aware control point instead of relying on broad network reachability or long-lived access routes.
Make Kubernetes restores usable without manual cleanup
Velero documented Restore Hooks for running init containers and exec commands against restored pods, plus ConfigMap-driven storage-class and image-repository remapping. That lets recovery plans encode the environment-specific fixups that otherwise happen after the restore, under pressure.
GitHub added SKU-level and all-AI-credits budget controls plus strictPluginOnlyCustomization for locking down Copilot customization sources; Mend expanded AI reporting with system-prompt and inventory views. Security and platform teams get clearer evidence of which AI capabilities are in use, where customization is allowed, and when spend crosses policy boundaries.
OCInferno adds SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure. credential enumeration, attack-path filters, and CSV/XLSX export to the network resources module︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Narrow an attack-path search to paths originating from users or groups and landing only at the tenancy level, cutting noise from child-compartment grants.
Trace all attack pathsattack pathsA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. from a specific user including IDD admin compound chains, capping results at 50 paths.
Export network inventory results to CSV or XLSX using the new --csv-out and --xlsx-out flags on process_network_resources.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
Filter attack-path starting nodes by principal type using the new --from-type flag (e.g. user,group) on the OpenGraphOpenGraphA web metadata protocol, created by Facebook, that lets a webpage declare structured properties—title, image, description, type—so link previews render consistently across social platforms and messaging apps. attack paths module. Not checked yet
Restrict attack-path targets to a specific scope using the new --to-scope flag (e.g. ocid1.tenancy) to skip child-compartment grants. Not checked yet
Enumerate IDD user SMTP credentials via the new list_smtp_credentials and save_idd_smtp_credentials methods, returning 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. metadata including creation status and expiry. Not checked yet
Network inventory now includes load-balancer backends as a navigable endpoint kind (KIND_BACKEND), surfaced in the inventory report alongside IPs, FQDNs, URLs, and CIDRs. Not checked yet
+2 moreshow less
OpenGraph attack paths now support IDD compound admin chains and annotated default targets for privilege-escalation path discovery. Not checked yet
Print running resource totals every 50 tables during long summary sweeps for real-time progress visibility. Not checked yet
Export network inventory results to CSV or XLSX using the new --csv-out and --xlsx-out flags on process_network_resources.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
Filter attack-path starting nodes by principal type using the new --from-type flag (e.g. user,group) on the OpenGraphOpenGraphA web metadata protocol, created by Facebook, that lets a webpage declare structured properties—title, image, description, type—so link previews render consistently across social platforms and messaging apps. attack paths module. Not checked yet
Restrict attack-path targets to a specific scope using the new --to-scope flag (e.g. ocid1.tenancy) to skip child-compartment grants. Not checked yet
Enumerate IDD user SMTP credentials via the new list_smtp_credentials and save_idd_smtp_credentials methods, returning 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. metadata including creation status and expiry. Not checked yet
adscan v15.0.0 adds engagement scoping, a licensing system for ADscan PRO, and significantly expands what adscan recheck can re-verify, alongside smaller additions to reporting and scan startup.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
6 FEATURES1 OF 6 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
Expanded recheck coverage for AD CS, delegation and DC settingsNot checked yetimproved90how completely this was documenteddepth32/40specificity28/30actionability30/3090 / 100
adscan recheck now covers 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. findings (ESC1–ESC9ESC9A Windows Active Directory privilege-escalation technique exploiting certificate template configurations where the template lacks the security extension, allowing an attacker to abuse certificate enrollment to impersonate other accounts., ESC11, ESC13, ESC15), delegated rights, LAPSLAPSA Microsoft feature that automatically generates, rotates, and stores unique local administrator passwords for each Windows machine in Active Directory, eliminating shared static credentials across a fleet. and gMSA password reads, DCSyncDCSyncAn attack that abuses Active Directory replication permissions to request password-related data from a domain controller. It imitates the synchronization normally performed between controllers. rights, and DC signing/channel-binding/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./LDAPS/Kerberos RC4 settings.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Rechecks can run as a chosen account via -u/--username and -p/--password, target a specific attack path with --path, and both adscan recheck and adscan engagement can write only the JSON document to stdout with --json.
Re-verify AD CS misconfigurations and DC security settings for a specific attack pathattack pathA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. after remediation, using a read-only account that is not stored.
— Lists every finding type and flag, with a runnable command examplev15.0.0
0200
Engagement scoping by host and accountNot checked yetnew88how completely this was documenteddepth32/40specificity28/30actionability28/3088 / 100
Adds --scope-allow and --scope-deny on adscan ci and adscan start, accepting IPs, CIDRs, ranges, hostnames, SIDs, DNs, DOMAIN\name, and UPNs, plus --scope-allow-file and --scope-deny-file for file-based lists and --scope-dc-access full to permit full DC contact beyond directory reads. An interactive scope shell command lets operators inspect, change, and explain the current engagement scope, and prompts before any widening of scope.
— Names every flag and the interactive command, no example attachedv15.0.0
0300
License management for ADscan PRONot checked yetnew84how completely this was documenteddepth28/40specificity28/30actionability28/3084 / 100
Adds the adscan license command with activate, status, check, deactivate, and relay import subcommands. PRO can be installed with adscan install --license-file, and offline or air-gapped licence refresh is supported via a file exported with --relay-out and imported with adscan license relay import.
— Full subcommand and flag set named, no runnable example givenv15.0.0
0401
PRO licensing enforcement and distribution changesNot checked yetbreaking65how completely this was documenteddepth26/40specificity24/30actionability15/3065 / 100
From v15.0.0, adscan start, adscan ci, adscan execute, and adscan recheck stop with an error on unlicensed machines, with adscan ci exiting 78. PRO images are no longer published to Docker Hub and GHCRGHCRGitHub Container Registry, GitHub's hosted service for storing and distributing OCI-compatible container images, giving cyber tools a versioned, access-controlled image store tied directly to a GitHub repository., with new versions published only to ADscan's own registry after a transition period, and --offline no longer suppresses domain registration telemetry for PRO licences.
— Names exact commands, exit code and registries, no migration stepsv15.0.0
0500
Compliance framework opt-out and policy agreement trackingNot checked yetnew64how completely this was documenteddepth24/40specificity22/30actionability18/3064 / 100
--frameworks none (or selecting None) omits compliance framework mapping from audit reports while recording the assessor's decision. A per-workspace agreed_policy key in scan config makes both reports name the policies in effect and their digests when a run deviates from the agreed policy.
— Names flag and config key but no worked examplev15.0.0
thinner coverage below
0600
Skip minimum memory check at startupNot checked yetnew47how completely this was documenteddepth12/40specificity15/30actionability20/3047 / 100
Passing --allow-low-memory starts the scan without enforcing the minimum memory check.
— Single flag, thin description of the check itselfv15.0.0
└──▷ BREAKING ON UPGRADE
!
ADscan PRO now requires an activated licence; from v15.0.0 adscan start, adscan ci, adscan execute, and adscan recheck stop with an error on unlicensed machines, and adscan ci exits 78.
!
PRO images are no longer published to Docker Hub and GHCR; new versions are published only to ADscan's own registry after a transition period.
!
--offline no longer suppresses domain registration telemetry for PRO licences.
Metasploit Pro is a penetration testing platform that automates vulnerability exploitation, network scanning, and security assessments to help professionals identify and remediate weaknesses.
Metasploit Pro 5.1.0 adds 16 new exploit and auxiliary modules spanning Citrix NetScaler, GitLab CI/CD, Portainer, OpenBullet2, Flowise, SPIP and HashiCorp Consul, alongside a new Linux ELFELFThe standard binary format for executables, shared libraries, and object files on Linux and most Unix-like systems, giving cyber tools a predictable structure to parse, instrument, or analyze compiled code. injector persistence module, Windows support for Docker Image Persistence, expanded payload architecture coverage, and shared Zimbra SOAPSOAPA W3C-standardized XML-based messaging protocol for exchanging structured data between services over HTTP or other transports, giving cyber tools a language-agnostic way to call remote APIs. infrastructure.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES1 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
New exploit modules for Citrix, GitLab, Portainer, OpenBullet2, Flowise, SPIP, ConsulNot checked yetnew85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Adds an unauthenticated RCERCERemote code execution, the ability to run attacker-chosen code on another system through a vulnerability. Its impact depends on the permissions and access that code receives. via command injectioncommand injectionAn attack that makes an application execute operating-system commands supplied through untrusted input. It often happens when input is passed unsafely to a shell. for Citrix NetScaler (CVE-2026-88771), reported exploited in the wild prior to disclosure; an integer overflow in GitLab CE/EE Linux amd64's CI/CD regular expression compiler enabling RCE as the git user (CVE-2026-97229); a Portainer exploit that uses valid credentials to create a privileged container, bind-mount the host filesystem, and execute a payload as root on the Docker host; two OpenBullet2 modules — an RCE via plain C# execution mode (CVE-2026-25856) and a credential disclosure scanner that forces NTLMv2NTLMv2A 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. hash disclosure via a malicious UNC path (CVE-2026-39908); an account takeover auxiliary module for Flowise versions 3.0.5 and earlier (CVE-2025-58434) that retrieves a valid password reset token directly from the API response; an unauthorized password change auxiliary module for SPIP before 4.4.23 via a validly-signed POST without id_auteur authorization checks; and a HashiCorp Consul version scanner.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Linux ELF injector persistence moduleNot checked yetnew64how completely this was documenteddepth30/40specificity22/30actionability12/3064 / 100
New persistence module injects into Linux ELF binaries using code cave and segment injection techniques, supporting x86, x64, and 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. architectures with architecture-specific trampolines that preserve the original execution flow.
Windows support in Docker Image Persistence moduleNot checked yetimproved64how completely this was documenteddepth28/40specificity22/30actionability14/3064 / 100
The Docker Image Persistence module now supports Windows, enabling Meterpreter sessions on Windows hosts running Docker Desktop to create a persistent Alpine container with access to the host's C: drive.
Payload support for loongarch64 and AArch64 WindowsNot checked yetnew48how completely this was documenteddepth18/40specificity20/30actionability10/3048 / 100
Adds loongarch64 shell payloads and the required configs to work with fetch payloads, and adds an AArch64 Windows DLLDLLA Windows file format containing compiled code and data that multiple programs can load and share at runtime, letting cyber tools inject functionality into other processes or hook system calls. template, hooking up payload generation to use it.
Shared Zimbra SOAP support across modulesNot checked yetnew48how completely this was documenteddepth22/40specificity18/30actionability8/3048 / 100
Adds shared Zimbra SOAP support for account and administrator authentication, account discovery, and version retrieval, letting Zimbra modules reuse consistent token routing, response validation, and error handling.
BloodHound is an Active Directory reconnaissance tool that maps attack paths and privilege escalation routes within Windows domain environments.
BloodHound's v9.10.0 release expands its API with endpoints for relationship and node kind lookups, management operation control, and client artifact storage, alongside new S3S3Amazon's object storage service, where files are stored in named buckets and retrieved over HTTP; cyber tools use it for scalable, cheap log or artifact storage without managing a filesystem.-backed artifact storage and admin UI actions for support bundles.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Relationship kind and node kind lookup endpointsNot checked yetnew70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Adds api/v2/relationship-kinds/{relationship_kind_id} to retrieve details about a specific relationship kind, and a new GET node kind endpoint to look up node kind details by ID.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Retrieve details about a specific relationship kind by its ID to understand edge types in your graph.
— Exact endpoint path and curl example given; node kind path not specified.v9.10.0
0200
Client artifact download, delete and S3 storageNot checked yetnew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds a download client artifact endpoint and a delete client artifact endpoint to retrieve and remove client artifacts via the API. Adds part_number support to the artifact upload flow for multipart uploads, and S3 configuration support to store and retrieve artifacts from S3-compatibleS3-compatibleAn object-storage API that mirrors Amazon S3's HTTP interface, so any client or cyber tool written for AWS S3 works unchanged against any compliant storage backend. object storage.
— Names config/flow surfaces but no exact endpoint paths or config keys.v9.10.0
thinner coverage below
0300
Management operations control and inspection endpointsNot checked yetnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds queue management operation endpoints to control and inspect running management operations via the API, plus a get-available management operation endpoint to query which management operations are available. Artifact metadata is now exposed on management operations responses.
— Describes operation types but omits exact endpoint paths.v9.10.0
0400
Download and delete client support bundle in admin UINot checked yetnew45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
Adds a download client support bundle UI action and a delete client support bundle UI action to the administration interface.
— UI action named but no exact navigation path given.v9.10.0
BruteSpray v2.7.6 adds telnet decoy-shell detection to catch fake logins and fixes circuit-breaker logic so -max-conn-fails works without requiring spray mode.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
BruteSpray is a Python tool that automatically performs credential brute-forcing against services discovered by Nmap scans using Medusa.
BruteSpray v2.7.6 adds telnet decoy-shell detection to catch fake logins and fixes circuit-breaker logic so -max-conn-fails works without requiring spray mode.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Circuit breaker fix for `-max-conn-fails`Not checked yetimproved84how completely this was documenteddepth28/40specificity28/30actionability28/3084 / 100
Passing -max-conn-fails alone now enables the circuit breaker under -skip-policy auto without also requiring -spray or an explicit policy flag, allowing host skipping outside spray mode.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Hosts mixing connection errors and auth rejections now stop after the configured -max-conn-fails threshold instead of spraying to the end of the credential list, a behaviour change versus v2.7.5.
Skip a host that keeps rejecting connections during a non-spray scan without needing to set an explicit spray policy.
— Named flags plus a runnable example commandv2.7.6
0200
Telnet decoy-shell detectionNot checked yetimproved69how completely this was documenteddepth32/40specificity22/30actionability15/3069 / 100
After an apparent successful telnet login, BruteSpray now sends a confirmation probe; if a second authentication screen appears, the result is downgraded from a success to a failed credential and a WARNtelnet-second-screen finding is emitted. This prevents fake-shell logins on DVRs, IP cameras, and managed switches from polluting success files. Telnet targets previously reported as successful under this condition now report the new finding instead, so old success files from telnet runs should be re-checked.
— Explains mechanism and before/after but no CLI flag to toggle itv2.7.6
└──▷ BREAKING ON UPGRADE
!
Hosts that mix connection errors and auth rejections now stop after the configured -max-conn-fails threshold instead of spraying to the end of the credential list — expected behaviour change versus v2.7.5.
!
Telnet targets previously reported as successful when a decoy shell was present now report telnet-second-screen findings instead; re-check old success files from telnet runs against this pattern.
Official documentation for Invicti AppSec Platform, Invicti Platform, and Invicti Enterprise — web application security testing, DAST, API security, and vulnerability management.
Invicti adds target-type filtering on the Scans page, configurable default Accept headers, GraphQL schema visibility in the API catalog, removed-operation tracking, API gateway connection testing, NTA renaming without token regeneration, and REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. support for linking APIs from a URL.
Filter scans by target type (Web or API) and see the target type in a new column on the Scans page. Not checked yet
Set the default Accept header the scanner sends on web and API requests using the Default Web Accept Header and Default API Accept Header settings in a target's advanced settings. Not checked yet
Link an API from a URL through the Invicti Platform REST API, matching what was previously only possible in the UI. Not checked yet
Updated detectionThe API catalog now shows GraphQL schemas with the same detail it shows for REST APIsREST APIsA convention for building HTTP-based interfaces where resources are addressed by URL and manipulated with standard verbs like GET, POST, and DELETE, giving cyber tools a predictable way to integrate with external services.. Not checked yet
The API catalog now marks operations that no longer appear in a re-imported API definition as Removed, with a status filter to show or hide them. Not checked yet
+7 moreshow less
Test the connection when saving an API gateway integration to catch connection problems immediately. Not checked yet
Rename a Network Traffic Analyzer (NTA) connection without generating a new token. Not checked yet
Zero Configuration discovery is now enabled by default. Not checked yet
Email notifications for new and updated APIs are now off by default; turn them on in profile notification settings. Not checked yet
Users can now assign only roles whose permissions they already hold, and only within the collections they manage. Not checked yet
When bulk-adding APIs from API discovery as targets, you can now review and change the base URL for each API. Not checked yet
Source Scan now looks for existing API specs in your source code to build a more complete picture of your application's API. Not checked yet
!Email notifications for new and updated APIs are now off by default — teams that relied on receiving these automatically must re-enable them in profile notification settings.
GitHub is a web-based platform for version control and collaborative software development using Git repositories.
GitHub's biggest change this window is making the Microsoft Copilot harness the default (and eventually only) VS Code agent runtime, replacing the Local harness ahead of a February 2027 removal; alongside that it shipped new SKU-level and all-AI-credits budget controls, a strictPluginOnlyCustomization managed setting for locking down Copilot customization sources, and a broad set of weekly Copilot updates covering GHES mobile support, VS Code Agents window UI, new models, dictation languages, and accessibility settings.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
16 FEATURES2 OF 16 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Copilot harness becomes default agent runtime in VS CodeNot checked yetbreaking95how completely this was documenteddepth40/40specificity30/30actionability25/3095 / 100
The Microsoft Copilot harness is now the default agent session runtime in VS Code (selectable via Copilot under Session Target), built on the Copilot SDK and shared with Copilot CLI and the GitHub Copilot app, replacing the Local harness which will be removed in February 2027 along with the vscode.temporaryDefaultToLocalHarness enterprise-managed setting — existing customizations are not automatically converted and must be reviewed for compatibility.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The harness adds Copilot Fusion, which automatically chooses models and, on supported tiers, coordinates drafting and review for a task; assisted permissions that reduce approval interruptions while still surfacing calls that fail risk assessment for manual confirmation; Copilot connectors Preview to bring in context from team services without configuring 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 manually; canvases Preview for planning work and exploring interactive diagrams on task boards; continuity of the same agent session across the editor and the Agents window while the session's Agent Host process stays running; and administrator-enforced managed runtime permissions and sandbox restrictions that the Local harness could not enforce.
Switch an existing VS Code Copilot agent session from the deprecated Local harness to the new Copilot harness before the February 2027 removal deadline.
📍In VS Code, start a new agent session and under Session Target select Copilot.
strictPluginOnlyCustomization managed setting for CopilotNot checked yetnew95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Copilot customizations can be restricted to plugins and managed settings — blocking standalone user and project configs — with the strictPluginOnlyCustomization managed setting, applicable to any combination of skills, custom agents, hooks, MCP servers, and executable Copilot extensions. Pairing it with strictKnownMarketplaces also restricts which marketplaces supply eligible plugins, letting enterprise admins distribute approved MCP tools and canvases through a shared plugin library.
Lock MCP servers and executable extensions to plugin-only sources while leaving skills, agents, and hooks open to per-user configuration.
SKU-level and all-AI-credits budget controlsNot checked yetnew78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
GitHub billing adds SKU-level budgets to cap overage spending on a specific product SKU, such as Copilot code review, Secret Protection AI credits, or GitHub Advanced Security — including selecting Advanced Security and the SKU for AI Scan and agentic autofix — and an All AI credits budget that caps total overage spending across every SKU that consumes AI credits (Copilot, Copilot cloud agent, Spark, and Advanced Security AI features), drawing on the shared AI credits allowance before counting overage.
Cap AI credit overage across all GitHub AI features org-wide to prevent unexpected spend from Copilot, Spark, and Advanced Security AI.
📍In GitHub billing settings, go to Budgets and create a new budget, select All AI credits as the budget scope, and set a spending limit. Available where overage spend is enabled.
— Clear UI steps and named SKUs, no API endpoint givenproduct docs
0400
Agents window enhancements in VS CodeNot checked yetnew75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
The VS Code Agents window adds Inbox mode to the sessions list to track agent sessions across all workspaces from one view, surfacing sessions needing attention first and letting you dismiss, hold, or snooze the rest; lets you move a chat out of the Agents window into its own window Preview to arrange the chat, its editors, and its terminals independently; and lets you find, install, and uninstall extensions without leaving the Agents window, showing a warning for extensions with unsupported features.
Use Inbox mode in VS Code to triage all agent sessions across workspaces and act on the ones waiting for input.
📍In VS Code, open the Agents window, switch to the sessions list, and enable Inbox mode — sessions needing attention appear first; use dismiss, hold, or snooze on the rest.
Compare Models agent tool in VS CodeNot checked yetnew70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Agent-driven model comparisons can be enabled in VS Code by turning on the Compare Models agent tools in settings, letting agents find available models, launch comparisons, and summarize findings.
Let an agent benchmark available models against each other and surface a summary, without running comparisons manually.
📍In VS Code settings, enable Compare Models under agent tools, then open the Agents window and ask the agent to compare available models for your task.
New Copilot models: Claude Fable 5.2 and Gemini 4 CarbonNot checked yetnew60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Adds Claude Fable 5.2 and Gemini 4 Carbon models, now available to Copilot Pro+, Max, Business, and Enterprise users; Copilot Business and Enterprise admins must enable Claude Fable 5.2 via a policy that is off by default.
GitHub Mobile enhancements: cross-device sessions and iPhone Duo supportNot checked yetnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
GitHub Mobile now lets you continue cloud and Codespace sessions on a phone via a new Open in menu with a GitHub Mobile option showing a QR code, and adds support for iPhone Duo with a layout that adapts when the device is unfolded and vertical tabs for navigating between Copilot, Pull Requests, Issues, and Notifications.
High contrast accessibility settings replace Increase contrastNot checked yetbreaking55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
High contrast can now be combined with red, green, or blue-yellow color filters in Settings > Accessibility, with a preview of combinations before applying; High contrast replaces the separate Increase contrast setting.
Zero data retention exemption for Claude modelsNot checked yetnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Claude Fable 5, 5.1, and 5.2 offer zero data retention (ZDR) through 2026 via a time-bound exemption; enterprises must contact GitHub to request access, and approved enterprises have requests routed automatically to the ZDR endpoint once an administrator enables those models.
— Names models and policy but process is vagueproduct docs
1000
Custom field filtering for issues and pull requestsNot checked yetnew50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Issues and pull requests can be filtered by custom fields, such as a GitHub Project's Size, from the Add filter menu.
Budget limit raised to 40,000 per accountNot checked yetNew supported platformimproved45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
GitHub Enterprise Cloud accounts can now create up to 40,000 budgets per account, up from 10,000, applying automatically on github.com and GHE.com with nothing to turn on.
MCP server reauthentication without leaving conversationNot checked yetimproved45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Users can sign back in to MCP servers such as Slack without leaving the conversation — when a server needs re-authentication, the conversation offers the matching connector and resumes the task.
Scheduled Project automations down to the minuteNot checked yetimproved40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Project automations can now be scheduled down to the minute, or using a custom cron schedule such as weekdays at 9:30.
Dependabot alert dismissal requests last one yearNot checked yetimproved35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Dependabot delegated alert dismissal requests now stay open for one year before expiring, up from one week, giving reviewers more time to respond without requiring resubmission.
The Local harness will be removed in February 2027; workflows must be migrated to the Copilot harness before then.
!
High contrast replaces the separate Increase contrast setting.
!
The vscode.temporaryDefaultToLocalHarness enterprise-managed setting will be removed in February 2027 along with the Local harness; keeping the exception configured will not keep the Local harness available.
!
The Local harness is removed in February 2027; existing customizations are not automatically converted when switching to the Copilot harness and must be reviewed for compatibility.
GitHub now allows bulk-starting AI Scans for up to 20 repositories at once from the code scanning organization alerts page, with no Copilot license required.
Start AI Scans for up to 20 repositories at once from the code scanning organization alerts page or the organization-level setting, without requiring a GitHub Copilot license. Not checked yet
Start an AI Scan for a single repository directly from its alerts page, with findings appearing in the code scanning backlog alongside CodeQL alerts. Not checked yet
Syzkaller is an unsupervised coverage-guided kernel fuzzer developed by Google that automatically finds bugs in OS kernels by generating and executing random syscall sequences.
syzkaller adds automatic AI cause bisection scheduling, KCSANKCSANA dynamic race-condition detector built into the Linux kernel that instruments memory accesses to catch data races in kernel code, giving cyber tools a reliable way to surface concurrency bugs during testing. flow improvements, and hardware breakpoint delay injection for race analysis︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds a hardware breakpoint delay helper to race_toolkit.h that opens a PERF_TYPE_BREAKPOINT on a pid/address and attaches a BPF_PROG_TYPE_PERF_EVENTBPFBPFA Linux kernel virtual machine that lets programs attach small, sandboxed bytecode filters to kernel hooks — syscalls, network events, tracepoints — so cyber tools can observe or redirect kernel behaviour without writing a kernel module. program to stall inside the #DB handler for a configurable number of microseconds, aiding precise data-race reproduction.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
Adds FailureDetectableBy output field to the KCSAN assessment flow to surface which layer can observe a detected data race. Not checked yet
Adds open_tree_attr syscall descriptions to sys/linux. Not checked yet
Adds x86 SYZOS memwrite instruction support and expands SMRAM coverage in the executor. Not checked yet
Adds automatic AI cause bisection scheduling to the dashboard, including rate limiting for older bugs via bisectCauseNewBugAge, maxBacklogBisectCauseJobs, and backlogBisectCauseWindow constants to prevent old bugs from saturating agents, and a maxAutoBisectCauseAttempts cap to bound automatic retries of failed or aborted cause-bisection workflows. Not checked yet
+5 moreshow less
Skips automatic AI job creation in decommissioned namespaces, gating on the cfg.Decommissioned flag. Not checked yet
Schedules repro-c generation automatically for harmful KCSAN data races. Not checked yet
Switches syz-agent Kubernetes bisection workflows to the Vertex backend. Not checked yet
Improves KVMKVMA Linux kernel module that turns the kernel into a hypervisor, letting a process run fully isolated virtual machines using hardware virtualisation extensions. Cyber tools use it to sandbox execution environments at near-native speed. dirty ring descriptions and adds tests in sys/linux, and updates KVM descriptions in sys/linux for linux-next. Not checked yet
Expands the KVM focus syscall allowlist in syz-cluster/pkg/fuzzconfig. Not checked yet
Adds a hardware breakpoint delay helper to race_toolkit.h that opens a PERF_TYPE_BREAKPOINT on a pid/address and attaches a BPF_PROG_TYPE_PERF_EVENTBPFBPFA Linux kernel virtual machine that lets programs attach small, sandboxed bytecode filters to kernel hooks — syscalls, network events, tracepoints — so cyber tools can observe or redirect kernel behaviour without writing a kernel module. program to stall inside the #DB handler for a configurable number of microseconds, aiding precise data-race reproduction.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
Adds FailureDetectableBy output field to the KCSAN assessment flow to surface which layer can observe a detected data race. Not checked yet
Adds open_tree_attr syscall descriptions to sys/linux. Not checked yet
Adds automatic AI cause bisection scheduling to the dashboard, including rate limiting for older bugs via bisectCauseNewBugAge, maxBacklogBisectCauseJobs, and backlogBisectCauseWindow constants to prevent old bugs from saturating agents, and a maxAutoBisectCauseAttempts cap to bound automatic retries of failed or aborted cause-bisection workflows. Not checked yet
Schedules repro-c generation automatically for harmful KCSAN data races. Not checked yet
The official changelog for the Snyk AI Trust Platform. Discover what's new in our security intelligence, AI-powered tools, and latest product enhancements.
Snyk added browser-based login support for authenticated API scanning of Postman and Bruno targets, removing the need for manual token management on OAuth 2.0OAuth 2.0An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms., SAMLSAMLA standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider., and SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management.-protected APIs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Browser login for Postman and Bruno API targetsNot checked yetnew81how completely this was documenteddepth32/40specificity27/30actionability22/3081 / 100
A new Browser login option under Settings > Authentication lets Snyk replay a browser-based sign-in at scan time and automatically extract the session credential, enabling authenticated scans against API targets that don't issue static API keys.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It supports OAuth 2OAuth 2An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs..0 Authorization Code, SAML, and SSO flows, including two-factor authentication (2FA2FATwo-Factor Authentication, an authentication scheme requiring a second proof of identity beyond a password, so a stolen credential alone cannot grant access.), and works with scheduled scans. The authentication settings page now groups options into Collection-defined login, Browser login, and Logout detection sections for Postman and Bruno targets.
Schedule an authenticated DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces. scan against a Postman or Bruno collection that uses OAuth 2.0, SAML, or SSO — without pre-generating or rotating tokens manually.
📍In the Snyk Web UI, open your Postman or Bruno API target, go to Settings › Authentication, select Browser login, configure the sign-in flow, and save. Snyk will replay the browser-based login automatically at each scheduled scan.
— Names exact UI path, flows, and 2FA support; no limits given2026-11-16-8b960aa6
Mend SAST is a static application security testing service that scans source code for vulnerabilities and helps teams prioritize remediation.
Mend SAST adds a guided onboarding wizard with repository selection, pilot scans, and team email delegation, plus engine-generation language filtering in Global Scan Configuration.
Start SAST scanning for repositories from the Mend Platform using a new guided onboarding wizard that handles repository selection and pilot scan execution without manual configuration. Not checked yet
Delegate SAST onboarding to colleagues by sending email invitations from within the wizard to drive team-wide adoption. Not checked yet
Filter Global Scan Configuration language options by engine generation so only supported languages appear during scan setup. Not checked yet
Veracode is a cloud-based application security platform that scans code for vulnerabilities using static, dynamic, and software composition analysis testing methods.
Veracode's latest DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces. updates focus on finer-grained target configuration, expanded Enterprise-mode authentication and reporting, and new ways to plug DAST into the broader Veracode Platform and automation via REST APIsREST APIsA convention for building HTTP-based interfaces where resources are addressed by URL and manipulated with standard verbs like GET, POST, and DELETE, giving cyber tools a predictable way to integrate with external services..︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
10 FEATURES0 OF 10 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Expanded DAST target configuration optionsNot checked yetimproved70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
New DAST target configuration options include Directory Restrictions to control which URL paths the scanner may follow, a business unit selection when creating a web application or API specification target (or on the DAST configuration page), and a custom host-to-IP address mapping for when DNS lookup is unavailable or undesired.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Configuration also gains an optional Domain field for HTTP basic authentication, the ability to assign multiple teams to a single target, and Full scan Enterprise mode as the new default, with the legacy Full scan option deprecated and no longer available for new or Quick scan targets.
Authenticate to a Windows domain-integrated web application in a DAST scan by supplying domain credentials alongside the username and password.
📍In the DAST target configuration, go to Authentication › HTTP Basic Authentication, fill in Username and Password, then set the optional Domain field to your Windows domain name (e.g. CORP).
Restrict a DAST scan to a specific subdirectory of your application so the crawler does not stray into unrelated paths.
📍In the DAST target configuration, go to Allowed URLs, add the URL, then enable Directory Restrictions and enter the permitted path prefix (e.g. /app/v2/).
New authentication methods in DAST Enterprise modeNot checked yetnew63how completely this was documenteddepth25/40specificity28/30actionability10/3063 / 100
DAST Enterprise mode adds AI-assisted login for complex login flows, login scripts, scanner variables, client certificates for web applications, Scriptable Request Modifications (SRM) for APIs, time-based one-time password (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.) seeds (including via the REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services.), and custom cookies. API Scanning also adds the ability to use JavaScript to modify an HTTP request at runtime when authenticating with a remote host (Scriptable Request Modification).
ISM proxy exclusions and EU region supportNot checked yetimproved55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
ISM endpoint 24.10.0 adds a proxy exclusion list so specified hosts bypass the configured proxy settings, and ISM is now available for Veracode Dynamic Analysis of web applications and API specifications in the European region.
Public REST API for DAST target and analysis managementNot checked yetnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
A Public REST API for DAST target configuration now enables automation of DAST target management and analysis triggering, and the Dynamic Analysis REST API can be used to set URL scan settings for all analyses and scans at the organization level.
DAST application linking to Veracode PlatformNot checked yetnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
DAST adds application linking, letting you link analysis run results to a Veracode Platform application to evaluate against policy and combine results from multiple scan types in a single report.
EASM-to-DAST automatic target creationNot checked yetnew40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
EASMEASMExternal Attack Surface Management: a discipline and category of tooling that continuously discovers and monitors an organization's internet-facing assets to identify exposures before attackers do. integration now automatically creates discovered targets in DAST, which can be mapped or converted to regular DAST targets for scanning.
DAST REST API scheduling endpoints changedNot checked yetbreaking40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
The DAST REST API scheduling endpoints have changed; integrations that use the REST API to manage a schedule must be updated to use the new endpoints, per the DAST API specification.
The DAST REST API scheduling endpoints have changed; integrations that use the REST API to manage a schedule must be updated to use the new endpoints (see the DAST API specification for details).
Veracode 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. adds --appname and --show-cli scan flags, Unified Policy assignment for EU and US Federal workspaces, SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. generation, upgrade-path-aware build-break rules, and updated backend API URLs.
Link SCA agent scan results to an application profile by passing --appname to the scan command (requires OAuth or HMACHMACA keyed hash that proves a message came from someone holding a shared secret and was not altered. Webhooks and API request signing commonly use it. authentication, Commercial region only). Not checked yet
Save JSON scan output to a file while displaying a human-readable summary in the console by passing --show-cli together with --json to the SCA agent scan command; using --show-cli without --json returns an error. Not checked yet
Assign policies to SCA agent-based scan workspaces in the US Federal region using the Unified Policy feature to create issues and break builds based on defined criteria. Not checked yet
Assign policies to SCA agent-based scan workspaces in the European region using the Unified Policy feature to create issues and break builds based on defined criteria. Not checked yet
Control when builds are broken based on upgrade-path availability by configuring the Vulnerability Severity rule in a policy (Commercial region). Not checked yet
+5 moreshow less
Generate SBOM files during SCA agent-based scans. Not checked yet
Use https://sca-downloads.veracode.com as the new default URL for downloading the SCA agent (the legacy https://download.sourceclear.com remains available for 12 months). Not checked yet
Use https://sca-api.veracode.com as the new default backend API URL for Commercial region SCA agent scans (legacy https://api.sourceclear.io remains available for 12 months). Not checked yet
Use https://sca-api.veracode.eu and https://sca-api.veracode.us as the new default backend API URLs for European and US Federal region SCA agent scans respectively (legacy https://platform-backend.analysiscenter.veracode.eu and https://platform-backend.analysiscenter.veracode.us remain available for 12 months). Not checked yet
Deep link support now redirects unauthenticated users to the login page and back to the original SCA results page. Not checked yet
Infisical is an open-source secret management platform that helps teams securely store, sync, and manage API keys, environment variables, and other sensitive configurations.
Infisical v0.167.11 adds a new dynamic secret provider for OpenRouterOpenRouterA unified API gateway that routes requests to dozens of LLM providers under one endpoint, letting cyber tools swap or compare models without rewriting provider-specific integration code., introduces output masking in PAMPAMBrokering administrator sessions through a gateway instead of handing out standing credentials. Access is granted for one session, to one target, and recorded., extends the database schema with 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. config support, and fixes the ServiceNow integration to read all workflow approvers.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
TOTP config table in database schemaNot checked yetnew45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Adds a totp_configs table to the sanitized database schema to support TOTP configuration.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact schema table but no behavior explained.v0.167.11
0200
OpenRouter dynamic secret providerNot checked yetnew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds a new dynamic secret provider for OpenRouter API keys, allowing Infisical to generate and manage dynamic credentials for OpenRouter.
— Names the provider but no setup or config detail given.v0.167.11
0300
ServiceNow integration reads all approversNot checked yetimproved40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
The ServiceNow integration now reads every approver from the approvals column, rather than only the first one, fixing incomplete approval processing.
— Explains before/after behavior but no config surface named.v0.167.11
0400
Output masking for PAMNot checked yetnew10how completely this was documenteddepth5/40specificity5/30actionability0/3010 / 100
Adds output masking for PAM (Privileged Access ManagementPrivileged Access ManagementBrokering administrator sessions through a gateway instead of handing out standing credentials. Access is granted for one session, to one target, and recorded.), though the release notes do not detail the mechanism or scope.
— Mentioned only in summary with no further detail.v0.167.11
LavaMoat is a security tool that uses JavaScript sandboxing to protect Node.js and browser apps from supply chain attacks by isolating package permissions.
LavaMoat's harden-v0.9.0 release refines its runner to better handle bin script conflicts and package manager detection, aimed at blocking more classes of bin script confusion.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Bin script and package manager handling in harden runnerNot checked yetimproved35how completely this was documenteddepth20/40specificity10/30actionability5/3035 / 100
LavaMoat harden's runner now accepts new bins that are not collisions with existing entries, reducing false positives in bin script confusion detection.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It also falls back on the detected package manager more eagerly when no explicit manager is configured.
— Describes behavior change but no exact flags, configs, or commands given.harden-v0.9.0
Fastly is a cloud edge platform providing CDN, DDoS protection, load balancing, and real-time content delivery to accelerate and secure web applications.
Fastly introduced a new Organizations API that lets administrators programmatically manage organization-level accounts, member invitations, memberships, and security requirements like SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. and two-factor authentication.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Organizations API for accounts, members, and securityNot checked yetnew58how completely this was documenteddepth28/40specificity18/30actionability12/3058 / 100
The new Organizations API adds endpoints to get and update an organization, including requiring SSO or two-factor authentication for every member.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It also covers managing accounts (list existing accounts, create new ones under the organization), member invitations (invite people, list invitations, resend an invitation, cancel an invitation), and memberships (list members filtered by name, email address, or role, change a member's roles, and remove members).
Netcap shipped exotic link-layer decoding with explicit device profiling, hard memory bounds across TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it., reassembly, and aggregate capture state, and an expanded MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server with paginated, count-only inventory queries.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Netcap is a framework for secure and scalable network traffic analysis - https://netcap.io
Netcap shipped exotic link-layer decoding with explicit device profiling, hard memory bounds across TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it., reassembly, and aggregate capture state, and an expanded MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server with paginated, count-only inventory queries.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
7 FEATURES0 OF 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Exotic link-layer decoding and device profilesNot checked yetnew95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds explicit device profile mapping for exotic link types via the new -link-profiles flag on net capture (accepted in PCAPPCAPA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic., live, and service modes); reconstructs link-layer payloads for ALP, MS/TP, 6LoBAC, and ROHC frames with source ranges and transformations preserved in audit records; decodes Darwin USB capture headers and adds bounded LinkFrame paths for AX.25, MS/TP, Bluetooth H4, I2C, MPEG-TSMPEG-TSA container format for multiplexing audio, video, and metadata into a continuous stream of fixed-size 188-byte packets, standardized by MPEG; tools use it because it tolerates packet loss and supports live or broadcast streaming., Upper PDU, ALP, and MDB link types; and extracts BACnetBACnetA communication protocol for building automation systems, standardized as ASHRAE 135, covering HVAC, lighting, and access control devices. Cyber tools use it to discover and interact with building infrastructure on IP or serial networks. NPDU/APDU metadata, MPEG-TS program/PES and H.264/H.265/AAC headers, Bluetooth 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./L2CAP/ATT/SMP metadata, and USB descriptor correlations in upper-layer profiles.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Capture from a PCAP containing exotic link types (e.g. MPEG-TS or Bluetooth H4) and supply an explicit device-profile mapping so Netcap knows how to frame each link layer.
— Names every protocol and flag with a runnable example.v0.16.9
0200
Bounded memory limits for TCP, reassembly, and aggregate stateNot checked yetnew95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Sets default bounds of 64 MiB for --max-retained-tcp-bytes and 32 MiB for --max-retained-reassembly-bytes, aborting capture rather than growing without limit when exceeded, to back TCP control/reassembly payloads, normalized Software observations, vulnerability/exploit deduplication, and optional network-layer payloads with private bounded storage. Separately, --max-aggregate-state-bytes (default 32 MiB, also readable from env var NC_MAX_AGGREGATE_STATE_BYTES) caps resident Connection, Host, DeviceProfile, Service, and 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. cache state and spills excess to private scratch storage, with 0 keeping everything in memory.
Live capture with a hard ceiling on TCP reassembly memory — useful on memory-constrained sensors where runaway reassembly must abort rather than exhaust RAMRAMWorking memory that holds programs and data while a computer is running. Its contents usually disappear when power is removed..
Limit resident aggregate cache to 64 MiB when analysing a large PCAP to keep peak RSS manageable; excess Connection/Host/Service state spills to scratch storage automatically.
— Flags, env var and defaults all named with runnable commands.v0.16.9v0.16.8
0300
MCP server inventory querying and pagingNot checked yetnew75how completely this was documenteddepth30/40specificity30/30actionability15/3075 / 100
Netcap's mcp command exposes current analysis and operational workflows through its stdio 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, described as a 119-tool MCP surface; it supports count-only inventory queries that scan all matching audit records without transferring record bodies, and paginates inventories with byte-bounded pages, stable generations, search, matched totals, generation checks, structured field/JSON Pointer projection, and complete oversized JSON artifacts.
— Lists concrete capabilities but no example command given.v0.16.8v0.16.9
thinner coverage below
0400
Automatic tshark follower namespace detectionNot checked yetimproved50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Discover the installed tshark follower namespace automatically — using modern tls.stream or falling back to legacy tcp.stream after an unsupported-field diagnostic.
— Names the fields involved but no usage example.v0.16.9
0500
PPI/DLT 192 wireless capture decodingNot checked yetnew35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Netcap now decodes PPIPPIPay-per-install, a distribution model where malware or adware operators pay affiliates for each successful installation of a payload, giving cyber tools a monetization mechanism to track and attribute malicious campaigns./DLT 192 capture headers and preserves wireless FCS provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build..
— Names the format but gives no further mechanism or example.v0.16.8
0600
Signed Windows CLI binariesNot checked yetimproved35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Sign production Windows CLI executables before archive and checksum generation; snapshot builds remain unsigned.
— Clear but thin operational note, no reader action.v0.16.9
0700
Stricter automatic Protobuf identificationNot checked yetimproved30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Require multi-field protocol evidence for automatic Protobuf identification while preserving configured single-field decoding.
— States the behavior change but no configuration detail.v0.16.9
Sniffnet is an open-source network monitoring tool that lets users easily track and analyse their internet traffic in real time.
Sniffnet adds live data rate display, a 20-category service taxonomy, an expanded view mode, and PCAPPCAPA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic. export path visibility.
└──▷ GET THIS VERSIONHomebrewDockergit
Homebrew
$ brew install sniffnet
# already installed? upgrade to this version:$ brew upgrade sniffnet
Docker
$ docker pull ghcr.io/gyulyvgc/sniffnet:v1.6.0
git
$ git clone --branch v1.6.0 https://github.com/GyulyVGC/sniffnet.git
# already have the repo? check out this version:$ git checkout v1.6.0
Homebrew lists this version · published under the project's GitHub account · checked 17 Nov
Sniffnet now shows current data rates in the UI so you can see live throughput at a glance. Not checked yet
Sniffnet now classifies upper-layer services into 20 categories via a service taxonomy view. Not checked yet
Sniffnet adds an expanded view setting that slims the header and hides the footer to maximize traffic data on screen. Not checked yet
Show the output file path in the Overview page when exporting a PCAP file. Not checked yet
Show more details about dropped packets in the UI. Not checked yet
Lacework FortiCNAPP is a cloud-native application protection platform that provides security monitoring, threat detection, and compliance across cloud infrastructure and workloads.
Lacework FortiCNAPP added a new exclusion filter condition for accounts in Explorer.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
'Is none of' account filter in ExplorerNot checked yetnew55how completely this was documenteddepth20/40specificity15/30actionability20/3055 / 100
Explorer queries now support an is none of condition for accounts, letting users exclude specific accounts from query results to narrow scope by exclusion rather than inclusion.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Exclude specific AWS accounts from an Explorer query so results show only accounts you care about.
📍In Explorer, open the account filter, select is none of, and enter the account IDs you want to exclude from the query results.
This repo hosts Prowler OSS (CLI and Local Server). Prowler is the world’s most widely used open-source cloud security platform that automates security and compliance across any cloud environment for Humans and AI Agents.
Prowler 5.50.0 adds a confidence-tuning key to cut secret-scanning false positives, three new AWS checks covering Bedrock guardrails, invocation job encryption, and CloudWatch data protection, seven new AI Security Framework requirements, and tightens session handling so SAML SSOSAML SSOAn authentication protocol that lets a user log in once with an identity provider and access multiple services without re-entering credentials, by passing signed XML assertions between parties. and API key tokens stay scoped to their issuing organization.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
New AWS checks for Bedrock and CloudWatch data protectionNot checked yetnew78how completely this was documenteddepth28/40specificity28/30actionability22/3078 / 100
Three new AWS checks ship in this release: bedrock_guardrail_iam_condition_enforcement_enabled verifies that IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. policies allowing bedrock:InvokeModel or bedrock:InvokeModelWithResponseStream enforce a guardrail via the bedrock:GuardrailIdentifier condition key; bedrock_model_invocation_job_output_encrypted_with_cmk verifies that S3 output from Bedrock model invocation jobs is encrypted with a customer-managed KMSKMSA managed service that creates, stores, rotates and controls access to encryption keys, usually backed by HSMs. Applications ask it to encrypt or decrypt rather than holding keys themselves. key (CMK); and cloudwatch_log_group_data_protection_policy_configured verifies that CloudWatch log groups have a data protection policy that audits and masks sensitive data such as personal information and credentials.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Run only the new Bedrock guardrail IAM enforcement check against your AWS account to verify guardrails are required on model invocation policies.
— Three named checks with mechanism, one with a runnable command5.50.0
0200
secrets_confidence tuning key for secret scanningNot checked yetnew75how completely this was documenteddepth25/40specificity22/30actionability28/3075 / 100
Tune secret-scanning noise across AWS, Cloudflare, and OpenStack providers by setting secrets_confidence to low, medium, or high in the provider config. Setting it to medium or higher suppresses the generic password, secret, and API key rules to reduce false positives.
Reduce false positives in secret scanningsecret scanningChecking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. by raising the minimum confidence threshold to medium, which silences generic password, secret, and API key rules.
yaml
secrets_confidence: medium
— Named config key with exact values and example YAML5.50.0
0300
Org-scoped sessions for SAML SSO and API keysNot checked yetbreaking70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
SAML SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. and API key sessions are now scoped to their issuing organization — POST /api/v1/tokens/switch rejects API keys and will not move such sessions to another organization.
— Names exact endpoint and behavior change, no example call shown5.50.0
thinner coverage below
0400
AI Security Framework gains manual requirementsNot checked yetnew40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
The AWS AI Security Framework gains seven Manual requirements covering Bedrock data retention, retrieval-augmented generationretrieval-augmented generationRetrieval-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. (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.) authorization, and agent governance.
— Describes scope but no commands or exact requirement names5.50.0
Plerion's latest release adds visibility into continuous scanning status via its integrations API and CLI, ships new checks that detect load balancers and AppSync GraphQL APIs exposed through AWS Global Accelerator and live accounts, and surfaces the tools used by Google ADKADKGoogle's Agent Development Kit, an open-source framework for building and orchestrating AI agents; cyber tools use it to compose multi-agent workflows with built-in tool-calling and state management. and Dialogflow CX agents.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Plerion is a cloud security platform that provides comprehensive risk management, vulnerability detection, and threat prioritization across cloud environments and workloads.
Plerion's latest release adds visibility into continuous scanning status via its integrations API and CLI, ships new checks that detect load balancers and AppSync GraphQL APIs exposed through AWS Global Accelerator and live accounts, and surfaces the tools used by Google ADKADKGoogle's Agent Development Kit, an open-source framework for building and orchestrating AI agents; cyber tools use it to compose multi-agent workflows with built-in tool-calling and state management. and Dialogflow CX agents.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Continuous scanning visibility in integrations API and CLINot checked yetnew86how completely this was documenteddepth30/40specificity28/30actionability28/3086 / 100
The list integrations API now returns continuousScanningEnabled on each integration and can be filtered with the integrationIds parameter.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The plerion integrations list CLI command gains a matching --integration-ids flag to filter to specific accounts, and its output now includes a CONTINUOUS SCANNING column.
Confirm continuous scanning is active for a specific AWS account integration without fetching all integrations.
$ plerion integrations list --integration-ids <integration-id>
Global Accelerator exposure checks for load balancersNot checked yetbreaking83how completely this was documenteddepth35/40specificity28/30actionability20/3083 / 100
New check PLERION-AWS-571 detects Application Load Balancers that are publicly accessible via an AWS Global Accelerator, tracing the attack pathattack pathA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. through the accelerator, its listener, and its endpoint group. New check PLERION-AWS-862 detects Network Load Balancers publicly accessible via an AWS Global Accelerator the same way. Load balancers that previously passed these checks can now fail, producing new findings on the next scan.
AppSync GraphQL API scanning expandedNot checked yetnew77how completely this was documenteddepth32/40specificity30/30actionability15/3077 / 100
New check PLERION-AWS-1253 detects AppSync GraphQL APIs that accept API key authorization on live AWS accounts. New check PLERION-AWS-1254 detects AppSync GraphQL APIs with introspection enabled on live AWS accounts. Existing checks PLERION-AWS-525 (public AppSync GraphQL API with no WAFWAFA reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. web 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.) and PLERION-AWS-521 (AppSync GraphQL API with field-level logging turned off) now also run against live AWS accounts, not only against templates.
Tool visibility for ADK and Dialogflow CX agentsNot checked yetNew supported platformNew vulnerability checknew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
A new Tools tab on each Google ADK agent (on Vertex AI Agent Engine and Amazon Bedrock AgentCore) lists the agent's functions, sub-agents, and built-in tools such as Google Search. A new Tools tab on each Dialogflow CX agent lists OpenAPIOpenAPIA vendor-neutral specification for describing REST APIs in a machine-readable format, maintained by the OpenAPI Initiative. Cyber tools use it to auto-generate clients, documentation, and validation from a single source of truth. operations, functions, data stores, webhooks, and playbook code actions, alongside the host and sign-in method for service-calling tools.
Load balancers behind an AWS Global Accelerator that previously passed checks PLERION-AWS-571 and PLERION-AWS-862 can now fail — expect new findings on the next scan.
Plerion adds GCP agent security, including a new workload type for Vertex AI Agent Engine with staging-bucket access via a PlerionAccess: Granted tag.
Tag a staging bucket with PlerionAccess: Granted to enable vulnerability, sensitive data, and SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. scanning for Vertex AI Agent Engine agents deployed from a staging bucket. Not checked yet
Plerion now scans Vertex AI Agent Engine agents as a new GCP workload type, covering vulnerabilities, sensitive data, and SBOM — container-image-deployed agents require no setup. Not checked yet
Grype is an open-source vulnerability scanner that detects security vulnerabilities in container images and filesystems by matching packages against known CVE databases.
Grype adds Docker Hardened Images OSVOSVOpen Source Vulnerabilities, a vulnerability database and schema maintained by Google that gives cyber tools a machine-readable, cross-ecosystem format for querying and sharing CVE-style advisories. advisory feed as a new vulnerability data source.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Docker Hardened Images OSV advisory feedNot checked yetnew35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Grype now ingests the Docker Hardened Images (DHI) OSV advisory feed as a vulnerability data source.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names the feed but no mechanism or usage detailv0.122.0
adm-controller's v1.39.0 release adds CELCELCommon Expression Language, an open-source expression language maintained by Google, used to embed lightweight, safe policy evaluation logic into tools without running a full scripting engine.-to-WasmWasmA binary instruction format for a stack-based virtual machine, maintained by the W3C, that lets code compiled from any language run at near-native speed inside a sandboxed environment across browsers and servers. policy compilation and configmap access for policy servers, extends the kwctl annotate CLI, and raises the minimum supported Kubernetes version to 1.31.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Force and inline flags for kwctl annotateNot checked yetimproved80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
The kwctl annotate command gains --force and -a flags, letting users force-overwrite existing annotations on a policy artifact or add an annotation inline without editing a separate metadata file, e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ kwctl annotate my-policy.wasm --force -a 'io.kubewarden.policy.author=alice@example.com'.
Force-overwrite existing annotations on a policy artifact, or add an annotation inline, without editing a separate metadata file.
— Exact flags and a runnable example given.v1.39.0
thinner coverage below
0200
Minimum Kubernetes version raised to 1.31Not checked yetbreaking50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
The minimum supported Kubernetes version was raised from 1.27 to 1.31.
— Before/after versions named but no migration steps.v1.39.0
0300
CEL-to-Wasm policy compilationNot checked yetnew35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Adds support for compiling and running CEL (Common Expression Language) policies to Wasm.
— States capability but no usage detail given.v1.39.0
0400
Configmap access for policy serversNot checked yetnew25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Policy servers can now access configmaps.
— Bare statement, no mechanism or scope given.v1.39.0
└──▷ BREAKING ON UPGRADE
!
Minimum supported Kubernetes version raised from 1.27 to 1.31.
Databricks is a unified data analytics platform that enables collaborative data engineering, machine learning, and analytics using Apache Spark in the cloud.
Databricks shipped a breaking change to streaming watermark behavior, GA'd the Genie Code CLI, and added governed tag propagation for classic compute, native IP address/CIDRCIDRA notation for a block of IP addresses, such as 10.0.0.0/24. The number after the slash says how many leading address bits identify the network. functions, Unity Catalog agent skill sharing via OpenSharing and Marketplace, an in-workspace support form, and daily budget thresholds for Unity Gateway.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
7 FEATURES0 OF 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Real-time watermark propagation for streaming queriesNot checked yetbreaking93how completely this was documenteddepth35/40specificity28/30actionability30/3093 / 100
New streaming queries in real-time mode now use real-time watermark propagation by default, advancing the event-time watermark within a batch so late events are filtered against the live watermark and state is evicted sooner than before.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Queries restarted from an existing checkpoint keep their original behavior, but new queries behave differently; disable the change by setting spark.databricks.streaming.realTimeMode.realTimeWatermark.enabled to false before starting a new query.
Preserve the previous watermark behavior for a new real-time streaming query that must not evict state sooner than before.
Get support form in workspaceNot checked yetnew75how completely this was documenteddepth30/40specificity20/30actionability25/3075 / 100
Open a Databricks support case directly from your workspace via Help > Get support form, which pre-fills issue details, auto-attaches diagnostic files, and suggests an AI-generated solution for review before you submit.
When you hit an error in your workspace and want to open a support case without leaving Databricks or manually gathering diagnostics
📍In the workspace, navigate to Help › Get support, fill in the issue details (the form auto-attaches diagnostic files), review the AI-generated solution suggestion, then click Submit.
Daily budget thresholds for Unity GatewayNot checked yetnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Unity Gateway budgets (including Genie) now support daily per-user thresholds in addition to or instead of monthly thresholds, with separate alert, webhook, and block-usage actions configurable per period; daily thresholds reset at 00:00 UTC.
Unity Catalog agent skills sharing via OpenSharing and MarketplaceNot checked yetNew integrationnew60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Share Unity Catalog agent skills through OpenSharing shares and Databricks Marketplace listings Beta, giving Databricks-to-Databricks recipients read-only access to each shared skill in their catalog with asynchronous provider updates.
Governed tag propagation for classic computeNot checked yetnew55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Governed tag propagation Beta now supports classic compute running Databricks Runtime 19 or above, so tags on a source propagate to derived tables and views on both classic and serverless compute.
IP functions for IP address and CIDR processingNot checked yetnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
New IP functions let workspaces query, join, and process IP addresses and CIDR blocks natively; they will soon be available by default for workspaces with the compliance security profile enabled.
New streaming queries in real-time mode now use real-time watermark propagation by default; state is evicted sooner than before. Queries restarted from an existing checkpoint keep their original behavior, but new queries will behave differently. Set spark.databricks.streaming.realTimeMode.realTimeWatermark.enabled to false before starting a new query to restore the previous behavior.
Databricks adds Beta support for querying Unity Catalog views from external Iceberg engines via the Iceberg REST catalogIceberg REST catalogA standard HTTP API specification for managing Apache Iceberg table metadata, letting any compatible engine or cyber tool discover, read, and write Iceberg tables without vendor-specific connectors..
Flashpoint empowers the world’s leading organizations with the best data for threat intelligence to protect people, places, and assets.
Flashpoint is introducing Agentic AI to Flashpoint Ignite, anchored by a new Agentic Hub environment and five purpose-built agents that automate investigation, alerting, prioritization, and reporting workflows, slated for availability in early 2027.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
7 FEATURES7 OF 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Alert Setup AgentNot checked yetnew65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Converts plain-language monitoring requirements into configured alert rules, letting teams preview results before saving.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Usable in Flashpoint Ignite by opening Agentic Hub, selecting the Alert Setup Agent, entering a request like 'Notify me when threat actors discuss exploits targeting financial sector VPNsVPNsA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection.', reviewing the previewed rules, then saving.
Use the Alert Setup Agent to quickly turn a plain-language brief into live alert rules without manually building query logic.
📍In Flashpoint Ignite, open Agentic Hub, select the Alert Setup Agent, type your monitoring requirement in plain language (e.g. 'Notify me when threat actors discuss exploits targeting financial sector VPNs'), review the previewed alert rules, then save.
PIR AgentNot checked yetnew65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Transforms plain-language intelligence requirements into structured Priority Intelligence Requirements (PIRs) for team review and approval, while surfacing emerging threats not covered by existing requirements. Usable via Agentic Hub by selecting the PIR Agent, entering requirements in plain language, reviewing/approving the drafted PIRs, and checking surfaced coverage gaps.
Use the PIR Agent to convert a team's intelligence priorities into structured PIRs and discover gaps in existing coverage before the next planning cycle.
📍In Flashpoint Ignite, open Agentic Hub, select the PIR Agent, enter your intelligence requirements in plain language, review the structured PIRs the agent drafts, approve or edit them, and check the emerging-threat gaps it surfaces that your current PIRs do not address.
Chat agent for multi-step investigationsNot checked yetnew55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
A Chat agent inside Agentic Hub turns a single natural-language question into a multi-step investigation, following leads across vulnerability, credential, fraud, and threat actor intelligence and returning source-linked findings.
Intelligence Briefing AgentNot checked yetnew55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Generates scheduled intelligence briefings tailored to executives, analysts, and technical teams, drawing on each team's selected alert rules, PIRs, investigations, assets, and credential exposure data.
Echosec Reporting AgentNot checked yetnew55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Transforms saved Echosec searches into scheduled intelligence reports containing assessments, cited findings, and recommended actions, preserving reports over time to track how threats evolve.
Alert Triage AgentNot checked yetnew50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Pre-filters low-context alert results, flags alerts that do not match monitoring intent, and labels and archives remaining alerts, keeping a log of the actions taken.
Agentic Hub environment in Flashpoint IgniteNot checked yetnew45how completely this was documenteddepth20/40specificity20/30actionability5/3045 / 100
A new environment inside Flashpoint Ignite that brings together a chat interface and purpose-built agents for multi-step threat investigations spanning cyber, vulnerability, fraud, and identity intelligence. Announced as part of Flashpoint's Agentic AI launch, available early 2027.
IsMalicious is a threat intelligence platform that checks IPs, domains, URLs, emails, phones and crypto wallets against indexed threat indicators.
isMalicious added access to third-party YARAYARAA pattern-matching language and engine, maintained by VirusTotal, that lets analysts write rules describing file or memory content so cyber tools can classify or hunt for malware at scale. and 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 collections via new API routes, with quota-exempt browsing and downloads.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
YARA and Sigma rule collections via `/rules` APINot checked yetnew83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
New /rules API routes expose third-party YARA and Sigma rules, each annotated with its source, author, and declared licence.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The yara-rules and sigma-rules collections can be browsed or polled without consuming request quota, as downloads and polling are quota-exempt; access is available on Pro, Enterprise, and feed trial plans.
— Names exact routes, collections and plan access; no usage example givensnapshot-20261117
OpenCTI is an open-source threat intelligence platform that helps organizations manage, analyze, and share cyber threat intelligence data.
OpenCTI 7.261116.0 adds asset classification fields, STIX 2.0STIX 2.0A JSON-based open standard from OASIS for representing threat intelligence objects and the relationships between them, letting cyber tools exchange indicators, TTPs, and actor data in a common machine-readable format. export via the Python client API for all SDOsSDOsStandards Development Organizations — bodies such as NIST, ISO, or IETF that publish formal technical standards; cyber tools cite them to ground detections or data formats in recognized, interoperable specifications. and SCOs, and several knowledge-management and UI refinements spanning investigation graphs, playbooks, custom fields, and config presets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Asset classification fields on system objectsNot checked yetnew65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Added category, subcategory, exposure, criticality, environment, owner, and platform fields to system objects, letting teams classify and prioritize assets in their inventory.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names all seven new fields but not where they're set7.261116.0
0200
STIX 2.0 export via Python client APINot checked yetnew60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Export STIXSTIXStructured Threat Information Expression, a standard format for describing threats, indicators and their relationships. It helps organizations exchange threat intelligence in a usable form. 2.0 objects via the Python client API for all SDOs and SCOs, including Malware.
— Names the API surface and object scope clearly7.261116.0
0300
Config-preset export/import for exclusion lists and taxonomiesNot checked yetimproved60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Export and import exclusion lists via the config-preset system alongside kill chain phases, vocabularies, status templates, and case templates.
— Names all five config-preset object types covered7.261116.0
thinner coverage below
0400
Investigation graph enrichment and entity actionsNot checked yetnew50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Trigger enrichment connectors directly from an investigation graph without leaving the investigation context, and use a new Add entities action on empty investigation graphs to start building from a blank canvas.
— Describes two UI actions but not full mechanism7.261116.0
0500
Report type manipulation in knowledge playbooksNot checked yetimproved50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Manipulate knowledge playbooks now support adding, replacing, and removing report types on entities.
— Clear capability, no exact playbook step named7.261116.0
0600
Decay rules and decimal type for custom fieldsNot checked yetnew45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
Select indicator decay rules on custom fields and add a decimal custom field type.
— Names the field capability but lacks setup detail7.261116.0
0700
Time series breakdown enabled by default on dashboardsNot checked yetimproved40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
The time series breakdown feature on dashboards is now enabled by default, with its feature flag removed.
— States before/after but no usage detail7.261116.0
0800
Platform theme import via partial importNot checked yetnew40how completely this was documenteddepth15/40specificity10/30actionability15/3040 / 100
Import platform themes via the partial import from section menus.
Transform the enterprise SOC with Torq — combining agentic SecOps and Hyperautomation to triage, investigate, and respond to threats faster than ever.
Torq introduced a 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. value dashboard quantifying automation ROI and reorganized its org and workspace settings layout.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
SOC value dashboardNot checked yetnew65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
A new dashboard shows alerts handled, cases resolved, analyst time saved, cost savings, and capacity gained.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It is found under Org Administration > Usage, letting teams review fully automated vs. analyst-handled cases and benchmark time and cost savings.
Review SOC automation ROI — see fully automated vs. analyst-handled cases and benchmark time and cost savings.
📍In Torq, go to Org Administration › Usage to view the SOC value dashboard.
Reorganized org and workspace settings layoutNot checked yetimproved20how completely this was documenteddepth10/40specificity5/30actionability5/3020 / 100
Org and workspace settings now follow a reorganized layout intended to make each setting easier to find.
Tines is an apps, agents and automations, in the complete environment for enterprise AI.
Tines shipped a single update giving admins control over AI credit allocations and limits for Tines-provisioned AI providers.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE0 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
AI credit allocations and limits in AI SettingsNot checked yetnew60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Admins can now set AI credit allocations and limits for Tines-provisioned AI providers via the AI credit allocations & limits section of the tenant's AI Settings page, allowing per-provider or per-Story caps on AI spend to prevent runaway credit consumption.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Cap AI spend per Story or provider to prevent runaway credit consumption across your tenant.
📍In the Tines console, go to AI Settings › AI credit allocations & limits and set per-provider or per-Story credit limits.
Exaforce runs AI Exabots that detect, triage, investigate and respond to threats across cloud, SaaS, identity, endpoint and code on a real-time knowledge graph.
Exaforce launched ExaU, a customizable AI agent workforce that lets practitioners build, schedule, and share their own Exabots with persistent memory, voice interaction, in-console action-taking, and autonomous email/Slack outreach, all gated by approval prompts and audit logging and reasoning over the same real-time security 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. as existing Exabots.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES8 OF 8 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
Persistent agent memory with inspectable Memory tabNot checked yetnew80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Each agent exposes a Memory tab split into three sections — Lessons, Team notes, and Only you — letting practitioners inspect what the agent has retained across sessions; agents persistently retain decisions, exceptions, and past instructions so context carries over without re-explanation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Inspect what a deployed Exabot has learned — your preferences, shared team notes, and on-the-job lessons — before trusting it with a privileged access review.
📍In the Exaforce console, open the agent, then select the Memory tab. Review the three sections: Lessons (things the agent learned on the job), Team notes (shared across all users of this agent), and Only you (your personal preferences, visible only to you).
Custom Exabot builder with scheduled rolesNot checked yetnew72how completely this was documenteddepth30/40specificity22/30actionability20/3072 / 100
Practitioners can build custom Exabots from a template or a plain-language description of the job, each with a named role such as threat hunter, access reviewer, policy officer, briefing agent, or security chief of staff, then deploy them to run on schedules inside the Exaforce platform with no new credentials or logins to provision.
Delegate a recurring CISO briefing task to an agent so it drafts the Monday status report automatically without manual prompting each week.
📍In the Exaforce console, create a new Exabot, describe its role as 'Draft the Monday morning status report for the CISO, pulling open risks and owner status from the team', set a weekly schedule, then save and deploy the agent.
In-console agent actions with approval and audit loggingNot checked yetnew70how completely this was documenteddepth35/40specificity20/30actionability15/3070 / 100
During a 1:1 chat session, agents can open Exaforce console pages, read them, and interact — click, type, scroll — using their own cursor; any data-changing action waits for an explicit Allow or Deny from the user. Every agent action is recorded in the Exaforce audit log, and agents operate within permission boundaries set by the deploying user.
Autonomous email and Slack actions with approval gatingNot checked yetnew60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
ExaU agents act autonomously over email and Slack for investigation and outreach, but any action affecting employees, systems, or communications requires approval first, and every step is recorded in the Exaforce audit log.
Agent sharing and cross-agent collaborationNot checked yetnew58how completely this was documenteddepth30/40specificity18/30actionability10/3058 / 100
Practitioners can share a read-only copy of any agent conversation with specific people or the whole organization while keeping the live chat private. Agents can also pass findings and tasks to other Exabots for multi-agent handoffs without manual coordination, and agents can be shared across the security organization so, for example, an analyst's threat-hunting agent and a CISO's briefing agent work in parallel with findings rolled into a single assessment.
Real-time knowledge graph reasoning for ExaU agentsNot checked yetnew50how completely this was documenteddepth25/40specificity20/30actionability5/3050 / 100
ExaU agents reason over the same real-time security knowledge graph already used by Exabots, covering identities, cloud activity, devices, SaaSSaaSSoftware delivered over the internet and billed by subscription, hosted and operated by the vendor so the buyer skips installation and infrastructure management. applications, and security telemetry, with no additional provisioning required.
Tenzir is a data pipeline engine for security teams that collects, transforms, enriches, and routes telemetry.
Tenzir's v7.0.0-rc.3 release lands a new deployment model with versioned packages and live rollout, an MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server and built-in assistant, alongside broad query pushdown to ClickHouse, Splunk, Defender (KQLKQLKusto Query Language, Microsoft's read-only query language for Azure Data Explorer and Microsoft Sentinel, used by cyber tools to filter, aggregate, and correlate large volumes of log and telemetry data at speed.), SentinelOne, SQL Server, MySQL, and DuckDB, new to_iceberg, Redis, and ClickHouse output operators, a reworked 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. function set (ocsf_derive, ocsf_cast, ocsf_compact, ocsf_trim), a new tenzir-test Python test harness, and configurable automatic partition-rebuild controls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES13 FEATURES2 OF 13 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
tenzir-test Python test harnessNot checked yetnew100how completely this was documenteddepth40/40specificity30/30actionability30/30100 / 100
A new tenzir-test package provides a pipeline test harness runnable with uvx tenzir-test or pinned via uv add tenzir-test (requires Python 3.13+ and Tenzir 7; pin to Tenzir 6 with uvx 'tenzir-test<3').︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ TENZIR_WORKSPACE controls which workspace is used (TENZIR_WORKSPACE=none loads package directories without one), TENZIR_BINARY selects the Tenzir binary to invoke (e.g. for prerelease testing via TENZIR_BINARY="uvx --prerelease allow tenzir"), and TENZIR_TEST_DISABLE_HOOKS=1 disables hook loading. Lifecycle hooks are registered with decorators from tenzir_test.hooks such as @hooks.startup and @hooks.test_failure, receiving a ctx with env, debug, update, coverage, tmp_dir, and project_results. Custom test runners are registered via register(runner, replace=False, aliases=None) or the @startup decorator from tenzir_test.runners, extending ExtRunner(name=..., ext=...) or Runner(name=...) with collect_tests(), using helpers from tenzir_test.run (run_subprocess, get_test_env_and_config_args, get_stdin_content, success, report_failure, print_diff, log_comparison, is_passthrough_enabled, is_update_mode) inside run(self, test, update, coverage=False). parallel-http entries in test.yaml declare parallel suites that reserve workers up to -j and start before sequential ones. CLI flags include --root <path>, -u (update mode), -j (worker count), -d (debug), and --runner-summary/--fixture-summary for per-runner and per-fixture statistics.
Run your Tenzir operator tests in CI without a system install, letting uv supply Python 3.13 automatically.
$ uvx tenzir-test --root ./mypackage
Test against a prerelease Tenzir build alongside your normal run to catch regressions before a release.
Declare sibling package dependencies so a package's tests resolve them from their current state on disk rather than a locked cache.
yaml
id: acme
name: Acme
dependencies:
- stix: ^0.0.1
— Exhaustive named flags, env vars, decorators, and runnable commands.product docs
0201
ocsf_cast, ocsf_compact, ocsf_trim become functionsNot checked yetbreaking94how completely this was documenteddepth38/40specificity28/30actionability28/3094 / 100
ocsf_cast, ocsf_compact, and ocsf_trim are now functions assigned to this (e.g. this = ocsf_cast(this, null_fill=true, encode_variants=true), ocsf = ocsf_cast(ocsf), this = ocsf_trim(this)) rather than standalone operators, decoupling schema operations from the mapper so each downstream pipeline decides which transformations to apply. ocsf_cast validates required fields and constraints and casts top-level or nested events (including lists of events, which the previous operator could not handle), supports null_fill and encode_variants, and leaves @name unchanged. ocsf_compact strips redundant enum strings from OCSF records. ocsf_trim removes optional and recommended OCSF fields, discarding their values (unlike ocsf_compact). Unlike the deprecated operators — which dropped events that could not resolve the OCSF version or class — the new functions return the event with a warning, keeping it in the pipeline for inspection, routing, or downstream enrichment.
Transform a top-level OCSF event in a pipeline, preserving the original if the class or version cannot be resolved.
$ ocsf_casted = ocsf_cast(this, null_fill=true, encode_variants=true)
this = ocsf_casted != null ? ocsf_casted : this
Cast a nested OCSF field without touching the rest of the event record.
$ ocsf = ocsf_cast(ocsf)
Validate and cast an OCSF event inline in a pipeline, preserving its name for downstream routing.
$ this = ocsf_cast(this, null_fill=true)
Strip all optional and recommended OCSF fields before transport to minimise payload size.
$ this = ocsf_trim(this)
Validate OCSF mapping completeness in package tests with null-fill to catch missing required fields before shipping events downstream.
$ this = ocsf_cast(this, null_fill=true)
— Names every function, flag, and behavior change with exact migration code.product docs
0300
New connectorsNot checked yetnew94how completely this was documenteddepth38/40specificity28/30actionability28/3094 / 100
Adds several new connectors: to_iceberg writes events to Apache IcebergApache IcebergAn open table format for large analytic datasets, maintained by the Apache Software Foundation, that gives cyber tools reliable schema evolution, time-travel queries, and atomic commits on object storage or HDFS. tables, managing file rotation, snapshot commits, and retry on concurrent updates, with rotation controlled by a size-in-bytes threshold or rotation interval, a byte budget across buffered Arrow batches, mode="append" projecting events onto an existing table's columns and serializing remaining fields into a string column such as other, and schema evolution that backfills nullable fields with nulls up to 64 MiB or one rotation interval before the open file's schema is fixed. to_redis pushes events to a Redis list (consumed in order by from_redis in another pipeline), publishes to a Redis pub/sub channel with command="publish" (e.g. export | to_redis command="publish"), and supports strings, sets, sorted sets, and hashes, while from_redis reads by popping from lists or receiving pub/sub messages. to_clickhouse sends structured pipeline events to an existing ClickHouse table, configured with table and tls options (e.g. to_clickhouse table="alerts", tls=false).
Write mixed OCSF events into an existing Iceberg table, projecting known columns and spilling extras into an other column, partitioned by day for efficient class-specific queries.
$ to_iceberg mode="append"
Buffer alert events into a Redis list so a separate consumer pipeline can process them in order.
$ to_redis "alerts"
Fan out events to all Redis pub/sub subscribers instead of queuing them in a list.
$ export | to_redis command="publish"
Ingest events from a Redis pub/sub channel for real-time pipeline processing.
$ from_redis "queue"
Forward pipeline output events into a Redis list or channel for downstream consumers.
$ to_redis "queue"
Write structured pipeline events directly into an existing ClickHouse table over a plain (non-TLS) connection.
$ to_clickhouse table="alerts", tls=false
— Detailed mechanism and config knobs, one example command. Names both operators, all supported data structures, and exact commands. Exact flags and runnable command, but little mechanism beyond that.product docs
0400
Query pushdown across connectorsNot checked yetnew94how completely this was documenteddepth36/40specificity30/30actionability28/3094 / 100
Adds query pushdown optimizations across multiple connectors: from_clickhouse gains a pushdown setting (default true in table mode) that hands where/filters, select, drop, summarize, sort, and limits to ClickHouse as native queries, including nested fields such as metadata.product.name; pushdown=false keeps drop, sort, top, rare, and filter operators in Tenzir with TQL semantics, and queries truncated by max_result_rows with result_overflow_mode='break' now fail the pipeline immediately instead of returning a partial result. The Splunk operator pushes where filters, field selection, summarize, sort, and head down as SPLSPLSplunk's proprietary query and data-manipulation language used to search, filter, and transform log data stored in a Splunk index, giving cyber tools a structured way to extract detections from large event datasets. stages, with pushdown=false disabling this. KQL pushdown for Defender now covers filter expressions such as isnull(x), tolower(x), strlen(x), and ipv4_is_in_range(x, '10.0.0.0/8'), warns when a result has exactly 100,000 rows (possible silent truncation unless a pushed-down take explains the count), and shows pushed operators under plan and the stopping reason under declined. The SentinelOne source offloads where, select/drop, summarize … by, sort, and head/tail (up to 1,600,000 rows) to PowerQuery, splitting where conjunctions at and, warns at exactly 1,600,000 rows, and surfaces SentinelOne's default 1,000-row cap and other warnings as pipeline warnings. from_microsoft_sql pushes where, select, summarize, sort, head, and tail down as T-SQL when directly chained, with pushdown=false to disable it, tenzir --dump-opt-ir showing plan/declined, NULL comparisons yielding NULL, collation-sensitive equality (e.g. name == 'alice' matching Alice), and IP addresses pushed as text like N'10.0.0.1'. from_mysql pushes where, select (including renames), summarize with group keys, and head into MySQL, splitting where at and and keeping nested fields, subnets, durations, ignore_case, and backslash strings in Tenzir. from_duckdb pushes down where, field selection (including renames and nested fields such as select ip=src_ip, host=meta.host), top-level drops, summarize with group keys, sort, and head, supporting struct fields, in, arithmetic (+ - * /), and the functions length_chars, to_lower, to_upper, trim, and abs, while other functions, subnets, optional fields such as x?, and strings with NUL bytes stay in Tenzir.
When downstream operators use TQL-specific semantics (e.g. comparing an integer column with a string) that ClickHouse would reject, opt out of pushdown to keep them running in Tenzir.
$ from_clickhouse "clickhouse.example.com" pushdown=false | sort -events | top src_ip
Inspect exactly which operators ClickHouse took over and what SQL was sent, to verify pushdown is working as expected.
$ tenzir --dump-opt-ir 'from_clickhouse table="logs.events" | where severity >= 3 | head 10'
Audit which KQL stages Tenzir pushed down to the service and why it stopped pushing — useful when results look unexpectedly large or semantics differ.
📍print the optimized pipeline to see operators listed under plan and the stopping reason under declined
Debug which pipeline stages are being offloaded to SentinelOne versus running locally in Tenzir.
$ tenzir 'from_sentinelone_data_lake "https://<tenant>.sentinelone.net", token=secret("s1"), start=2024-01-01, end=2024-01-02 | where event.type == "DNS Resolved" | head 10'
Inspect which parts of a pipeline SQL Server actually executes to confirm pushdown is working as expected.
$ tenzir --dump-opt-ir 'from_microsoft_sql table="dbo.alerts", host="db.example.com" | where severity >= 3 | head 10'
Verify which parts of a pipeline were handed off to MySQL versus staying in Tenzir, so you can tune your query for maximum pushdown.
$ tenzir --dump-opt-ir 'from_mysql table="alerts", host="db.example.com" | where severity >= 3 | head 10'
Verify which pipeline steps DuckDB takes over versus which stay in Tenzir, so you can trust the results of a pushed-down query.
$ tenzir --dump-opt-ir 'from_duckdb "events.duckdb", table="alerts" | where severity >= 3 | head 10'
— Names the exact flag, affected operators, and limit behaviour with commands. Names the flag and pushed operators but gives no runnable example. Names specific functions pushed down and a debugging technique. Named operators, exact row limits, and an example query. Exact flag, debug command, and concrete semantic caveats given. Names pushed operators and exact unsupported-predicate list. Exhaustively names supported functions and exclusions.product docs
0500
Configurable automatic partition-rebuild controlsNot checked yetnew91how completely this was documenteddepth35/40specificity28/30actionability28/3091 / 100
tenzir-ctl rebuild show lists each active automatic rebuild batch's schema, elapsed duration, input partition IDs, and combined input store size. tenzir.rebuild-merge-margin (default 0.6) sets the minimum fraction of partitions a rebuild must eliminate; tenzir.rebuild-timezone (defaults to the system time zone) sets the IANA time zone used to align rebuild time buckets; tenzir.rebuild-memory-budget caps total decoded memory shared across concurrent rebuilds (0 disables the limit; by default the node estimates it from available memory). Automatic rebuilds now group undersized partitions by maximum import time, using four-hour buckets for recent data and collapsing each local day older than 24 hours into a single bucket.
Tune automatic partition-rebuild behavior: require at least 70% of input partitions to be eliminated, align buckets to Berlin time, and cap memory at 4 GB.
Check the progress of an in-flight automatic rebuild to see which schemas are being processed and how large the input stores are.
$ tenzir-ctl rebuild show
— Names every config key with defaults and a diagnostic command.product docs
0600
ClickHouse text index for log-line searchNot checked yetnew83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
On ClickHouse 26.2+, a text index (with tokenizer = 'splitByNonAlpha') replaces the tokenbf_v1 Bloom filter, giving exact per-token row lookups instead of probabilistic ones at the cost of more index space, e.g. INDEX idx_raw_data (raw_data) TYPE text(tokenizer = 'splitByNonAlpha') GRANULARITY 1. Recommended sort keys depend on query pattern: (class_uid, time) for one class and a time range, (class_uid, device.hostname, time) for one class and a host, or (toStartOfHour(time), class_uid, time) for latest events across all classes.
Replace a Bloom filter with an exact text index on ClickHouse 26.2+ to get precise token-level row lookups for log-line search.
sql
-- ClickHouse 26.2 or later; use tokenbf_v1(32768, 3, 0) on older versions
INDEX idx_raw_data (raw_data) TYPE text(tokenizer = 'splitByNonAlpha') GRANULARITY 1
— Exact index syntax and sort-key options given.product docs
0700
ocsf_derive function derives missing OCSF fieldsNot checked yetnew82how completely this was documenteddepth32/40specificity25/30actionability25/3082 / 100
The new ocsf_derive function computes missing OCSF classification fields such as category_uid, type_uid, category_name, and type_name for top-level events (this = ocsf_derive(this)) or nested OCSF events (ocsf = ocsf_derive(ocsf)). It warns about inconsistent field pairs without modifying them and appends derived fields to the end of the record while preserving existing field positions; the ocsf_compact operator is now deprecated in favour of ocsf_derive.
Enrich a top-level OCSF event with derived classification fields such as category_uid, type_uid, category_name, and type_name in-place.
$ this = ocsf_derive(this)
Derive OCSF fields on a nested event field, preserving the rest of the record, while keeping the original intact for routing if resolution fails.
$ ocsf = ocsf_derive(ocsf)
— Full mechanism and exact commands given; single release only.product docs
thinner coverage below
0800
tenzir help command for CLI guidanceNot checked yetnew50how completely this was documenteddepth15/40specificity15/30actionability20/3050 / 100
A new tenzir help command gives contextual help in the CLI for looking up syntax or operator usage without leaving the terminal.
Look up syntax or operator usage without leaving the terminal.
version() function for runtime node versionNot checked yetnew47how completely this was documenteddepth12/40specificity15/30actionability20/3047 / 100
A new version function retrieves the running Tenzir node version at query time, e.g. version().
Check which node version is handling a pipeline at runtime.
$ version()
— Exact command given but no further mechanism described.product docs
1002
Deployment model with versioned packages and live rolloutNot checked yetbreaking32how completely this was documenteddepth15/40specificity12/30actionability5/3032 / 100
Tenzir adds a new deployment model with configuration management, versioned packages, and live rollout. Platform and deployments have been reimagined — existing deployments may require migration, and Tenzir Node v6 continues maintenance releases until the migration path is ready.
Homebrew installation with automatic PATH setupNot checked yetimproved32how completely this was documenteddepth10/40specificity12/30actionability10/3032 / 100
Tenzir now installs via Homebrew and places tenzir on the system PATH automatically.
The ocsf_cast operator is deprecated; replace operator calls with the assignment form this = ocsf_cast(this), and note that unlike the operator the function leaves this unchanged unless explicitly assigned.
!
The ocsf_cast, ocsf_compact, and ocsf_trim operators are deprecated; unlike the new function equivalents (which return the event with a warning), the operators drop events that cannot resolve the OCSF version or class.
!
The ocsf_cast, ocsf_compact, and ocsf_trim operators are deprecated and emit warnings; replace each operator call with an assignment to this using the function of the same name (e.g. this = ocsf_cast(this, null_fill=true)).
!
The deprecated operators drop events when they cannot resolve the OCSF version or class, whereas the new functions return the event with a warning — pipelines that relied on silent event dropping must handle the returned events explicitly.
!
The new ocsf_cast function leaves @name unchanged, whereas the operator may have set it; set @name explicitly if downstream pipelines depend on it.
!
Platform and deployments have been reimagined — existing deployments may require migration; Tenzir Node v6 continues maintenance releases until the migration path is ready.
Trend Vision One's AI Scanner can now repeat each attack multiple times within a single scan to measure how consistently a target responds, configurable via config file, CLI flag, or the scan wizard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Trend Vision One is a unified cybersecurity platform that integrates threat detection, response, and risk management across endpoints, networks, and cloud environments.
Trend Vision One's AI Scanner can now repeat each attack multiple times within a single scan to measure how consistently a target responds, configurable via config file, CLI flag, or the scan wizard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Repeat attack passes in AI ScannerNot checked yetnew95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Set settings.repeat_count (0–50, requires config version 2.17.0 or later) to run every attack N+1 times in a single scan, with results grouped by attack configuration across passes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The repeat count can be overridden for a single scan without editing the config file using the --repeat flag on ./tmas aiscan llm (--repeat 0 forces a single pass even if settings.repeat_count is higher), or set via the interactive scan wizard under Performance → Repeat count. The global settings.max_scan_duration_minutes limit applies across all passes, so it should be scaled up with the repeat count.
Run each attack three times in a single scan to spot inconsistent 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. responses without touching the config file.
$ ./tmas aiscan llm -c config.yaml --repeat 2
Force a single-pass scan on the fly to override a non-zero settings.repeat_count already set in the config file.
Vuls is an open-source, agentless vulnerability scanner for Linux and FreeBSD servers that detects security vulnerabilities in installed software and packages.
Vuls v0.43.0 adds a flag to skip redundant Trivy database refreshes and improves vendor attribution for Windows package scans.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Skip Trivy DB update flagNot checked yetnew83how completely this was documenteddepth25/40specificity28/30actionability30/3083 / 100
Pass -trivy-skip-db-update to vuls report or vuls tui to skip the Trivy vulnerability database update check and download, using the DB already present in the -trivy-cachedb-dir path.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Useful when managing the DB separately or scanning offline.
Run a report without re-downloading the Trivy DB when you manage the DB yourself or are working offline.
Defectdojo is an open-source Unified Vulnerability Management, DevSecOps & ASPM
└──▷ GET THIS VERSION
$ git clone --branch 3.5.200 https://github.com/DefectDojo/django-DefectDojo.git
# already have the repo? check out this version:$ git checkout 3.5.200
Fleet is an open-source platform for managing and querying device fleets, enabling security teams to monitor endpoints using osquery at scale.
Fleet adds an MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server at /api/v1/fleet/mcp, Google conditional access device-ID endpoints, AI-powered config profile generation, macOS patch deadlines, multi-VPP-token support, and AI tool software inventory.
└──▷ GET THIS VERSION
$ git clone --branch fleet-v4.95.0 https://github.com/fleetdm/fleet.git
# already have the repo? check out this version:$ git checkout fleet-v4.95.0
Access a built-in MCP server (Fleet Premium) at /api/v1/fleet/mcp, on by default and disabled with server_settings.mcp_disabled, so AI tools can connect using an API-only user token. Not checked yet
New integrationBind or remove an iOS, iPadOS, or Android host's Google device ID with the new PUT /api/v1/fleet/hosts/:id/google_device_id and DELETE /api/v1/fleet/hosts/:id/google_device_id endpoints (Fleet Premium) for Google conditional access. Not checked yet
Use new API endpoints that generate a configuration profile, or its name and description, from plain-language instructions using AI. Not checked yet
Add a Deadline option for macOS Fleet-maintained app patch policies so Fleet Desktop notifies end users 1 hour and 5 minutes before the deadline, then closes and updates the app (requires Fleet Desktop 1.5.0). Not checked yet
Configure patch deadline days and time per fleet and for Unassigned in Software > Library > Settings, the API, and GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control.; deadlines use each host's local time and default to Tuesday at 17:00. Not checked yet
+6 moreshow less
Assign multiple VPP tokens to a fleet; specify the token per App Store app via vpp_token_id in the API, or via location in GitOps. Not checked yet
Collect AI tools from fleetd's ai_tools table (Fleet Premium) — MCP servers, AI CLI tools, and AI skills appear as new software types — and filter them with the new ai_tool filter and field on the software, host software, and device software API endpoints. Not checked yet
Use $FLEET_VAR_HOST_END_USER_IDP_EXTERNAL_ID in configuration profiles, declarations, scripts, managed app configurations, certificate templates, and host name templates — it resolves to the host end user's 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.externalId. Not checked yet
New integrationStore software installers, bootstrap packages, icons, and org logos in Azure Blob StorageAzure Blob StorageMicrosoft's object-storage service for unstructured data in Azure, offering scalable, cheap storage for files of any size; cyber tools use it to store logs, artifacts, or large datasets without managing infrastructure. instead of S3 by setting the new FLEET_CLOUD_STORAGE_AZURE_FILES_* environment variables. Not checked yet
Enable the experimental agent 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. config-change notification with the new websocket.osquery_config_enabled server setting; hosts fall back to polling every 10 minutes via websocket.osquery_config_poll_interval. Not checked yet
Install a bootstrap package during manual enrollment or MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. migration with the new macos_enable_bootstrap_package_during_manual_enrollment and macos_enable_bootstrap_package_during_migration setup experience settings. Not checked yet
!Fleet no longer sends Nudge settings to fleetd for hosts on macOS 13 and older; fleetd's built-in Nudge integration is removed.
!fleetctl gitops and batch APIs now reject configuration profiles, scripts, reports, and labels whose names differ only by letter case, accents, or trailing spaces.
!fleetctl gitops on Fleet Free now returns an error for custom EST and Smallstep certificate authorities.
!Windows BitLockerBitLockerA full-disk encryption feature built into Windows, maintained by Microsoft, that protects data at rest by encrypting entire volumes; cyber tools use it to audit encryption status or recover keys from managed endpoints. key escrow now requires server.private_key.
!The Technician role can no longer run ad hoc scripts (script_contents) through the API or fleetctl run-script.
!The FLEET_ALLOW_BOOTSTRAP_PACKAGE_DURING_MIGRATION environment variable is deprecated in favor of macos_enable_bootstrap_package_during_migration.
N-able N-central's 2026.4 HF3 release focuses on session-hardening: it adds a new Inactive Assets management tab and configurable appliance token behaviour for handling inactive Agents, while permanently blocking legacy APIs and requiring device identifiers for Agent connections.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
N-able N-central is a secure endpoints and automate IT operations at scale. N-central delivers unified endpoint management with advanced RMM capabilities for complex environments.
N-able N-central's 2026.4 HF3 release focuses on session-hardening: it adds a new Inactive Assets management tab and configurable appliance token behaviour for handling inactive Agents, while permanently blocking legacy APIs and requiring device identifiers for Agent connections.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
4 FEATURES2 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
Inactive Assets tab for Agent managementNot checked yetnew70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
A new Inactive Assets tab appears under Configuration > Asset Discovery > Discovered Assets, listing Agents flagged inactive after session-hardening changes (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ from cloned VMs or re-images), with every column filterable. Administrators can use Set Active, Delete, and Export (to CSV or PDF) on inactive Agents from this tab, with all actions logged for audit.
After upgrading Agents to HF3, review which Agents were marked inactive (e.g. from cloned VMs or re-images) and restore the correct one for a device.
📍In N-central, go to Configuration › Asset Discovery › Discovered Assets, then select the Inactive Assets tab. Filter by device name, select the correct inactive Agent, and click Set Active to confirm.
Appliance token behaviour controls for inactive AgentsNot checked yetnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
New options in the Appliance token behaviour section of Administration > Mail and Network Settings > Network Setup let administrators control how N-central handles inactive Agents, such as requiring them to upgrade before reconnecting. Changes take effect immediately without a server restart.
Tune how N-central handles Agents it marks inactive — for example, requiring them to upgrade before reconnecting — without restarting the server.
📍In N-central, go to Administration › Mail and Network Settings › Network Setup and locate the Appliance token behaviour section to configure inactive Agent handling. Changes apply immediately.
Device identifier requirement for Agent connectionsNot checked yetbreaking50how completely this was documenteddepth25/40specificity20/30actionability5/3050 / 100
N-central now rejects Agent connections when both the SMBIOS ID and machine ID are missing from a device, requiring at least one identifier to communicate with the server. Agents and Probes not upgraded to 2026.4.1 HF3 are susceptible to impersonation and are not fully protected by this session-hardening change.
Legacy APIs permanently blockedNot checked yetbreaking30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
The Legacy APIs configuration option has been removed and legacy APIs are now permanently blocked; any integration relying on legacy APIs will stop working after upgrading.
The configuration option for legacy APIs has been removed and legacy APIs are now permanently blocked — any integration relying on legacy APIs will stop working after upgrading.
!
Devices without both a SMBIOS ID and a machine ID are now rejected by the N-central server — Agents on such devices will be unable to communicate until at least one identifier is present.
!
Agents and Probes not upgraded to 2026.4.1 HF3 are susceptible to impersonation and are not fully protected by the new session-hardening changes.
Iru is a device-centric platform that unifies security, IT, and compliance around devices and everything they touch.
Iru adds Android work profile certificate delegation and outbound 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. to Iru Identity.
New supported platformIru now supports delegating certificate installation and selection permissions to managed apps in the Android work profile. Not checked yet
New integrationIru Identity adds outbound SCIM support. Not checked yet
Censys is an internet intelligence platform that continuously scans and indexes internet-connected devices, services, and certificates to help security teams discover attack surfaces.
Censys adds fields and exclude_fields to asset lookup API endpoints, human-readable host reputation summaries, and updated Palo Alto Cortex and Google SecOpsSecOpsThe practice of merging security and IT operations teams so that threat detection, response, and infrastructure management share the same workflows, giving cyber tools a single pipeline from alert to remediation.SOARSOARSecurity orchestration, automation and response, coordinating incident workflows across tools. Playbooks can gather evidence, assign work or carry out approved response actions. integrations.
Filter API responses on the Get host enrichment, Get host, Get web property, and Get certificate endpoints by passing fields to include only specific fields or exclude_fields to omit specific fields. Not checked yet
Generate human-readable summaries of host reputation scores to understand a host's label more easily. Not checked yet
Censys's Palo Alto Cortex integration (v3.2.4) now adds a Determine IP score using Censys Host Reputation data (for Censys Core customers) configuration parameter that scores IPs as Malicious, Suspicious, or Good based on the Censys host reputation label. Not checked yet
The Palo Alto Cortex integration now accepts custom labels in the IP Malicious labels and IP Suspicious labels parameters beyond the listed options, and also considers service labels alongside host labels when scoring. Not checked yet
The Google SecOps SOAR integration now supports enriching hosts using the get host enrichment API. Not checked yet
Qualys CyberSecurity Asset Management continuously discovers, inventories, and assesses all IT assets across hybrid environments to eliminate security blind spots and reduce attack surface risk.
Qualys ETM Identity adds an ISPMISPMIdentity Security Posture Management: a discipline for continuously discovering, assessing, and remediating identity-related risks across users, accounts, and entitlements, giving cyber tools a unified view of identity exposure. layer correlating identity exposure with Enterprise 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., covering attack-path analysis, real-time AD monitoring, and closed-loop remediation.
New integrationNew detectionBuild a unified identity inventory across 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., 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., and Okta, covering human, machine, service, and shadow identities and their relationships. Not checked yet
Correlate identity risk with Enterprise TruRisk by combining Qualys Cloud Agent and native connector data with Identity TruRisk scoring. Not checked yet
Surface high-risk identity exposure including stale accounts, privileged identities, excessive access, and toxic combinations. Not checked yet
Understand attack pathsattack pathsA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. and trust relationships through AI-summarized attack-path analysis and a Domain Trust Map showing how identity exposure can reach critical assets. Not checked yet
Monitor identity changes in real time with AD Real-Time Monitoring to catch changes that introduce new exposure. Not checked yet
+1 moreshow less
Verify risk reduction by re-scoring with Identity TruRisk and rolling results into organizational TruRisk. Not checked yet
Automox replaced group-based exclusion window scheduling with direct per-device assignment and control, while deprecating the old group-scoped scheduling API in favor of new per-device endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Automox is a check out our full list of release notes, and stay up to date with what
Automox replaced group-based exclusion window scheduling with direct per-device assignment and control, while deprecating the old group-scoped scheduling API in favor of new per-device endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Group-scoped exclusion window endpoints deprecatedNot checked yetbreaking85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
The group-scoped scheduled window API endpoints — Create, Get, Update, Delete, List, Check Active, Check Status for Server Groups, List Next Dates by Group, and List Next Dates by Device — are deprecated and replaced by new per-device exclusion window API endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Additionally, moving a device between groups no longer adds or removes its exclusion window, since exclusion windows are now managed independently of group membership.
Review the Automox API docs for deprecation notices on group-scoped endpoints and identify the new per-device exclusion window endpoints to migrate your automation scripts.
Per-device exclusion window managementNot checked yetnew58how completely this was documenteddepth28/40specificity15/30actionability15/3058 / 100
Exclusion windows can now be assigned and managed directly on individual devices instead of through group assignments, using a new device-selection workflow in the Automox console. A new Edit Devices action lets admins add or remove devices from an exclusion window, and updated Device Details pages and tables now show which exclusion windows apply to each specific device.
Existing group-scoped scheduled window API endpoints (Create, Get, Update, Delete, List, Check Active, Check Status for Server Groups, List Next Dates by Group, List Next Dates by Device) are deprecated; migrate to the new per-device exclusion window endpoints.
!
Moving a device between groups will no longer add or remove its exclusion window — exclusion windows are now managed independently of group membership.
Discover the latest features, improvements, and updates to Ory.
Ory shipped granular outbound HTTP limits for Hydra, session risk rules for Enterprise projects, persistent SAML SPSAML SPA SAML Service Provider is a web application or service that delegates authentication to an external Identity Provider, accepting signed XML assertions as proof of identity instead of managing credentials itself. entity IDs, and custom OAuth 2.0OAuth 2.0An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms.access tokenaccess tokenA credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. prefixes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Per-feature outbound HTTP limits in HydraNot checked yetnew85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Ory Hydra v26.4.16 lets you configure outbound HTTP limits per feature using default_http_client for the global default and feature-specific http_client overrides (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ max_conns_per_host), so a single feature's outbound connections can be capped without affecting the global default.
Cap outbound HTTP connections for a specific Hydra feature without affecting the global default.
SAML SP entity ID storageNot checked yetnew65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Each 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. provider on Ory Network now stores its SP entity ID in sp_entity_id, representing the audience its IdPIdPA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. sends, shipped in v26.4.14.
Custom OAuth 2.0 access token prefixNot checked yetnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Enterprise projects on Ory Network can now set a custom prefix for issued OAuth 2OAuth 2An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs..0 access tokensaccess tokensA credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. on a per-project basis, added in v26.2.13.
Clerk is an authentication and user-management platform that provides pre-built UI components, APIs, and SDKs for adding sign-up, sign-in, and identity features to applications.
Clerk's 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 gained three new tools for listing and searching organizations, their memberships, and user-organization relationships, requiring reconnection to pick up a new permission scope.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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.
0100
Organization listing tools in MCP serverNot checked yetnew67how completely this was documenteddepth20/40specificity27/30actionability20/3067 / 100
Three new MCP tools let agents query organization data: list_organizations lists or searches organizations with filters and pagination, list_organization_memberships lists an organization's members with their roles and permissions, and list_user_organization_memberships lists the organizations a user belongs to along with their role and permissions in each.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
New organizations:read permission required for MCP toolsNot checked yetbreaking65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
The new organization MCP tools require an organizations:read permission. Existing Clerk MCP server connections may be missing this permission — users should reconnect by signing out and connecting again, and can verify the permission is present by asking the agent to run whoami.
Verify your MCP connection has the required organizations:read permission before running any organization tools.
Existing Clerk MCP server connections may be missing the new organizations:read permission required by the organization tools — reconnect by signing out and connecting again.
ConductorOne's biggest change this window is the c1i 0.10.1 CLI release, which adds new 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. commands for entitlements, apps, and automations alongside a long list of breaking changes to output format, flags, and exit codes; the platform itself also gained AI-assisted connector sync debugging, no-expiry risk acceptance for findings, and OAuth2OAuth2An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs. token parameter support for custom 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.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
ConductorOne is an identity governance platform that automates workforce access management and deploys AI agents to streamline access reviews and provisioning.
ConductorOne's biggest change this window is the c1i 0.10.1 CLI release, which adds new 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. commands for entitlements, apps, and automations alongside a long list of breaking changes to output format, flags, and exit codes; the platform itself also gained AI-assisted connector sync debugging, no-expiry risk acceptance for findings, and OAuth2OAuth2An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs. token parameter support for custom 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.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES1 OF 8 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
c1i output format and safety behavior changesNot checked yetbreaking98how completely this was documenteddepth38/40specificity30/30actionability30/3098 / 100
Commands that create, update, or delete something now print the API response without its wrapper key, and a delete prints {} — e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ .app.id becomes .id for apps create and .policy.id becomes .id for policies create. Commands that used to print a text line now print JSON. --dry-run now prints one JSON object {"dryRun":true,"requests":[...]} instead of text and shows credential values as [redacted]; setting C1I_DRY_RUN=yes or another unparseable value now causes a hard failure instead of silently sending the change. Passing --fields to a command that changes something is now an error. --error-format json now makes everything c1i writes to stderr NDJSONNDJSONA text format where each line is a self-contained JSON object, making it easy to stream, append, and parse large datasets record-by-record without loading the whole file into memory., including notices and progress, not just errors — filter with jq 'select(.error)'. apps add-owner and apps remove-owner now take the app as the first argument and the user as --user-id; the old argument order exits with an error and sends nothing. Invalid input (blank ID, ID of . or .., malformed input file, or an unparseable C1I_DRY_RUN, C1I_DEBUG, or C1I_MAX_RETRIES value) now exits 2; stuck pagination exits 6; failure reaching the docs site exits 8.
Delete an app by ID and confirm the response is a bare object rather than a wrapped one, using the new 0.10.1 output format.
$ c1i apps delete <app-id> | jq '.id'
Preview a destructive automation change safely — credentials are redacted and nothing is sent.
Custom OAuth2 parameters for MCP server token requestsNot checked yetnew55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Custom MCP servers using OAuth2 client credentialsOAuth2 client credentialsAn OAuth 2.0 grant type where a service authenticates directly with an authorization server using its own ID and secret, receiving an access token without any user involvement, enabling machine-to-machine API authorization. can now send extra token request parameters such as audience or resource, so providers like Auth0 no longer reject the token request.
New c1i CRUD commands for entitlements, apps, and automationsNot checked yetnew50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
c1i v0.10.1 adds commands to read a single task and update, delete, or manage owners and webhooks for entitlements, apps, and automations, and to filter the users list by origin.
Richer shadow app details for Google WorkspaceNot checked yetimproved50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Shadow apps discovered through Google Workspace now show each account's last OAuth event, granted scopes, and last known IP address.
Immediate entitlement linking for custom-created accountsNot checked yetimproved50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Accounts created with Custom values are now linked to their user immediately, so entitlement grants can follow right away without waiting for the next sync.
Connector error detail in automation run infoNot checked yetimproved50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
When a connector action step fails inside an automation, the Run info drawer now shows the connector's own error message instead of only 'app action failed.'
Commands that create, update, or delete something now print the API response without its wrapper key, and a delete prints {} — update any jq paths that read the wrapped id, such as .app.id to .id for apps create and .policy.id to .id for policies create.
!
Commands that used to print a text line now print JSON.
!
--dry-run now prints one JSON object {"dryRun":true,"requests":[...]} instead of text, and shows credential values as [redacted].
!
Passing --fields to a command that changes something is now an error.
!
--error-format json now makes everything c1i writes to stderr NDJSON, including notices and progress, not just errors — select errors with jq 'select(.error)'.
!
apps add-owner and apps remove-owner now take the app as the first argument and the user as --user-id; the old argument order exits with an error and sends nothing.
!
Invalid input (blank ID, ID of . or .., malformed input file, or unparseable C1I_DRY_RUN, C1I_DEBUG, or C1I_MAX_RETRIES value) now exits 2; stuck pagination exits 6; failure reaching the docs site exits 8 — several other exit codes also changed.
Auth0 introduced Embedded Authorize Beta, a new API-driven way to build in-app sign-in flows without redirecting to Universal Login.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Secure users, AI agents, and more with Auth0, a production-ready authentication and authorization platform built to help you ship faster and drive sign-ups.
Auth0 introduced Embedded Authorize Beta, a new API-driven way to build in-app sign-in flows without redirecting to Universal Login.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Embedded Authorize beta for in-app sign-inNot checked yetnew88how completely this was documenteddepth32/40specificity28/30actionability28/3088 / 100
A new POST /e/authorize endpoint lets apps build in-app sign-in flows without redirecting to Universal Login; it returns the allowed next steps for the app to render until Auth0 issues an authorization code.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ During Beta it supports email and phone one-time code sign-in, and second-factor 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. via email 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., phone OTP, 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., push, and recovery code. It has out-of-the-box compatibility with Auth0 Universal Components for web, iOS, and Android.
Kick off an in-app sign-in flow — no browser redirect required — and receive the first allowed step your UI should render.
Teleport is an open-source access platform that provides secure, identity-based access to SSH servers, Kubernetes clusters, databases, and web applications.
Teleport v18.11.10 adds replay support for Beam-related audit events, including traffic captures and session end events.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Replay support for Beam audit eventsNot checked yetnew30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Teleport can now replay Beam-related audit events, including traffic captures and session end events, through the audit log.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names the event types but no mechanism or UI path given.v18.11.10
Fhevm is a zama uses Fully Homomorphic Encryption (FHE) so institutions can issue, trade and manage confidential assets on public blockchains, fully verifiable.
fhEVM's v0.14.7 release adds access control to HCU limit enforcement and introduces relayer API key authentication to its end-to-end test suite.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Allowlist for HCULimit host contractsNot checked yetnew45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Adds an allowlist to HCULimit host contracts to control which addresses are subject to HCU limits.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names the contract but not allowlist mechanics or management.v0.14.7
0200
Relayer API key authentication in end-to-end testsNot checked yetnew25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds relayer API key authentication support to the end-to-end test suite.
— Bare statement, no key format, endpoint or config shown.v0.14.7
CISO Assistant is a one-stop-shop GRC platform for Risk Management, AppSec, Compliance & Audit, TPRM, BIA, Privacy, and Reporting. It supports 200+ global frameworks with automatic control mapping, including ISO 27001, NIST CSF, SOC 2, CIS, PCI DSS, NIS2, DORA, GDPR, HIPAA, CMMC, and more.
CISO Assistant's v4.3.3 release adds a small workflow automation capability: inline event triggers that set field defaults automatically.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Field defaults via inline workflow event triggersNot checked yetnew33how completely this was documenteddepth15/40specificity8/30actionability10/3033 / 100
Workflows can now set field defaults through inline event triggers, reducing manual configuration when a workflow step fires.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Describes mechanism but no exact config key or UI path givenv4.3.3
CloudFormation Guard is an open-source CLI tool that validates AWS CloudFormation templates against policy-as-code rules written in a custom DSL.
CloudFormation Guard 3.2.2 adds two DSL conveniences — a key accessor and optional function naming — and splits the Guard language out into a standalone library separate from the CLI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
New `key` method and function naming in Guard DSLNot checked yetnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Guard DSL rules gain a key method to access the key of a key-value pair during evaluation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Built-in Guard DSL functions can now also accept an optional function name parameter, intended to improve rule readability and error reporting.
— Names both DSL additions but no example usage shown.3.2.2
0200
Guard DSL extracted as standalone libraryNot checked yetnew25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
The Guard language is now extracted as a standalone library, available separately from the CLI.
— Only a one-line mention, no package name or usage given.3.2.2
RegScale is a continuous compliance automation platform that helps organizations manage security controls, audit evidence, and regulatory requirements in real time.
RegScale's Trust Center 1.1.0 Beta introduces per-user access roles for its customer-facing portal, a new Admin Console Home page, FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one. vulnerability reporting, and support for serving the Trust Portal from a custom domain.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
0 FEATURES4 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
Per-user RBAC roles for Trust PortalNot checked yetnew40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Trust Center adds a signed-in view of the Trust Portal for customers, partners, and internal viewers, with a single role assigned per user controlling access.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Runlayer 6.0.0 adds agent error notifications across Slack, Teams, and webhooks, starts logging refused OAuth token requests in audit trails, and tightens both the response format and validation of the policies API.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Runlayer is an MCP gateway that enforces identity-mapped permissions and detects threats across the agents and MCP servers employees use.
Runlayer 6.0.0 adds agent error notifications across Slack, Teams, and webhooks, starts logging refused OAuth token requests in audit trails, and tightens both the response format and validation of the policies API.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
4 FEATURES2 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
Policy scope fields returned as listsNot checked yetbreaking95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
GET, POST, and PUT on /api/v1/policies now return scope.servers, scope.tools, and scope.resources as lists — "*" becomes ["*"].︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Clients that compare a scope field to "*" must also accept ["*"].
— Exact endpoint, methods, fields, and migration note given6.0.0 (2026-11-16)
0202
Strict validation of policy scope keysNot checked yetbreaking72how completely this was documenteddepth30/40specificity22/30actionability20/3072 / 100
A request scope or agent account connection policy with an unknown key (e.g. a misspelled tool) now returns HTTP 422 instead of being silently ignored.
— Clear before/after behavior but endpoint not restated6.0.0 (2026-11-16)
0300
Audit logs for refused OAuth token requestsNot checked yetnew69how completely this was documenteddepth28/40specificity26/30actionability15/3069 / 100
Refused OAuth token requests now appear in audit logs with the client ID, agent or user involved, and the reason — covering wrong client secrets, failed PKCEPKCEProof Key for Code Exchange, an OAuth safeguard that binds an authorization code to the client that requested it. An intercepted code cannot be redeemed without the client's matching verifier. checks, and replayed ID-JAGs.
— Specific failure causes named but no endpoint or log location6.0.0 (2026-11-16)
0400
Agent error notifications to Slack, Teams, and webhooksNot checked yetnew67how completely this was documenteddepth28/40specificity24/30actionability15/3067 / 100
Configure agent error notifications to Slack, Microsoft Teams, or signed HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. webhook destinations, with cooldowns and recent delivery history, for agent failures and unresolved tool errors.
— Names channels and cooldown mechanism but no exact config key6.0.0 (2026-11-16)
└──▷ BREAKING ON UPGRADE
!
GET, POST, and PUT on /api/v1/policies now return scope.servers, scope.tools, and scope.resources as lists — "*" becomes ["*"]. Clients that compare a scope field to "*" must also accept ["*"].
!
A request scope or agent account connection policy with an unknown key (e.g. a misspelled tool) now returns HTTP 422 instead of being silently ignored.
Docker Sandboxes v0.54.0 adds dedicated port management subcommands and a setting to disable post-quantumpost-quantumCryptography designed to stay secure against a large quantum computer, which could break today's RSA and elliptic-curve keys. NIST standardized the first algorithms in 2024 as ML-KEM, ML-DSA and SLH-DSA. TLS key exchange for proxy-restricted networks, alongside several breaking security hardening changes affecting SSH config, clone-mode Git remotes, root home-directory resolution, and kit permission checks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Docker Sandboxes run AI coding agents in isolated environments on your machine or on Docker-managed cloud infrastructure
Docker Sandboxes v0.54.0 adds dedicated port management subcommands and a setting to disable post-quantumpost-quantumCryptography designed to stay secure against a large quantum computer, which could break today's RSA and elliptic-curve keys. NIST standardized the first algorithms in 2024 as ML-KEM, ML-DSA and SLH-DSA. TLS key exchange for proxy-restricted networks, alongside several breaking security hardening changes affecting SSH config, clone-mode Git remotes, root home-directory resolution, and kit permission checks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
13 FEATURES4 OF 13 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
Port management subcommands for sandboxesNot checked yetnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
New commands let you manage published ports on a sandbox: list them with sbx port ls <SANDBOX>, publish a port with sbx port publish <SANDBOX> <HOST_PORT>:<SANDBOX_PORT> (omit the host port to assign one automatically), and remove mappings with sbx port unpublish <SANDBOX> <SANDBOX_PORT> or <HOST_PORT>:<SANDBOX_PORT> to remove a single mapping.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Publish a specific host-to-sandbox port mapping on a running sandbox, e.g. to expose a web server on port 8080.
$ sbx port publish my-sandbox 8080:8080
— Exact subcommand syntax with runnable example givenv0.54.0
0200
Disable post-quantum TLS key exchangeNot checked yetnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
For firewalls or TLS-inspecting proxies that can't handle post-quantum key exchangepost-quantum key exchangeA cryptographic handshake algorithm designed to resist attacks from quantum computers, using math problems like lattices that quantum algorithms cannot efficiently solve, letting tools stay secure against future quantum-capable adversaries., it can be disabled by setting tls.postQuantumKeyExchange to false via sbx settings set tls.postQuantumKeyExchange false, then restarting the daemon with sbx daemon restart.
Turn off post-quantum key exchange when a TLS-inspecting proxy is dropping HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. connections, then restart the daemon to apply the change.
$ sbx settings set tls.postQuantumKeyExchange false
sbx daemon restart
— Named config key and exact command sequence with examplev0.54.0
0301
Clone-mode Git remote transport hardenedNot checked yetbreaking80how completely this was documenteddepth35/40specificity25/30actionability20/3080 / 100
Clone-mode sandbox-<name> Git remote fetches now use the daemon socket instead of an unauthenticated localhost TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. port, requiring the sandbox to be running to fetch; the default transport also now rejects publishing sandbox TCP port 9418. TCP compatibility for Git clients whose remotes ignore the uploadpack setting can be restored with sbx settings set clone.legacyTcpRemote true, which exposes the repository to other local accounts.
— Mechanism, risk, and exact opt-out setting all namedv0.54.0
0402
SSH config regeneration required after upgradeNot checked yetbreaking65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Generated SSH configuration now prevents crafted host or user names from executing shell commands with older OpenSSH clients; existing configuration must be regenerated by rerunning sbx setup ssh (local) and sbx --cloud setup ssh (cloud) after upgrading.
— Security fix explained with exact remediation commandsv0.54.0
0503
Root home directory resolution changed on UnixNot checked yetbreaking65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Running sbx as root on Unix now uses root's registered home directory; inherited overrides HOME, XDG_CONFIG_HOME, XDG_STATE_HOME, XDG_CACHE_HOME, SANDBOXES_STORAGE_ROOT, and DOCKER_SANDBOXES_API are ignored. Any older root daemon using custom storage must be stopped before upgrading.
— All affected env vars named plus upgrade precautionv0.54.0
thinner coverage below
0600
Stable per-check IDs in diagnostics outputNot checked yetnew55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
sbx diagnose --format json and --format yaml now include a stable id per check, suitable for matching checks in scripts.
— Command and formats named but no worked examplev0.54.0
0700
MCP mode visibility in sandbox inspectNot checked yetimproved50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
sbx inspect now shows a local sandbox's static or dynamic 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. mode and its connected servers.
— Describes what's shown, clear command to checkv0.54.0
0800
Clearer cloud API proxy error messagesNot checked yetimproved50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Cloud API connection failures behind HTTP proxies now report that the API is unreachable and suggest running sbx --cloud diagnose, instead of returning a generic 500 error.
— Before/after behavior and a follow-up command namedv0.54.0
0900
Network policy check names matching ruleNot checked yetimproved45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
sbx policy check network now names which network policy rule allowed a target, instead of just confirming access.
— Command named but behavior described brieflyv0.54.0
1000
Working directory for scheduled sandbox runsNot checked yetnew45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
Scheduled sandboxes can now run in a specific working directory using --workdir or -w on scheduled runs.
— Flag named but no example or further mechanismv0.54.0
1100
`sbx skills delete` aliasNot checked yetnew40how completely this was documenteddepth10/40specificity15/30actionability15/3040 / 100
Adds the sbx skills delete alias for removing installed skills.
— Single named command with no further detailv0.54.0
1200
Architecture-aware cloud sandbox creationNot checked yetimproved40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Cloud sandbox creation now honors the requested architecture when combining published kits with locally built mixins.
— Behavior change stated without a command or examplev0.54.0
1304
Kit permission re-confirmation from stronger digestsNot checked yetbreaking35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Existing kit permissions may require confirmation again after upgrading because permission checks now use stronger service digests.
— States impact but not the mechanism or digest typev0.54.0
└──▷ BREAKING ON UPGRADE
!
Rerun sbx setup ssh (local) and sbx --cloud setup ssh (cloud) after upgrading — generated SSH configuration now prevents crafted host or user names from executing shell commands with older OpenSSH clients, and existing configuration must be regenerated.
!
On Unix, running sbx as root now uses root's registered home directory; inherited overrides HOME, XDG_CONFIG_HOME, XDG_STATE_HOME, XDG_CACHE_HOME, SANDBOXES_STORAGE_ROOT, and DOCKER_SANDBOXES_API are ignored. Stop any older root daemon using custom storage before upgrading.
!
Clone-mode sandbox-<name> Git remote fetches now use the daemon socket instead of an unauthenticated localhost TCP port; the sandbox must be running to fetch. Use sbx settings set clone.legacyTcpRemote true to restore TCP access (exposes the repository to other local accounts). Clone-mode sandboxes using the default transport now reject publishing sandbox TCP port 9418.
!
Existing kit permissions may require confirmation again after upgrading because permission checks now use stronger service digests.
ongrid's AIOpsAIOpsA practice that applies machine learning and data analytics to IT operations data—logs, metrics, events—so that cyber tools can automate anomaly detection, correlate alerts, and reduce noise at scale. engine gained traceable evidence in root-cause analysis reports, finer control over model reasoning and tool compatibility, the ability to approve policy-denied remediation commands, and support for persisting large tool results.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Approval for policy-denied host commandsNot checked yetnew35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Operators can now approve policy-denied host commands, unblocking remediation actions that were previously rejected by policy.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Clear capability but no UI path or command namedv0.21.0
0200
Model reasoning-level and tool compatibility controlNot checked yetnew33how completely this was documenteddepth15/40specificity8/30actionability10/3033 / 100
The AIOps engine now supports model reasoning levels and tool compatibility selection, letting operators tune which model capabilities are used.
— Names a control but no flag or config key givenv0.21.0
0300
Traceable evidence in RCA reportsNot checked yetnew28how completely this was documenteddepth15/40specificity8/30actionability5/3028 / 100
The AIOps engine now adds traceable evidence to root-cause analysis reports, grounding each conclusion in observed data.
— Describes benefit but no mechanism or format namedv0.21.0
0400
Persistence of large tool resultsNot checked yetimproved28how completely this was documenteddepth15/40specificity8/30actionability5/3028 / 100
The AIOps engine now persists and analyzes large tool results that previously exceeded in-memory limits.
— States behaviour change but no limit or storage detailv0.21.0
ToolHive's v0.66.0 release hardens Docker workload isolation with an opt-in read-only root filesystem, strengthens ID-JAG token issuance with actor validation, and adds audit and telemetry refinements.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
ID-JAG minting from exchange grants with actor validationNot checked yetimproved45how completely this was documenteddepth25/40specificity15/30actionability5/3045 / 100
ToolHive now mints ID-JAGs (identity JSON Assertion Grants) from exchange grants, names the acting agent inside the issued token, and validates the actor before issuance.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Explains mechanism but no concrete API or command shownv0.66.0
0200
Read-only root filesystem for Docker workloadsNot checked yetnew40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Workloads running on Docker can now opt in to a read-only root filesystem, hardening container isolation.
— Names the capability but no flag or config key givenv0.66.0
0300
Audit event subjects for vMCP embeddersNot checked yetimproved30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
vMCP embedders can now add audit event subjects to emitted audit records.
— States the capability only, no schema or API detailv0.66.0
0400
Server profile in anonymous usage metricsNot checked yetimproved15how completely this was documenteddepth10/40specificity5/30actionability0/3015 / 100
Anonymous usage metrics now include the server profile.
H5i is an Axum-based Rust web framework with Lean 4-verifiable application kernels that run on servers, bare-metal embedded devices, and GPUs, plus integrated security testing.
h5i's v0.5.6 release adds three new CLI plugins for security testing: browser automation behind a policy-checking proxy, a websec workbench for replaying captured HTTP requests, and a recon ledger for crawling attack surfacesattack surfacesThe 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..︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Browser automation with policy-checking proxyNot checked yetnew90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Run browser automation sessions backed by a policy-checking proxy using h5i browser open, h5i browser snapshot, h5i browser requests, and h5i browser audit to inspect what the browser requested and what the proxy refused.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Audit a live target's HTTP traffic during a browser session, then inspect every request the browser made and what was refused.
— Four named subcommands plus a runnable multi-step examplev0.5.6
0200
Recon ledger plugin for attack surface discoveryNot checked yetnew85how completely this was documenteddepth25/40specificity30/30actionability30/3085 / 100
Install the recon ledger plugin with h5i plugin install recon --from ./h5i-recon and discover attack surfaces by crawling a target with h5i recon crawl --max-requests, capping the number of requests made.
Crawl a target to map its 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., capping the run at 200 requests.
— Install and crawl commands with flag plus a runnable examplev0.5.6
0300
Websec workbench plugin for replaying requestsNot checked yetnew70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Install the websec workbench plugin with h5i plugin install websec --from ./h5i-websec to replay and modify captured HTTP requests via h5i websec replay.
— Exact install and replay commands given, no usage examplev0.5.6
Minimal is a secure, declarative runtimes for Claude Code, Gemini, Codex, Pi and more, so you can run multiple agents safely on your stack from a verified software supply chain.
Minimal shipped a new min secret command for managing secrets, extended min box with listing, JSON/YAML output and a tamper-evident audit trail, and added configurable detach keys plus a daily release-check notice.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Box listing and show with JSON/YAML outputNot checked yetnew75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
List and show box types with min boxlist and show commands, supporting -o json or -o yaml output via min box show -o json|yaml — useful for exporting a box's full spec for CI ingestion.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Export the full spec for a box as JSON for downstream processing or CI ingestion.
Onyx Security is a control plane that discovers, monitors and governs enterprise AI agents inline across browsers, coding assistants, cloud workloads and MCP servers.
Onyx adds a Glean integration enabling agent discovery, automated governance reviews, intent-aware runtime policy enforcement, and browser-level Glean Assistant controls.
Connect Onyx to Glean via the Glean API for read-only discovery of agent inventory, ownership, permissions, tools, and data access. Not checked yet
Use Glean's runtime hooks to evaluate prompts, responses, and proposed tool executions against enterprise AI policies at supported checkpoints, blocking violations before execution. Not checked yet
Identify and block out-of-policy employee use of Glean Assistants in the browser through Onyx runtime controls. Not checked yet
New integrationAccess the Onyx Secure AI Control Plane on the Glean Connector hub to manage Glean agents alongside third-party copilots, custom agents, and cloud AI services in a single inventory. Not checked yet
Cloudflare is a connectivity cloud platform delivering internet security, performance, and developer infrastructure services.
Cloudflare WAFWAFA reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. now supports payload logging for custom rules, letting Enterprise accounts capture matched request payloads under public-key encryption.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ 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
Payload logging for WAF custom rulesNot checked yetnew67how completely this was documenteddepth30/40specificity22/30actionability15/3067 / 100
Enterprise accounts can enable payload logging for WAF custom rules, encrypting matched payloads with an account-level public key or a zone-level public key, where the zone-level key takes precedence over the account-level one.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Arcade's latest release focuses on access control and integration hardening: project API keys gain scoping and deactivation, OAuth connections get named profiles, remote 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 get Client ID Metadata DocumentClient ID Metadata DocumentAn OAuth 2.0 mechanism letting a client publish its own metadata (redirect URIs, grant types, contacts) at a well-known URL so authorization servers can fetch and verify it without manual registration. authorization, and five toolkit integrations (Google Drive, Google Docs, Gmail, Linear, GitHub) pick up new parameters and filtering — alongside breaking changes to deployment and the runner image.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Arcade is the actions runtime for enterprise AI agents â one control point to enforce, execute, and govern every action, every time.
Arcade's latest release focuses on access control and integration hardening: project API keys gain scoping and deactivation, OAuth connections get named profiles, remote 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 get Client ID Metadata DocumentClient ID Metadata DocumentAn OAuth 2.0 mechanism letting a client publish its own metadata (redirect URIs, grant types, contacts) at a well-known URL so authorization servers can fetch and verify it without manual registration. authorization, and five toolkit integrations (Google Drive, Google Docs, Gmail, Linear, GitHub) pick up new parameters and filtering — alongside breaking changes to deployment and the runner image.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
13 FEATURES4 OF 13 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
Toolkit integration upgrades across Google, Linear, GitHubNot checked yetimproved80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Google Drive's query parameter is now optional and searches every shared drive by default, flags incomplete results, and reports last editor and sharer.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Google Docs' EditDocument can now return only named tabs instead of the whole document. Gmail's GetThread takes a flag to leave out each message's HTML body. Linear adds server-side filtering for ListInitiatives and ListProjectComments now returns discussion comments too. GitHub's DownloadFile on a directory now explains and lists contents, with GraphQL tools now working on GitHub Enterprise Server.
Custom APT packages for deployed serversNot checked yetnew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Deployed servers can declare apt_packages in .arcade/deploy.json to install Debian packages at build time, so additional system packages are available on first pod start without recompiling.
Declare additional Debian packages your deployed server needs at build time, so they are available on first pod start without recompiling.
Pending deployment cap for self-hosted installsNot checked yetnew80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Self-hosted installs can cap pending deployments per project with deployments.max_pending_per_project in engine.extraConfig, preventing a CI pipeline or runaway automation from flooding a project's deployment queue.
Prevent a CI pipeline or runaway automation from flooding a project's deployment queue by capping how many deployments can be pending at once.
Scoped and deactivatable project API keysNot checked yetnew60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Admins creating a project API key now choose its scope — call tools, manage the project, or both — instead of always granting full access. Admins can also deactivate a project API key immediately without deleting it, and reactivate it without issuing a new secret.
Nullable API key/gateway columns in tool execution historyNot checked yetbreaking55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
The tool-execution-history API key/gateway columns are now nullable and required — existing integrations must handle null values.
Client ID Metadata Document auth for remote MCPNot checked yetnew50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Authorization requests and responses now record an expected issuer, supporting Client ID Metadata Document authorization for remote MCP servers.
Registry tools for MCP catalog browsingNot checked yetnew45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
A gateway can expose two Registry tools letting a signed-in agent browse the full project MCP catalog, behind a per-gateway setting that is off by default.
New error kind for tool refusalsNot checked yetimproved40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
Tool execution results now report a new error kind for deliberate tool refusals (bad input or business rules); the prior fatal-error kind is now reserved for unhandled crashes.
The tool-execution-history API key/gateway columns are now nullable and required — existing integrations must handle null values.
!
The old account-based gateway binding is dropped; any gateway still using it will be blocked until migrated (see Upgrade notes).
!
The porter deployment provider is removed (see Upgrade notes).
!
The runner image's preinstalled unixODBC, libaio, GSSAPI, and Oracle Instant Client compatibility link are removed from the deployed-server runner image (see Upgrade notes).
Was this useful?
No tools match. Clear the filter and try again.
my-toolchain — 0 tools
Know when your tools change
Add what you run. We’ll show what each tool shipped since your version, and which breaking changes to check first.
Copy this, send it to your AI assistant, then come back with its reply.
Nothing is sent from here. You paste the reply in the next step.
1 Copy
2 Paste
3 Confirm
Paste the reply
One tool per line is best. Versions are optional, and any format works. Names we don’t track are sent to us, without versions, so we can consider adding them.