Title: Applications providing information flow control must uniquely authenticate destination domains when transferring information.
Vulnerability ID: V-32230
IA Controls: None
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.
Specific examples of flow control enforcement can be found in boundary protection devices (e.g., proxies, application gateways, guards, cross domain systems) employing rule sets or establish configuration settings restricting information system services, provide a packet-filtering capability based on header information, or message-filtering capability based on content (e.g., using key word searches or document characteristics).
Attribution, (e.g., the ability to attribute actions to individuals), processes or systems, is a critical component of a security concept of operations.
The ability to identify source and destination points for information flowing in an information system, allows forensic reconstruction of events when required, and increases policy compliance by attributing policy violations to specific organizations/individuals.
This requirement is specific to network devices designed to perform information 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]
As noted, this does not apply to SQL Server databases.
The closest we have in SQL Server to controlling the travel of information is via the use of linked servers and endpoints.
Be sure to check your SQL Servers for any configured linked servers and endpoints and be aware of what they are used for.