OpenControls Logo

STIG Viewer

STIGViewer Support

Symantec ProxySG must use Transport Layer Security (TLS) to protect the authenticity of communications sessions.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-94311SYMP-AG-000490SV-104265r1_ruleCCI-001184high
Description
Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. This requirement focuses on communications protection for the application session rather than for the network packet and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. Depending on the required degree of confidentiality and integrity, web services/SOA will require the use of mutual authentication (two-way/bidirectional).
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.

NET-09Session Integrity
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (30) 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
AU-10(1)Association of Identities
1.00
AU-10(2)Validate Binding of Information Producer Identity
1.00
AU-9(3)Cryptographic Protection
1.00
CM-14Signed Components
1.00
CM-5(3)Signed Components
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
IA-2(1)Multi-factor Authentication to Privileged Accounts
1.00
IA-2(12)Acceptance of PIV Credentials
1.00

+20 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.15
1.00
CCI1 mapping
CCI-001184
1.00

Details

Check Text (C-104265r1_chk)

Verify that only FIPS-compliant HMAC algorithms are in use. 1. Log on to the ProxySG CLI via SSH. 2. Type "show management services". 3. Verify the "Cipher Suite" attribute lists only cipher suites that use FIPS-compliant HMAC algorithms. If any cipher suites are listed that use non-FIPS-compliant HMAC algorithms, this is a finding.

Fix Text (F-100427r1_fix)

Configure the ProxySG to use only FIPS-compliant HMAC algorithms. 1. Log on to the ProxySG SSH CLI. 2. Type "enable" and enter the enable password. 3. Type "configure terminal" and press "Enter". 4. Type "management-services" and press "Enter". Type "edit HTTPS-Console" and press "Enter". 5. Type "view" to display the list of configured cipher suites. 6. Type "attribute cipher-suite" followed by a space-delimited list of only cipher suites from step 5 that use FIPS-compliant HMAC algorithms and press "Enter".