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-74219

CAT II (Medium)

The use of a Solidcore 7.x local Command Line Interface (CLI) Access Password must be documented in the organizations written policy.

Rule ID

SV-88893r1_rule

STIG

McAfee Application Control 7.x Security Technical Implementation Guide

Version

V1R4

CCIs

CCI-000200

Discussion

The Solidcore client can be configured locally at the CLI, but only when accessed with the required password. Since the McAfee Application Control configuration is to be managed by ePO policies, allowing enablement of the CLI to would introduce the capability of local configuration changes. Strict management of the accessibility of the CLI is necessary in order to prevent its misuse. The misuse of the CLI would open the system up to the possible configuration changes potentially allowing malicious applications to execute unknowingly.

Check Content

Note: The CLI Access is in lockdown mode by default when being managed by ePO. Since the CLI Access can be recovered for troubleshooting, this requirement needs to be met.

Consult with the ISSO/ISSM to obtain a copy of the organization's documented policy for application whitelisting.

Review the written policy for how and when the Solidcore CLI is used by the organization.

If the use of the CLI is not documented in the organization's written policy, this is a finding.

Fix Text

Follow the formal change and acceptance process to update the organization's written policy with the use of the CLI.