THE CONNECTIONS BEHIND THE INCIDENTS
Incident linkage map
Generated in your browserAn interactive view of how publicly reported incidents connect — in particular, supply-chain breaches where one provider's compromise reaches several organisations.
Each node is an incident, labelled by organisation and coloured by its role. Arrows point from an upstream incident to the records it affected; dashed links join separate incidents at the same organisation. Click a node to inspect it, double-click to open it in the directory. Positions show connections, not geography or severity.
- Direct incidents
- —
- Upstream incidents
- —
- Standalone incidents
- —
— downstream records excluded, including incidents with both roles.
Direct incidents = upstream + standalone, based on recorded causal links. Standalone incidents have no upstream or downstream causal links, but may have other links, such as separate events at the same organisation.
- Incidents in map
- —
- With recorded connections
- —
- Recorded connections
- —
- Connected networks
- —
- Upstream
- Downstream
- Unlinked(—)
- Both roles
- Other related
- Recorded relationship (arrow = upstream → downstream)
Drag to pan, scroll to zoom, hover a node for its name. Unlinked nodes have no recorded connection; proximity does not imply a relationship.
Reading the map
Orange marks upstream incidents (a provider whose breach reached others), blue downstream incidents, and purple unlinked incidents with no recorded connection. Teal marks incidents with both roles; charcoal marks other related incidents, such as separate events at the same organisation. A missing connection does not establish that two incidents are unrelated.
About this map
The graph is generated in your browser from the published incident data using a force-directed layout. Larger nodes are providers that affected more organisations. It is an overview of recorded relationships, not a complete map of cyber incidents in Singapore.