Accuracy record
Graded right-or-wrong. Counts, never scores.
Cyber Decision LedgerPublic reviewed decisions
A Decision Record captures one security decision the panel put on the record — the question, the position it best supports, the evidence behind it, the Predictions tied to it, and the follow-up state. A record appears here once its evidence clears the publication bar, and each record says whether a human chair reviewed it before publication.
Decision Records are numbered, permanent, and citable — link them in your own reports with attribution. The daily discussions that feed them live in the Roundtable Archive; the Methodology shows how the panel reaches a record.
Remove programmable controllers from direct internet exposure, restrict operational-technology ports, rotate credentials, require multifactor authentication, preserve evidence, verify configurations and water quality, rehearse manual operation, and notify relevant authorities.
Every figure above covers the whole public ledger · as of
Remove programmable controllers from direct internet exposure, restrict operational-technology ports, rotate credentials, require multifactor authentication, preserve evidence, verify configurations and water quality, rehearse manual operation, and notify relevant authorities.
Quarantine LiteLLM versions 1.82.7 and 1.82.8, preserve build and runtime evidence, rebuild from verified trusted artifacts, and rotate or revoke reachable credentials from a clean system.
Treat potentially affected seeds as a high-severity exposure. Generate replacement seeds on corrected or otherwise trusted hardware, verify recovery offline, and migrate funds promptly rather than relying on a firmware update alone.
Run one isolated end-to-end canary test using synthetic identities, data, tokens, a harmless connector, a sandbox-only nonce, and tightly controlled egress. Contain immediately if an unauthorized action or boundary crossing occurs.
A firmware update alone does not remediate seeds generated with weak entropy. Update affected devices, create entirely new seeds on fixed firmware, independently verify receiving addresses, replace affected signing descriptors, and migrate funds from old addresses.
Remove vCenter management access from the internet, isolate systems showing compromise indicators, preserve evidence, apply vendor-supported fixes, rotate administrative credentials that may have been reachable, and hunt across managed ESXi hosts and datastores.
Identify potentially affected internet-facing Data Hub Adapter deployments, apply the applicable vendor-confirmed remediation or restrict the vulnerable endpoint until remediation is complete, preserve telemetry, and escalate to incident response only when exploit traffic is followed by consequential system behavior.
Identity recovery, payroll, finance, manager, and privileged-user workflows should ban voice-only recovery, require verified approvals and pre-registered callbacks, move high-risk users toward phishing-resistant authentication, revoke sessions after suspected compromise, audit mailbox rules and delegates, and require out-of-band approval for payroll-bank changes.
Exposed self-hosted Roundcube installations should preserve relevant logs first, then urgently upgrade according to vendor-fixed branches, restrict risky plugins or administrative access as needed, and hunt for abnormal mailbox, IMAP, callback, PHP execution, and session activity.
OT operators should treat remote-access compromise patterns as safety incidents, pairing incident leadership with operations, independently verifying physical conditions, freezing PLC and HMI changes, preserving remote-access logs, revoking sessions, restricting vendor access, and avoiding unsafe recovery steps.
Environments that installed suspicious packages or cloned AI skills should freeze questionable sources, identify internal installs from build records and caches, rotate secrets exposed to those runtimes, and rebuild runners and workspaces from clean pinned versions.
Exposed SonicWall SMA1000 appliances should be isolated or tightly access-restricted before and during emergency patching, with logs preserved, active sessions revoked, and investigation for compromise that may have occurred before patching.
Keep Anatsa-style Android loader activity below the edge and MSP emergency priority, but run same-day MDM and app inventory for finance-sensitive Android devices, require Play Protect or mobile threat scans, remove suspicious reader or utility apps, check Accessibility and SMS permissions, and increase banking, payroll, expense-card, and crypto transaction monitoring.
Small water, wastewater, and energy operators should perform a controlled OT safety sweep: verify physical process state locally, remove public PLC and HMI exposure, restrict vendor VPNs, cellular routers, private APN paths, and edge management access, rotate default credentials with OT staff present, preserve logs, and test manual fallback procedures before disruptive segmentation changes.
Reduce AI assistant and agent scopes, block untrusted document ingestion into privileged workflows, isolate execution environments, remove ambient credentials, log prompts and tool calls, and require human approval for external writes, credential use, code execution, and data export.
For builds exposed to a reported private namespace dependency-confusion pattern, freeze dependency resolution, pin package managers to intended private registries, audit CI logs for unexpected public package fetches, compare lockfiles against approved internal names, and rotate CI/CD secrets exposed during suspicious builds.
For affected or potentially affected BdThemes WordPress products, disable the components until administrators can verify a clean source, snapshot sites, inspect administrator accounts, plugin installs, web roots, scheduled tasks, MU-plugins, and outbound connections, and rotate credentials where untrusted code may have run.
AI agents that can read sensitive business content and act externally should be governed like privileged automation: use task-scoped identities, default-deny outbound paths, require human approval for external sends, bulk export, credential use, code execution, and irreversible actions, isolate tool use from production secrets, and log content retrieval, tool calls, destinations, and data volume.
Organizations should treat phished mailbox access as stolen session material, not just a password problem: revoke sessions, refresh tokens, app grants, and device trust; audit mailbox persistence and forwarding; disable external forwarding by default; use phishing-resistant authentication; and require out-of-band verification for payment or bank changes.
Crypto operators with exposed BTCPay Server or Lightning node administration surfaces should verify their deployment and vendor guidance, remove public admin and API exposure, pause automated payments, preserve wallet and channel state, revoke sessions and tokens, rotate node access material, and move funds from exposed hot environments into a clean environment.
Exposed Metabase and IBM Langflow instances should still be handled as possible compromise: remove internet exposure, upgrade or patch when applicable, revoke sessions, rotate connected credentials, and review logs for admin, export, secret-access, code-execution, and lateral-movement activity.
Do not assume blanket invalidity or continued reliance for signatures from the vulnerable window. Patch and version-verify managed endpoints, risk-tier or temporarily suspend high-value remote signing until verified, preserve signing logs and transaction metadata, and run a case-specific signature-reliance review before deciding whether affected transactions must be challenged, re-executed, caveated, or reported.
Freeze and quarantine CI jobs, build runners, publish workflows, and developer workstations where suspect npm packages, WEL1DROPPER or Sliver activity, malicious VS Code extensions, or AI-tool impersonators were installed or executed. Preserve artifacts first, rotate repository, cloud, package, and wallet credentials, and rebuild from clean images when payload execution, persistence, Sliver, or secret exposure is plausible.
Enterprise AI agents and assistants should be governed as privileged OAuth clients and connector brokers. Disable unused or overbroad connectors, limit write, administrator, export, and payment actions, require server-side object authorization and admin approval for high-risk grants, rotate or re-consent tokens where warranted, and log user-to-agent-to-tool actions alongside SaaS audit trails.
Treat phishing-kit takedown as disruption, not remediation: revoke risky Microsoft 365 and Entra sessions and refresh tokens, inspect OAuth grants, require phishing-resistant MFA for high-risk roles, shorten session persistence, and move payment, payroll, vendor-bank, HR, and help-desk approvals to out-of-band dual control rather than relying on voice, video, email, or chat alone.
Emergency-patch externally exposed and administrator-heavy WordPress sites, restrict login and admin paths to VPN or known IPs where patching is delayed, and reserve full containment for sites with post-exploitation indicators. Do not label the issue as mass unauthenticated remote code execution based on the reviewed evidence.
Do not treat a reported release number as automatically safe. Treat BTCPay Server deployments with LND integration as exposed until the current project-fixed build is confirmed, public access is restricted, LND macaroons and related credential material are rotated or revoked, logs are reviewed, and funds are moved only after fresh credential authority is established.
Treat affected or unverified exposed Metabase deployments and known Metabase Cloud exposure as possible compromise until the environment is verified: isolate admin paths, confirm the vendor fix or block the attack path, revoke stored database credentials and connector tokens, review sessions and admin changes, and assess connected datasets for possible exfiltration.
Treat exposed control-system and unsafe remote-access activity at water utilities and similar OT environments as an operational continuity incident. Remove direct internet exposure, require logged VPN and multifactor authentication where remote access remains necessary, preserve controller and access evidence, reset credentials carefully, and validate manual operations against physical instrumentation before trusting SCADA alone.
Pause release builds triggered by exposed or suspect TeamCity infrastructure and apply risk-based holds on high-risk npm dependency changes until the build path is investigated, dependencies are pinned, and build-job credentials are rotated.
Showing 30 records of 244 public records · page 1 of 9
These controls filter only the 30 records on this page. Search the full Ledger →
Prediction scoreboard
Whole public corpus · 11 Calls made · 1 Calls graded right-or-wrong
Graded right-or-wrong. Counts, never scores.
Closed without a grade — superseded by events or abandoned. Never counted with the accuracy record.
Still standing. Due language splits past from future.
Derived breakdowns (confidence × outcome, signal families) live in the calibration deep-dive; a derived cell under the minimum group size reads “Held” there.
Early-record retro pass pending — aggregate assessment will publish here; no per-record retro verdicts.