Primary Domain
Risk and Accountability
Within the Primary Domain facet, Risk and Accountability intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
North America Institutional
Three Mile Island made control-room instrumentation a nuclear-operations accountability test
The Three Mile Island Unit 2 accident was initiated by equipment trouble, but it became severe inside an operating system that repeatedly converted physical evidence into misleading or unusable information. A relief valve remained open while its control-room light implied…
Asia-Pacific Institutional
Bhopal made methyl isocyanate containment a process-safety accountability test
Bhopal's physical trigger was water entering a methyl isocyanate tank, but the public catastrophe emerged from a wider loss of control over inventory, maintenance, safeguards, warning, medical evidence and long-term repair. Reconstructing that chain before assigning…
Europe and Middle East Institutional
Piper Alpha made permit-to-work handover an offshore-safety accountability test
Piper Alpha was not destroyed because one form went missing. The disaster showed what happens when maintenance status, shift knowledge, production authority, fire protection, pipeline dependencies and emergency command cease to operate as one controlled system. The accountability…
Europe and Middle East Institutional
King's Cross made escalator maintenance and emergency response a transit-safety accountability test
The 1987 King's Cross Underground fire began as a small, survivable ignition beneath a wooden escalator and became a mass-fatality disaster in about 20 minutes. The public inquiry found not one inexplicable failure but a connected control breakdown: combustible and contaminated…
Europe and Middle East Institutional
Herald of Free Enterprise made bow-door status a ferry-operations accountability test
The Herald of Free Enterprise did not capsize because a ferry operator lacked a person nominally assigned to close its bow doors. It capsized because an open-door departure remained possible after earlier warnings, because the bridge had neither a positive closure report nor a…
Global Institutional
Heartbleed made shared cryptographic maintenance a systemic-dependency accountability test
Heartbleed was a small bounds-checking error inside a widely shared cryptographic library, but its accountability footprint extended far beyond one function or one project. The defect could expose process memory without authentication, while reliable historical exploitation…
North America Institutional
Nasdaq's Facebook IPO failure made order matching a market-infrastructure accountability test
Facebook's May 2012 market debut did not fail because an exchange stopped matching orders altogether. It failed because one special-purpose cross entered a cancellation-driven calculation loop, operators launched modified software before they understood the state it would use…
North America Institutional
Robinhood's March 2020 outages made change management a retail-trading accountability test
Robinhood's breakdown during volatile markets was not one undifferentiated outage. The 2-3 March failure followed an overload and cascade; the 9 March interruption followed an untested protocol change combined with a coding error. The durable accountability question is why a…
Asia-Pacific Institutional
Tokyo Stock Exchange made hardware failover a market-continuity accountability test
Tokyo Stock Exchange did not lose an entire trading day on 1 October 2020 merely because one memory card failed. The card failed inside a redundant shared-disk device; the configured standby did not take over; market-data and market-control functions shared that dependency; and…
Europe and Middle East Institutional
British Airways made data-centre power recovery a passenger-continuity accountability test
British Airways' May 2017 disruption began with a power failure at its primary data centre and became a three-day test of whether an airline could recover the digital operating fabric behind check-in, flight dispatch, baggage, customer communication and rebooking. The public…
Global Cloud Services
GitLab made backup-restore proof a developer-platform accountability test
GitLab is a risk and accountability case because the 2017 GitLab.com database incident showed how a hosted developer platform can make backup evidence, restore drills, administrator access, replica separation, and customer communication part of the product trust boundary. The…
Global Cloud Services
Codecov made Bash uploader trust a CI-secret accountability test
Codecov is a risk and accountability case because the 2021 Bash uploader compromise showed how a developer telemetry tool can become a credential collection point inside customer CI environments. The issue is not only that a script was modified. The issue is who controlled…
Global Cloud Services
CircleCI made customer secret rotation a cloud-CI accountability test
CircleCI's January 2023 security incident became a cloud-CI accountability case because the platform did not merely store build metadata. It held customer environment variables, project keys, OAuth tokens, API tokens, SSH keys, and runner secrets that could connect customer code…
Global Cloud Services
Retool made MFA support workflows a social-engineering accountability test
Retool's 2023 social-engineering incident became an enterprise automation accountability case because the failure path did not stop at one phished employee. Retool said the attacker combined SMS phishing, a voice call, a fake identity portal, a one-time code, cloud-synced…
Global Cloud Services
OneLogin made AWS key exposure an identity-provider accountability test
OneLogin is a risk and accountability case because the May 2017 AWS key incident showed how a cloud identity provider can turn one infrastructure credential exposure into a customer-wide trust-chain reset problem. The public record matters for enterprise customers, employees…
Global Institutional
British Library made ransomware recovery a cultural public-service continuity test
British Library is a risk and accountability case because the October 2023 ransomware attack showed that cultural institutions now operate critical digital public services whose continuity must be judged by access to collections, research workflows, public communication, data…
North America Institutional
City of Atlanta made SamSam recovery a municipal-service accountability test
City of Atlanta is a risk and accountability case because the March 2018 SamSam ransomware incident showed how local-government technology debt can turn into public-service delay, emergency procurement, resident burden, and taxpayer cost. The public record matters for residents…
North America Institutional
Baltimore made ransomware recovery a civic cost-transfer accountability test
Baltimore City is a risk and accountability case because the 2019 ransomware disruption showed how municipal cyber harm can be paid through delayed civic transactions, emergency remediation, public uncertainty, and taxpayer-funded recovery even when the original intrusion path…
Global Cloud Services
VFEmail made backup independence an email-service accountability test
VFEmail is a risk and accountability case because its 2019 destructive attack showed how a small hosted email provider can become continuity infrastructure for users, small businesses, senders, recipients, and administrators when mailbox data, backup independence, recovery…
North America Institutional
Knight Capital made deployment rollback a market-control accountability test
Knight Capital Group is a risk and accountability case because the August 2012 trading incident showed how a software deployment failure can become a market-control failure when release management, dormant-code removal, pre-trade risk limits, real-time supervision, and…