← Back to Trellix Application Control 8.x Security Technical Implementation Guide

V-213316

CAT II (Medium)

A Trellix Application Control written policy must be documented to outline the organization-specific variables for application whitelisting.

Rule ID

SV-213316r961479_rule

STIG

Trellix Application Control 8.x Security Technical Implementation Guide

Version

V3R2

CCIs

CCI-001774

Discussion

Enabling application whitelisting without adequate design and organization-specific requirements will either result in an implementation which is too relaxed or an implementation which causes denial of service to its user community. Documenting the specific requirements and trust model before configuring and deploying the Trellix Application Control software is mandatory.

Check Content

Consult with the ISSO/ISSM to review the organizational-specific written policy for the Trellix Application Control software.

If no written policy exists, this is a finding.

Fix Text

Document fully the written policy for the Trellix Application Control software, to include processes for password management, vetting application for whitelist/blocking, frequency of reviewing application whitelist, and settings for other requirements in this STIG.

Submit the written policy to be initially approved by and maintained by the Information System Security Officer/Information System Security Manager (ISSO/ISSM/AO) at that location.

Formalize a change control process to ensure changes to the written policy are made in a controlled manner. 

Formalize a review process requiring signed acceptance by the ISSO/ISSM/AO for any changes made to the written policy. 

If a formal Change Advisory Board (CAB) or Configuration Control Board (CCB) exists, the Trellix Application Control written policy must be under the CAB/CCB oversight.