Ukraine 2015 power grid cyberattack: what CISA's report says
On 23 December 2015 attackers opened breakers at three Ukrainian utilities, affecting about 225,000 customers. What happened and what CISA advises.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
On 23 December 2015 attackers opened breakers at three Ukrainian utilities, affecting about 225,000 customers. What happened and what CISA advises.
The 2015 Ukrainian grid attack left about 225,000 customers without power. What CISA's alert says about access, impact and the defenses it recommends.
Bill Gates sent the Trustworthy Computing memo on 15 January 2002. Four pillars, and the lesson for any company that wants security treated as a priority.
The 2016 DAO hack explained: a reentrancy bug in splitDAO, about 3.6 million ETH moved, the hard fork that followed, and the lessons for contract developers.
Systemic risk is many failures from one shared dependency. A checklist to find your concentration points, with examples from CISA and Microsoft sources.
Geomagnetic storms can induce currents in power grids and disrupt GPS and satellites. What NOAA states, and what IT teams can plan for without panic.
CISA's SolarWinds advisory describes how the actor kept cloud access via service principals, federation trusts and forged SAML tokens. What to review.
Small counts bounce around by chance. A quick Poisson check tells you whether a rise from 3 to 5 incidents means anything before you reorganise the team.
One team can beat another in every severity group and still look worse overall. A worked patching example of Simpson's paradox and how to avoid it.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.