The organizations written policy must include procedures for how often the whitelist of allowed applications is reviewed.

From McAfee Application Control 7.x Security Technical Implementation Guide

Associated with: CCI-001774

SV-88881r1_rule The organizations written policy must include procedures for how often the whitelist of allowed applications is reviewed.

Vulnerability 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 often the application whitelist is reviewed. If no written policy exists, this is a finding. If written policy does not include a process for how often the application whitelist is reviewed, this is a finding.

Fix text

Follow the formal change and acceptance process to update the written policy to include a process for how often the application whitelist is reviewed.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.