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

The Cyber Toolchain — issue 037, August 6, 2026

THE CYBER TOOLCHAIN NO. 037
Tail
THE DAILY RELEASE FIREHOSE
PUBLISHED AUGUST 6, 2026 · EVERY DAY
EDITIONS tail grep head ls diff uniq

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

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

VIEW
ISSUE VIEW scroll
ISSUE WIDTH reading width
Do you prefer scroll?
ADDITIONAL FILTERS
$ tct list   # 41 tools matched
Offensive Security
◆  Exploitation & C2

Horizon3 NodeZero

Sources Release page → 1 release · seen 2026-08-06 Notes

Horizon3 NodeZero is an autonomous security tool that continuously identifies and exploits vulnerabilities in networks to assess organizational risk.

Horizon3 NodeZero's biggest addition this window is Tripwires — automatically deployed decoy files and credentials that flag intruder interaction during pentests — alongside expanded Rapid Response exploit coverage, 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. detection improvements, and MCP ServerMCP ServerA process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface., MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs., and Vulnerability Management Hub upgrades.

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

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

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

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

01 00
NodeZero Tripwires decoy files and credentials new 75

NodeZero automatically deploys decoy files and credentials — up to two tripwires per asset — along critical 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. during autonomous pentests, placed at points where NodeZero has gained access via a Remote Access Tool (RAT) or direct file write; any interaction triggers an immediate alert. Tripwires are included in NodeZero Elite and Pro license packages and available as an add-on for other tiers. A subsequent update introduced more-flexible Tripwire deployment that reduces reliance on the RAT, cutting Endpoint Detection and Response (EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device.) noise during deployments.

— Names mechanism, per-asset limit, license tiers; no config surface given. snapshot-20260806
02 00
Expanded Rapid Response exploit coverage new 65

Rapid Response exploitability testing now covers Cisco Unified Communications Manager, SonicWall SMA1000, Adobe ColdFusion, and ManageEngine ADAudit Plus, viewable via Rapid Response Details pages showing Asset Breakdown, CVE or H3 IDs, References, and a Relevant Assets table with Action Items and Fix Actions guidance, plus a Take Action menu to run tests, add notes, or create tickets.

— Names covered products and UI actions, no API detail. snapshot-20260806
thinner coverage below
03 00
Tripwires dashboard in NodeZero Portal new 45

A Tripwires dashboard in the NodeZero Portal, opened from the portal's top navigation, gives visibility into deployed tripwires across the environment.

— Names exact UI path but no further behaviour detail. product docs
04 00
Vulnerability Management Hub port info and sorting improved 40

The Vulnerability Management Hub adds port information and improved sorting for completed pentests.

— Names the hub and new fields but no navigation steps. snapshot-20260806
05 00
Active Directory group and DCSync detection improvements improved 35

Active Directory enhancements improve group enumeration, 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. posture assessment, and 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. detection.

— Names three capabilities but no mechanism or scope detail. snapshot-20260806
06 00
MSP contract, asset, and co-branding controls improved 35

MSP enhancements strengthen contract enforcement, asset allocation, and co-branding controls for managed service providermanaged service providerA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. environments.

— Names three MSP controls without configuration or UI detail. snapshot-20260806
07 00
MCP Server authentication and toolset updates improved 30

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 updates deliver stronger authentication, a streamlined toolset, and expanded documentation for safer integrations.

— Vague on what auth or toolset changes actually entail. snapshot-20260806
Was this useful?
◆  Reconnaissance & OSINT

ProjectDiscovery subfinder

Sources Release notes → 1 release · 2026-08-05 Notes

Fast passive subdomain enumeration tool.

Subfinder v2.15.0 adds a new passive discovery source and machine-readable output for listing supported sources.

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

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

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

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

01 00
Machine-readable source listing via -ls -oJ new 75

Running subfinder -ls -oJ outputs the available passive sources in JSONLJSONLA text format where each line is a self-contained, valid JSON object, making it easy to stream, append, and process large datasets line by line without parsing a full JSON array into memory. format, useful for feeding into automation or auditing which sources subfinder supports.

Get a machine-readable list of all available passive sources to feed into automation or audit which sources subfinder supports.
$ subfinder -ls -oJ
— Exact flag and output format given, with runnable example. v2.15.0
02 00
New shodanct passive source new 75

Adds shodanct as a new passive subdomain discovery source, leveraging Shodan's certificate transparency data; can be invoked with subfinder -d example.com -s shodanct.

Run subdomain enumeration using only the new shodanct source to leverage Shodan's certificate transparency data.
$ subfinder -d example.com -s shodanct
— Named source and exact command shown, mechanism briefly noted. v2.15.0
Was this useful?
Application Security
◆  SAST / SCA / Code Security

Snyk

Sources Blog / feed →Product docs → 1 release · 2026-08-06 Docs Blog

Snyk is a developer security platform that finds and fixes vulnerabilities in open source dependencies and container images.

Snyk added 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. v2 authentication support for Web targets in Snyk API & Web, allowing authenticated DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces. scans of Windows-protected internal applications.

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

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

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

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

01 01
NTLM v2 authentication for Web targets new 83

Snyk API & Web now supports NTLM v2 authentication for Web targets, configurable via Target Settings > Authentication tab in the Basic Auth / NTLM module, with fields for username, password, domain, and workstation. This enables authenticated scans of Windows-protected internal applications without separate tooling.

Enable authenticated scanning of a Windows NTLM-protected internal application that was previously unscanned.
📍In the Snyk web UI, go to Target Settings › Authentication tab, locate the Basic Auth / NTLM module, select the NTLM option, and enter the username, password, domain, and workstation credentials for the target application.
— Names exact UI path and auth fields but no API/flag. 2026-08-06-a1520ef7
Was this useful?

Portkey

Sources Release page → 1 release · seen 2026-08-06 Notes

Portkey is an AI gateway providing observability, security, and reliability features for LLM applications with multi-model support.

Portkey's March 2026 release adds vault-backed Secret References, weekly and endpoint-scoped rate limits, cross-cloud GCS logging via GCP Workload Identity Federation, new Zscaler and Akto guardrail integrations, and expanded model/provider support including DeepInfra, DeepSeek, Bedrock, Vertex AI, and Azure AI Foundry rerank.

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

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

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

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

01 01
Weekly rate-limit budgets new 45

Adds weekly (rpw) budget and usage windows so rate-limit caps align with weekly spend planning, not only per-minute or monthly aggregates.

— Names the `rpw` unit but no config path or command. snapshot-20260806
02 00
Analytics for archived workspaces and slug filters improved 45

Enables analytics for archived workspaces and accepts workspace slugs (alongside IDs) in saved filters, keeping reporting stable as workspaces are wound down or renamed.

— Describes behaviour but no filter syntax or API path. snapshot-20260806
03 02
Removal of forwarded header to prevent loops breaking 45

The gateway no longer forwards the x-portkey-forward-headxers header, preventing header-forwarding loops; any setup relying on that header being passed through will stop working.

— Names the removed header but no migration path given. snapshot-20260806
└──▷ BREAKING ON UPGRADE
  • !
    The gateway no longer forwards the x-portkey-forward-headxers header, preventing header-forwarding loops — any setup relying on that header being passed through will stop working.
Was this useful?

Openlayer

Sources Release page → 1 release · seen 2026-08-06 Notes

Openlayer is a platform for monitoring and evaluating large language model performance, quality, and safety in production.

Openlayer shipped a Gantt-style trace timeline view that visualizes span timing and nesting to help spot slow steps and unexpected branches.

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

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

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

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

01 00
Gantt-style trace timeline view new 45

A new trace timeline view lines up every span by start time, duration, and nesting so slow steps and unexpected branches are immediately visible at a glance.

— Describes behavior but no navigation path or config named. snapshot-20260806
└──▷ ALSO FROM THESE RELEASES
Was this useful?

Veracode

Sources Blog / feed → 2 releases · 2026-08-05 → 2026-08-06 Blog

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

Veracode expanded its 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. module with real-time scan notifications, AI-powered risk prioritization, scan scheduling, and a new DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces. Candidate export path into DAST Essentials, while its training platform shipped Get Lesson Progress API enhancements, OWASP Top 10:2025OWASP Top 10:2025A ranked list of the ten most critical web application risk categories, maintained by the Open Worldwide Application Security Project, used by cyber tools to prioritize detection, testing, and remediation coverage. content, and deeper Security Labs integration into the Veracode Platform via 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..

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

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

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

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

01 00
Get Lesson Progress API enhancements improved 95

Adds updatedAfter parameter to support incremental loads of lesson progress data and excludeNotStarted=true to filter out lessons that have not been started. The response now also includes stack and updated_on fields, and surfaces Not Started status when both start_time and end_time are null.

— Names exact params, fields and status logic. Training updates (2026-08-06)
02 01
Security Labs default URL change breaking 80

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

— Exact old/new URLs plus migration note given. Training updates (2026-08-06)
03 02
DAST Candidate export to DAST Essentials new 70

Enables export of web applications from EASM directly into DAST Essentials by marking assets as DAST Candidates.

— Names target product and exact marking mechanism. EASM updates (2026-08-05)
04 03
OWASP Top 10:2025 Security Labs lessons new 60

New Security Labs lessons cover all ten OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Top 10:2025 categories, including two new categories: A03 (Software Supply Chain Failures) and A10 (Mishandling of Exceptional Conditions).

— Names categories but only prose description. Training updates (2026-08-06)
05 00
OWASP Top 10:2025 eLearning courses new 60

New eLearning courses aligned to OWASP Top 10:2025 are available in English, Spanish, French, Portuguese, and Chinese, covering Software Security Awareness and secure coding for .NET, Java, JavaScript, PHP, and Python.

— Lists languages and topics, no further mechanism. Training updates (2026-08-06)
06 00
eLearning skills assessment quizzes new 60

New assessment quiz courses (skills assessments) are available in English, Portuguese, and Spanish for Static Analysis, Dynamic Analysis, SCASCASoftware composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. agent-based scanning, IDE scanning, and user/application setup.

— Named topics and languages, no navigation detail. Training updates (2026-08-06)
07 00
CWE tagging on Security Labs lessons new 60

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

— Explains search and display behavior for CWEs. Training updates (2026-08-06)
08 00
OWASP API Security Top 10 upgraded to 2023 improved 60

Upgrades OWASP API Security Top 10 coverage in Security Labs from the 2019 list to the 2023 list, adding lessons for three new categories.

— Named version change and category count. Training updates (2026-08-06)
thinner coverage below
09 04
Security Labs terminology rename breaking 55

In Security Labs, Teams are now called Organizations and Roles are now called Teams; any documentation, automation, or integrations referencing these terms must be updated.

— Exact term mapping given, no further mechanism. Training updates (2026-08-06)
10 05
Security Labs user/team management via IAM new 55

Integrates Security Labs user and team management into the Veracode Platform via Veracode IAM, accessible under Security Training after migration.

— Names IAM and Security Training location, little else. Training updates (2026-08-06)
11 06
33 deprecated eLearning courses removed deprecated 55

33 deprecated eLearning courses (OWASP 2017, OWASP Top 10 2021, and language-specific Secure Coding courses for .NET, Java, JavaScript, PHP, and Python) are no longer available as of June 10, 2026. OWASP Top 10 (2021) Security Labs lessons are also no longer available as of that date.

— Specific count and date, no replacement steps. Training updates (2026-08-06)
12 00
In-app guidance for campaigns and reporting new 50

New in-app guidance in Security Labs for creating campaigns and using reporting; requires third-party cookies enabled in Chrome, Edge, Firefox, Safari, and Internet Explorer 9+.

— Lists browser requirement, no exact UI path. Training updates (2026-08-06)
13 00
Dashboard Heatmap, World map, Things widgets new 50

Adds Dashboard Heatmap, World map, and Things widgets with filterable data views and a shortcut to create reports.

— Named widgets, limited on filter/report detail. EASM updates (2026-08-05)
14 00
Container Security in Docker lesson series new 48

New Security Labs lesson series on Container Security in Docker, covering capabilities, users, virtualization, networking, resources, and inventory across dozens of hands-on lessons.

— Topic list given, no lesson count or path. Training updates (2026-08-06)
15 00
Real-time in-app scan notifications new 45

Adds real-time in-app notifications when scans complete, fail, or are cancelled.

— States trigger events, no further detail. EASM updates (2026-08-05)
16 00
Findings view with prioritization workflows new 45

Adds a Findings view with improved prioritization workflows and expanded reporting capabilities.

— Names the view, but workflow details are thin. EASM updates (2026-08-05)
17 00
Business units management new 45

Adds business units management: create, assign, and manage business units with domain associations.

— Names CRUD actions and domain association. EASM updates (2026-08-05)
18 00
Deep Discovery work queue improvements improved 43

Enhances Deep Discovery with an improved work queue, selection toggles, and clearer result indicators.

— Named UI elements, no workflow specifics. EASM updates (2026-08-05)
19 00
Security Labs team search for admins new 35

Adds Security Labs team search capability for Security Labs administrators and managers.

— Brief description, no mechanism or scope. Training updates (2026-08-06)
20 00
Scan scheduling for orchestration new 33

Adds scan scheduling to streamline scan orchestration across projects.

— Names capability but no config or frequency detail. EASM updates (2026-08-05)
21 00
Issues capability for remediation new 33

Adds Issues capability to streamline remediation efforts and improve cyber hygiene focus.

— Names the feature, mechanism unspecified. EASM updates (2026-08-05)
22 07
Security Labs community edition deprecated deprecated 30

The Security Labs community edition will be deprecated on July 31, 2026.

— Date given but no migration guidance. Training updates (2026-08-06)
23 00
Code syntax highlighting in lessons improved 30

Adds code syntax highlighting to Security Labs lessons, tailored per programming language.

— Minimal description of a UI-only change. Training updates (2026-08-06)
24 00
Multi-project visibility for risk management new 30

Adds multi-project visibility for centralized risk management across all projects.

— Generic description, no mechanism named. EASM updates (2026-08-05)
25 00
AI-powered intelligence for risk prioritization new 20

Adds AI-powered intelligence for accelerated risk prioritization.

— Vague marketing-level description of mechanism. EASM updates (2026-08-05)
└──▷ BREAKING ON UPGRADE
  • !
    The default Security Labs URL has changed from https://securitylabs.veracode.com/ to https://securitylabs.veracode.com/security-labs/; customers using SSO with a stand-alone account must update their configured URL.
  • !
    In Security Labs, Teams are now called Organizations and Roles are now called Teams; any documentation, automation, or integrations referencing these terms must be updated.
  • !
    The Security Labs community edition will be deprecated on July 31, 2026.
  • !
    33 deprecated eLearning courses (OWASP 2017, OWASP Top 10 2021, and language-specific Secure Coding courses for .NET, Java, JavaScript, PHP, and Python) are no longer available as of June 10, 2026.
  • !
    OWASP Top 10 (2021) Security Labs lessons are no longer available as of June 10, 2026.
Was this useful?
◆  Web Application Security

ProjectDiscovery Katana

Sources Release notes →Source code → 1 release · 2026-08-05 Notes Code

A next-generation crawling and spidering framework.

Katana v1.7.0 expands its knowledge base with secrets and endpoint extractors, adds content similarity deduplication to cut near-duplicate pages, and opens up headless engine callbacks with a Context field for external lifecycle control.

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

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

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

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

01 00
Content similarity deduplication of crawled pages new 100

The -pcs / -page-content-similar flag (also aliased as -sdd / -similarity-deduplication) enables Layer-2 content similarity filtering to deduplicate near-identical pages during crawls. Mode is set via -pcsm / -page-content-similar-mode (simhash, tfidf, or bm25; default simhash), tuned with -pcsd / -page-content-similar-distance (SimHash max Hamming distance, default 3), -pcst / -page-content-similar-threshold (TF-IDF/BM25BM25The classic keyword-ranking formula behind traditional search engines. Hybrid search combines it with embedding similarity so exact terms and meaning both count. min score 0–1, default 0.85), and -pcsn / -page-content-similar-budget (pages fully processed per similarity cluster, default 1).

Crawl a target and skip near-duplicate pages using TF-IDF similarity scoring to reduce noise on large sites.
$ katana -u https://example.com -pcs -pcsm tfidf -pcst 0.90
— Full flag set with defaults and a runnable example. v1.7.0
02 00
Secrets extractor in knowledge base new 85

The -kb-secrets flag enables a secrets extractor within the knowledge base that automatically detects exposed credentials and tokens during crawls. The -kb-validate-secrets flag validates detected secrets live against their respective providers by sending real API calls.

Crawl a target and extract secrets from the knowledge base, then validate them live against their providers.
$ katana -u https://example.com -kb -kb-secrets -kb-validate-secrets
— Named flags, mechanism, and runnable example given. v1.7.0
03 00
Context field for lifecycle control new 70

Adds a Context field to the Options struct for external lifecycle control — cancelling the provided context.Context stops the rate limiter, crawl session, queue, known-files requests, and headless browser.

— Named struct field with clear behaviour, no code sample. v1.7.0
04 00
Endpoints extractor in knowledge base new 60

The -kb-endpoints flag enables an endpoints extractor that classifies REST, GraphQL, SOAP, and XHR requests found during crawling.

— Named flag and classification types, but no example. v1.7.0
thinner coverage below
05 00
Headless engine callbacks new 30

Adds callbacks to the headless engine, enabling programmatic interception of headless browser events.

— Describes capability but no API names or usage shown. v1.7.0
Was this useful?
◆  Secrets Detection & Management

GitGuardian Detection Engine

Sources Blog / feed → 2 releases · 2026-08-03 → 2026-08-04 Blog

GitGuardian Detection Engine scans code repositories to identify and alert on exposed secrets, credentials, and sensitive data in real-time.

GitGuardian's Detection Engine expanded its secret-detection coverage with eight new detectors (Lovable, Slack Workflow Builder, n8n, Atlassian, AWS Cognito, OpenAI, Vercel OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user., OpenCode) and a new Supabase JWTJWTAn open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. checker, while also tightening validation on GitHub, npm and PostgreSQL detectors and removing/disabling two detectors.

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

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

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

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

01 00
PostgreSQL credentials detector expanded matching improved 70

PostgreSQL credentials detectors now match usernames containing dashes (e.g. workflow-prod-user) and raise the username length bound from 20 to 30 characters.

— Gives concrete example and exact numeric limit change Detection Engine Updates Version 2.169 (2026…
02 00
New detectors for Slack, n8n, Atlassian and others new 65

Seven new detectors were added: Slack Workflow Builder webhook trigger URLs, n8n API keys, Atlassian auth keys (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 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. issued by auth.atlassian.com), AWS Cognito User Pool access tokens, OpenAI platform access tokens, Vercel OIDC workload-identity tokens, and OpenCode API keys.

— Names each detector type but no config/API to act on Detection Engine Updates Version 2.169 (2026…
03 00
Azure Event Hub/Service Bus checker false-valid fix improved 65

Azure Event Hub and Azure Service Bus checkers now only report a key as valid when the 200 response is a genuine Service Bus Atom feed, blocking false-valid results behind intercepting proxies.

— Explains exact validation mechanism and threat scenario fixed Detection Engine Updates Version 2.169 (2026…
thinner coverage below
04 00
GitHub token detector format validation improved 50

The GitHub Personal Access Token, GitHub OAuth Token, and GitHub App Token detectors now skip values that fail format validation, reducing false positives from generic detectors.

— Names three specific detectors and the fix's effect Detection Engine Updates Version 2.169.1 (20…
05 00
Grafbase access token detector removed breaking 50

The grafbase_access_token detector and checker have been removed entirely.

— Names exact detector removed, no migration guidance Detection Engine Updates Version 2.169 (2026…
06 00
npm Token detector format validation improved 45

The npm Token detector now skips values that fail format validation, reducing false positives from generic detectors.

— Clear mechanism but single narrow detector Detection Engine Updates Version 2.169.1 (20…
07 00
Amadeus OAuth credentials detector disabled breaking 45

The Amadeus OAuth credentials detector and checker have been disabled.

— Names detector disabled, no reason or migration path given Detection Engine Updates Version 2.169 (2026…
08 00
Supabase service_role JWT checker new 40

A new checker validates Supabase service_role JWTsJWTsJSON Web Tokens — an open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object. Cyber tools use them for stateless authentication without server-side session storage..

— Names exact JWT type but no detail on validation logic Detection Engine Updates Version 2.169 (2026…
09 00
Lovable token detectors new 35

New detectors identify Lovable project access tokens and Lovable git tokens.

— Names the token types but no mechanism given Detection Engine Updates Version 2.169.1 (20…
10 00
Generic Database Assignment detector port variant improved 35

The Generic Database Assignment detector now incorporates the attached-port variant.

— Names the detector but mechanism is vague Detection Engine Updates Version 2.169 (2026…
└──▷ BREAKING ON UPGRADE
  • !
    The grafbase_access_token detector and checker have been removed entirely.
  • !
    The Amadeus OAuth credentials detector and checker have been disabled.
Was this useful?
Network Security
◆  Firewalls & Network Defense

Sophos DNS Protection

Sources Release page → 1 release · 2026-08-05 Notes

Sophos DNS Protection is a security service that blocks malicious websites and threats by filtering DNS queries at the network level.

Sophos DNS Protection adds a dedicated Generative AI web category, giving filtering policies granular control over AI services separate from other business categories.

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

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

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

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

01 00
Generative AI filtering category new 57

A new Generative AI category is added to the Business and generative AI category group (formerly Business-relevant site categories), letting filtering policies block or allow generative AI websites independently of other business categories.

— Names the category and group but no policy config path given 2026.32Released on August 5, 2026
Was this useful?

Fastly

Sources Blog / feed → 1 release · 2026-08-04 Blog

Fastly is a content delivery network and edge computing platform that accelerates website performance and provides security services globally.

Fastly's Next-Gen WAFWAFA reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. now surfaces who created a given rule or signal, adding a created_by field to its API responses.

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

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

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

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

01 00
created_by field in Next-Gen WAF APIs new 60

The Next-Gen WAF Rules API and Next-Gen WAF Signals API responses now include a created_by field, identifying the email address of the user who created the rule or signal.

— Names exact field and two APIs but no example request/response shown. Next-Gen WAF: `created_by` field now include…
Was this useful?
Cloud & Container Security
◆  Runtime Security

Docker Sandboxes

Sources Release notes → 1 release · 2026-08-06 Notes

Docker Sandboxes provides isolated, lightweight environments for securely running and testing AI models and applications with controlled dependencies.

Docker Sandboxes' v0.38.0 release adds local model routing for Claude Code, first-class 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 management, enterprise proxy/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./KerberosKerberosA network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. support, per-sandbox network deny rules, and experimental GPUGPUA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference. passthrough, while accompanying docs detail a new AI Governance Audit Logs feature (0.35.0+) and OpenCode Zen API key integration.

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

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

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

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

01 00
OpenCode Zen API key custom secret with host proxy substitution new 90

sbx secret set-custom -g --host opencode.ai --env OPENCODE_API_KEY --value stores OpenCode Zen API keys so the real key stays in the host secret store while the sandbox receives a placeholder that the host-side proxy substitutes on requests to opencode.ai. Sandboxes also need sbx policy allow network opencode.ai:443 to reach the OpenCode Zen service.

Store an OpenCode Zen API key as a global custom secret so all OpenCode sandboxes can authenticate to opencode.ai without exposing the real key inside the sandbox.
$ sbx secret set-custom -g \
  --host opencode.ai \
  --env OPENCODE_API_KEY \
  --value "$OPENCODE_API_KEY"
Allow an OpenCode sandbox to reach the OpenCode Zen API over HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. after adding the custom secret.
$ sbx policy allow network opencode.ai:443
— Exact runnable commands and mechanism given product docs
02 01
AI Governance Audit Logs with local and cloud delivery new 85

Requires Docker Sandboxes 0.35.0+ and an AI Governance subscription. The sandbox daemon writes local audit records as .jsonl.jsonlA text format where each line is a self-contained, valid JSON object, making it easy to stream, append, and process large datasets line by line without parsing a full JSON array into memory. files (JSON Lines) to per-OS paths — ~/Library/Logs/com.docker.sandboxes/sandboxes/auditkit/ (macOS), ${XDG_STATE_HOME:-~/.local/state}/sandboxes/sandboxes/auditkit/ (Linux), %LOCALAPPDATA%\DockerSandboxes\sandboxes\logs\auditkit\ (Windows) — named audit-<utc-timestamp>-<process-uuid>-<seq>.jsonl, finalized by atomic rename at rotation thresholds of 5 minutes, 1000 events, or 50 MiB. Records include evaluation events (resource, action, verdict, deny_reason) and session lifecycle events linked by audit_session_id, with fields like audit_event_id, schema_version, username, org_id, hostname, network_egress. Local delivery supports SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. ingestion via log shippers (Splunk Universal Forwarder, Filebeat, CrowdStrike Falcon LogScale); Docker Cloud delivery (on by default when AI Governance is enabled) additionally powers a hosted audit log view, CSV export, and SIEM streaming from app.docker.com, configurable by org owners or custom-role users. Run sbx policy ls to confirm a Governance: Managed by <org> line, a prerequisite for audit records to be written.

Confirm that governance is active and audit logging is enabled before relying on local audit records.
$ sbx policy ls
— Full field/path/rotation detail plus one verification command, no enable steps product docs
03 00
Local model routing for Claude Code new 85

sbx run --model <name> claude serves a local GGUFGGUFThe single-file model format used by llama.cpp and Ollama, holding the weights, usually quantized, together with the tokenizer and settings needed to run the model locally. model via llmman, or an already-running Ollama install using an ollama/ prefix, routing Claude Code away from api.anthropic.com. Requires enabling sbx settings set platform.allowExperimentalFeatures true and sbx settings set feature.model true first.

Route Claude Code at a local GGUF model instead of api.anthropic.com — useful for air-gapped or cost-sensitive environments.
$ sbx settings set platform.allowExperimentalFeatures true
sbx settings set feature.model true
sbx run --model llama3.2 claude
— Exact commands and enabling flags provided v0.38.0
04 00
Enterprise proxy support with NTLM/Kerberos and TLS options new 85

Settings-driven upstream-proxy configuration via proxy, proxy.sandbox, proxy.daemon, and matching no_proxy keys defaults to the host OS system proxy and proxies daemon traffic (image pulls, telemetry) too. proxy.integratedAuth enables NTLM/Kerberos/Negotiate proxy authentication on Windows, and tls.allowNegativeSerial supports TLS-inspecting proxies issuing certificates with negative serial numbers. Blocked HTTPS proxy connections now appear in sbx policy log even when the client aborts the TLS handshake.

Configure a corporate HTTPS proxy for all sandbox and daemon traffic with NTLM authentication on Windows.
$ sbx settings set proxy http://proxy.corp.example.com:8080
sbx settings set proxy.integratedAuth true
— Named settings keys with a runnable configuration example v0.38.0
05 02
Per-sandbox network deny rules new 65

--deny-network HOST flag on sbx run and sbx create records per-sandbox egress deny rules at creation time, e.g. to block a sandbox from reaching a specific host to prevent exfiltration.

Block a sandbox from reaching a specific host at creation time, e.g. to prevent exfiltration to an external service.
$ sbx run --deny-network api.example.com claude
— Exact flag with runnable example command v0.38.0
06 03
First-class MCP server management with live index refresh improved 60

sbx mcp becomes a first-class, no-longer-hidden subcommand for MCP server management, with sbx mcp add supporting --dir and OAuth override flags; registering a server immediately refreshes the mcp-find/mcp-add index in every running sandbox without recreating them. Dynamic MCP tools mcp-find, mcp-add, and mcp-config-set are now also available in local sandbox mode.

— Named subcommand and flags but no worked example v0.38.0
07 04
Experimental NVIDIA GPU passthrough new 60

sbx run --gpu (experimental) enables NVIDIA VFIOVFIOA Linux kernel framework that lets userspace programs take direct ownership of a PCI device, bypassing kernel drivers, giving cyber tools low-latency, isolated hardware access without running in kernel space. GPU passthrough on Linux; enable with sbx settings set feature.sandbox-gpu true.

— Named flag and enabling setting, no worked walkthrough v0.38.0
thinner coverage below
08 00
sbx mount host bind-mount at matching path improved 55

sbx mount <sandbox> <host> now bind-mounts the host path at the same path inside the sandbox when no container target is given; :ro mounts are enforced read-only at the virtio-fs host edge.

— Behaviour and enforcement point described, no example v0.38.0
09 05
Secrets default to global scope breaking 50

Service and custom secrets are now global by default, with a --sandbox flag for sandbox-scoped secrets; legacy positional and --global forms are deprecated with warnings.

— Names flag and deprecation but no migration example v0.38.0
10 06
sbx mcp bundle command removed breaking 40

The sbx mcp bundle command has been removed; single-server management via sbx mcp add/ls/rm is now the only supported flow.

— States removal and replacement, no migration steps v0.38.0
11 00
sbx daemon restart command new 40

sbx daemon restart stops and restarts the sandboxd daemon in the background.

— Command named but no further mechanism described v0.38.0
12 00
Claude Vertex multi-region endpoint support improved 40

Claude Vertex sandboxes now support us and eu multi-region endpoints.

— Names regions but no configuration steps given v0.38.0
13 00
Configurable cloned workspace volume size new 35

DOCKER_SANDBOXES_CLONED_WORKSPACE_SIZE environment variable configures the size of the cloned workspace volume.

— Env var named, no default or usage example given v0.38.0
14 00
Homebrew stapled .dmg installer on macOS improved 35

Homebrew installs now use a stapled .dmg artifact instead of a .tar.gz archive, improving Gatekeeper compatibility on macOS.

— Names artifact change, nothing for the reader to run v0.38.0
15 00
sbx inspect shows custom secrets improved 30

sbx inspect now displays custom secrets configured for a sandbox.

— Single-line change with no further detail v0.38.0
└──▷ BREAKING ON UPGRADE
  • !
    The sbx mcp bundle command has been removed; single-server management via sbx mcp add/ls/rm is the only supported flow.
  • !
    Service and custom secrets default to global scope; legacy positional and --global forms are deprecated with warnings.
Was this useful?

NVIDIA OpenShell

Sources Release notes → 1 release · 2026-08-05 Notes

OpenShell is the safe, private runtime for autonomous AI agents.

OpenShell v0.0.99 adds a system CA root mode for sandboxes, starts honoring OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. image working directories, and fixes a TCP_NODELAY latency issue.

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

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

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

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

01 00
System CA root mode for sandboxes new 50

Adds a system CA root mode to the build, enabling sandboxes to trust the host's system certificate authorities.

— Names the capability and effect but no flag or config surface given. v0.0.99
02 00
TCP_NODELAY latency fix improved 30

The release includes a latency fix related to TCP_NODELAY, though no further explanation of the change is given.

— Names the socket option but lacks context on scope or impact. v0.0.99
03 00
Honors OCI image working directories improved 25

OpenShell now honors the working directory specified in OCI images, per the release summary; no further mechanism is described.

— Only mentioned briefly in the summary, no detail on behavior. v0.0.99
Was this useful?
◆  Container & Image Security

Sigstore cosign

Sources Release notes → 1 release · 2026-08-06 Notes

Code signing and transparency for containers and binaries

cosign v3.1.3 adds support for signing OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. images with an X.509X.509A standard defining the format of public-key certificates, maintained by the ITU-T, used by cyber tools to authenticate identities and establish encrypted connections over TLS and similar protocols. certificate chain and auto-detects digest algorithms for public keys.

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

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

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

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

01 01
OCI signing with X.509 certificate chain new 45

cosign now supports OCI signing with an X.509 certificate chain, enabling bring-your-own PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets. workflows for container image signing.

— Names capability but no flag or command shown. v3.1.3
02 00
Auto-detected digest algorithm for public keys improved 40

cosign auto-detects the default digest algorithm for public keys, removing the need to manually specify it.

— Describes behaviour change but no flag or command detail. v3.1.3
Was this useful?
◆  Cloud Security Posture

Prowler

Sources Release notes →Source code → 1 release · 2026-08-06 Notes Code

Prowler is the Open Cloud Security Platform trusted by thousands to automate security and compliance in any cloud environment. With thousands of ready-to-use checks and compliance frameworks, delivers real-time, customizable monitoring and seamless integrations, making cloud security simple, scalable, cost-effective for organizations of any size.

Prowler 5.38.0 expands M365 compliance coverage with 12 new checks, adds 20 AWS privilege-escalation Attack Paths queries plus outcome-category metadata, and introduces Compliance Watchlists and multi-domain 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. in Prowler Cloud/Private Cloud.

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

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

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

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

01 00
New M365 checks for CIS Foundations Benchmark v7.0.0 new 85

Adds 12 M365 provider checks: admincenter_shared_bookings_disabled (control 1.3.9); defender_priority_account_protection_enabled and defender_strict_preset_security_policy_enabled (controls 2.4.1, 2.4.2); exchange_owa_mailbox_policy_personal_accounts_disabled and exchange_organization_reject_direct_send_enabled (controls 6.3.2, 6.5.5); teams_external_access_trial_tenants_blocked (control 8.2.4); and six device-registration checks — entra_device_registration_join_restricted, entra_device_registration_max_devices_per_user_limited, entra_device_registration_global_admins_not_local_admins, entra_device_registration_registering_user_not_local_admin, entra_device_registration_laps_enabled, and entra_policy_default_user_cannot_read_bitlocker_keys (controls 5.1.4.x), all mapped to CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline. Microsoft 365 Foundations Benchmark v7.0.0.

— Named checks and exact CIS control mappings given 5.38.0
02 00
20 new AWS privilege-escalation queries in Attack Paths new 80

Attack Paths adds 20 AWS privilege-escalation detection queries sourced from pathfinding.cloud, covering iam:PassRole escalations across AWS Batch, Braket, Cognito Identity, ECSECSElastic Common Schema, an open specification maintained by Elastic that defines a standard field naming convention for log and event data, letting cyber tools share and correlate records without per-source field mapping., EMR, EMR Serverless, GameLift, Glue, EC2EC2Amazon's cloud virtual-machine service, letting tools run on-demand servers without managing physical hardware. Image Builder, Kinesis Analytics, HealthOmics, EventBridgeEventBridgeAWS's managed event bus service that routes events between cloud services, SaaS apps, and custom code using rules and targets, letting tools react to state changes without polling or managing message infrastructure. Scheduler, SSM, and Step Functions, plus CodeDeploy/Step Functions existing-resource abuse, permissions-boundary removal with role assumption, and 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. Identity Center permission-set policy injection.

— Detailed services and escalation paths, no direct usage step 5.38.0
03 00
Outcome category on Attack Paths query metadata improved 70

Attack Paths query metadata now exposes an outcome category (Code execution, Privilege escalationPrivilege escalationGaining permissions beyond those an account or process initially had. It can turn limited access into administrator control or access to another user's resources., Public exposure, or Resource inventory) on the queries endpoint, enabling terminal outcome nodes in the graph.

— Names the endpoint and category values but no path/method 5.38.0
04 00
Expanded privilege-escalation combinations in IAM policy check improved 65

iam_policy_allows_privilege_escalation check gains 22 additional escalation combinations from pathfinding.cloud across AWS Batch, Braket, CodeDeploy, Cognito Identity, ECS, EMR, EMR Serverless, GameLift, Glue, EC2 Image Builder, Kinesis Analytics, HealthOmics, and EventBridge Scheduler.

— Named check and services covered, but no run instructions 5.38.0
05 00
Multi-domain SAML SSO configuration improved 65

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. SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. now supports one primary email domain plus up to 19 additional domains under a single Identity Provider configuration and a single stable ACS URL (Prowler Cloud/Private Cloud).

— Exact domain limit and ACS URL detail, no config path 5.38.0
thinner coverage below
06 00
Compliance Watchlist for pinned frameworks new 55

Compliance Watchlist (Prowler Cloud/Private Cloud) lets teams pin frameworks from any compliance view, filter the Compliance section to pinned frameworks only, and see pinned framework scores on the Overview page.

— Describes behaviour and UI location, no config key 5.38.0
07 00
Sign-in method tags in Users table new 50

Users table in Prowler Cloud now shows each account's sign-in methods as tags, including email/password, Google, GitHub, SAML with linked domains, and Partner SSO.

— UI location given, no further mechanism 5.38.0
08 00
SBOMs and build-provenance attestations for container images new 50

Prowler API, UI, SDK, and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. container images now publish per-architecture SBOMsSBOMsA 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. and build-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. attestations as OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. attestations.

— Names artifacts and format but no retrieval command 5.38.0
09 00
Grype scanning alongside Trivy in image security gates improved 40

Grype now runs alongside Trivy across container-image security gates, blocking on fixable high and critical findings.

— Names tools and gate behaviour, no config surface 5.38.0
10 00
Checksum verification for downloaded build binaries improved 35

API and SDK container builds now verify checksums of downloaded PowerShell, Trivy, and zizmor binaries before installation.

— Names binaries but process is internal, not user-actionable 5.38.0
Was this useful?

Wiz

Sources Blog / feed → 1 release · 2026-08-06 Blog

Wiz is a cloud security platform that identifies and remediates risks across cloud infrastructure and applications.

Wiz added automated DISA STIGSTIGA configuration standard published by DISA that specifies hardening requirements for a given OS, application, or device, giving cyber tools a concrete checklist to audit or enforce against. compliance assessment for Amazon Linux 2023 and Windows Server 2025 in AWS GovCloud, closing gaps where official SCAP content isn't yet available.

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

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

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

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

01 00
Automated DISA STIG assessment for AL2023 and Windows Server 2025 new 68

Wiz adds automated DISA STIG compliance assessment covering Amazon Linux 2023 (AL2023 V1R2 and V1R3 benchmarks) and Windows Server 2025, filling gaps where official SCAP content is not yet available. It delivers continuous hardening validation for federal agencies and defense contractors operating in AWS GovCloud, supporting 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. Rev5, FedRAMP 20xFedRAMP 20xA GSA-led overhaul of the FedRAMP cloud-authorization program aimed at cutting compliance burden through continuous, automated evidence collection rather than point-in-time audits, letting vendors reach federal markets faster., CMMC, and DoD authorization requirements.

— Names benchmarks and frameworks but no config or API surface given. 2026-08-06-c676879b
Was this useful?
◆  CNAPP

Wiz Cloud

Sources Blog / feed → 1 release · 2026-08-06 Blog

Wiz Cloud is a cloud security platform that identifies and remediates risks across cloud infrastructure, applications, and data.

Wiz added automated DISA STIGSTIGA configuration standard published by DISA that specifies hardening requirements for a given OS, application, or device, giving cyber tools a concrete checklist to audit or enforce against. compliance assessment for Amazon Linux 2023 and Windows Server 2025, surfacing agentless host-level findings directly in the Compliance Posture dashboard.

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

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

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

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

01 00
DISA STIG Amazon Linux 2023 assessment via HCR new 80

Adds DISA STIG Amazon Linux 2023 benchmark support via Host Configuration Rules (HCR), providing continuous agentless assessment across all connected cloud instances without SCAP content or scan credentials. Enable it in the Wiz portal under Compliance Posture > Manage Frameworks by searching for DISA STIG Amazon Linux 2023 — assessment begins automatically for all connected instances.

Enable the DISA STIG Amazon Linux 2023 framework to start continuous agentless assessment across your entire AL2023 fleet.
📍In the Wiz portal, go to Compliance Posture › Manage Frameworks, search for DISA STIG Amazon Linux 2023, and enable the benchmark — assessment begins automatically for all connected instances.
— Names HCR mechanism and exact portal path, no API. 2026-08-06-d1ea617b
02 00
DISA STIG Windows Server 2025 assessment via HCR new 77

Adds DISA STIG Microsoft Windows Server 2025 benchmark support via Host Configuration Rules (HCR), with an initial automated rule set and expanding coverage planned in upcoming releases. Enable it via Compliance Posture > Manage Frameworks by searching for DISA STIG Microsoft Windows Server 2025 — new instances are assessed automatically on deployment.

Enable the DISA STIG Microsoft Windows Server 2025 framework to continuously assess Windows Server 2025 hosts as they are deployed.
📍In the Wiz portal, go to Compliance Posture › Manage Frameworks, search for DISA STIG Microsoft Windows Server 2025, and enable the benchmark — new instances are assessed automatically on deployment.
— Exact portal steps given; rule set breadth unspecified. 2026-08-06-d1ea617b
thinner coverage below
03 00
STIG findings in Compliance Posture dashboard new 50

STIG findings for both new frameworks surface in the Compliance Posture dashboard alongside existing frameworks, with per-rule pass/fail status per instance and rollup into category and subcategory scores.

— Describes rollup behaviour but no exact dashboard path. 2026-08-06-d1ea617b
04 01
Filter findings by STIG severity category new 45

Supports filtering findings by STIG severity category (CAT I, CAT II, CAT III) to prioritize high-impact failures.

— Names the three categories, no filter UI detail. 2026-08-06-d1ea617b
05 00
Compliance trend, reports and automation for STIG checks new 45

Enables Compliance Posture Trend tracking, auditor report generation, and automation rules to create tickets or trigger remediation workflows for failed STIG checks.

— Lists linked capabilities without configuration specifics. 2026-08-06-d1ea617b
06 00
STIG assessment available under existing licenses new 25

Available to all Wiz for Government customers under existing Wiz licenses with no additional license required.

— Simple licensing note with no mechanism or steps. 2026-08-06-d1ea617b
Was this useful?
Detection & Response
◆  Endpoint Security (EDR/XDR)

Iru

Sources Release page → 3 releases · seen 2026-08-06 Notes

Iru shipped three Apple device management updates: Apple beta program enrollment via the Software Update Library Item, phased rollout support extended to Managed OS updates, and Authenticated Guest Mode for Platform SSOPlatform SSOA macOS framework from Apple that lets identity providers hook into the operating system login flow, enabling enterprise single sign-on at the platform level rather than per-app. on macOS.

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

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

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

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

01 00
Apple beta program enrollment via Software Update Library Item new 60

The Software Update Library Item now supports Apple beta program enrollment, allowing end users to opt-in or letting admins enforce a specific beta program without tying it to a specific version.

— Names the library item and behavior but no config keys. Offer Apple beta releases with the Software …
thinner coverage below
02 00
Phased rollouts for Managed OS updates new 50

Extends phased rollout support — previously available for Mac Auto Apps — to Apple Managed OS, letting admins stage OS update declarations across their device fleet instead of pushing to all devices simultaneously.

— Explains mechanism and scope but no config surface named. Phased Rollouts for Managed OS for Apple dev…
03 00
Authenticated Guest Mode for Platform SSO on Mac new 40

Adds Authenticated Guest Mode configuration support to the Single Sign-On Extension Library Item when using Platform SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. with macOS.

— Names the library item but lacks detail on how it works. Platform SSO for Mac: Authenticated guest mode
Was this useful?
◆  Detection Engineering

Tenzir

Sources Blog / feed → 2 releases · 2026-08-06 Blog

Tenzir is a security data platform that ingests, transforms, and analyzes security telemetry and threat intelligence data.

Tenzir's v6.9.0 release line adds native 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. output, automatic NetFlow/IPFIXIPFIXAn IETF standard protocol for exporting network flow records from routers and probes to a collector, giving cyber tools a vendor-neutral stream of structured traffic metadata without full packet capture. decoding, and OCSF 1.9.0OCSF 1.9.0An open schema standard, maintained by the OCSF community under CISA and industry backing, that defines a common event format for security telemetry so cyber tools can share and ingest logs without custom normalization. schema support, alongside several new configuration keys for faster, lower-memory catalog startup and data-integrity validation.

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

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

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

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

01 00
Native Apache Iceberg output via to_iceberg new 95

A new to_iceberg operator writes events directly into Apache Iceberg tables through a REST catalog, with mode (create_append, create, append), partition_by supporting hidden-partition transforms (year, month, day, hour, bucket, truncate), plus max_size, timeout, and buffer_size for file rotation. It writes zstd-compressed Parquet with automatic schema evolution for heterogeneous streams, and connects to 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. stores via aws_iam, s3_endpoint, s3_path_style, bearer-token catalogs via token, AWS Glue/Amazon S3 Tables via catalog_aws_service, and Google BigLake via gcp_service_account_key or gcp_auth.

Write a live 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. stream to an Iceberg table partitioned by class and day, with automatic schema evolution.
$ subscribe "ocsf"
ocsf::cast
to_iceberg "security.ocsf", catalog = "https://catalog.example.com", partition_by = [class_uid, day(time)]
Write a live OCSF stream to an Apache Iceberg table partitioned by class and day, creating the table automatically if it doesn't exist.
$ subscribe "ocsf"
ocsf::cast
to_iceberg "security.ocsf", catalog = "https://catalog.example.com", partition_by = [class_uid, day(time)]
02 00
Faster catalog startup via index tuning config keys new 95

New config keys reduce startup time and memory on nodes with many partitions: tenzir.index.load-concurrency tunes worker threads for concurrent partition synopsis loading (defaults to hardware concurrency); tenzir.index.lazy-sketches defers Bloom-filter sketch loading to query time, bounding warm memory via an LRU cache sized by tenzir.index.sketch-cache-bytes (default 1 GiB); and tenzir.index.skip-synopsis-verification skips recursive FlatBuffers verification of partition synopses at startup, trading corruption robustness for speed on trusted networked storage such as NFS.

Reduce startup memory and load time on a node with many partitions backed by NFS.
yaml
tenzir.index.load-concurrency: 16
tenzir.index.lazy-sketches: true
tenzir.index.sketch-cache-bytes: 2147483648
tenzir.index.skip-synopsis-verification: true
Reduce startup memory and time on a node with many partitions by deferring Bloom-filter sketch loading and skipping synopsis verification on trusted NFS storage.
yaml
tenzir.index.lazy-sketches: true
tenzir.index.skip-synopsis-verification: true
tenzir.index.sketch-cache-bytes: 2147483648  # 2 GiB
tenzir.index.load-concurrency: 16
— Named config keys with defaults and a runnable config example. Tenzir Node v6.9.0-rc.2: Native Apache Icebe…Tenzir Node v6.9.0: Native Apache Iceberg ou…
03 00
Automatic NetFlow and IPFIX decoding new 90

A new read_netflow operator automatically decodes NetFlow v5, NetFlow v9, and IPFIX from byte streams 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. envelopes in a single pipeline, learning templates per exporter and preserving unknown elements as blobs, with no manual parser configuration or protocol pre-selection needed.

Ingest mixed NetFlow v5/v9 and IPFIX from UDP on port 2055 in a single pipeline.
$ accept_udp "0.0.0.0:2055", binary = true
read_netflow
Ingest mixed NetFlow v5/v9 and IPFIX traffic from a UDP listener without pre-selecting a protocol version.
$ accept_udp "0.0.0.0:2055", binary = true
read_netflow
— Names operator, versions handled, and a runnable UDP example. Tenzir Node v6.9.0-rc.2: Native Apache Icebe…Tenzir Node v6.9.0: Native Apache Iceberg ou…
04 00
Store batch validation for corruption diagnosis new 60

The tenzir.validate-store-batches config key fully validates every Arrow record batch read from a persisted Feather store, helping diagnose on-disk corruption including malformed UTF-8; disabled by default.

05 00
Faster ocsf::cast variant encoding and null-filling improved 60

ocsf::cast with encode_variants=true now encodes free-form objects such as unmapped significantly faster, lowering CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware. usage for high-volume streams, and ocsf::cast with null_fill=true now uses significantly less memory and CPU by avoiding per-batch column rebuilds.

— Named operator and flags but no example command. Tenzir Node v6.9.0-rc.2: Native Apache Icebe…
thinner coverage below
06 00
Dynamic field assignment with expression keys new 45

Fields can now be assigned using expression keys via result[key] = value, letting field names be determined per-event at runtime instead of being fixed at pipeline-definition time.

— Syntax named but no runnable example given. Tenzir Node v6.9.0: Native Apache Iceberg ou…
07 00
OCSF 1.9.0 schema support new 40

Adds support for OCSF 1.9.0 (and all earlier bundled stable versions), plus preview support for OCSF 1.10.0-dev.

Was this useful?

Beelzebub

Sources Release notes → 1 release · 2026-08-05 Notes

A secure low code deception runtime framework, leveraging AI for System Virtualization.

Beelzebub v3.9.0 shifts plugin management to declarative YAML configuration, adds boot-time background plugins, and introduces shared JSON Schema validation for honeypot configs.

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

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

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

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

01 00
ServicePlugin background plugins at boot new 50

Adds ServicePlugin support for background plugins that start automatically at boot time.

— Names concrete plugin type but no usage steps v3.9.0
02 00
Shared JSON Schema validation for honeypot configs new 43

Adds shared JSON Schema validation for honeypot configurations, catching config errors before deployment.

— Names format and benefit, lacks schema location or command v3.9.0
03 00
YAML-based plugin declarations improved 33

Plugin declarations move to YAML config files, enabling declarative plugin management via configuration files instead of the prior approach.

— Names config format but no key or file path given v3.9.0
04 00
Improved installer experience improved 5

Improves the installer experience.

— No detail on what changed or how v3.9.0
Was this useful?
◆  SIEM

Sumo Logic

Sources Blog / feed → 1 release · 2026-08-05 Blog

Sumo Logic is a cloud-based monitoring and analytics platform for logs, metrics, and security data.

Sumo Logic added Mobot, a chat-based assistant that builds and edits Automation Service playbooks from natural-language descriptions.

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

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

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

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

01 00
Mobot natural-language playbook creation new 60

Mobot supports playbook creation and editing via natural-language chat: you describe the automation you want, Mobot checks available integrations, asks clarifying questions, proposes a plan, configures each step, and saves the result as a draft for review and publishing.

— Describes full workflow but no UI path or config named Manage Playbooks with Mobot (Automation Serv…
Was this useful?
◆  Threat Intelligence

Feedly Threat Intelligence

Sources Blog / feed → 1 release · 2026-08-07 Blog

Feedly Threat Intelligence aggregates security feeds and threat data to help organizations monitor emerging cybersecurity threats and vulnerabilities.

Feedly's Vulnerability Intel Agent added a dedicated Atlassian security release filter with product, attack-path, and patch-policy filtering, alerting, and expanded vendor advisory coverage.

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

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

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

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

01 00
Attack path filtering for CVEs new 65

CVEs can be filtered by 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. — attack vector, privileges required, and user interaction — to isolate unauthenticated, no-interaction reachable vulnerabilities.

— Names specific attack-path dimensions used for isolation. Enrich and triage Atlassian security release…
02 00
Patch policy threshold filtering (CVSS/EPSS) new 65

Filtering by patch policy thresholds supports CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. score cutoffs, EPSSEPSSExploit Prediction Scoring System, an estimate of the probability that a published vulnerability will be exploited in the next 30 days. It helps prioritize investigation and patching. probability cutoffs, or both combined, letting teams isolate CVEs that breach both thresholds simultaneously to match internal patch policies.

— Names exact scoring metrics and combined-threshold behavior. Enrich and triage Atlassian security release…
03 00
Latest Atlassian Security Release filter new 60

A Latest Atlassian Security Release filter in the Vulnerability Intel Agent always points to the most recent Atlassian advisory, ingested within minutes of publication, eliminating the need for manual updates each cycle.

— Names the exact filter but not full UI steps. Enrich and triage Atlassian security release…
04 00
Product-level CVE filtering for Atlassian stack new 60

Filtering supports scoping Atlassian CVEs down to specific products in a team's stack, such as Confluence Data Center, Sourcetree, and Jira, to surface only relevant exposures.

— Names concrete products but not exact filter mechanics. Enrich and triage Atlassian security release…
thinner coverage below
05 00
Expanded vendor advisory coverage improved 45

Vendor advisory support in the Vulnerability Intel Agent now includes Adobe, Android, Apache, Apple, Microsoft, Oracle, and Atlassian.

— Lists named vendors but no usage mechanism. Enrich and triage Atlassian security release…
06 00
Alerting on filtered CVE matches new 35

Alerts are available via a deployed Intel Agent, notifying teams when newly published CVEs match their configured filters.

— Mechanism described briefly, no setup detail. Enrich and triage Atlassian security release…
07 00
Configurable enrichment columns in output table improved 35

Enrichment columns in the Vulnerability Intel Agent's output table are reorderable and individually showable or hidable to match team triage workflows.

— Describes UI capability without exact navigation path. Enrich and triage Atlassian security release…
Was this useful?
Exposure & Vulnerability Management
◆  Vulnerability Management

Tenable

Sources Blog / feed → 1 release · 2026-08-05 Blog

Tenable is a cybersecurity platform that identifies, measures, and remediates vulnerabilities across an organization's entire attack surface.

Tenable introduced Hexa AI, an agentic capability within Tenable One that automates exposure remediation end-to-end using intent-driven Routines and human-approval guardrails.

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

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

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

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

01 01
Intent-driven Routines for remediation workflow new 55

Routines encode the multi-step remediation workflow — asset scoping, policy targeting, patch execution, status check, and re-scan confirmation — into a single automated sequence triggered by intent.

— Lists workflow steps but no exact command or config to invoke 2026-08-05-bfc66599
02 02
Tenable Hexa AI agentic remediation new 48

Tenable Hexa AI is an agentic capability within Tenable One that automates the full remediation cycle — scoping, patch deployment, and verification — across integrated platforms such as Jamf.

— Describes scope and integration but no config or API surface 2026-08-05-bfc66599
03 00
Human approval guardrails on AI autonomy new 35

AI autonomy is bound strictly to defined user permissions within the Tenable One harness, with human approval gates required before changes are applied.

— Explains safety mechanism conceptually, no configurable permission details given 2026-08-05-bfc66599
Was this useful?
◆  Attack Surface & Exposure Management

Tenable One

Sources Blog / feed → 1 release · 2026-08-05 Blog

Tenable One is an integrated cybersecurity platform that unifies vulnerability management, cloud security, and compliance across an organization's entire attack surface.

Tenable One introduces Tenable Hexa AI, an agentic engine that turns natural-language objectives into gated, end-to-end vulnerability remediation routines.

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

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

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

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

01 01
Natural-language intent-driven routines with guardrails new 70

Intent-driven routines let practitioners define an objective, guardrails (e.g., 'Never launch a credentialed scan against anything tagged OT,' 'Open no more than twenty-five tickets in a run'), and a cadence (on-demand or scheduled) in plain natural language — no scripts required.

— Concrete guardrail examples give a clear starting point 2026-08-05-1fa9e5be
02 02
Proposal-gated execution before changes new 60

Before writing any changes, Hexa presents a plan showing device count, device list, policy, deployment window, and blast radius, and requires explicit approval before proceeding.

— Detailed plan fields but no exact command to trigger it 2026-08-05-1fa9e5be
thinner coverage below
03 03
Hexa AI agentic remediation engine new 55

The new Tenable Hexa AI agentic engine automates end-to-end vulnerability remediation within a single conversational workflow — enumerating affected assets, mapping CVEs to fix versions, and executing patch deployments without manual tool-switching.

— Explains mechanism but no concrete UI path or command 2026-08-05-1fa9e5be
04 04
Mid-workflow scope narrowing new 40

Supports scope narrowing mid-workflow — tell Hexa to restrict enumeration to a single business unit and it re-scopes and returns a revised plan before executing.

— Describes behavior with a concrete example but no exact syntax 2026-08-05-1fa9e5be
05 00
Routines adapt to infrastructure changes improved 35

Routines adapt automatically to infrastructure changes such as new asset classes, renamed tags, or failed scans, without requiring script updates.

— States behavior but no mechanism detail 2026-08-05-1fa9e5be
06 00
Explicit conflict surfacing between objective and guardrails new 25

Hexa surfaces conflicts between an objective and its guardrails explicitly rather than silently dropping either constraint.

— Brief prose description, no mechanism or UI detail 2026-08-05-1fa9e5be
Was this useful?
Identity, Access & Data Protection
◆  Identity & Access Management

iDenfy

Sources Release page → 1 release · seen 2026-08-06 Notes

iDenfy is an identity verification platform that performs KYC/AML checks through document scanning and biometric analysis for compliance.

iDenfy's headline shipment this window is Age Estimation — a selfie-only age-gating capability with automatic document step-up, webhook delivery, and a full dashboard for session configuration and review — alongside new Bank Verification, Face Authentication, Fraud Prevention, AMLAMLAnti-Money Laundering: a set of laws, regulations, and procedures that financial institutions must follow to detect and report suspicious financial activity; cyber tools use it to automate transaction monitoring and compliance workflows. Screening and KYBKYBKnow Your Business — a regulatory compliance process for verifying the legal identity, ownership, and legitimacy of a business entity, used by cyber tools to screen counterparties or customers against fraud and sanctions risk. APIs, plus a long tail of KYB/IDV language, workflow, billing, and SDK improvements.

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

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

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

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

01 00
Age Estimation session management dashboard new 96

New Age Estimation section in the dashboard for browsing, filtering, searching and inspecting sessions, with a New estimation form exposing Minimum age (1–120), Safety margin (0–20 years), ID verification for uncertain results, Retry limit (1–3), Save selfie photo, and Link expiry time across General settings and Verification redirects tabs. Supports a per-session Webhook URL override and per-outcome redirect URLs (Success, Underage, Uncertain); the session list groups results into Results, Needs Attention, In Progress, Expired with filtering by client ID/creation date and search by session ID or client reference; session detail view surfaces a Step-up link to the underlying identity verification. Step-up Document Scans bill from Age Estimation finances rather than counting against document scan usage; viewing requires the View age estimation data permission and creating sessions requires MANAGE_AGE_ESTIMATION.

— Exact config keys, ranges, permission names and nav given snapshot-20260806
02 01
Age Estimation capability, API and webhooks new 83

Selfie-only minimum-age check that avoids a document scan in the common case; triggers an automatic document step-up to read an exact date of birth from the ID and compare the ID portrait against the capture selfie when the AI model lacks confidence. Session outcomes SUCCESS, UNDERAGE, UNCERTAIN, FACE_MISMATCH, ATTEMPTS_EXCEEDED are delivered via a signed Age Estimation Webhooks HTTP POST with idempotent delivery as soon as a session finishes; lifecycle statuses PENDING, PROCESSING, COMPLETED, FAILED, EXPIRED are returned by the Partner API, which pre-checks finances and rejects requests with 402 when funds are insufficient. Billed from a dedicated Age Estimation finances pool separate from standard KYCKYCKnow Your Customer — a regulatory requirement that financial services verify the identity of their users before granting access, used by cyber tools handling payments or financial data to stay compliant. charges.

— Names outcomes, statuses, 402 behavior; lacks endpoint paths snapshot-20260806
03 00
Branded email templates for KYB workflows new 77

New Email template configuration under Business Verifications → Configurations → Email template lets teams create branded emails for three template types — a new business verification session URL, a renewed session URL requesting an information update, and a completed-company verification result — with an Add verification link action that inserts a session URL placeholder into the email body.

— Exact UI path and template types given, no API surface product docs
04 02
KYB API for company verification new 62

New KYB API enables company verification via registry data retrieval, beneficial owner screening, and AML checks, with dashboard-based compliance reviews. A Stakeholder Roles reference documents five roles — CEO, Representative, Shareholder, UBOUBOuBlock Origin, a browser extension maintained by Raymond Hill that blocks ads and trackers using filter lists; cyber tools embed or reference it to strip unwanted content from web traffic or scraped pages., and ABO — including mappings for partnerships, foundations, and holding chains.

— Names roles and checks, no endpoint paths given product docs
thinner coverage below
05 03
Fraud Prevention API new 50

New Fraud Prevention API adds AI risk scoring, VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. and proxy detection, phone validation, and address verification checks.

— Lists check types, no endpoint or scoring detail product docs
06 04
AML Screening API new 50

New AML Screening API supports sanctions, PEP, and adverse media checks, offered as single checks or ongoing monitoring.

— Lists check categories, no endpoint or config product docs
07 00
Android SDK screenshot blocking, camera detection, and 3D liveness improved 50

Android SDK 8.7.1 adds screenshot blocking and virtual camera detection; Android SDK 8.7.6 adds optional 3D liveness and reduces SDK size.

— Names exact SDK versions and features snapshot-20260806
08 05
Bank Verification API new 47

New Bank Verification API verifies customer bank accounts and financial information programmatically, with session creation and webhook callbacks.

— Describes flow and webhook, no endpoint path product docs
09 06
Face Authentication API new 47

New Face Authentication API supports biometric face matching to re-authenticate returning users during account login, high-risk actions, and periodic checks.

— Names use cases, no endpoint or session model product docs
10 00
Tax identification fields in KYB new 41

Dedicated tax identification fields — VAT Number, EIN, TIN — added to KYB workflows.

— Names exact fields, no form location given snapshot-20260806
11 00
Bank Card Verification step in KYC flow new 38

New Bank Card Verification step confirms that the card used at onboarding belongs to the verified user, added as an additional step in the KYC flow.

— Describes purpose, no config or trigger detail snapshot-20260806
12 00
Supported Languages reference (36 languages) new 38

New Supported Languages reference documents 36 languages, including Latin and non-Latin scripts, with full locale codes for KYC and KYB flows.

— Gives a concrete count, but no lookup mechanism product docs
13 00
Risk assessment in company verification API new 35

The company verification API now returns risk assessment results as part of KYB responses.

— No endpoint name or response field detail given snapshot-20260806
14 00
External Reference field in KYC reports new 35

External Reference field added to KYC verification reports.

— Names the field, no usage detail snapshot-20260806
15 00
Blocklist API endpoint new 34

New Blocklist API endpoint for managing blocklisted identities.

— Names the endpoint but not its path or method snapshot-20260806
16 00
KYB automation re-run endpoint new 34

New API endpoint to re-run KYB automation on existing records.

— Names capability, no path or method given snapshot-20260806
17 00
Dedicated accounting email for PAYG partners new 33

Pay-As-You-Go partners can set a dedicated accounting email address for invoices and payment receipts.

— Describes what it does, no UI path named snapshot-20260806
18 00
IDV mobile bottom sheet layout option new 32

Identity verification (IDV) flows on mobile gain a bottom sheet layout option.

— Names UI option, no toggle location given product docs
19 00
Configurable KYB company expiration period new 30

KYB company verification records now support a configurable expiration period.

— Names the setting, no default value or location snapshot-20260806
20 00
KYC API documentation for document checks and review improved 30

Identity Verification (KYC) API documentation now covers document checks, liveness detection, and AI plus human review.

— Documentation scope only, no new mechanism described product docs
21 00
New Digital ID support: Austrian Handy Signatur, Freja eID, Mobile ID new 30

New Digital ID support added: Austrian Handy Signatur, Freja eID, Mobile ID (Sprint 126).

— Names three schemes, no integration detail snapshot-20260806
22 00
Companies House integration new 29

Companies House integration added (Sprint 125) for company data lookups.

— Names integration, no API or field detail snapshot-20260806
23 00
Risk Assessment PDF export new 28

Risk Assessment PDF export now available.

— Names the export, no trigger or location given snapshot-20260806
24 00
Custom redirect URL for iFrame new 28

Custom redirect URL for iFrame added (Sprint 125).

— Names config surface, no key or field name snapshot-20260806
25 00
KYB shared identity verification across companies new 27

KYB now supports shared identity verification across multiple companies.

— Bare description, no mechanism explained snapshot-20260806
26 00
KYB Verify Later automated IDV reminders new 27

KYB Verify Later feature introduces automated IDV reminders.

— Names feature, no cadence or config given snapshot-20260806
27 00
iOS SDK NFC improvements improved 27

iOS SDK 8.7.7 adds NFCNFCNear Field Communication, a short-range (≤4 cm) wireless standard maintained by the NFC Forum, enabling data exchange between devices; cyber tools use it to probe, emulate, or intercept contactless card and tag transactions. improvements.

— Names version, no specifics on the improvement snapshot-20260806
28 00
New digital IDs for India and Philippines new 25

New digital ID support added for India and the Philippines.

— Names countries but no scheme names or mechanism snapshot-20260806
29 00
Brazil Digital CNH document support new 25

Brazil Digital CNH (driver's license) document support added.

— Names document type, no scope or flow detail snapshot-20260806
30 00
Auto document type detection new 23

Auto document type detection for direct processing added (Sprint 126).

— Bare description of the feature snapshot-20260806
31 00
PAYG social login new 21

Pay-As-You-Go partners can now offer social login during onboarding.

— Bare description, no providers or config named snapshot-20260806
32 00
AI reviewer spelling variation matching improved 21

The AI reviewer gains spelling variation matching.

— Bare description, no scope or examples snapshot-20260806
33 00
Korean and Traditional Chinese IDV language support new 21

Korean and Traditional Chinese language support added to IDV (Sprint 124).

— Names languages, no locale codes given snapshot-20260806
34 00
SMS verification new 21

SMSSMSShort Message Service, the protocol built into cellular networks for sending text messages between phones; cyber tools use it for alerting, two-factor authentication delivery, or phishing simulation over mobile channels. verification added (Sprint 123).

— Bare feature name, no flow detail snapshot-20260806
35 00
Arabic language and RTL support for IDV new 21

Arabic language and RTLRTLRegister Transfer Level, a hardware design abstraction describing how data moves between registers each clock cycle; cyber tools use it to analyze or synthesize digital circuits from HDL source. support added to IDV (Sprint 127).

— Names language/RTL, no config detail snapshot-20260806
36 00
KYC multi-theme branding support new 21

KYC multi-theme branding support added (Sprint 127).

— Named feature, no theming mechanism snapshot-20260806
37 00
KYB sole proprietorship identity verification new 21

KYB sole proprietorship identity verification added (Sprint 127).

— Names entity type, no flow detail snapshot-20260806
38 00
AI KYB Reviewer fraud prevention capabilities improved 21

AI KYB Reviewer gains fraud prevention capabilities (Sprint 122).

— No mechanism or scope described snapshot-20260806
39 00
Spanish language support for KYB new 19

Business verification (KYB) now supports the Spanish language.

— Single sentence, no config or scope detail product docs
40 00
PNG logo uploads new 19

PNG logo uploads now supported.

— One-line addition, no location named snapshot-20260806
41 00
KYB Dynamic Workflows new 19

KYB Dynamic Workflows introduced (Sprint 124).

— Named but undescribed feature snapshot-20260806
42 00
Dashboard records open in new tab improved 19

Dashboard records can now be opened in a new browser tab.

— Small UI tweak, minimally described snapshot-20260806
43 00
Turkish translation improvements for IDV improved 18

Turkish-language translations for IDV flows were improved.

— No specifics on what changed product docs
44 00
Watermarks on PDFs new 15

Watermarks on PDFs added (Sprint 122).

— One-line addition, no configuration detail snapshot-20260806
Was this useful?

Clerk

Sources Blog / feed → 1 release · 2026-08-05 Blog

Clerk is a user authentication and identity management platform that provides sign-up, login, and user profile management for web and mobile applications.

Clerk added Device Trust to require a second factor on new-device password sign-ins, introduced Google Workspace Directory Sync with role mapping, and published community-maintained Flutter integration docs.

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

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

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

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

01 00
Google Workspace Directory Sync new 43

Syncs users and groups directly from Google Workspace into Clerk, with support for role mapping and custom attributes.

— Names role mapping and custom attributes but no setup steps Google Workspace Directory Sync (2026-08-05)
02 00
Device Trust for new-device sign-ins new 38

A new Device Trust capability automatically requires a second factor when a user signs in with a password from a new device and has not enabled 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..

— Explains behaviour but no config surface or flag named product docs
03 00
Community-maintained Flutter integration docs new 23

Adds community-maintained Flutter integration support, with dedicated documentation for integrating Clerk into Flutter applications.

— Only states docs exist, no specific API or steps given product docs
Was this useful?

SailPoint

Sources Blog / feed → 1 release · 2026-07-22 Blog

SailPoint is an identity governance and access management platform that automates user access provisioning, certification, and compliance across enterprise systems.

SailPoint introduced Agentic Fabric, a full AI agent and non-human identitynon-human identityA non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. governance layer for Identity Security Cloud spanning endpoint and browser sensors, SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents./EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device. and cloud source connections, a unified Non-Human Identity Registry, sanctioned/unsanctioned app classification, identity graphs, audit reporting, and configurable aggregation, alongside new Dark Mode support across Agentic Fabric and select Identity Security Cloud pages.

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

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

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

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

01 01
Endpoint agent sensor for AI discovery new 70

A background endpoint agent, managed by navigating to Admin > Global > Agent Settings > Sensors and selecting the Endpoint Agent tab, discovers AI agent software installed on managed laptops and desktops.

After activating Agentic Fabric, manage the endpoint agent sensor that discovers AI software running on corporate endpoints.
📍In Identity Security Cloud, go to Admin › Global › Agent Settings › Sensors, then select the Endpoint Agent tab to view and update endpoint agent configuration.
— Exact admin path given; describes purpose but not internals. product docs
02 02
SIEM and EDR connections for agent monitoring new 68

Navigating to Admin > Global > Agent Settings and selecting SIEM and EDR Connections lets admins connect EDR or SIEM platforms so Agentic Fabric can discover and monitor AI agents.

Connect an EDR or SIEM platform post-activation so Agentic Fabric can automatically find available data sources for AI agent monitoring.
📍In Identity Security Cloud, go to Admin › Global › Agent Settings, then select SIEM and EDR Connections from the left panel to add or update your EDR/SIEM integration.
— Exact nav path and example steps, but UI-only action. product docs
03 03
Identity provider correlation for AI agent ownership new 68

Under Admin > Security Settings > Service Provider, admins manage identity providersidentity providersA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. (Microsoft Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. or Okta) post-activation to correlate human identities to the AI agents they own.

— Named path and providers, but no example walkthrough. product docs
04 04
Business Apps sanction status grouping new 68

A new Business Apps grouping lets administrators declare a sanction status — sanctioned, unsanctioned, or unknown — for logical applications and agents, with matching agents automatically inheriting that classification.

Classify which AI tools and agents are permitted or prohibited so that matching agents automatically inherit the sanctioned/unsanctioned status.
📍In Identity Security Cloud, go to Agentic Fabric › Business Apps, select a business app, and set its sanction status to Sanctioned, Unsanctioned, or Unknown.
— Exact statuses and example steps, though UI-only. product docs
05 05
Cloud platform sources for non-human identity aggregation new 65

Via Admin > Connections > Sources, admins connect cloud platforms (AWS, Azure, and other AI platforms) as sources for aggregating non-human identitiesnon-human identitiesA non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls..

— Named path and platforms, no example given. product docs
06 06
Browser extension sensor for GenAI governance new 60

A browser extension sensor, managed via Admin > Global > Agent Settings > Sensors under the Browser Extension tab, governs GenAI usage across managed and unmanaged SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. environments.

— Named admin path but no usage example provided. product docs
thinner coverage below
07 07
Configurable per-dataset aggregation for non-human identities new 57

A datasets and resources model lets SailPoint sources aggregate non-human identities, AI agents, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers, credentials, and 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. role objects on a configurable per-dataset aggregation schedule.

— Names object types and schedule concept, no exact config key. product docs
08 08
Non-Human Identity Trends widget new 55

A new widget on the MySailPoint home page shows total non-human identity counts over a selected time window, with day-level detail available on hover.

— Describes behaviour but no interaction steps. product docs
09 09
Non-Human Identity Registry new 50

A new unified Non-Human Identity Registry centralizes discovery and management of agents, applications, accounts, MCP servers, credentials, and endpoints.

— Names object types covered but no navigation or config given. product docs
10 10
Audit and compliance reporting for AI agents new 45

Audit and compliance reporting produces auditor-ready records covering agent inventory, ownership, action audit trails, and compliance evidence packaging.

— Lists record types but no access path or format. product docs
11 00
Dark Mode across Agentic Fabric and ISC new 45

Dark Mode support is added across SailPoint Agentic Fabric and a select number of Identity Security Cloud pages, and is user-configurable per account. Custom branding colors are not applied in Dark Mode and continue to appear only in Light Mode.

— Describes scope and branding caveat, no toggle location named. Enhancement: Dark Mode Support Across SailPo…
12 11
Continuous shadow AI monitoring and alerts new 42

Continuous post-activation monitoring fires shadow AI alerts for unsanctioned tools and updates identity correlations in real time.

— Describes alerting behaviour, no configuration detail. product docs
13 12
Embedded Identity Graph per agent new 40

An embedded Identity Graph is now available per agent and per application for visualizing relationships between non-human identities.

— Describes purpose only; no interaction detail. product docs
└──▷ BREAKING ON UPGRADE
  • !
    Custom branding colors will not be applied in Dark Mode — they continue to appear in Light Mode only.
Was this useful?
◆  Data Security & DLP

Immuta

Sources Release page → 1 release · seen 2026-08-06 Notes

Immuta is a data governance platform that controls access to sensitive data and ensures compliance through automated policies and masking.

Immuta shipped a native Trino/Starburst integration with direct policy enforcement on Trino objects, alongside a Connections UI overhaul adding health-state indicators, per-object policy sync controls, tag inheritance, and Redshift automated data discovery — plus several breaking changes affecting Databricks query audit and Snowflake policy roles.

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

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

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

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

01 01
Native Trino/Starburst integration new 70

A new Trino integration lets teams register a Trino connection so Immuta can administer access controls and enforce Immuta policies directly on objects and end-user access within Trino. It includes customizable Trino plugin properties to tailor the plugin configuration, write access mapping to customize how read/write access policies are enforced for Starburst (Trino), rotation of the system API key for the integration, and supported authentication methods and audit features for compliance.

— Describes mechanism and config surfaces but no exact commands product docs
02 00
Automated data discovery for Redshift viewless integration new 65

Automated sensitive data discovery now supports Immuta's Amazon Redshift viewless integration, covering regex, dictionary, and column-name-regex identifier types.

— Names integration and identifier types supported snapshot-20260806
03 00
Per-object policy sync toggle new 60

A new per-object policy sync setting in Connections controls whether Immuta pushes policy down to the data platform for a given data object, showing a Custom label when a child object's setting differs from its parent's.

— Names the setting and UI label, no exact steps snapshot-20260806
04 00
Configurable New tag behavior new 60

App Settings now includes a configurable New tag behavior, enabled by default for columns and disabled by default for data sources.

— Names exact setting location and defaults snapshot-20260806
05 00
New Immuta-managed built-in groups new 60

Three new Immuta-managed built-in groups — All Agents, All Users, and All Identities — are now available for use in subscription policies and data policies.

— Names the exact groups and where they apply snapshot-20260806
thinner coverage below
06 00
Connection health state indicator new 55

Connections in the Connections UI now display an ACTIVE, INACTIVE, or UNHEALTHY health state for Databricks Unity Catalog and Snowflake integrations.

— Names states and UI location but no workflow detail snapshot-20260806
07 00
Tag inheritance at database/schema level new 50

Tags can now be inherited at the database or schema level, with bulk assignment or removal propagating to all attached data sources.

— Explains behavior but no config path given snapshot-20260806
08 00
Snowflake resync covers subscription policies improved 50

Snowflake data policy resync now resyncs both data policies and subscription policies when triggered from a data source health check.

— Names trigger and scope, no manual steps given snapshot-20260806
09 00
Force-delete unhealthy connections new 45

Connections in an UNHEALTHY state can now be force-deleted.

— Clear capability, minimal mechanism explained snapshot-20260806
10 00
Integration settings moved into Connections UI improved 45

Integration settings for Databricks Unity Catalog and Snowflake connections now live directly within the Connections UI rather than in a separate settings area.

— Names new UI location, little further detail snapshot-20260806
11 00
Detail pages for leaf data objects new 40

New detail pages exist for leaf data objects in Connections, each including a direct link to the corresponding data source.

— Names UI surface, little mechanism detail snapshot-20260806
12 02
Snowflake integration error banners removed breaking 40

Integration error banners for Snowflake integration validation failures will no longer be displayed; errors will instead appear in the new Connections experience.

— States change but not exact new error location snapshot-20260806
└──▷ BREAKING ON UPGRADE
  • !
    Starting August 26, 2026, Databricks will mask query_text in the query_history system table by default; Immuta query audit will no longer contain query text and all query audit events will show as Indeterminant unless the Immuta service principal is added to the databricks_pii_access group in Databricks.
  • !
    Immuta policy role names used to grant users access to Snowflake data sources will be renamed and recreated as part of the Snowflake integration architecture update rolling out from July 23, 2026 (user role names remain unchanged).
  • !
    Integration error banners for Snowflake integration validation failures will no longer be displayed; errors will instead appear in the new Connections experience.
Was this useful?
◆  Secure Access (VPN / SASE / ZTNA)

OpenVPN

Sources Release notes →Source code → 1 release · 2026-08-06 Notes Code

OpenVPN is an open source VPN daemon

OpenVPN v2.7.6 simplifies default configuration by making tun the implicit device and enabling TCP_NODELAY by default, while capping keepalive timers at 24 hours.

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

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

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

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

01 01
TCP_NODELAY enabled by default breaking 78

The TCP_NODELAY socket flag is now always enabled on the local socket, whereas previously it required --tcp-nodelay. In server mode, --tcp-nodelay now specifically pushes socket-flags TCP_NODELAY to clients that may not have this default.

— Explains mechanism and server-side push behavior with flag names. v2.7.6
02 00
Default device changed to tun improved 70

Omitting --dev from an OpenVPN config now defaults to --dev tun, removing a previously required boilerplate option for the common tun case.

— Names exact flag and default change, no example. v2.7.6
03 02
24-hour cap on ping and keepalive intervals breaking 70

The --ping and --keepalive options now reject values exceeding 86400 seconds (24 hours); configs with larger values will need to be updated.

— Gives exact limit and required migration action. v2.7.6
└──▷ BREAKING ON UPGRADE
  • !
    The --ping and --keepalive options now reject values exceeding 86400 seconds (24 hours); configs with larger values will need to be updated.
  • !
    TCP_NODELAY is now enabled by default on all sockets; previously it was opt-in via --tcp-nodelay.
Was this useful?

Zscaler

Sources Blog / feed → 1 release · 2026-08-05 Blog

Zscaler is a cloud-based security platform providing zero-trust network access, threat prevention, and data protection for organizations.

Zscaler shipped AI Guard integration with Anthropic's Claude inference hooks, extending Zero Trust DLPDLPData Loss Prevention: a category of controls that inspect and block sensitive data from leaving an organisation via email, web, or removable media, giving cyber tools a policy enforcement layer over data in motion and at rest. policy enforcement directly into the Claude model layer.

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

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

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

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

01 01
AI Guard integration with Claude inference hooks new 62

Zscaler AI Guard integrates with Anthropic Claude inference hooks to enforce Zero Trust data-loss-prevention policy natively at the Claude model layer, evaluating full conversation context in real time rather than individual messages. Existing Zscaler platform policies extend to Claude Enterprise touchpoints with no additional governance stack required, and existing Zscaler customers can activate the feature using their current policy configuration.

— Names product and integration point but no config key or endpoint. 2026-08-05-1bd71b85
Was this useful?

ScoutDNS

Sources Release page → 1 release · seen 2026-08-06 Notes

ScoutDNS is a DNS reconnaissance and security tool that maps domain infrastructure, identifies misconfigurations, and monitors DNS records for vulnerabilities.

ScoutDNS shipped a ground-up console redesign this cycle, adding explicit match/subtree controls and comments for allow/block list rules, an auto-generated Zero Trust TLDTLDThe rightmost label in a domain name (e.g., .com, .gov, .uk), maintained by IANA's root zone. Cyber tools filter or pivot on TLDs to scope scans, flag suspicious registrations, or classify traffic by geography or type. allowlist, per-policy Secure Scores, a cross-tenant MSPMSPA managed service provider, a company that operates IT services for customers. It may manage systems, networks, backups or other ongoing technology needs. dashboard, and dark mode.

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

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

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

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

01 00
Match/subtree option on allow/block list rules new 65

Every custom allow/block list rule now carries a match or subtree option that makes explicit whether the rule covers a single hostname or a domain and all its subdomains; a single wildcard entry using subtree now covers both the domain and its subdomains, removing the need for two separate entries.

— Names the exact rule option but no config path shown The all-new ScoutDNS console is live
02 00
Auto-generated Zero Trust TLD allowlist new 62

Zero Trust TLD filtering can now auto-generate a TLD allowlist from the last 30 days of real query traffic for any organization.

— Clear mechanism and lookback window, no UI path given The all-new ScoutDNS console is live
thinner coverage below
03 00
Deployments subtab on Policies page new 57

A new Deployments subtab on the Policies page shows every policy assignment across sites, profiles, and personas in one account-wide view, with inline editing.

— Names exact UI location and scope, no deeper mechanism The all-new ScoutDNS console is live
04 00
Per-policy Secure Score new 53

Each policy now carries a 0–100 Secure Score with a per-item breakdown showing what to enable to raise it.

— Scale and breakdown named, no navigation path given The all-new ScoutDNS console is live
05 00
Stateful site health based on WANs and relays improved 45

Sites now report stateful up/down health based on WANs and relays rather than recent query volume, changing how connectivity status is determined.

— Explains the before/after but no config or metric detail The all-new ScoutDNS console is live
06 00
MSP dashboard for cross-tenant view new 45

A new MSP dashboard under the Organizations tab gives a cross-tenant view of all managed accounts.

— Names tab location, lacks detail on what's shown The all-new ScoutDNS console is live
07 00
Comments on allow/block list entries new 37

Comments can now be added to any allow or block list entry to preserve the reason a rule was created.

— Simple feature stated plainly, no further mechanism given The all-new ScoutDNS console is live
08 00
Dark mode in console new 30

Dark mode is now available, selectable from the console header.

— Bare description with a UI location, nothing more The all-new ScoutDNS console is live
09 00
Rebuilt help site with full-text search improved 28

The help site was rebuilt with full-text search and current screenshots for every tab and function.

— Documentation update stated with minimal further detail The all-new ScoutDNS console is live
Was this useful?
Governance, Risk & Compliance
◆  Continuous Control Monitoring (CCM)

RegScale

Sources Blog / feed → CLI 6.38.0 (2026-08-06) Blog

RegScale is a compliance and regulatory management platform that automates governance, risk, and compliance (GRC) workflows for organizations.

RegScale CLI 6.38.0 adds eMASSeMASSA U.S. DoD web application that manages the Risk Management Framework process, tracking system authorizations, controls, and POA&Ms so cyber tools can automate compliance reporting into a single authoritative record. CAC authentication support for custom CA bundles (e.g. DoD PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets.) via config, env var, and CLI flag.

└──▷ TRY IT
Register an eMASS API connection trusting a DoD PKI CA bundle when running in a CI/CD pipeline where env vars are preferred over config files.
$ EMASS_SSL_CA_CERT=/etc/ssl/dod-root-ca.pem regscale emass_api register
Persist the DoD PKI CA bundle path in the RegScale config so all eMASS commands trust it without repeating the flag.
yaml
emass:
  ssl_ca_cert: /etc/ssl/dod-root-ca.pem
Supply the CA bundle inline at registration time without modifying config or environment.
$ regscale emass_api register --ca-cert /etc/ssl/dod-root-ca.pem
  • Adds emass.ssl_ca_cert config key to trust a custom CA bundle (e.g. DoD PKI) when verifying the eMASS server certificate during CAC authentication.
  • Adds EMASS_SSL_CA_CERT environment variable as an alternative to emass.ssl_ca_cert for supplying the custom CA bundle path.
  • Adds --ca-cert option to the emass_api register command to specify the custom CA bundle at registration time.

3 details in Everything

Was this useful?
Build
◆  AI Coding Agents

Cline

Sources Release notes →Source code → 4 releases · 2026-08-05 → 2026-08-06 Notes Code

Autonomous coding agent as an SDK, IDE extension, or CLI assistant.

Cline this window focused on model catalog updates and a major overhaul of reasoning-effort handling, standardizing it across all AI SDK providers including Ollama, alongside a friendlier UX for retired free-model promotions.

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

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

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

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

01 01
Unified reasoning effort control across AI SDK providers breaking 65

Reasoning effort settings (effort levels and enable/disable toggles) now map to a shared path across all AI SDK providers, including Ollama, instead of going through per-provider thinking overrides; disabling reasoning is respected everywhere. Per-provider thinking overrides are replaced by the AI SDK's native reasoning setting, so existing configurations relying on those overrides will need to be updated.

— Explains mechanism and migration need but no exact config key given. cli-v3.0.51sdk/sdk/v0.0.71v4.1.5
thinner coverage below
02 00
meta/muse-spark-1.2-contributor added to Cline provider new 50

Adds meta/muse-spark-1.2-contributor as a selectable model on the Cline provider, alongside a refreshed model catalog.

— Names the exact model id but no further detail on catalog changes. v4.1.6cli-v3.0.51sdk/sdk/v0.0.71
03 00
Dedicated notice for retired free model promotions new 40

When a retired free model is requested, Cline shows a dedicated notice with a button to pick another model, instead of a generic error with only a Retry prompt.

— Describes behavior change but no UI path or config named. v4.1.5
└──▷ BREAKING ON UPGRADE
  • !
    Per-provider thinking overrides are replaced by the AI SDK's native reasoning setting; existing configurations relying on those overrides will need to be updated.
Was this useful?

OpenAI Codex CLI

Sources Release notes →Source code → 5 releases · 2026-08-05 → 2026-08-06 Notes Code

Lightweight coding agent that runs in your terminal

OpenAI Codex CLI's rust v0.147.0 alpha series added per-session code-mode execution limits, a --concurrent-requests flag for the exec-server, managed authentication enforcement via requirements.toml, Amazon Bedrock hosted web search with cached fallback, and new thread-section and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. APIs, alongside a long tail of sandboxingsandboxingRunning code inside a restricted environment that limits what it can access or change. The isolation reduces the impact of mistakes or untrusted code, depending on the sandbox's controls., telemetry, and TUITUIA text-based user interface that runs inside a terminal, using characters and ANSI escape codes to render menus, panes, and widgets without a graphical desktop, letting cyber tools ship rich interactivity with no GUI dependency. reliability improvements.

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

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

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

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

01 00
`--concurrent-requests` flag for exec-server new 88

Adds --concurrent-requests flag (alias concurrent-requests, default 1) to the exec-server subcommand to enable opt-in concurrent request dispatch across connections, e.g. codex exec-server --concurrent-requests 4 --listen ws://127.0.0.1:9000.

Run the exec-server with concurrent request processing enabled to handle multiple client requests in parallel.
$ codex exec-server --concurrent-requests 4 --listen ws://127.0.0.1:9000
— Exact flag, default and runnable example given. rust-v0.147.0-alpha.10
02 00
Managed auth enforcement via `requirements.toml` new 83

Enforces managed authentication requirements locally via a requirements.toml allowlist for login methods and ChatGPT workspaces, combining managed and existing workspace restrictions by intersection and failing closed when no usable login method remains.

— Config file and logic named; exact schema not given. rust-v0.147.0-alpha.12
03 00
`create_session_with_limits` for per-session execution caps new 78

Adds create_session_with_limits and session-scoped cell execution limits via CodeModeSessionCellExecutionLimits, clamping execute and wait yield times to max_yield_time_ms without terminating the running cell.

— API names and field given but no calling example shown. rust-v0.147.0-alpha.11
04 00
`thread/section/move` API and section ordering new 73

Adds a thread/section/move API endpoint and section_position sorting to thread/list, allowing threads to be reorganized into sections and listed in section order.

— API names given but no request/response schema shown. rust-v0.147.0-alpha.13
05 00
Guardian reviews switch to `gpt-5.6-luna` for API-key auth improved 72

Switches Guardian approval reviews authenticated with an API key to use gpt-5.6-luna, while retaining codex-auto-review for ChatGPT authentication; falls back to the bundled Guardian policy when the selected model has no catalog-provided review policy.

— Models and fallback named but no configuration surface exposed. rust-v0.147.0-alpha.11
06 00
`image_resize_notice` developer message feature new 70

Adds the disabled-by-default image_resize_notice feature: when enabled, it appends a developer message after resized images in user messages or tool outputs, reporting each image's original and prepared dimensions.

— Mechanism and flag named but no enable command shown. rust-v0.147.0-alpha.12
07 00
Hidden --psp flag for PSP routing new 65

A hidden, global --psp flag was added to the main CLI and app-server to enable process-scoped PSP routing of first-party ChatGPT requests.

— Flag named but usage and routing effect not detailed. rust-v0.147.0-alpha.13rust-v0.147.0-alpha.10
08 00
Amazon Bedrock hosted web search with cached fallback new 64

Enables hosted web search for Amazon Bedrock, automatically resolving unsupported live and indexed modes to cached search, or disabling the tool when cached search is prohibited by managed requirements.

— Fallback logic described but no toggle flag given. rust-v0.147.0-alpha.6.5rust-v0.147.0-alpha.10
09 00
500 ms bound on TUI telemetry shutdown improved 63

Bounds interactive TUI telemetry shutdown to a 500 ms budget via OtelProvider::shutdown_with_timeout, preventing a stalled OTLPOTLPOpenTelemetry Protocol, a standard way to send traces, metrics and logs between applications, collectors and monitoring systems. It lets telemetry move across compatible tools. exporter from blocking indefinitely on exit.

— Exact timeout and API named, no user config exposed. rust-v0.147.0-alpha.11
10 00
Case-insensitive Windows path URI comparisons improved 60

Makes Windows path URI comparisons ASCII-case-insensitive for drive and UNC paths while preserving case-sensitive POSIXPOSIXA family of standards for operating-system interfaces, including process, file and shell behavior. Software that uses these interfaces is easier to move between compatible systems. behavior, including starts_with and relative_path_from operations.

— Named operations given but no user-facing example. rust-v0.147.0-alpha.12
thinner coverage below
11 00
`McpBinding` caching per MCP runtime improved 58

Caches McpBinding per published MCP runtime once the tool catalog revision is stable, reusing it across sampling steps and rebuilding only after a runtime publish or catalog change.

— Internal caching mechanism described, no user-facing action. rust-v0.147.0-alpha.11
12 00
Symlinked skill discovery path preservation improved 53

Preserves discovery paths for symlinked skills in the skill catalog, allowing either the discovery path or canonical path to be used for structured selections and linked skill mentions.

— Mechanism described but no catalog location or command. rust-v0.147.0-alpha.12
13 00
Secret redaction in app-server command execution display improved 46

Redacts secrets, including bearer tokensbearer tokensA credential that grants access to whoever presents it, without a separate proof of possession. Protecting the token matters because a stolen copy can be used by someone else., from app-server command execution items in display output.

— Specifies bearer tokens but no redaction pattern or config. rust-v0.147.0-alpha.10
14 00
`shell_command` restricted to single local environment improved 45

The shell_command tool is now restricted to a single local environment.

— Names the tool but no override or config option given. rust-v0.147.0-alpha.13
15 00
Trust prompt for local project directories improved 45

Prompts before trusting local project directories and rejects implicitly discovered bare Git repositories.

— Behaviour described, no exact prompt text or flag given. rust-v0.147.0-alpha.10
16 00
Skip symlinks when installing plugins improved 43

Skips symbolic links and other non-file, non-directory entries when installing plugins into the store instead of rejecting the installation.

— Behaviour change explained without exact install command. rust-v0.147.0-alpha.6.5
17 00
Name forked chats from the TUI new 42

Users can now assign names to forked chats directly from the TUI.

— UI action described but no exact command shown. rust-v0.147.0-alpha.13
18 00
MCP credential isolation by environment improved 41

Hosted MCP credentials are now restricted to local environments, and MCP OAuthMCP OAuthAn authentication layer for the Model Context Protocol that lets MCP clients obtain delegated access tokens so cyber tools can call MCP servers on a user's behalf without handling raw credentials. credentials are isolated by environment.

— Explains scope but no config surface named. rust-v0.147.0-alpha.13
19 00
Cloud-managed MCP servers in CLI commands improved 40

MCP CLI commands now load cloud-managed servers in addition to locally configured ones.

— One-line description, no command names given. rust-v0.147.0-alpha.13
20 00
Tool registry collision policy configuration new 38

Adds tool registry collision policy configuration with strict tool name collision errors enforced.

— Policy named but no config key or values given. rust-v0.147.0-alpha.10
21 00
MCP read-only hints in tool call items new 35

Tool call items now expose MCP read-only hints, surfacing whether a called MCP tool is read-only.

— Brief description without schema or UI location. rust-v0.147.0-alpha.13
22 00
Deny network access on failed allow amendment improved 35

Network access is now denied when an allow amendment fails, closing a previous path that could permit access.

— Behaviour change described without trigger conditions. rust-v0.147.0-alpha.13
23 00
Legacy Linux bundle archives no longer published breaking 35

Legacy Linux bundle archives are no longer published as release artifacts.

— States removal but no migration guidance given. rust-v0.147.0-alpha.13
24 00
Paginated transcript history in TUI improved 30

Paginates transcript history in the TUI for large threads.

— Feature named without page size or navigation detail. rust-v0.147.0-alpha.10
25 00
Attempted tool calls recorded in response metadata new 29

Attempted tool calls are now recorded in response metadata.

— Brief mention without metadata schema. rust-v0.147.0-alpha.13
26 00
Normalized sandbox violation events recorded new 29

Sandbox violation events are now recorded in a normalized format.

— No detail on where events surface or their format. rust-v0.147.0-alpha.13
27 00
Option to disable built-in image viewer new 28

Allows disabling the built-in image viewer.

— Mentions toggle exists but no flag or config key given. rust-v0.147.0-alpha.10
28 00
Distinct unknown MCP authentication status improved 27

The CLI now distinguishes an unknown MCP authentication status from other authentication states.

— Minimal description, no state names or UI given. rust-v0.147.0-alpha.13
29 00
Durable per-thread user submission queues new 27

Adds durable per-thread user submission queues.

— Bare mention without persistence mechanism detail. rust-v0.147.0-alpha.10
30 00
Detects connectors in external agent sessions new 25

The CLI now detects which connectors are used in external agent sessions.

— One-line mention, no connector list or usage. rust-v0.147.0-alpha.13
31 00
Remote compaction for Amazon Bedrock new 23

Enables remote compaction for Amazon Bedrock.

— One-line mention without mechanism explained. rust-v0.147.0-alpha.10
32 00
Support for Enterprise automation account plans new 21

Adds support for Enterprise automation account plans.

— Bare mention with no setup or scope detail. rust-v0.147.0-alpha.13
33 00
Skills enabled in the MCP server new 21

Enables skills within the MCP server.

— Single-line mention with no mechanism given. rust-v0.147.0-alpha.13
34 00
Safer TUI defaults for cyber models improved 19

Adds safer TUI defaults for cyber models.

— Bare mention with no specifics on what changed. rust-v0.147.0-alpha.10
└──▷ BREAKING ON UPGRADE
  • !
    Legacy Linux bundle archives are no longer published.
Was this useful?

Claude Code

Sources Release notes →Source code → 1 release · 2026-08-06 Notes Code

Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.

Claude Code v2.1.223 adds owner-level wildcard controls for marketplace allow/block lists, a /teleport command for moving cloud sessions to a local machine, and an upgraded /code-review with effort levels and PR targeting, alongside new env vars for controlling context-window behavior.

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

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

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

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

01 00
/code-review effort levels and PR targeting improved 95

Makes /review an alias of /code-review; /code-review now accepts an effort level and PR number via /code-review <level> <pr#>, with /code-review ultra triggering a deep cloud review (e.g. /code-review ultra 4321). It also remembers the last effort level used when invoked without one, so repeat reviews don't require retyping the level.

Run a deep review of a pull request straight from the terminal using the new effort-level syntax.
$ /code-review ultra 4321
— Exact command syntax and runnable example given v2.1.223
02 00
Owner wildcard marketplace controls new 90

Adds "owner/*" wildcard entries to strictKnownMarketplaces and blockedMarketplaces managed settings, allowing or blocking all marketplace repos under a GitHub org in a single entry, e.g. {"blockedMarketplaces": ["acme-corp/*"]}.

Block all marketplace repos from a specific GitHub org in managed settings with a single wildcard entry instead of listing each repo.
json
{
  "blockedMarketplaces": ["acme-corp/*"]
}
— Exact config keys and runnable example given v2.1.223
03 00
/teleport cloud-to-local session handoff new 80

Adds a claude --teleport <session id> flag and a /teleport hint shown in cloud sessions, letting a user continue a cloud session locally.

Pick up a cloud session on your local machine when you need to switch environments mid-task.
$ claude --teleport <session id>
— Exact command shown, underlying mechanism unexplained v2.1.223
04 00
Expanded 1M context auto-compaction cap improved 70

Expands CLAUDE_CODE_DISABLE_1M_CONTEXT to cap every Claude model with a native 1M context windowcontext windowThe maximum amount of text, counted in tokens, a model can take in and produce in one request. Everything the model knows about the task has to fit inside it. to 200K via auto-compaction, rather than only a fixed model list, and adds a startup warning when auto-compaction isn't holding the session to 200K.

— Named env var and behavior, no usage example v2.1.223
05 00
Opt-out of unknown model context window enforcement new 70

Adds CLAUDE_CODE_DISABLE_UNKNOWN_MODEL_WINDOW_ENFORCEMENT=1 env var to opt out of the new behavior that keeps sessions on unrecognized model IDs within the assumed context window.

— Named env var given, no example command v2.1.223
thinner coverage below
06 00
Warning for restricted subagent model fallback new 45

Adds a warning when a workflow agent, forked skill, slash command, or resumed background agent's requested subagent model is restricted and the parent model runs instead.

— Describes behavior only, no named surface or example v2.1.223
Was this useful?

OpenCode

Sources Release notes →Source code → 1 release · 2026-08-05 Notes Code

The open source coding agent.

OpenCode adds Poolside as a supported provider with self-hosted deployment configuration, and streamlines xAI (Grok) authentication with a device-code OAuth flow alongside API key access.

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

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

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

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

01 00
Poolside provider support with self-hosted deployment config new 95

OpenCode adds Poolside as a supported provider via its OpenAI-compatible API, with API keys configured at platform.poolside.ai or stored locally at ~/.secrets/poolside-key for self-hosted deployments. Self-hosted Poolside instances are set up as a custom OpenAI-compatible provider with a custom provider ID and base URL (e.g. https://poolside.example.com/openai/v1), discovering model IDs via the /openai/v1/models endpoint, and support the reasoning_content field plus interleaved reasoning mode for thinking-capable models.

Configure a self-hosted Poolside deployment as a custom provider, storing credentials outside the config file.
json
{
  "id": "poolside-deployment",
  "name": "Poolside deployment",
  "baseURL": "https://poolside.example.com/openai/v1",
  "apiKey": "{file:~/.secrets/poolside-key}",
  "models": [
    {
      "id": "<served-model-id>",
      "name": "Poolside deployment model",
      "reasoning": "interleaved",
      "field": "reasoning_content"
    }
  ]
}
— Named endpoint, file path and full JSON config example included. product docs
02 00
xAI (Grok) authentication via SuperGrok OAuth and API key improved 60

OpenCode adds two xAI authentication paths: a SuperGrok subscription via device-code OAuth, where OpenCode opens xAI's verification link with the user code pre-populated and automatically polls the token endpoint, or a pay-as-you-go API key obtained from the xAI console. In v1.18.14 this login flow was simplified to a single device-code flow to better support headless and remote environments.

— Describes mechanism and simplification but gives no exact command. v1.18.14
Was this useful?

OpenHands

Sources Release notes → 1 release · 2026-08-05 Notes

OpenHands: AI-Driven Development

OpenHands v1.10.0 adds activity log export, a featured automations dashboard, manifest-driven automation sub-pages, faceted skills filtering, and switches Canvas's default model to GLM 5.2.

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

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

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

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

01 00
Faceted skills filtering new 40

Adds faceted rail filtering to the Skills page for faster skill discovery.

— Names UI location (Skills page) but no filter facets listed v1.10.0
02 00
Manifest-driven automation sub-pages new 35

Adds manifest-driven sub-pages to the automation interface, enabling structured automation workflows.

— Mentions manifest-driven mechanism but no schema or file path v1.10.0
03 00
GLM 5.2 default model for Canvas improved 35

Sets GLM 5.2 as the default model for Canvas.

— Names specific model and feature but no config or override info v1.10.0
04 00
Featured automations landing dashboard new 30

Ships a featured automations landing dashboard for discovering and launching automations.

— Describes purpose but no navigation path or details v1.10.0
05 00
Activity log export new 25

Adds activity log export capability to the interface.

— Names the capability but no format or location given v1.10.0
Was this useful?
Agent
◆  AI Agent Frameworks

CrewAI

Sources Release notes → 1 release · 2026-08-05 Notes

Framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.

CrewAI 1.15.12 consolidates project scaffolding into a single command, adds a URL-reading tool for agent workflows, and attaches app metadata to platform action tools.

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

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

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

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

01 00
Unified `crewai create <resource>` scaffolding improved 70

Replaces separate scaffold commands with a single unified crewai create <resource> command for generating new CrewAI resources such as crews or flows.

Scaffold a new CrewAI resource (crew, flow, etc.) using the unified create command.
$ crewai create <resource>
— Names exact command, runnable as given 1.15.12
thinner coverage below
02 00
URLReadTool for reading arbitrary URLs new 40

Adds URLReadTool, letting agent workflows read arbitrary URLs.

— Names the tool but no usage detail 1.15.12
03 00
App metadata on platform action tools improved 20

Adds app metadata to platform action tools, per the release notes.

— Bare mention, no mechanism or fields named 1.15.12
Was this useful?
Deploy
◆  Local LLM Runtimes

Ollama

Sources Release notes →Source code → 1 release · 2026-08-04 Notes Code

Get up and running with Kimi-K2.6, GLM-5.2, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.

Ollama v0.32.6 brings OpenAI-compliant streaming usage reporting and automatic speculative decodingspeculative decodingSpeeding up generation by letting a small draft model guess several tokens ahead and having the large model check them all at once. Output is unchanged; accepted guesses save time. for Qwen3.5 on Apple GPUsGPUsA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference., while removing the experimental image generation feature.

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

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

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

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

01 00
stream_options.include_usage in chat completions API improved 90

Adds stream_options.include_usage support in /v1/chat/completions so usage is returned in a separate trailing chunk, matching OpenAI's streaming wire format — role now appears only on the first chunk and finish_reason on its own chunk.

Stream a chat completion and receive token usage in a separate trailing chunk, matching OpenAI's wire format.
$ curl http://localhost:11434/v1/chat/completions -d '{"model": "gemma4", "stream": true, "stream_options": {"include_usage": true}, "messages": [{"role": "user", "content": "Why is the sky blue?"}]}'
— Named endpoint, field, and runnable curl example provided v0.32.6
thinner coverage below
02 00
Automatic MTP speculative decoding for Qwen3.5 on Apple GPUs improved 50

Qwen3.5 inference on Apple GPUs is faster because the MLXMLXApple's machine-learning framework for Apple silicon, which uses the unified memory shared by CPU and GPU to run and fine-tune models on a Mac. engine now automatically uses the model's MTP head for speculative decoding.

— Explains mechanism but no config or flag to invoke it v0.32.6
03 00
Experimental image generation removed breaking 45

Experimental image generation has been removed in v0.32.6; users must continue using v0.32.5 for image generation support.

— Clear removal noted with version to revert to v0.32.6
└──▷ BREAKING ON UPGRADE
  • !
    Experimental image generation is no longer available in v0.32.6; the feature has been removed and requires staying on v0.32.5.
Was this useful?
Govern
◆  AI/LLM Security

Giskard

Sources Release notes → 1 release · 2026-08-06 Notes

Open-Source Evaluation & Testing library for LLM Agents

Giskard v1.0.1b6 extends its vulnerability scanner with third-party integration, tightens judge check reliability, and exposes internal scan generators publicly.

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

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

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

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

01 00
Public export of default registry generators improved 60

Default registry generators are now exposed on the public API via chore(scan): export default registry generators on the public API, making it easier to inspect and reuse built-in ScenarioGenerator instances.

— Names API export and ScenarioGenerator class but no usage example. giskard-core/v1.0.1b6
thinner coverage below
02 00
Third-party scan integration in vulnerability_scan new 55

vulnerability_scan now integrates third-party scan support via the new feat(scan): integrate third party scan capability, extending the scanner beyond its built-in generators.

— Names the function and capability but not the third-party interface. giskard-core/v1.0.1b6
03 00
Non-blank judge reason enforcement improved 50

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.-as-judge checks now enforce non-blank judge reasons — evaluations that return an empty reason string fail explicitly instead of silently passing.

— Explains behaviour change clearly but no config/flag given. giskard-core/v1.0.1b6
Was this useful?

ToolHive

Sources Release notes → 1 release · 2026-08-05 Notes

ToolHive is an enterprise-grade platform for running and managing Model Context Protocol (MCP) servers.

ToolHive's v0.42.0 release introduces a full CLI 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. for AI-tool plugin management via thv ai-plugin, complete with a registry catalog and Sigstore signature verification, alongside concurrent stdio-server sharing across 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. clients — and ships several breaking changes touching CRDCRDA Kubernetes extension that adds a new object type to the cluster, so a tool's configuration is stored, validated and versioned by Kubernetes itself rather than in a file beside it. status fields, Cedar authorization ordering, panic logging, and internal telemetry APIs.

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

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

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

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

01 00
Removed status.referencingWorkloads fields from config CRDs breaking 90

status.referencingWorkloads and status.referenceCount fields (and the References printer column) are removed from all six config CRDsCRDsA Kubernetes extension that adds a new object type to the cluster, so a tool's configuration is stored, validated and versioned by Kubernetes itself rather than in a file beside it. (MCPOIDCConfig, MCPAuthzConfig, MCPExternalAuthConfig, MCPToolConfig, MCPWebhookConfig, MCPTelemetryConfig); replace any automation that reads them with workload field queries.

— Names exact CRDs, fields, and required migration path v0.42.0
02 00
Cedar authorization evaluated post-mutation breaking 90

Cedar authorization policy is now evaluated against the post-mutation MCP request — if you run a mutating webhook (--webhook-config with a mutating: entry, or MCPWebhookConfig.spec.mutating) alongside Cedar authz, policy decisions and audit records (type, target.name) can change on upgrade; re-audit policies against the post-mutation shape before upgrading.

— Details exact flags, audit fields, and required re-audit action v0.42.0
thinner coverage below
03 00
thv ai-plugin CLI and REST API new 55

Adds thv ai-plugin subcommand with a full CLI and REST API for end-to-end AI-tool plugin management.

— Names command and API but no endpoints or flags listed v0.42.0
04 00
Removed pkg/telemetry/providers and optimizerdec constants breaking 55

pkg/telemetry/providers was deleted and two long-published optimizerdec constants were removed from the Go API, breaking any out-of-tree importers that reference them.

— Names removed package and constants but no migration guidance v0.42.0
05 00
Sigstore signature verification for plugins new 50

Adds Sigstore signature verification for skills/plugins at install, sync, and upgrade time.

— Names trigger points but no config flag or command v0.42.0
06 00
Recovered HTTP panics no longer logged breaking 50

Recovered HTTP panics no longer emit a slog.Error log line or stack trace — setups relying on log-based alerts or support bundles to diagnose recovered panics will silently lose that diagnostic output (a patch fix is expected).

— Explains impact and notes upcoming fix, no interim action given v0.42.0
07 00
ai-plugin registry catalog new 40

Adds a registry catalog to thv ai-plugin for discovering and deploying plugins from a curated index.

— Describes purpose but no catalog commands or fields given v0.42.0
08 00
Concurrent stdio server sharing across MCP clients improved 30

Enables multiple MCP clients to share a single stdio server concurrently.

— Brief statement with no mechanism or configuration detail v0.42.0
└──▷ BREAKING ON UPGRADE
  • !
    status.referencingWorkloads and status.referenceCount fields (and the References printer column) are removed from all six config CRDs (MCPOIDCConfig, MCPAuthzConfig, MCPExternalAuthConfig, MCPToolConfig, MCPWebhookConfig, MCPTelemetryConfig); replace any automation that reads them with workload field queries.
  • !
    Cedar authorization policy is now evaluated against the post-mutation MCP request — if you run a mutating webhook (--webhook-config with a mutating: entry, or MCPWebhookConfig.spec.mutating) alongside Cedar authz, policy decisions and audit records (type, target.name) can change on upgrade; re-audit policies against the post-mutation shape before upgrading.
  • !
    Recovered HTTP panics no longer emit a slog.Error log line or stack trace — setups relying on log-based alerts or support bundles to diagnose recovered panics will silently lose that diagnostic output (a patch fix is expected).
  • !
    pkg/telemetry/providers was deleted and two long-published optimizerdec constants were removed from the Go API, breaking any out-of-tree importers that reference them.
Was this useful?
Platforms & Utilities
◆  General Utilities & Libraries

Obsidian

Sources Blog / feed → 2 releases · 2026-08-05 Blog

Obsidian is a personal knowledge management app that lets users create, link, and organize markdown notes locally with powerful search and graph visualization.

Obsidian's early-access desktop and mobile builds add a new plugin API hook, richer startup diagnostics, and several mobile tab and UI refinements including swipe-to-close tabs and proportional checkbox scaling.

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

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

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

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

01 00
SettingDefinitionBase#disabled API addition new 45

The desktop API gains SettingDefinitionBase#disabled, letting plugin developers mark setting definitions as disabled.

— Names the API field but gives no usage detail. Obsidian 1.13.5 Desktop (Early access) (2026…
02 00
Swipe-to-close gesture in tab switcher new 45

Mobile adds a swipe-to-close gesture to dismiss tabs directly from the tab switcher, with tabs animating to their new position after a tab is closed.

— Describes gesture and resulting animation, no exact UI path. Obsidian 1.13.5 Mobile (Early access) (2026-…
03 00
Icons in mobile toolbar settings improved 40

The mobile toolbar settings page now displays icons alongside each command for easier identification.

— Names the settings page but no further mechanism detail. Obsidian 1.13.5 Mobile (Early access) (2026-…
04 00
Proportional checkbox scaling improved 35

Checkboxes now scale proportionally to the configured font size on mobile.

— States behaviour change but no config key or values given. Obsidian 1.13.5 Mobile (Early access) (2026-…
05 00
More granular startup stats window improved 25

The startup stats window now shows more granular information about startup speed.

— Vague on what new metrics are shown. Obsidian 1.13.5 Desktop (Early access) (2026…
Was this useful?
browse all tools → score card for your toolchain →