Bare Metal Cyber

This week’s roll-up opens with a cloud ransomware outage that disrupted hundreds of companies and local governments in Japan, showing how one provider incident can spread across many operations. A sweeping FortiGate campaign also shows the danger of stolen privileged credentials, persistent administrator accounts, and ransomware access at the network edge. In Denmark, misuse of a trusted company’s registry access exposed identity data tied to millions of people. The issue also tracks active NetScaler compromises that can outlive patching and attacks against self-hosted Atlassian systems within hours of disclosure. Together, these stories make one theme clear: resilience depends on third-par…This week's stories:Japan cloud ransomware outage disrupts 495 organizationsStolen FortiGate access locks out admins and fuels ransomwareDenmark registry breach exposes data tied to 8.8 million peopleNetScaler attacks disrupt remote access and leave hidden controlSensitive Atlassian files face attacks within hours of disclosureFBI disrupts China-linked attacks on critical infrastructurePentagon breach creates long-term identity risk for millionsOld SharePoint gaps drive ransomware into critical servicesCountry-code registry breaches enable trusted website impersonationSouth Korean bank breaches expose customer and worker dataDeveloper secrets exposed by a compromised Tensorlake packageDeveloper access turns into cloud exposure through GitHub workflowsGitHub users face malware across 17,610 FakeGit repositoriesHelpdesk breach reaches full server control in seconds with AIExposed AI servers become cryptomining and attack launchpadsMore cybersecurity coverage at BareMetalCyber.com.

This week’s roll-up opens with ransomware crews exploiting TeamCity servers, putting trusted software build pipelines and downstream customers at risk. It then turns to actively exploited edge and security systems that can hand attackers control over network access and policy. A third major theme is scale: AI-assisted attacks reportedly stole more than 600,000 payment card records while reaching scores of retailers. The issue also examines altered water controls and a phishing service tied to 12,000 compromised Microsoft inboxes. Across the week, defenders face the same pressure: shorten patch windows, protect privileged control planes, and verify identities that ordinary reviews overlook.…This week's stories:Software pipelines face ransomware through exploited TeamCity serversNetwork access and security tools face active edge-system attacksOnline retailers lose 600,000 payment cards in AI-assisted attacksForeign hackers alter water controls at two Colorado utilitiesDevice-code phishing compromises 12,000 Microsoft inboxesGyazo breach exposes 23.62 million users and screenshot metadataAI agent crosses Australian government access controls unnoticedFBI jobs portal incident puts personnel and applicants at riskForgotten Microsoft 365 accounts expose emails, chats and filesFake job interviews infect 30,000 devices across 100 countriesWordPress attacks begin within hours of a critical security fixSharePoint attacks put unpatched and unsupported servers at riskNearly 1,000 Zyxel switches breached across 48 countriesRoundcube attacks threaten exposed webmail accounts and dataGitLab email tokens can open private code and software pipelinesMore cybersecurity coverage at BareMetalCyber.com.

Retiring a legacy system sounds simple until you realize one platform has quietly become the backbone of revenue, reporting, and regulatory history. In “The Last Legacy System: Planning for the Day You Finally Turn It Off,” the narrated version walks leaders through why one or two systems always outlive every modernization wave and why that matters for risk, resilience, and strategy. You will hear how technical entanglements, business lore, and hero culture combine to keep that last legacy system alive long after it should have been a conscious, time-bound decision.From there, the episode follows the structure of the Wednesday “Headline” feature from Bare Metal Cyber Magazine. It explores how to move from migration talk to a true business decision, how to model and rehearse the turn-off so it fails safely instead of catastrophically, and how to handle the humans in the loop whose identities are tied to keeping the system running. It closes by looking forward: what it means to design today’s systems with explicit exit strategies, clearer ownership, and governance that treats decommissioning as a first-class concern, so you do not quietly build the next untouchable relic.

When a major incident hits, most organizations still cling to the promise of “getting back to normal.” In this narrated Headline, “Real-World Recovery: When ‘Return to Normal’ Is the Wrong Goal,” we look at why that mindset quietly undermines resilience. The episode walks through how complex, cloud-heavy environments never truly return to a previous baseline, and why leaders are better served by thinking in terms of new, intentional steady states instead of rewinds. This audio is developed from my Wednesday “Headline” feature in Bare Metal Cyber Magazine, with a focus on the decisions that shape recovery long after the alerts stop.Across the narration, we explore the myth of “normal operations,” reframing recovery as a large-scale reconfiguration of identity, trust boundaries, and vendor dependencies. We dive into planned degraded modes and deliberate sacrifice decisions, then move into a portfolio view of recovery using named operating states rather than a single DR script. Finally, we turn to the leadership side: how to communicate that “normal has changed,” how to align boards and regulators on new baselines, and how to reward sustainable resilience instead of just fast restores. It is a practical guide for leaders who know incidents are inevitable and want their recovery story to match reality.

In this narrated edition of “Culture of Disclosure: From ‘Don’t Tell Anyone’ to ‘Report Early, Fix Faster’”, we walk through what really decides whether your organization hears the truth in time to act. You will hear how informal stories, career incentives, and leadership reactions quietly create a shadow “don’t tell anyone” policy, even when formal reporting channels exist. We connect those patterns to hard security outcomes: time-to-discovery, who finds your issues first, and how much room you have to maneuver when something goes wrong. This is a practical listen for leaders who suspect they are getting a filtered view of reality.The episode then breaks down the architecture of a healthy disclosure culture in plain, leader-ready terms. We look at psychological safety as a security control, the design of simple pipes for early reporting, and the metrics that reward high-signal disclosures instead of only counting fires. Finally, we explore what it looks like to lead when disclosure gets painful, from late-breaking findings before a launch to regulatory and customer communications. The narration is based on my Wednesday “Headline” feature in Bare Metal Cyber Magazine and is designed to help you pressure-test your own culture of disclosure.