security-map.mdx

title	Security Map | Security Alliance
description	Explore the SEAL Security Map: trace assets, attack surfaces, threats, and controls, assess implementation locally, and open exact framework guidance.
tags	Security Specialist Operations & Strategy
contributors	role users wrote mattaereal role users reviewed role users fact-checked

import { SecurityMap, TagList, AttributionList, ContributeFooter } from '../../../components'

Security Map

:::warning[Experimental] The Security Map is experimental. Coverage, layout, and local assessment format may change. :::

🔑 Key Takeaway: Click a field. Related fields in the other columns are what actually connect to it. Assess controls, not threats. Ratings stay in this browser.

Six columns follow how a failure actually travels: what can be lost, who holds it, how it is reached, how it fails, what reduces that failure, and where the Frameworks page lives.

Click one field. Related fields in the other columns light up. The default view is one job (multisig), not every node. Other chips cut the map to deployment, domains, signers, supply chain, response, AI agents, ENS, disclosure, or the threat model. All is last. Certification modules sit in the guidance column and use evaluated-by, not a seventh column. The docs column is too narrow for six columns plus guidance, so open the full map in a new tab.

Shareable URLs may include view and focus. They never include assessment state. Bare /map opens the multisig job. Use view=view-all for every node.

The Attack Surface Overview is a separate radial checklist of threat vectors. This map is the graph of assets, surfaces, threats, and controls.

How to read the map

• Assets are things whose confidentiality, integrity, availability, authenticity, or control matters.
• Components are the people, devices, accounts, pipelines, and services in play.
• Attack surfaces are specific workflows or trust boundaries, not whole domains.
• Threats are adversarial actions or failure modes. They are not assessment items.
• Controls are the only things you rate. Not assessed is the default.
• Guidance opens the matching Frameworks page. Response procedures sit in this column.

Numbers on a field are related threats. Zero incidents in this seed. An incident needs a source.

Local assessment

Assessment files are versioned JSON stored under seal-security-map-assessment:v1. Import replaces the current assessment after a preview. Treat exports as sensitive: they can reveal missing controls.

Further reading

• docs/data/security-map/README.md in this repository: how maintainers add nodes and edges
• Content model: page contracts the map links into
• Contributing: PR workflow for framework-scoped map expansions
• Attack Surface Overview: radial threat-vector checklist

---