JB3

Implementation of MANRS Actions

• Action 1: Prevent propagation of incorrect routing information All announcements are default denied with a small subset of permissive rules to ensure that all BGP announcements are valid, we RPKI our outgoing routes as well as our incoming ones.
• Action 2: Prevent traffic with spoofed source IP addresses Reverse path filtering is heavily utilised to prevent IP address spoofing. No services that are vulnerable to amplification attacks are left exposed unprotected (e.g. DNS resolvers)
• Action 3: Facilitate global operational communication and coordination We confirm and amend contact details on a regular basis on public directories such as PeeringDB, as well as on our domain at locations such as https://jb3.dev/.well-known/security.txt, all communications are treated as high priority and responded to in a timely manner.
• Action 4: Facilitate validation of routing information on a global scale All prefixes AS211224 announces are signed with RPKI, as well as having valid IRR routing entries.