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 087, September 27, 2026

THE CYBER TOOLCHAIN NO. 087
Tail
THE DAILY RELEASE FIREHOSE
PUBLISHED SEPTEMBER 27, 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 1326 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
INFORMATION DENSITY everything
ISSUE WIDTH reading width
Do you prefer scroll?
ADDITIONAL FILTERS
$ tct list   # 4 tools matched

What stands out across today's releases, grouped by what it lets you do. Every tool named links to its entry below.

Three unrelated things stand out. GitGuardian now strips secrets out of model context on more coding assistants and agent CLIs, so a pasted .env doesn't leave the laptop. Plerion extended workload scanning across Azure compute families with attack-path and exploit checks. Lookyloo surfaces console messages, WebAuthnWebAuthnA web standard that lets a browser prove possession of a passkey or hardware key to a website. It is the browser-facing part of FIDO2 sign-in. and OPFSOPFSA browser-native filesystem API, standardized by WHATWG, that gives web apps a private sandboxed storage area with synchronous access from Web Workers, enabling fast local file I/O without server round-trips. from a capture, and auto-tags .onion hosts.

  • protect

    Keep secrets out of what the AI coding assistant sends upstream

    AI Hooks now withholds secrets from model context across more assistants and covers new agent CLIs, so a credential sitting in the open file or shell history isn't shipped to a third-party model as ambient context. The configurable ggshield API timeout is the quieter win: monorepo scans that previously died mid-run and got waved through now finish.

    GitGuardian SaaS

  • protect

    Cover the Azure compute you were quietly skipping

    Workload scanning now reaches nearly every Azure compute family, with 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. findings, exploit checks and registry access permissions behind it. Agentless coverage gaps are where unpatched VMs hide; closing the family list means the console inventory and the scanned inventory finally match, and a vulnerable host is ranked by whether it's actually reachable rather than by 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. alone.

    Plerion

  • detect

    See what a page did, not just what it loaded

    Captures now expose console messages, WebAuthn and OPFS entries, which is where obfuscated loaders and browser-side persistence leave traces that never appear in the HARHARAn HTTP Archive file, a JSON-format log of all network requests and responses captured by a browser's developer tools, used by cyber tools to replay, inspect, or analyze web traffic without re-running a live session.. Onion Lookup integration auto-tags .onion hosts during capture, with optional push to AIL, so an analyst stops hand-checking whether a hidden service is already known.

    Lookyloo

  • govern

    Show an auditor the evidence without exporting the database

    v4.0.7 adds a downloadable audit log, risk trajectory tracking and batch control management, plus an overhauled x-rays module with domain-level checks. Trajectory turns a static risk register into something you can show moving over a quarter, and batch edits remove the click-per-control slog that makes framework mappings go stale.

    CISO Assistant

Application Security
◆  Secrets Detection & Management

GitGuardian SaaS

Sources Blog / feed → AI Hooks keep leaked tool output away from the model (2026-09-25) Blog Rank Why this rank top features scored 90/80/60, +10 product media, +6 runnable example — 92.67 How ranking works →

GitGuardian SaaS is a cloud-based security platform that detects and prevents secrets leakage in git repositories and source code.

GitGuardian SaaS made ggshield's API timeout configurable to stop large-repo scans from failing, and expanded AI Hooks to withhold secrets from model context on more coding assistants while extending coverage to new agent CLIs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ 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
Configurable API timeout for ggshield scans Not checked yet improved 90

ggshield previously enforced a fixed 60-second API timeout that could cause large-repo scans to fail with read timeouts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ A new api_timeout config key (set in ~/.gitguardian/.gitguardian.yaml) and a GITGUARDIAN_API_TIMEOUT environment variable let users raise this limit, e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ GITGUARDIAN_API_TIMEOUT=120 ggshield secret scan repo . or api_timeout: 120 in the config file.

Prevent large-repo scans from failing with a read timeout by raising the API timeout above the old 60-second hard limit.
📍GITGUARDIAN_API_TIMEOUT=120 ggshield secret scan repo .
Set a persistent API timeout in the ggshield config file so every scan honours the higher limit without needing an environment variable.
yaml
api_timeout: 120
Raise the API timeout when large scans are failing with read timeouts in CI or on slow networks.
yaml
api_timeout: 120
Override the API timeout via environment variable in a CI pipeline where the config file is not available.
📍GITGUARDIAN_API_TIMEOUT=120 ggshield secret scan repo .
— Names config key, env var, file path, and runnable commands. AI Hooks keep leaked tool output away from t…
02 00
AI Hooks coverage extended to Kiro and Junie CLI Not checked yet new 80

AI Hooks and the 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. inventory now cover Amazon Kiro (IDE and CLI) and Junie CLI, blocking secrets in commands and file reads. A new ggshield machine setup subcommand registers AI Hooks for Kiro and Junie CLI in one step.

Register AI Hooks for Kiro and Junie CLI on a developer workstation after upgrading to ggshield 1.55.0.
$ ggshield machine setup
— Names exact new subcommand and the covered integrations. AI Hooks keep leaked tool output away from t…
03 00
AI Hooks withhold leaked tool output from model Not checked yet improved 60

AI Hooks now withhold shell-command output containing secrets from the model context on Claude Code, Codex, and Mistral Vibe — the assistant receives only the ggshield message, keeping the secret out of the model session transcript.

— Explains mechanism and before/after but gives no setup step. AI Hooks keep leaked tool output away from t…
└──▷ ALSO FROM THESE RELEASES
AI Hooks keep leaked tool output away from the model (2026-09-25) Blog LatestStable

AI Hooks now withhold tool output from Claude Code, Codex, and Mistral Vibe, and extend coverage to Kiro and Junie CLI.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ USE IT
Raise the API timeout when large scans are failing with read timeouts in CI or on slow networks.
yaml
api_timeout: 120
Register AI Hooks for Kiro and Junie CLI on a developer workstation after upgrading to ggshield 1.55.0.
$ ggshield machine setup
Override the API timeout via environment variable in a CI pipeline where the config file is not available.
📍GITGUARDIAN_API_TIMEOUT=120 ggshield secret scan repo .
  • Adds api_timeout config key and GITGUARDIAN_API_TIMEOUT environment variable to override the previously fixed 60-second API timeout.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds ggshield machine setup subcommand to register AI Hooks for Kiro and Junie CLI in one step.
  • AI Hooks now withhold shell-command output containing secrets from the model context on Claude Code, Codex, and Mistral Vibe — the assistant receives only the ggshield message, keeping the secret out of the model session transcript.
  • Extends AI Hooks and the 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. inventory to cover Amazon Kiro (IDE and CLI) and Junie CLI, blocking secrets in commands and file reads.
  • Adds api_timeout config key and GITGUARDIAN_API_TIMEOUT environment variable to override the previously fixed 60-second API timeout.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds ggshield machine setup subcommand to register AI Hooks for Kiro and Junie CLI in one step.

2 more in Everything

Was this useful?
Cloud & Container Security
◆  CNAPP

Plerion

Sources Release page → Azure workload scanning covers every workload family: Notes Rank Why this rank top features scored 78/60/50, +6 runnable example — 68.67 How ranking works →

Plerion is a cloud security platform that discovers and manages vulnerabilities and misconfigurations across infrastructure.

Plerion expanded Azure workload scanning to cover nearly every Azure compute workload family, backed by new 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. findings, exploit checks, registry access permissions, and inventory coverage.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 5 FEATURES 2 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 01
Azure workload scanning expands to new workload types Not checked yet new 78

Vulnerability, sensitive data, and SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. scanning now covers Azure App Service web apps, Virtual Machine Scale Sets, Container Apps, Container Instances, and Batch pools, in addition to previously covered virtual machines and functions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Service Fabric node types are covered through their underlying scale sets, and Uniform-orchestration scale sets are sampled by image, scanning one member per distinct image. Each workload type must be enabled individually under the subscription's workload scanning settings.

Enable scanning for newly supported workload types on an Azure subscription so Container Apps and Batch pools are included in vulnerability and SBOM assessments.
📍In the Plerion console, go to the subscription's Workload Scanning Settings and toggle on App Service web apps, Container Apps, Container Instances, and Batch pools.
— Names workload types, scan types, sampling mechanism, and toggle path Azure workload scanning covers every workloa…
02 00
New exploit checks for container and Batch pool images Not checked yet new 60

Six new Azure checks flag exploitable and known-exploited vulnerabilities in container workload and Batch pool images: PLERION-AZURE-452 (Container App exploitable), PLERION-AZURE-453 (Container App known-exploited), PLERION-AZURE-454 (Container Instance exploitable), PLERION-AZURE-455 (Container Instance known-exploited), PLERION-AZURE-459 (Batch pool image exploitable), and PLERION-AZURE-460 (Batch pool image known-exploited).

— Names all six checks but no direct reader action Azure workload scanning covers every workloa…
thinner coverage below
03 02
Attack path findings for exposed vulnerable workloads Not checked yet new 50

Plerion generates attack path findings for publicly exposed Azure workloads that have high or critical severity vulnerabilities, flagged via check PLERION-AZURE-446.

— Names the check but no reader action described Azure workload scanning covers every workloa…
04 00
AcrPull permission for scanning appliance Not checked yet new 45

The Azure install script now grants AcrPull to the appliance identity so container images stored in Azure Container Registries can be pulled and scanned.

— Names the permission but action is automatic via install script Azure workload scanning covers every workloa…
05 00
Inventory coverage for OpenShift, Service Fabric, Batch Not checked yet new 25

Plerion's inventory now includes OpenShiftOpenShiftRed Hat's Kubernetes distribution that adds developer workflows, built-in CI/CD, and stricter security defaults on top of upstream Kubernetes, giving cyber tools a managed container platform with enterprise auth and RBAC already wired in., Service Fabric, and Batch resources.

— Brief statement with no mechanism or reader action Azure workload scanning covers every workloa…
Azure workload scanning covers every workload family: Notes LatestStable

Plerion Azure workload scanning expands to App Service, VM Scale Sets, Container Apps, Container Instances, and Batch pools⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ HOW TO FIND IT
Enable scanning for newly supported workload types on an Azure subscription so Container Apps and Batch pools are included in vulnerability and SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. assessments.
📍In the Plerion console, go to the subscription's Workload Scanning Settings and toggle on App Service web apps, Container Apps, Container Instances, and Batch pools.
  • Extends vulnerability, sensitive data, and SBOM scanning to Azure App Service web apps, Virtual Machine Scale Sets, Container Apps, Container Instances, and Batch pools — in addition to the virtual machines and functions already covered.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Covers Service Fabric node types through their underlying scale sets.
  • Samples Uniform-orchestration scale sets by image, scanning one member per distinct image.
  • Generates 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. findings for publicly exposed workloads with high or critical vulnerabilities (PLERION-AZURE-446).
  • Grants AcrPull to the appliance identity via the install script so container images in Azure Container Registries can be pulled for scanning.
+3 more show less
  • Adds OpenShiftOpenShiftRed Hat's Kubernetes distribution that adds developer workflows, built-in CI/CD, and stricter security defaults on top of upstream Kubernetes, giving cyber tools a managed container platform with enterprise auth and RBAC already wired in., Service Fabric, and Batch resources to the inventory.
  • Adds six new Azure checks for exploitable and known-exploited vulnerabilities in container workload and Batch pool images: PLERION-AZURE-452 (Container App exploitable), PLERION-AZURE-453 (Container App known-exploited), PLERION-AZURE-454 (Container Instance exploitable), PLERION-AZURE-455 (Container Instance known-exploited), PLERION-AZURE-459 (Batch pool image exploitable), PLERION-AZURE-460 (Batch pool image known-exploited).
  • Enables each workload type individually under the subscription's workload scanning settings.
  • Extends vulnerability, sensitive data, and SBOM scanning to Azure App Service web apps, Virtual Machine Scale Sets, Container Apps, Container Instances, and Batch pools — in addition to the virtual machines and functions already covered.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Covers Service Fabric node types through their underlying scale sets.
  • Samples Uniform-orchestration scale sets by image, scanning one member per distinct image.
  • Generates 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. findings for publicly exposed workloads with high or critical vulnerabilities (PLERION-AZURE-446).
  • Grants AcrPull to the appliance identity via the install script so container images in Azure Container Registries can be pulled for scanning.
+2 more show less
  • Adds six new Azure checks for exploitable and known-exploited vulnerabilities in container workload and Batch pool images: PLERION-AZURE-452 (Container App exploitable), PLERION-AZURE-453 (Container App known-exploited), PLERION-AZURE-454 (Container Instance exploitable), PLERION-AZURE-455 (Container Instance known-exploited), PLERION-AZURE-459 (Batch pool image exploitable), PLERION-AZURE-460 (Batch pool image known-exploited).
  • Enables each workload type individually under the subscription's workload scanning settings.

1 more in Everything

Was this useful?
Detection & Response
◆  Threat Intelligence

Lookyloo

Sources Release notes → v1.41.1 Notes Rank Why this rank top features scored 65/50/40 — 51.67 How ranking works →

Lookyloo is a web interface that allows users to capture a website page and then display a tree of domains that call each other.

Lookyloo's v1.41.1 release expands capture data exposure to include console messages, WebAuthnWebAuthnA web standard that lets a browser prove possession of a passkey or hardware key to a website. It is the browser-facing part of FIDO2 sign-in., and OPFSOPFSA browser-native filesystem API, standardized by WHATWG, that gives web apps a private sandboxed storage area with synchronous access from Web Workers, enabling fast local file I/O without server round-trips. entries, adds a large-deployment kvrockskvrocksAn open-source distributed key-value store maintained by the Apache Software Foundation, compatible with the Redis protocol but backed by RocksDB, giving tools persistent storage with lower memory cost than Redis. tuning sample, and integrates Onion Lookup for automatic .onion tagging with optional AIL push.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ 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
Kvrocks config sample for large deployments Not checked yet new 65

Adds a kvrocks config sample at full_index/kvrocks.conf-big_instance for tuning large deployments.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

— Exact file path given but no tuning specifics v1.41.1
thinner coverage below
02 00
Onion Lookup integration for .onion tagging Not checked yet new 50

Lookyloo integrates with Onion Lookup to automatically tag .onion captures and optionally push full captures to AIL.

— Names integration and behavior but no config detail v1.41.1
03 00
Expanded browser data capture exposure Not checked yet new 40

Lookyloo now gathers and renders browser console messages during captures, and exposes WebAuthn entries and Origin Private File System (OPFS) entries discovered during page captures.

— Names three data types exposed but no mechanism or UI path v1.41.1
v1.41.1 Notes LatestStable

Lookyloo v1.41.1 adds console message capture, WebAuthnWebAuthnA web standard that lets a browser prove possession of a passkey or hardware key to a website. It is the browser-facing part of FIDO2 sign-in./OPFSOPFSA browser-native filesystem API, standardized by WHATWG, that gives web apps a private sandboxed storage area with synchronous access from Web Workers, enabling fast local file I/O without server round-trips. exposure, and onion-site tagging via Onion Lookup.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v1.41.1 https://github.com/Lookyloo/lookyloo.git
# already have the repo? check out this version:
$ git checkout v1.41.1
  • Adds a kvrocks config sample at full_index/kvrocks.conf-big_instance for tuning large deployments.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Not checked yet
  • Gathers and renders browser console messages during captures.
  • Exposes WebAuthn entries discovered during page captures.
  • Exposes Origin Private File System (OPFS) entries discovered during page captures.
  • Integrates with Onion Lookup to automatically tag .onion captures and optionally push full captures to AIL.

5 details in Everything

Was this useful?
Governance, Risk & Compliance
◆  Integrated & IT Risk Management

CISO Assistant

Sources Release notes → v4.0.7 Notes Rank Why this rank top features scored 70/55/50, +6 runnable example — 64.33 How ranking works →

CISO Assistant is a one-stop-shop GRC platform for Risk Management, AppSec, Compliance & Audit, TPRM, BIA, Privacy, and Reporting. It supports 200+ global frameworks with automatic control mapping, including ISO 27001, NIST CSF, SOC 2, CIS, PCI DSS, NIS2, DORA, GDPR, HIPAA, CMMC, and more.

CISO Assistant v4.0.7 adds in-app notifications, a downloadable audit log, risk trajectory tracking, an overhauled x-rays module with domain-level checks, and Mermaid diagram support in documentation, alongside batch control management and HelmHelmA package manager for Kubernetes, maintained by the CNCF, that lets tools define, version, and deploy clusters of Kubernetes resources as a single reusable unit called a chart. chart flexibility.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ WHAT SHIPPED · 12 FEATURES 1 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 00
Mermaid diagram support in documentation fields Not checked yet new 70

Adds Mermaid diagram support in markdown documentation fields — insert a fenced code block with the mermaid language tag to embed architecture or threat-model diagrams alongside control descriptions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

Embed a Mermaid architecture or threat-model diagram directly in a documentation field to keep visual context alongside control descriptions.
📍In a markdown documentation field, insert a fenced code block with the mermaid language tag — e.g.: mermaid graph LR A[Asset] --> B[Control] B --> C[Risk]
— Runnable example with exact syntax provided v4.0.7
thinner coverage below
02 00
Batch ETA date on applied controls Not checked yet new 55

Adds batch mode on applied controls to set an ETA date across multiple controls at once, via a batch actions menu that lets users select controls and choose Set ETA date.

Set an ETA date on multiple applied controls at once to keep remediation timelines visible across a programme.
📍In Applied Controls, select the controls you want to update, open the batch actions menu, and choose Set ETA date.
— Exact UI steps given for a runnable action v4.0.7
03 01
Downloadable audit log (pro) Not checked yet new 50

Adds a downloadable audit log (pro tier) so teams can export a full activity trail for compliance evidence or incident investigation.

Download the full audit log to review who changed what and when — useful for compliance evidence or incident investigation.
📍In the pro console, go to Audit Log and click the Download button to export the activity trail.
— Names exact UI path to download the log v4.0.7
04 00
Helm chart: custom command/args, Qdrant image, managed OIDC keys Not checked yet new 50

Adds custom command/args, Qdrant image, and managed 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. key options to the Helm chart.

— Names three concrete Helm options, no key names or values v4.0.7
05 00
X-rays module: domain-level checks and evidence flagging Not checked yet improved 45

The x-rays page is reworked to add domain-level x-rays checks that surface compliance and control gaps at the domain scope, plus flagging of active controls that lack evidence.

— Names two concrete checks but no exact UI steps v4.0.7
06 00
Applied controls on audit via data wizard and CLI Not checked yet new 35

Adds support for applied controls on audit via the data wizard and CLI.

— Names concrete surfaces (data wizard, CLI) but no usage detail v4.0.7
07 00
Controls status column in findings binder Not checked yet new 30

Adds a controls status column to the findings binder view.

— Names exact view but no further mechanism v4.0.7
08 00
In-app notifications center Not checked yet new 25

Adds an in-app notifications center for real-time alerts within the platform.

— Described only in prose, no config or UI path given v4.0.7
09 00
Risk trajectory and projection view Not checked yet new 25

Adds a risk trajectory and projection view to track how risk posture changes over time.

— No mechanism or navigation detail given v4.0.7
10 00
Real TTP techniques on EBIOS operational scenarios Not checked yet new 25

Adds real TTPTTPTactics, techniques and procedures, the goals, methods and specific behaviors used by an attacker. They describe how an attack works, rather than only the files or addresses it leaves behind. techniques exposed on EBIOS operational scenarios.

— Names the EBIOS feature but no mechanism detail v4.0.7
11 00
Organisation-scoped custom feature flags Not checked yet new 25

Allows users to redefine their own feature flags within the boundaries of their organisation.

— No config key or flag names given v4.0.7
12 00
Workflow enablers and AI blocks Not checked yet improved 20

Adds more workflow enablers — documents, tasks, and validations — and improved AI blocks.

— Generic list with no specifics on what changed v4.0.7
v4.0.7 Notes LatestStable

CISO Assistant v4.0.7 adds in-app notifications, audit log download, risk trajectory, domain-level x-rays, and Mermaid diagram support.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

└──▷ GET THIS VERSION
$ git clone --branch v4.0.7 https://github.com/intuitem/ciso-assistant-community.git
# already have the repo? check out this version:
$ git checkout v4.0.7
└──▷ HOW TO FIND IT
Download the full audit log to review who changed what and when — useful for compliance evidence or incident investigation.
📍In the pro console, go to Audit Log and click the Download button to export the activity trail.
Set an ETA date on multiple applied controls at once to keep remediation timelines visible across a programme.
📍In Applied Controls, select the controls you want to update, open the batch actions menu, and choose Set ETA date.
Embed a Mermaid architecture or threat-model diagram directly in a documentation field to keep visual context alongside control descriptions.
📍In a markdown documentation field, insert a fenced code block with the mermaid language tag — e.g.: mermaid graph LR A[Asset] --> B[Control] B --> C[Risk]
  • Adds in-app notifications center for real-time alerts within the platform.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds downloadable audit log (pro) so teams can export a full activity trail.
  • Adds risk trajectory and projection view to track how risk posture changes over time.
  • Adds domain-level x-rays checks to surface compliance and control gaps at the domain scope.
  • Adds x-rays flagging for active controls that lack evidence, with a reworked x-rays page.
+8 more show less
  • Adds Mermaid diagram support in markdown documentation fields. Not checked yet
  • Adds batch mode on applied controls to set an ETA date across multiple controls at once.
  • Adds real TTPTTPTactics, techniques and procedures, the goals, methods and specific behaviors used by an attacker. They describe how an attack works, rather than only the files or addresses it leaves behind. techniques exposed on EBIOS operational scenarios.
  • Adds support for applied controls on audit via the data wizard and CLI.
  • Adds more workflow enablers — documents, tasks, and validations — and improved AI blocks.
  • Allows users to redefine their own feature flags within the boundaries of their organisation. Not checked yet
  • Adds custom command/args, Qdrant image, and managed 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. key options to the Helm chart.
  • Adds controls status column to the findings binder view.
  • Adds in-app notifications center for real-time alerts within the platform.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
  • Adds downloadable audit log (pro) so teams can export a full activity trail.
  • Adds risk trajectory and projection view to track how risk posture changes over time.
  • Adds domain-level x-rays checks to surface compliance and control gaps at the domain scope.
  • Adds Mermaid diagram support in markdown documentation fields. Not checked yet

8 more in Everything

Was this useful?
Saved in this browser. Sign in to sync your tools.