STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to McAfee Application Control 7.x Security Technical Implementation Guide

V-74205

CAT II (Medium)

The organizations written policy must include a process for how whitelisted applications are deemed to be allowed.

Rule ID

SV-88879r1_rule

STIG

McAfee Application Control 7.x Security Technical Implementation Guide

Version

V1R4

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

Check Content

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

Verify the written policy includes a process for how applications are vetted and deemed to be allowed.

If no written policy exists, this is a finding.

If written policy does not include a process for vetting applications before allowing them, this is a finding.

Fix Text

Follow the formal change and acceptance process to update the written policy to include a process for how applications are vetted and deemed to be allowed.