OpenControls Logo

STIG Viewer

STIGViewer Support

Symantec ProxySG must fail securely in the event of an operational failure.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-94325SYMP-AG-000560SV-104279r1_ruleCCI-001126medium
Description
If a boundary protection device fails in an unsecure manner (open), information external to the boundary protection device may enter, or the device may permit unauthorized information release. Secure failure ensures that when a boundary control device fails, all traffic will be subsequently denied. Fail secure is a condition achieved by employing information system mechanisms to ensure that in the event of operational failures of boundary protection devices at managed interfaces (e.g., routers, firewalls, guards, and application gateways residing on protected subnetworks commonly referred to as demilitarized zones), information systems do not enter into unsecure states where intended security properties no longer hold. Depending on the deployment architecture, there are many configurations to check that are external to the ProxySG to ensure that an operational failure results in a secure state. With these external configurations in place, the ProxySG meets this requirement inherently. However, if a ProxySG hardware appliance is configured in a transparent, physically in-path manner, the check and fix on the ProxySG will apply.
STIGDate
Symantec ProxySG ALG Security Technical Implementation Guide2020-03-27

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.

SEA-01Secure Engineering Principles
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 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.

SC-7(18)Fail Secure
1.00
CCI1 mapping
CCI-001126
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (3) 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.

PR.IRTechnology Infrastructure Resilience
0.50
PR.IR-01
0.50
PR.IR-03
0.50

Details

Check Text (C-104279r1_chk)

Verify that the transparent, physically in-line hardware ProxySG appliance is configured to fail securely in the event of an operational failure. 1. Browse to Configuration >> Network >> Adapters >> Bridges. 2. Select the appropriate bridge-pair (whichever is in use) and click "Edit". 3. Verify that the "fail-closed" radio button is selected. If the "fail-closed" radio button is not selected, this is a finding.

Fix Text (F-100441r2_fix)

Configure the transparent, physically in-line hardware ProxySG appliance to fail securely in the event of an operational failure. 1. Browse to Configuration >> Network >> Adapters >> Bridges. 2. Select the appropriate bridge-pair (whichever is in use) and click "Edit". 3. Select the "fail-closed" radio button and click "Apply".