previous: Restrict Control
Plane Access | Contents page | next: Restrict Agentic Write Access
Minimize Network Exposure
BSSC Node Operation - Audit Framework
Domain: Security and Access Control |
Level: MUST | Type: Preventive
Statement of Requirement:
The network exposure of node clients MUST be minimized to include
only the services essential for effective network operation.
See it in the specification
Purpose
Minimize attack surfaces
Audit Procedures
Verify that
network services each node type is intended to expose is justified
by its operational requirements
only a minimum set of ports/services are exposed by each node
documentation accurately describes and responsible personnel
understand how to determine which services to expose, how new services
are evaluated, and what process governs opening network ports.
Key Evidence
Network exposure policy/baseline listing required services per node
type with justification
Port scan results showing only expected services listening
Firewall/security group configurations (AWS SG, iptables, K8s
NetworkPolicies)
Node client configuration files showing disabled optional services
and localhost-only bindings
Success Criteria
Documented baseline exists defining minimum required network
services per node type
Firewall rules enforce default-deny allowing only documented
services
Port scans confirm no undocumented services externally
accessible
Node client configuration explicitly disables optional services not
required
Failed connection attempts to services that should not be externally
accessible
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
No documentation defining required network services
Firewall rules are permissive (allow all inbound, wide port ranges)
without justification
Port scans reveal undocumented exposed services (e.g. debug
endpoints, admin RPC)
Node clients running with default configs exposing unnecessary
services
Common Failure Patterns
Node clients run with default flags exposing JSON-RPC, WebSocket,
and debug on 0.0.0.0 rather than localhost;
firewall rules accumulate permissive exceptions;
monitoring/metrics endpoints are exposed externally;
execution client RPC exposed to internet "for convenience";
P2P ports are restricted but gRPC management ports left open;
permissive test or staging configurations are inadvertently promoted
to production.
Other Relevant Standards
A.8.20, A.8.22, A.8.9, A.8.8
CC6.1, CC6.6, CC7.1
1.2.1, 1.3.1, 2.2.4, 11.3.1
PR.AC-05, PR.PS-01, DE.CM-01
previous: Restrict Control
Plane Access | Contents page | next: Restrict Agentic Write Access