OpenControls Logo

STIG Viewer

STIGViewer Support

Symantec ProxySG providing forward proxy encryption intermediary services must use NIST FIPS-validated cryptography to implement encryption services.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-94303SYMP-AG-000450SV-104257r1_ruleCCI-002450medium
Description
Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The network element must implement cryptographic modules adhering to the higher standards approved by the Federal government since this provides assurance they have been tested and validated. This requirement applies only to ALGs that provide encryption intermediary services (e.g., HTTPS, TLS, or DNSSEC).
STIGDate
Symantec ProxySG ALG Security Technical Implementation Guide2020-03-27

Related Frameworks

1 mapping across 5 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.

CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
CRY-01.2Export-Controlled Cryptography
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (29) 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-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-3Access Enforcement
1.00
AU-9(3)Cryptographic Protection
1.00
CM-5(6)Limit Library Privileges
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
IA-2(8)Access to Accounts — Replay Resistant
1.00
IA-2(9)Network Access to Non-privileged Accounts — Replay Resistant
1.00
IA-3(1)Cryptographic Bidirectional Authentication
1.00
IA-5(1)Password-based Authentication
1.00

+19 more (top 10 by confidence shown)

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.11
1.00
CCI1 mapping
CCI-002450
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 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.DS-01
1.00
PR.DS-02
1.00
PR.DS-10
1.00

Who does this work

8 NICE work roles and 7 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-104257r1_chk)

Verify that TLS intermediary services are configured to comply with NIST FIPS-validated cryptography. 1. Log on to the Web Management Console. 2. Click Configuration >> Visual Policy Manager. 3. Click "Launch". While in the Visual Policy Manager, for each SSL Access Layer that is configured, verify there is a rule with an action set to "Deny" that also has "Source" and "Destination" fields that contain a negated list of NIST FIPS-validated SSL/TLS protocols and ciphers. If Symantec ProxySG providing forward proxy encryption intermediary services does not use NIST FIPS-validated cryptography to implement encryption services, this is a finding.

Fix Text (F-100419r1_fix)

Configure TLS intermediary services to comply with NIST FIPS-validated cryptography. 1. Log on to the Web Management Console. 2. Click Configuration >> Visual Policy Manager. 3. Click "Launch". While in the Visual Policy Manager, click Policy >> Add SSL Access Layer. 4. Right-click the "Source" field of the existing rule and select "Set". Click "New" and select "Combined Source Object". 5. Click "New" and select "Client Negotiated Cipher". Select all ciphers that should be permitted and click "OK". 6. Click the upper "Add" button and click the "Negate" checkbox. 7. Click "New" and select "Client Negotiated SSL Version". Select all NIST FIPS-validated SSL versions that should be permitted and click "OK". 8. Click the upper "Add" button. 9. Click "OK" and then "OK" again. 10. Repeat steps 4-9 for the "Destination" field using the "Server Negotiated Cipher" and "Server Negotiated SSL Version" objects. 11. Right-click the "Action" field of the rule, click "Set", and select "Deny". 12. Click File >> Install Policy on SG Appliance.