|Finding ID||Version||Rule ID||IA Controls||Severity|
|To prevent malicious or accidental leakage of traffic, organizations must implement a deny-by-default security posture at the network perimeter. Such rulesets prevent many malicious exploits or accidental leakage by restricting the traffic to only known sources and only those ports, protocols, or services that are permitted and operationally necessary. Applications, protocols, TCP/UDP ports, and endpoints (specific hosts or networks) are identified and used to develop rulesets and access control lists to restrict traffic to and from an enclave.|
|Network Infrastructure Policy Security Technical Implementation Guide||2018-09-27|
|Check Text ( C-7782r8_chk )|
| Determine if a deny-by-default security posture has been implemented for both inbound and outbound traffic on the perimeter router or firewall. |
If a deny-by-default security posture has not been implemented at the network perimeter, this is a finding.
|Fix Text (F-11043r6_fix)|
|Implement a deny-by-default security posture on either the enclave perimeter router or firewall.|