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 5 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-74197

CAT II (Medium)

The requirement for scheduled Solidcore client Command Line Interface (CLI) Access Password changes must be documented in the organizations written policy.

Rule ID

SV-88871r1_rule

STIG

McAfee Application Control 7.x Security Technical Implementation Guide

Version

V1R4

CCIs

CCI-000199

Discussion

The Solidcore client can be configured locally at the CLI, but only when accessed with the required password. The misuse of the CLI would open the system up to the possible configuration, allowing malicious applications to execute unknowingly. Strict management of the accessibility of the CLI is necessary in order to prevent its misuse.

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 the Solidcore client interface is used by the organization.

Verify the policy identifies the frequency with which the CLI password is changed.

If the written policy does not contain specific information on frequency with which the CLI password is changed, this is a finding.

Fix Text

Follow the formal change and acceptance process to update the written policy with specific information on the frequency with which the CLI password is changed.