Trellix Application Control 8.x STIG Version Comparison

There are 14 differences between versions v2 r1 (Oct. 23, 2020) (the "left" version) and v2 r2 (Jan. 24, 2024) (the "right" version).

Check MCAC-PO-000100 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

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

Check Content

Consult with the ISSO/ISSM to review the organizational-specific written policy for the McAfee Trellix Application Control software. If no written policy exists, this is a finding.

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 McAfee Trellix Application Control software is mandatory.

Fix

Document fully the written policy for the McAfee 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 McAfee Trellix Application Control written policy must be under the CAB/CCB oversight.