OpenControls Logo

STIG Viewer

STIGViewer Support

The RUCKUS ICX perimeter router must be configured to deny network traffic by default and allow network traffic by exception.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-273604RCKS-RTR-000370SV-273604r1110881_ruleCCI-001109high
Description
A deny-all, permit-by-exception network communications traffic policy ensures that only connections that are essential and approved are allowed. This requirement applies to both inbound and outbound network communications traffic. All inbound and outbound traffic must be denied by default. Firewalls and perimeter routers should only allow traffic through that is explicitly permitted. The initial defense for the internal network is to block any traffic at the perimeter that is attempting to make a connection to a host residing on the internal network. In addition, allowing unknown or undesirable outbound traffic by the firewall or router will establish a state that will permit the return of this undesirable traffic inbound.
STIGDate
RUCKUS ICX Router Security Technical Implementation Guide2025-06-03

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

NET-04.1Deny Traffic by Default & Allow Traffic by Exception
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (6) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-4Information Flow Enforcement
1.00
SC-24Fail in Known State
1.00
SC-5Denial-of-service Protection
1.00
SC-7Boundary Protection
1.00
SC-7(11)Restrict Incoming Communications Traffic
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.13.6
1.00
CCI1 mapping
CCI-001109
1.00

Details

Check Text (C-273604r1110881_chk)

Confirm that external interfaces are configured with ACLs that permit traffic by exception. ip access-list extended EXT-ACL sequence 10 permit sshow host x.x.x.x host y.y.y.y log sequence 20 permit ip x.x.x.0 0.0.0.255 any sequence 30 deny ip any any log interface ethernet x/x/x ip access-group EXT-ACL in logging enable If the ACL or filter is not configured to allow specific ports and protocols and deny all other traffic, this is a finding. If the filter is not configured inbound on all external interfaces, this is a finding.

Fix Text (F-77600r1109833_fix)

Apply ACL configuration to apply desired traffic restrictions: ip access-list extended EXT-ACL sequence 10 permit sshow host x.x.x.x host y.y.y.y log sequence 20 permit ip x.x.x.0 0.0.0.255 any sequence 30 deny ip any any log interface ethernet x/x/x ip access-group EXT-ACL in logging enable