Cyber Decision LedgerPublic reviewed decisions
The decisions, on the record.
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.
Decision Records
npm supply-chain credential exposure response
Freeze affected npm promotion paths, block verified affected package versions, rebuild CI runners where install scripts may have executed, audit lockfiles and publish history, and rotate npm, GitHub, cloud, Kubernetes, and vault credentials where exposure is plausible.
Microsoft 365 account compromise containment
Do not rely on password reset alone after suspected or confirmed Microsoft 365 AiTM, payroll, or finance mailbox compromise. Revoke active sessions and refresh tokens, remove suspicious forwarding and inbox rules, review OAuth and device-code grants, re-register MFA or device trust from clean devices, and add out-of-band payment controls.
N-able N-central compromise handling
Treat exposed or MSP-connected N-able N-central environments as a compromise investigation, not a patch-only task. Isolate affected systems from direct internet and customer reach, apply the current vendor-fixed release, rotate administrative and remote-control credentials, and hunt downstream for unauthorized access and possible persistence.
Separate tracking for distinct incident classes
Do not treat the discussed incidents as one homogeneous campaign on the current packet evidence. Track separate evidence classes for CI/CD control-plane abuse, water-sector operational control exposure, identity trust abuse, cloud malware, SaaS or token exposure, and supply-chain activity until shared technical pivots justify merging them.
Token and session revocation before password resets
For exposed automation tokens, credential-based tenant compromise, or MFA phishing, revoke API tokens, workflow credentials, OAuth grants, sessions, remembered devices, recovery factors, and newly enrolled authenticators before relying on password resets.
Clean rebuild and secret rotation after developer or CI exposure
When indicators or confirmed exposure show malicious packages or trojanized installers touched developer workstations, CI runners, or publishing paths, rebuild affected systems from clean sources, rotate npm, Git, cloud, package-publishing, signing, and service-account secrets, and review artifacts and release logs before normal release activity resumes.
Operational emergency handling for water-utility PLC and HMI activity
When a water utility has reported or suspected PLC or HMI compromise, stand up an operations-led OT incident bridge, disable unnecessary remote access, tightly gate vendor access, validate physical plant state outside the HMI path, preserve controller state, and avoid blind PLC or SCADA changes during service risk.
Contain risky network-accessible Paperclip instances
Treat network-accessible Paperclip instances with risky default or authenticated configuration as emergency risk: restrict access or take them offline, disable registration and import paths where possible, preserve relevant logs and snapshots, upgrade after validating the fixed stream, and rotate reachable secrets.
Revoke reusable identity trust before rotating passwords
For credential-based intrusions, revoke active sessions, refresh tokens, OAuth grants, SAML sessions, remembered devices, API keys, and weak trust paths before or alongside scoped password rotation; move targeted privileged users toward phishing-resistant MFA.
Freeze executable dependency trust paths after package compromise
Freeze only build paths that can execute untrusted code, block known poisoned versions from authoritative sources, disable lifecycle scripts where possible, rebuild affected CI runners from clean images, and rotate exposed package, repository, cloud, Kubernetes, Vault, and deploy credentials.
Weak wallet seeds require asset migration
Treat affected or uncertain weak-randomness wallet seeds as exposed: stop new deposits to suspect addresses, create fresh keys on trusted systems, sweep funds to new seed material, rotate affected multisig cosigners, and monitor old addresses.
Water-sector exposed control-path containment
Operators should remove public exposure from controllers, HMIs, engineering workstations, VPNs, cellular modems, and vendor remote-access paths; preserve controller state; verify physical process conditions; and restore only after safe local control and trusted access paths are validated.
Coldcard seed-provenance fund migration
Yes. Where Coldcard seed provenance is affected or uncertain, treat the seed material as unsuitable for continued custody: generate fresh seed material on verified unaffected hardware or through an audited ceremony, migrate funds in staged transactions, and rotate multisig signers where provenance is uncertain.
AI-agent and SaaS identity token-broker lockdown
Yes. Treat AI-agent automation and SaaS identity flows as token-broker control planes tonight: restrict device-code authentication and OAuth consent, review high-risk app scopes, rotate automation and API tokens, use task-scoped least-privilege agent roles, require human approval for privileged tool calls, patch affected agent-framework deployments as vendor updates are available, and log tool-call provenance.
Water and wastewater OT safety-first continuity handling
Yes. Treat reported water and wastewater OT activity as a safety and continuity incident: verify local process state first, remove exposed cellular, PLC, HMI, and remote-access paths in an OT-safe sequence, rotate compromised credentials, prepare manual-safe operations, and coordinate with public-sector and public-health partners where needed.
Exposed N-able N-central compromise-assumption response
Yes. For exposed N-able N-central deployments, operate on a compromise assumption: isolate exposed access, restrict downstream remote-control paths, preserve logs, revoke administrative sessions and remote-management credentials, and hunt for persistence before restoring managed access.
Reusable trust artifact revocation for automation exposure
Respond to automation and token-abuse exposure by revoking reusable trust artifacts, not resetting passwords only. Pause exposed or autonomous workflows that can cross trust zones, revoke sessions and API tokens, rotate workflow-stored and connector secrets, restrict device-code and OAuth consent paths, segment automation runners, and log which identity called which API.
Developer-tool one-click execution patching
Engineering fleets, especially privileged developer workstations, should patch vendor-confirmed fixed releases immediately. Review telemetry for editor-launched shells or credential tooling after commit-link activity, and rotate GitHub, npm, cloud, CI, or signing credentials only where execution is suspected or privileged telemetry is missing.
Shai-Hulud npm publishing and CI/CD containment
Do not reopen npm publishing and CI/CD normally after Shai-Hulud package cleanup. Freeze risky publishing and dependency updates, identify affected direct and transitive paths from local lockfiles and inventories, hunt build hosts and developer endpoints, rotate reachable developer, cloud, and CI secrets, rebuild runners, and restore release authority only from clean credentials and verified packages.
N-able N-central control-plane containment
Treat exposed N-able N-central administration as an incident-response control-plane problem: remove direct internet exposure, apply vendor-confirmed fixes or mitigations, rotate administrative and API credentials, revoke active sessions, hunt for remote-control abuse and persistence, and review managed endpoints and customer access logs.
Harden hotel network use for high-risk travel
Yes. For executive, diplomatic, defense, energy, media, government, and similar high-risk travel, use separate or managed devices, phishing-resistant MFA, avoid sensitive logins over unmanaged hotel networks, and revoke or refresh tokens after travel.
Govern privileged AI agents as untrusted automation
Yes. Treat AI agents with CI/CD, cloud, browser, or internet authority as untrusted automation by removing long-lived secrets, using least-privilege tokens, separating read-only from write-capable agents, requiring human approval for privileged actions, blocking production credentials, filtering egress, logging tool calls, and alerting on unexpected workflow or secret-handling behavior.
Isolate exposed water control paths
Yes. If a water or wastewater control path is reachable from the internet, isolate or firewall it now, verify the physical process locally, preserve controller and network evidence, and require engineering approval before PLC logic, restart, patching, or network changes.
AI-mediated CI privileged automation controls
Treat AI agents and AI-mediated CI workflows as untrusted automation principals. Do not allow untrusted issues, comments, model output, or agent messages to directly drive privileged CI/CD or cloud actions; disable autonomous merge, deploy, and remediation authority until reviewed; use least-privilege short-lived credentials, deny-by-default sandbox egress, and human approval for privileged steps.
ChainDrop npm credential-compromise response
Treat ChainDrop exposure as developer and CI/CD credential compromise rather than simple package cleanup. Revoke and recreate package, source-control, cloud, Vault, Kubernetes, federation, registry, and build-system credentials; disable affected runners and publishing paths; rebuild clean workspaces; and block dependency versions identified by validated intelligence before restoring trusted publishing.
N-able N-central containment for exposed management environments
Treat exposed N-able N-central and Take Control environments as a critical containment event, not as patch-only remediation. Restrict management access, patch to validated fixed releases, revoke active admin sessions and credentials, and hunt for unauthorized remote-control activity and tunnel persistence before closure.
AI agent runtime isolation
Govern enterprise AI agents and evaluation sandboxes like privileged automation runtimes: use scoped identities, restrict secrets, control egress, isolate workspaces, narrow tool permissions, log activity, and require human approval for sensitive external actions.
FastJson urgent exposure management
For internet-facing Java services that parse untrusted JSON with affected FastJson 1.x, handle the issue as urgent exposure management: inventory deployed artifacts quickly, apply appropriate mitigations or replacement builds, plan migration, and hunt for runtime indicators.
Fleet-control command constraint during exposure validation
Fleet operators should temporarily disable or tightly constrain high-impact remote vehicle commands while validating exposed fleet-tracking data and API control paths.
Accelerated maintenance for exposed Oracle ERP and E-Business Suite
Approve emergency maintenance for Oracle ERP and E-Business Suite environments where externally reachable components, integrations, SSO paths, supplier portals, or mission-critical instances are confirmed exposed, while avoiding blind shutdowns without exposure confirmation.
Showing 30 records · page 2 of 9
These controls filter only the 30 records on this page. Search the full Ledger →