DoD STIGs – V-32587

Overview:

Title: For those instances where the organization requires encrypted traffic to be visible to information system monitoring tools, the application transmitting the encrypted traffic must make provisions to allow that traffic to be visible to specific system monitoring tools.

Vulnerability ID: V-32587

STIG ID:

IA Controls: None

Severity: medium

Description: There is a recognized need to balance encrypting traffic versus the need to have insight into the traffic from a monitoring perspective.

For some organizations, the need to ensure the confidentiality of traffic is paramount; for others, the mission-assurance concerns are greater.

This requirement is specific to network applications responsible for encrypting and decrypting network traffic. This requirement is NA for databases.

Check Text: This check is NA for databases.

Fix Text: This fix is NA for databases.

[divider]

Interpreting V-32587:

As noted, this does not apply to SQL Server databases.

SQL Server is capable of using SSL or TLS to secure the data being transferred between host and client. This is done using a certificate and configuring the SQL Server service to use the certificate to encrypt connections. If you do not have a certificate available, the “force encryption” server configuration option will generate a self-signed key to use.

Return to the DoD STIGs – Database Security Requirements Guide

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.