research: establish global network address book baseline
This commit is contained in:
@@ -0,0 +1,15 @@
|
||||
# Security and resilience
|
||||
|
||||
| Entity/initiative | Scope | Function | Public directory |
|
||||
|---|---|---|---|
|
||||
| FIRST | Global | Community and standards for incident response and security teams | [Member teams](https://www.first.org/members/teams/) |
|
||||
| Trusted Introducer | European community | Trust/accreditation services and CSIRT directory | [Team directory](https://www.trusted-introducer.org/directory/teams.html) |
|
||||
| MANRS | Global | Practical routing-security norms and participant recognition | [Participants](https://manrs.org/participants/) |
|
||||
| Route Views | Global measurement | Public BGP visibility for analysis | [Collectors](https://www.routeviews.org/routeviews/index.php/collectors/) |
|
||||
| RIPE RIS | Global measurement | Routing data and distributed collectors | [RIS](https://ris.ripe.net/) |
|
||||
|
||||
## Important distinction
|
||||
|
||||
A directory entry is not an authorization to send sensitive incident data. Follow each team's published reporting policy, use role-based channels, validate cryptographic identity where provided, and respect traffic-light/protected-sharing rules.
|
||||
|
||||
Routing security is also broader than route observation: later rounds should map RPKI trust anchors, ROA publication, validator software, ASPA deployment, IRR databases, and operational adoption metrics.
|
||||
Reference in New Issue
Block a user