STIGViewer Support

Symantec ProxySG must fail to a secure state upon failure of initialization, shutdown, or abort actions.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-94315SYMP-AG-000510SV-104269r1_ruleCCI-001190medium
Description
Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Network elements that fail suddenly and with no incorporated failure state planning may leave the hosting system available but with a reduced security protection capability. Preserving system state information also facilitates system restart and return to the operational mode of the organization with less disruption to mission-essential processes. An example is a firewall that blocks all traffic rather than allowing all traffic when a firewall component fails (e.g., fail closed and do not forward traffic). This prevents an attacker from forcing a failure of the system to obtain access. Depending on the deployment architecture, there are many configurations to check external to the ProxySG to ensure that failures of initialization, shutdown, or abort actions result 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 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 (9) 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.

BCD-01Business Continuity Management System (BCMS)
1.00
CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
SEA-01Secure Engineering Principles
1.00
SEA-01.2Achieving Resilience Requirements
1.00
SEA-02Alignment With Enterprise Architecture
1.00
SEA-07.2Fail Secure
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

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

AU-3(2)Centralized Management of Planned Audit Record Content
1.00
AU-5Response to Audit Logging Process Failures
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
CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

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

Who does this work

13 NICE work roles and 8 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-104269r1_chk)

Verify that the transparent, physically in-line hardware ProxySG appliance is configured to fail securely in the event of failures of initialization, shutdown, or abort actions. 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 "failed-closed" radio button is not selected, this is a finding.

Fix Text (F-100431r1_fix)

Configure the transparent, physically in-line hardware ProxySG appliance to fail securely in the event of failures of initialization, shutdown, or abort actions. 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".