DoD STIGs – V-32226

Overview:

Title: Applications must prevent encrypted data from bypassing content-checking mechanisms.

Vulnerability ID: V-32226

STIG ID:

IA Controls: None

Severity: medium

Description: Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information.

Information flow enforcement mechanisms compare security attributes on all information (data content and data structure), source and destination objects, and respond appropriately (e.g., block, quarantine, alert administrator) when the mechanisms encounter information flows not explicitly allowed by the information flow policy. When data is encrypted, devices and software designed to examine data content to detect attacks or malicious code are unable to accomplish the task unless they are capable of decrypting the data. Example includes decrypting email in order to scan attachments.

This requirement applies only to network devices specifically for handling flow control. 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-32226:

As this requirement focuses on network device compliance, it doesn’t really apply to SQL Server. You should still make sure connections used by SQL Server are secure. This means setting up SQL Server to use SSL on connections, to verifying you are aware of what each linked server and endpoint is used for and secured.

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.