McAfee Application Control 8.x Security Technical Implementation Guide

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]

Details

Version / Release: V1R6

Published: 2020-03-27

Updated At: 2020-05-11 21:06:41

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-88849r1_rule MCAC-PO-000100 CCI-001774 MEDIUM A McAfee Application Control written policy must be documented to outline the organization-specific variables for application whitelisting. 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 specif
    SV-88869r2_rule MCAC-PO-000103 CCI-000197 MEDIUM The Solidcore client Command Line Interface (CLI) Access Password protection process must be documented in the organizations written policy. 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 capab
    SV-88871r2_rule MCAC-PO-000104 CCI-000199 MEDIUM The requirement for scheduled Solidcore client Command Line Interface (CLI) Access Password changes must be documented in the organizations written policy. 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 man
    SV-88873r1_rule MCAC-PO-000105 CCI-002041 MEDIUM The process by which the Solidcore client Command Line Interface (CLI) Access Password is made available to administrators when needed must be documented in the organizations written policy. 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 capab
    SV-88875r1_rule MCAC-PO-000106 CCI-001240 MEDIUM The McAfee Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be confined to the organizations enclave. Data will be leaving the endpoint to be analyzed by the ATD. Because data could feasibly be intercepted en route, risk of outside threats is minimized by ensuring the ATD is in the same enclave as the endpoints.
    SV-88877r1_rule MCAC-PO-000108 CCI-001774 MEDIUM The configuration of features under McAfee Application Control Options policies Enforce feature control must be documented in the organizations written policy. By default, the McAfee Application Control prevents installation of ActiveX controls on endpoints, enforces memory protection techniques on endpoints, and prevents MSI-installers from running on endpoints. The Feature Control allows for those safeguards t
    SV-88879r1_rule MCAC-PO-000109 CCI-001774 MEDIUM The organizations written policy must include a process for how whitelisted applications are deemed to be allowed. 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 specif
    SV-88881r1_rule MCAC-PO-000110 CCI-001774 MEDIUM The organizations written policy must include procedures for how often the whitelist of allowed applications is reviewed. 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 specif
    SV-88883r2_rule MCAC-TE-000100 CCI-001774 MEDIUM The Solidcore client must be enabled. The Application Control whitelisting must be enabled on all workstation endpoints. To enable Application Control, the Solidcore client needs to be in enabled mode.
    SV-88885r2_rule MCAC-TE-000101 CCI-001762 HIGH The Solidcore client Command Line Interface (CLI) must be in lockdown mode. By default, when an endpoint's Solidcore installation is managed by the ePO server, the CLI will automatically be in lockdown mode. This will ensure the endpoint receives all of its Solidcore configuration settings from the ePO server. The CLI can, howeve
    SV-88887r1_rule MCAC-TE-000102 CCI-001774 HIGH The Solidcore client Command Line Interface (CLI) Access Password must be changed from the default. 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 capab
    SV-88889r3_rule MCAC-TE-000103 CCI-001774 MEDIUM The organization-specific Rules policy must only include executable and dll files that are associated with applications as allowed by the organizations written policy. To ensure Solidcore clients are only configured to STIG and organization-specific settings, organization-specific ePO policies must be applied to all organization workstation endpoints. The McAfee Application Control installs with two Default Rules polic
    SV-88891r3_rule MCAC-TE-000104 CCI-001240 MEDIUM The McAfee Application Control Options Reputation setting must be configured to use the McAfee Global Threat Intelligence (McAfee GTI) option. If a Threat Intelligence Exchange (TIE) server is being used in the organization, reputation for files and certificates is fetched from the TIE server. The reputation values control execution at endpoints and are displayed on the Application Control pages
    SV-88893r2_rule MCAC-PO-000101 CCI-000200 MEDIUM The use of a Solidcore 8.x local Command Line Interface (CLI) Access Password must be documented in the organizations written policy. 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 capab
    SV-88895r1_rule MCAC-PO-000102 CCI-001619 MEDIUM The Solidcore client Command Line Interface (CLI) Access password complexity requirements must be documented in the organizations written policy. 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 man
    SV-88897r2_rule MCAC-TE-000105 CCI-001774 MEDIUM The McAfee Application Control Options Reputation-Based Execution settings, if enabled, must be configured to allow Most Likely Trusted or Known Trusted only. When a file is executed on an endpoint, the Application Control performs multiple checks to determine whether to allow or ban the execution. Only files with a reputation of "Most Likely Trusted", "Known Trusted" or "Might be Trusted" are considered to be
    SV-88899r2_rule MCAC-TE-000106 CCI-001240 MEDIUM The McAfee Application Control Options Advanced Threat Defense (ATD) settings must not be enabled unless an internal ATD is maintained by the organization. This option will automatically send files with a specific file reputation to ATD for further analysis. This option is not selected by default and must only be selected if an ATD is being used.
    SV-88901r2_rule MCAC-TE-000107 CCI-001240 MEDIUM The McAfee Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be configured to send all binaries with a reputation of Might be Trusted and below for analysis. When the file reputation of "Might be Trusted" is configured for being forwarded to ATD, all files with the reputation of "Might be Trusted", "Unknown", "Might be Malicious", "Most Likely Malicious" and "Known Malicious" are forwarded to the ATD. The fil
    SV-88903r2_rule MCAC-TE-000108 CCI-001240 MEDIUM The McAfee Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be configured to only send binaries with a size of 5 MB or less. Since binaries can be large, the file size must be limited to avoid congestion on the network and degradation on the endpoint when sending the binaries to the ATD.
    SV-88905r2_rule MCAC-TE-000109 CCI-001774 MEDIUM Organization-specific McAfee Applications Control Options policies must be created and applied to all endpoints. To ensure Solidcore clients are only configured to STIG and organization-specific settings, organization-specific ePO policies must be applied to all organization workstation endpoints rather than resorting to the McAfee Applications Control (Default) pol
    SV-88907r2_rule MCAC-TE-000110 CCI-001774 MEDIUM The McAfee Application Control Options policy must be configured to disable Self-Approval. The McAfee Application Control Self-Approval feature allows the user to take an action when a user tries to run a new or unknown application.
    SV-88909r2_rule MCAC-TE-000111 CCI-001774 MEDIUM The McAfee Application Control Options policy End User Notification, if configured by organization, must have all default variables replaced with the organization-specific data. The "User Message" option will show a dialog box when an event is detected and display the organization-specified text in the message.
    SV-88911r2_rule MCAC-TE-000112 CCI-001774 MEDIUM The McAfee Application Control Options policies memory protection feature must not be enabled. By default, the McAfee Application Control prevents installation of ActiveX controls on endpoints, enforces memory protection techniques on endpoints, and prevents MSI-installers from running on endpoints. The Feature Control allows for those safeguards t
    SV-88913r2_rule MCAC-TE-000113 CCI-001774 MEDIUM Enabled features under McAfee Application Control Options policies Enforce feature control must not be configured unless documented in written policy and approved by ISSO/ISSM. By default, the McAfee Application Control prevents installation of ActiveX controls on endpoints, enforces memory protection techniques on endpoints, and prevents MSI-installers from running on endpoints. The "Feature Control" allows for those safeguards
    SV-88915r2_rule MCAC-TE-000114 CCI-001774 MEDIUM The McAfee Application Control Options Inventory option must be configured to hide OS Files. By default, the Windows operating system files are excluded from the inventory. By selecting this option, the overwhelming the inventory with legitimate Windows Files in the \Windows folder which are signed by the Microsoft certificate and all files in th
    SV-88917r3_rule MCAC-TE-000115 CCI-001774 MEDIUM The McAfee Application Control Options Inventory interval option must be configured to pull inventory from endpoints on a regular basis not to exceed seven days. When McAfee Application Control is deployed on a system, it creates a whitelist of all executable binaries and scripts present on the system. The whitelist contains all authorized files, and only files that are present in the whitelist are allowed to exec
    SV-88921r2_rule MCAC-TE-000117 CCI-001774 MEDIUM The McAfee Applications Default Rules policy must be part of the effective rules policy applied to every endpoint. To ensure Solidcore clients are only configured to STIG and organization-specific settings, organization-specific ePO policies must be applied to all organization workstation endpoints. The McAfee Application Control installs with two Default Rules polic
    SV-88923r2_rule MCAC-TE-000118 CCI-001774 MEDIUM A copy of the McAfee Default Rules policy must be part of the effective rules policy applied to every endpoint. To ensure Solidcore clients are only configured to STIG and organization-specific settings, an organization-specific ePO policies must be applied to all organization workstation endpoints. The McAfee Application Control installs with two Default Rules po
    SV-88925r2_rule MCAC-TE-000119 CCI-001774 MEDIUM The organization-specific Rules policies must be part of the effective rules policy applied to all endpoints. To ensure Solidcore clients are only configured to STIG and organization-specific settings, an organization-specific ePO policies must be applied to all organization workstation endpoints. The McAfee Application Control installs with two Default Rules po
    SV-88927r2_rule MCAC-TE-000120 CCI-001774 MEDIUM The organization-specific Solidcore Client Policies must be created and applied to all endpoints. McAfee Application Control is deployed with default policies. To ensure the default policies are not used and that an organization knowingly configures their systems to their own configuration requirements, organization-specific policies will need to be c
    SV-88929r2_rule MCAC-TE-000121 CCI-001774 MEDIUM The Throttling settings must be enabled and configured to settings according to organizations requirements. The throttling settings regulate the data flow between the clients and McAfee ePO. The value for each category defines the number of entries that will be sent to the McAfee ePO daily. Clients start caching for the defined category when the specified thres
    SV-88931r2_rule MCAC-TE-000123 CCI-001774 MEDIUM The Solidcore Client Exception Rules must be documented in the organizations written policy. When exceptions are created for applications, it results in potential attack vectors. As such, exceptions should only be created with a full approval by the local ISSO/ISSM. The organization's entire written policy requires approval by the ISSO/ISSM/AO an