PAGES
Free Head is the only free newsletter you can have delivered to your inbox — the week’s best releases, every Friday. Sign up here →

This Week's Highlights — issue 021, November 20, 2026

THE CYBER TOOLCHAIN NO. 021
Head
THE WEEK'S TOP PICKS
PUBLISHED NOVEMBER 20, 2026 · FRIDAYS
EDITIONS tail grep head ls diff uniq

The best tooling updates that shipped this week.

The week in numbers · Nov 13–19

Changes per week, last 12 weeks · Nov 13–19

Changes we read in that week's dailies, including docs and API changes. A gap means no daily was published.

468
Aug 28
593
Sep 4
591
Sep 11
732
Sep 18
640
Sep 25
922
Oct 2
570
Oct 9
533
Oct 16
519
Oct 23
825
Oct 30
1016
Nov 6
912
Nov 13

Category moves this month

Checking Plays…

Every feature release from the 1326 tools on our watchlist goes into the daily newsletter. Once a week we read the whole field side by side and grade each release from 1 to 5 on three things, weighted equally:

  • Depth. How complete is the best new capability?
  • Impact. How much does it change what you can do?
  • Novelty. Has any other tool done this before? We check every capability against the history of every tool we track. Features most tools already have earn nothing here. Being first earns the most.

A tool is judged on everything it shipped that week, so a project that releases daily gets credit for the sum — and still only takes one slot. We would rather run a short list than a padded one.

VIEW
ISSUE VIEW scroll
INFORMATION DENSITY everything
ISSUE WIDTH reading width
Do you prefer scroll?

The picks in full

01 Humanix announced · Nov 17, 2026 Firewalls & Network Defense

Humanix detects and stops social engineering attacks as they unfold across email, chat, voice, and help desk workflows.

// WHY IT MADE THE LIST Depth 4/5 Impact 5/5 Novelty 5/5

Humanix adds Complete Call Context, spawning a micro-agent per sensitive service-desk request that correlates live call behaviour with IdP and ITSM records in real time — flagging mismatched managers, non-existent ticket numbers, or unverified identity claims before the call ends, closing a gap no other tracked tool addresses.

Humanix adds Complete Call Context: per-request micro-agents correlate live service-desk calls with IdPIdPA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. and ITSMITSMIT Service Management: a framework of practices for delivering and supporting IT services, covering ticketing, change control, and incident response. Cyber tools integrate with it to automate alert-to-ticket workflows. records to detect vishing in real time.

  • New detectionNew integrationAdds Complete Call Context, which spawns a micro-agent per sensitive service-desk request (such as an 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. reset or password change) to correlate call behaviour with identity provideridentity providerA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. and IT service management records, then raises a severity-rated alert with a plain-language explanation when any discrepancy or missing evidence is found. Not checked yet
  • Micro-agents now check caller claims against directory, ticketing, and identity provider records in real time — flagging conflicts such as a mismatched manager, a non-existent ticket number, or an unverified identity claim — rather than waiting until after the call. Not checked yet

2 details in Everything

Good pick?
Good reason?

Zenity discovers, secures and governs enterprise AI agents from buildtime to runtime across SaaS, endpoint and cloud.

// WHY IT MADE THE LIST Depth 5/5 Impact 5/5 Novelty 5/5

Zenity now treats agent sandboxes as a first-class security surface: continuous discovery of every sandbox and template, posture checks that flag real API keys or wildcard egress, active red-team testing inside each sandbox profile, and runtime enforcement that evaluates actions against the full session context — no other tracked tool covers this attack surface.

Zenity adds a full sandbox security layer: discovery, posture checks with active red-team testing, runtime protection with taint and intent tracking, four containment levels, a trajectory view, and a new Sandboxes policy page.

  • New integrationA new Sandboxes page lets security teams write per-agent file, network, and runtime policies — including specific blocked paths, egress allow-lists, and environment variable listings by name — that the sandbox enforces directly. Not checked yet
  • New sandbox discovery continuously inventories every sandbox and sandbox template, linking each to its agent, credentials, workspace, egress policy, owner, image, and mid-session-installed packages, skills, 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. servers, including shadow sandboxes and sandboxes without a managed platform. Not checked yet
  • Posture checks now flag misconfigured sandboxes — such as real API keys in the environment or image, wildcard egress rules, internet-reachable sandboxes, or root-running containers — as posture violations with risk descriptions and remediation guidance. Not checked yet
  • Posture is now also tested actively: a red-team agent runs inside each sandbox profile attempting to escape, reach denied hosts, read credentials, or tamper with hooks, and every path found becomes a hardening rule for that profile. Not checked yet
  • New detectionNew integrationUpdated integrationRuntime protection now evaluates each action against the full session context — combining harness intent, taint from untrusted content, and low-level process, file, and network telemetry — blocking actions that conflict with the agent's declared task. Not checked yet
+6 more show less
  • Zenity Boundaries now extend enforcement into the sandbox itself, applying the same rules used in the agent harnessagent harnessThe software around an AI agent that manages its tools, execution loop, state and limits. It determines how the model's proposed actions are run and checked. across any supported platform. Not checked yet
  • Four containment levels — Steer, Restrict, Contain, and Kill-and-recover — are now available directly from a finding, or can be triggered automatically by a boundary, with each step preserving evidence and rotating exposed credentials. Not checked yet
  • A trajectory view now shows every network request, process, and file action on a single timeline alongside the prompt and tool call that caused it, spanning from intent to kernel. Not checked yet
  • On supported platforms, posture checks now extend to saved snapshots, verifying them before an agent resumes or forks. Not checked yet
  • AI Security Posture Management (AISPM) now gains sandboxes and sandbox templates as asset types, linked to their workspaces, credentials, and policies. Not checked yet
  • AI Detection and Response now gains visibility into sandbox-level activity beyond what the agent itself reports, with the full sandbox history available for investigation. Not checked yet

11 details in Everything

1 more release this week · 2026-11-18 → 2026-11-19

Zenity adds actor-identity resolution via 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. for GitHub Enterprise, where GitHub settings hide actor names, enabling full attribution of coding-agent actions.

  • New integrationUpdated integrationWhere enterprise settings hide actor names, Zenity uses Microsoft Entra ID to resolve them, so the security team can see whose agent made a change. Not checked yet

1 detail in Everything

Good pick?
Good reason?
03 Wallarm Your security team just got bigger (2026-11-19) WAF, Bot & API Protection
// WHY IT MADE THE LIST Depth 5/5 Impact 5/5 Novelty 5/5

Wallarm ships seven autonomous Agentic Operators — Radar, Sift, Trim, Tune, Lens, Bard, and Wally — that run the full WAAP operations loop (attack-spike investigation, hourly false-positive clearing, rule-set pruning, policy tuning, inventory review, posture briefing, and on-demand configuration) without prior art among tracked tools.

Wallarm introduced seven AI Agentic Operators that autonomously triage alerts, prune rules, and tune policies, manageable via an MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server and an audit-logged autonomous mode.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 3 FEATURES 3 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
Seven Agentic Operators for triage and policy tuning Not checked yet new 70

Wallarm added seven named Agentic Operators: Radar, which detects attack spikes, investigates them, and suggests a response; Sift, which clears false positives on an hourly cycle so alerts remain actionable; Trim, which tidies the active ruleset to prevent rule sprawl; Tune, which adjusts protection policies to match observed application behaviour; Lens, which reviews the API inventory and flags risky endpoints; Bard, which converts the current security posture into a human-readable briefing; and Wally, which answers questions and handles configuration requests on demand.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Names all seven operators and their functions but no setup steps here Your security team just got bigger (2026-11-…
02 02
Agentic Operators managed via MCP server Not checked yet new 60

All Agentic Operators can be managed through Wallarm's MCP server, letting them plug into external agentic workflows without returning to the console; a customer success team enables Agentic Operators, after which an agentic workflow connects to the MCP server to invoke operators such as Sift, Radar, and Wally programmatically.

Plug Wallarm Agentic Operators into an external agentic workflow via the MCP server so your own agents can trigger Sift, Radar, or Wally without opening the Wallarm console.
📍Contact your customer success team to enable Agentic Operators, then connect your agentic workflow to Wallarm's MCP server to invoke operators such as Sift, Radar, and Wally programmatically.
— Has concrete enablement and connection steps via MCP server Your security team just got bigger (2026-11-…
thinner coverage below
03 03
Autonomous mode with audit logging Not checked yet new 40

Agentic Operators support an autonomous mode where routine approved actions run without manual confirmation, with every finding logged to the audit trail.

— Describes behaviour but no config to enable or scope it Your security team just got bigger (2026-11-…
Good pick?
Good reason?
04 Auth0 Auth0 Security Agent is now in Early Access (2026-11-19) Identity & Access Management

Auth0 is an identity and access management platform that provides authentication, authorization, and user management services for applications via APIs and SDKs.

// WHY IT MADE THE LIST Depth 4/5 Impact 5/5 Novelty 5/5

Auth0's Security Agent detects credential stuffing attacks that stay under rate limits by computing per-tenant traffic baselines and alerting when failed logins deviate from normal for a sustained period — a class of attack that threshold-based controls miss entirely — then triages the attack and recommends specific Attack Protection and Tenant ACL configuration changes an admin can apply in one step.

Auth0 shipped three distinct capabilities this window: general availability of OpenID ConnectOpenID ConnectOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. for third-party apps, a beta in-app sign-in flow called Embedded Authorize, and a reworked Email Templates editor with live preview and agent-prompt handoff.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ 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
Embedded Authorize for in-app sign-in (Beta) Not checked yet new 95

A new POST /e/authorize endpoint lets apps build in-app sign-in without redirecting to Universal Login; it returns the allowed next steps for the app to render until Auth0 issues an authorization code.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ During Beta it supports email and phone one-time-code sign-in and second-factor MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. (email OTPOTPOne-time password: a short-lived numeric or alphanumeric code valid for a single authentication attempt, generated via TOTP or HOTP standards, giving cyber tools phishing-resistant second-factor verification without stored shared secrets., phone OTP, TOTPTOTPA one-time password algorithm (RFC 6238) that generates short-lived codes from a shared secret and the current time, giving cyber tools phishing-resistant second-factor authentication without a server round-trip., push, recovery code), and works out-of-the-box with Auth0 Universal Components for web, iOS, and Android.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Kick off an in-app sign-in flow — no browser redirect required — and receive the first allowed step your UI should render.
$ curl -X POST https://<your-tenant>.auth0.com/e/authorize \
  -H 'Content-Type: application/json' \
  -d '{"client_id": "<client_id>", "redirect_uri": "<redirect_uri>", "response_type": "code", "scope": "openid profile email"}'
— Runnable endpoint with method, path, and example request Embedded Authorize (Beta): in-app sign-in, w…
02 00
OpenID Connect for third-party apps (GA) Not checked yet new 80

Third-party apps can now use OpenIDOpenIDAn open standard for decentralized authentication that lets a user prove their identity to a site via a trusted third-party provider, so tools can delegate login without managing credentials themselves. Connect, with per-app control over which standard scopes (profile, email, address, phone) they may request via OpenID Connect Settings in the dashboard. Dynamically registered apps (via Client ID Metadata DocumentsClient ID Metadata DocumentsOAuth 2.0 documents hosted at a client's own URL that declare its identity and redirect URIs, letting authorization servers fetch and verify client metadata without manual registration.) can't receive 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. settings directly, so OIDC is instead configured through Application Profiles, which all apps registered under that profile inherit; third-party apps now get profile claims in the ID token while the /userinfo endpoint returns only sub for them.

Turn on OIDC for a third-party app and restrict it to email and profile claims only.
📍In the Auth0 dashboard, go to Applications › your third-party app › Settings › OpenID Connect Settings, enable Allow ID tokens, and check only profile and email under allowed scopes.
Enable OIDC for a dynamically registered app that cannot receive OIDC settings at registration time.
📍In the Auth0 dashboard, go to Applications › Application Profiles › your profile › OpenID Connect Settings and enable OIDC there, so all apps registered via that Client ID Metadata Document inherit the setting.
— Names exact scopes, endpoint behavior, and UI path OpenID Connect for Third-Party Apps is now G…
03 02
Email Templates editor with live preview and agent prompt Not checked yet new 72

A dedicated editor at Emails > Templates in the dashboard lists all templates with status and opens each on its own detail page, where editor and live preview tabs show the From line, Subject line, and rendered email. A new Variables panel lets users search and copy template variables, and a Copy agent prompt action copies the template's variables, current body, and deploy steps for handoff to a coding agent.

When iterating on a branded email template, switch to the live preview tab to see exactly how the rendered email, From line, and Subject look before deploying.
📍In the Auth0 dashboard, go to Emails › Templates, select the template you want to edit, then click the Preview tab to see the rendered output alongside From and Subject fields.
When delegating email template authoring to a coding agent, use the Copy agent prompt button to give the agent full context — variables, body, and deploy steps — in one action.
📍In the Auth0 dashboard, go to Emails › Templates, select a template, then click Copy agent prompt to copy a prompt containing the template's variables, current body, and deploy steps for use with a coding agent.
— Clear UI navigation path but no API/config surface Email Templates Editor UX Improvements (2026…
└──▷ ALSO FROM THESE RELEASES

Auth0 Security Agent Early access adds guided triage and remediation: it recommends Attack Protection and Tenant ACLACLAn access control list, a set of rules allowing or denying operations for particular users, services or network addresses. It decides who can use a resource. changes and lets admins apply them after authenticating.

  • The Security Agent triages detected attacks and recommends Attack Protection and Tenant ACL configuration changes, letting an Auth0 tenant administrator review and apply each one after authenticating. Not checked yet
  • Re-run triage after applying recommendations to check the current status of an ongoing attack. Not checked yet

2 details in Everything

Good pick?
Good reason?
05 StepSecurity announced · Nov 18, 2026 Software Supply Chain Security
// WHY IT MADE THE LIST Depth 5/5 Impact 5/5 Novelty 5/5

StepSecurity ships two first-of-kind supply chain controls this week: Secure Registry routes npm/pnpm/Bun installs through a cooldown proxy that blocks known-compromised packages and holds new versions for a configurable window, integrated into Harden-Runner with a single flag; and Harden-Runner now enforces network, DNS, process, and HTTPS monitoring inside Kata Containers and Amazon EKS Nitro Sandbox microVMs, closing a gap where CI hardening stopped at the VM boundary.

StepSecurity's biggest release this window is a free community tier for its Secure Registry, which intercepts npm/pnpm/Bun installs in Harden-Runner to block compromised packages and enforce a cooldown; it also shipped a new fork-PR approval audit control and remediation tracking for Threat Center.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ 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
Secure Registry community tier in Harden-Runner Not checked yet New supported platform new 95

Enable protection for any GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. job by adding secure-registry: true to a step-security/harden-runner@v2 step, which routes npm, pnpm, and Bun 1.4.4+ installs through community.registry.stepsecurity.io/javascript/ and blocks known-compromised packages via StepSecurity SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. flagging (always on).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Installs are held back for a configurable cooldown of 0–30 days (default 2 days) using the secure-registry block's npm.cooldown.days key, with exemptions for specific packages/versions such as typescript@* or [email protected]; a custom block list can also refuse specific packages or versions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Disable the registry for a job (e.g. one running npm publish) with npm: mode: off, and inspect held/blocked versions in the job summary (with a ready-to-paste allow snippet) or review every request on the new Packages tab in Harden-Runner Insights, which shows request type, status, and evaluated controls per download.

Add Secure Registry protection to a CI job so all npm installs are checked for the two-day cooldown and known-compromised packages before they reach your build.
yaml
- name: Harden the runner
  uses: step-security/harden-runner@v2
  with:
    egress-policy: audit
    secure-registry: true
Extend the cooldown to three days and exempt a pinned TypeScript version so the registry holds other new releases but lets a known-good version through.
yaml
- name: Harden the runner
  uses: step-security/harden-runner@v2
  with:
    egress-policy: audit
    secure-registry: |
      npm:
        cooldown:
          days: 3
          exemptions:
            - "typescript@*"
            - "@typescript/*"
Turn off Secure Registry in a publish job so npm publish can reach the public registry directly without being intercepted.
yaml
- name: Harden the runner
  uses: step-security/harden-runner@v2
  with:
    egress-policy: audit
    secure-registry: |
      npm:
        mode: off
Enable Secure Registry on a public repo to block compromised npm packages and apply a 7-day cooldown before new versions reach your CI build.
yaml
- name: Harden Runner
  uses: step-security/harden-runner@v2.23.0
  with:
    secure-registry: true
— Names exact config keys, defaults, cooldown range, and runnable YAML Harden-Runner GitHub Action v2.23.0: Secure …launch-20261118-cefeb282
02 00
Remediation tracking in Threat Center Not checked yet new 75

Threat Center findings can now be marked remediated individually (via row menu, with an optional comment) or all at once in the current view via Remediate all; the incident API endpoint now returns each finding's remediation status, and new endpoints let you mark findings remediated or reopen them for one organization or tenant-wide. Matched components and Matched IOCsIOCsAn indicator of compromise, an observable clue that may point to malicious activity, such as a suspicious file hash or domain. It is evidence to investigate, rather than proof by itself. tables show status, who remediated each finding, when, and their comment, with All, Active, and Remediated filter tabs plus source-based search; incidents move to a Remediated tab once fully cleared and move back automatically if a finding reappears, flagged with a 'Reappeared:' title prefix and a notification through existing threat intel channels. A summary banner shows outstanding vs. fully remediated findings, every action is recorded in audit logs, and remediating requires Read & write access to the Threat Center permission.

Track remediation progress through the Threat Center UI, using the status tabs to separate active from resolved incidents.
📍In Threat Center, go to the Affecting You tab and open an incident. Use the All / Active / Remediated tabs in the findings table to filter by status, then select Remediate all to close every active finding in the current view, or choose Remediate from an individual finding's row menu to add a comment before marking it done.
— Rich behaviour described but no exact API endpoint paths given Threat Center: Remediation Tracking (2026-11…
03 02
Fork PR approval control audits org policy hourly Not checked yet New detection new 65

A new 'Fork pull request workflows should require approval' control, rated Critical and listed under Code Injection in the Overview dashboard, checks every GitHub organization and public repository's fork PR workflow approval policy every hour and links directly to the fix in GitHub's Settings > Actions > General. Findings are also surfaced through the existing control tools in the StepSecurity MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server, and the check requires the StepSecurity GitHub App to have Administration: read permission on the organizations and repositories it scans.

Review the new fork PR approval control findings for your organization via the StepSecurity Overview dashboard after granting the required permission.
📍In StepSecurity, go to Overview dashboard › All Controls › Code Injection, then select 'Fork pull request workflows should require approval' to see which organizations and public repositories are on the least restrictive policy, and click Open Settings on any finding to jump directly to Settings › Actions › General in GitHub.
— Names control, category, permission, and dashboard path but no API launch-20261118-fff0dbd5

Harden-Runner agent v1.9.7 adds runtime monitoring and egress policy enforcement inside microVM-isolated ARC runner pods, covering network, DNS, process, and HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. events.

  • New supported platformSet runtimeClassName: isolated-sandbox on runner pods to enable Harden-Runner monitoring and egress enforcement inside Amazon EKSEKSAmazon's managed Kubernetes service, run by AWS, that handles control-plane provisioning so teams can deploy containerized workloads without operating the underlying cluster infrastructure themselves. Nitro Sandbox microVMs. Not checked yet
  • HTTPS visibility inside microVMs now covers requests from Go programs and HTTP/2HTTP/2The second major version of the HTTP protocol, standardized by the IETF, adding multiplexed streams, header compression, and binary framing over a single TCP connection to cut latency and reduce overhead. traffic — including calls from gh and other Go tools that carry their own TLS and bypass system OpenSSL — plus Docker-in-Docker image pulls. Not checked yet

2 details in Everything

Dev Machine Guard adds stable device identity and per-session scanning for pooled virtual desktops, device tagging and retirement on uninstall, virtualization detection, and prompt-free agent configuration via configure flags.

  • New supported platformSet device_id to {hostname} in agent config to keep a stable device record and history when a session host is rebuilt from an image, suiting Azure Virtual Desktop, Citrix, and Horizon host pools. Not checked yet
  • Exclude an imaging machine from scanning by running configure --image-builder or setting MSI property IMAGEBUILDER=1 during deployment. Not checked yet
  • Label a device for its host pool using device_tag, and remove it from the dashboard and license count on teardown with --retire or by setting retire_on_uninstall. Not checked yet
  • Adds per-session scanning on Windows Enterprise multi-session and Remote Desktop Session Host servers, reporting each signed-in user's inventory and findings independently under the one device record for that machine. Not checked yet
  • Every scan now reports whether the machine is virtual or physical and which hypervisor or cloud it runs on. Not checked yet
+2 more show less
  • Every agent setting can now be set without prompts: configure accepts a flag for every setting, so MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. or MSI deployments no longer need a bootstrap JSON file for anything beyond credentials. Not checked yet
  • New supported platformJavaScript configuration audits now read npm, pnpm, Yarn, and Bun configuration from each tool's own paths and formats, including pnpm rc, YAML, and auth files, custom Yarn rc file names, and Bun global settings, and record which values could not be resolved on the device separately from observed file settings. Not checked yet

7 details in Everything

StepSecurity adds a Critical-severity dashboard control that flags weak fork PR approval policies at both org and repo level, with hourly refresh.

  • Each finding distinguishes whether the weak policy comes from the organization's default or a repository-level override, so repositories that deviate from the org setting are caught separately. Not checked yet
  • New detectionFindings update on the next hourly scan after the setting changes; to remediate, set the policy to Require approval for all external contributors under Settings > Actions > General in GitHub. Not checked yet

2 details in Everything

Good pick?
Good reason?

Where each pick stands · Nov 13–19

Tools with changes in each pick's category over the last 12 weeks, including the pick itself.

Each pick's release rhythm · Nov 13–19

Changes per week for the last 12 weeks. The bright bar is this week; a dash marks a week with no daily.

Which categories moved · Nov 13–19

The thick bar is this week. The thin bar is the average of the four weeks before, counting only weeks with a daily.

  • Software Supply Chain Security 110usual 46.2
  • Code Security 109usual 69.8
  • SIEM 53usual 54
  • Secrets Detection & Management 49usual 19.5
  • Identity & Access Management 43usual 66.8
  • Detection Engineering 41usual 9.8
  • Secure Access (VPN / SASE / ZTNA) 32usual 22.2
  • Attack Surface Management 27usual 1.5
  • WAF, Bot & API Protection 25usual 20
  • Application Security Posture 20usual 2
  • Endpoint Security (EDR/XDR) 20usual 16
  • Network Analysis & Monitoring 19usual 13.2

Who shipped the most · Nov 13–19

Changes per tool this week. Volume is not a quality score.

Upcoming conferences →

Saved in this browser. Sign in to sync your tools.