{"stig":{"title":"McAfee Application Control 7.x Security Technical Implementation Guide","version":"1","release":"4"},"checks":[{"vulnId":"V-74175","ruleId":"SV-88849r1_rule","severity":"medium","ruleTitle":"A McAfee Application Control written policy must be documented to outline the organization-specific variables for application whitelisting.","description":"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.","checkContent":"Consult with the ISSO/ISSM to review the organizational-specific written policy for the McAfee Application Control software.\n\nIf no written policy exists, this is a finding.","fixText":"Document fully the written policy for the McAfee Application Control software, to include processes for password management, vetting application for whitelist/blocking, frequency of reviewing application whitelist, and settings for other requirements in this STIG.\n\nSubmit the written policy to be initially approved by and maintained by the Information System Security Officer/Information System Security Manager (ISSO/ISSM/AO) at that location.\n\nFormalize a change control process to ensure changes to the written policy are made in a controlled manner. \n\nFormalize a review process requiring signed acceptance by the ISSO/ISSM/AO for any changes made to the written policy. \n\nIf a formal Change Advisory Board (CAB) or Configuration Control Board (CCB) exists, the McAfee Application Control written policy must be under the CAB/CCB oversight.","ccis":["CCI-001774"]},{"vulnId":"V-74195","ruleId":"SV-88869r1_rule","severity":"medium","ruleTitle":"The Solidcore client Command Line Interface (CLI) Access Password protection process must be documented in the organizations written policy.","description":"The Solidcore client can be configured locally at the CLI, but only when accessed with the required password.\n\nSince 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. \n\nStrict management of the accessibility of the CLI is necessary in order to prevent its misuse.\n\nThe misuse of the CLI would open the system up to the possible configuration changes potentially allowing malicious applications to execute unknowingly.","checkContent":"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.\n\nConsult with the ISSO/ISSM to obtain a copy of the organization's documented policy for application whitelisting.\n\nReview the written policy for how the Solidcore client interface is used by the organization.\n\nVerify the policy identifies how the CLI password is protected.\n\nAsk the ePO admin, \"What protection measures are used for the CLI password?\"\n\nThe protection measures should include, at a minimum, storage in a sealed envelope, which is then stored in an approved safe.\n\nNote: The envelope will contain the last access date along with those authorized to use it.\n\nIf the written policy does not contain specific information on how the CLI password is protected and/or if that policy does not include, at a minimum, that the password be stored in a sealed envelope in an approved safe with the last access date noted, this is a finding.","fixText":"Follow the formal change and acceptance process to update the written policy with specific information on how the CLI password is protected and that the password must be stored in a sealed envelope in an approved safe with the last access date noted.","ccis":["CCI-000197"]},{"vulnId":"V-74197","ruleId":"SV-88871r1_rule","severity":"medium","ruleTitle":"The requirement for scheduled Solidcore client Command Line Interface (CLI) Access Password changes must be documented in the organizations written policy.","description":"The Solidcore client can be configured locally at the CLI, but only when accessed with the required password.\n\nThe 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.","checkContent":"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.\n\nConsult with the ISSO/ISSM to obtain a copy of the organization's documented policy for application whitelisting.\n\nReview the written policy for how the Solidcore client interface is used by the organization.\n\nVerify the policy identifies the frequency with which the CLI password is changed.\n\nIf the written policy does not contain specific information on frequency with which the CLI password is changed, this is a finding.","fixText":"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.","ccis":["CCI-000199"]},{"vulnId":"V-74199","ruleId":"SV-88873r1_rule","severity":"medium","ruleTitle":"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.","description":"The Solidcore client can be configured locally at the CLI, but only when accessed with the required password.\n\nSince 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. \n\nStrict management of the accessibility of the CLI is necessary in order to prevent its misuse.\n\nThe misuse of the CLI would open the system up to the possible configuration changes potentially allowing malicious applications to execute unknowingly.","checkContent":"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.\n\nConsult with the ISSO/ISSM to obtain a copy of the organization's documented policy for application whitelisting.\n\nThe policy must contain procedures for accessing the CLI password, to include the SA gaining access to an approved safe in order for obtaining the password.\n\nIf a procedure does not exist for accessing the CLI password as described above, this is a finding.","fixText":"Follow the formal change and acceptance process to update the written policy to include procedures for accessing the CLI password and how the SA gains access to an approved safe in order for obtaining the password.","ccis":["CCI-002041"]},{"vulnId":"V-74201","ruleId":"SV-88875r1_rule","severity":"medium","ruleTitle":"The McAfee Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be confined to the organizations enclave.","description":"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.","checkContent":"If an ATD server is not being used in the environment, this is Not Applicable.\n\nConsult with the ISSO/ISSM to review the written policy to ensure the usage of an ATD is documented.\n\nIf the usage of an ATD is not documented in the written policy, this is a finding.\n\nDetermine the location of the ATD being used by the organization and verify the ATD is confined to the organization's enclave.\n\nIf the location of the ATD being used by the organization cannot be determined and the ATD is not confined to the organization's enclave, this is a finding.","fixText":"Relocate or reinstall the ATD being used by the organization to be confined to the organization's enclave.","ccis":["CCI-001240"]},{"vulnId":"V-74203","ruleId":"SV-88877r1_rule","severity":"medium","ruleTitle":"The configuration of features under McAfee Application Control Options policies Enforce feature control must be documented in the organizations written policy.","description":"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 to be bypassed and in doing so renders the McAfee Application Control less effective.","checkContent":"Consult with the ISSO/ISSM to obtain a copy of the organization's documented policy for application whitelisting.\n\nReview the written policy for how the Solidcore client interface is used by the organization.\n\nVerify the written policy identifies whether additional features are enabled or not under \"Enforce feature control\" of the McAfee Application Control Options ePO policy.\n\nIf the written policy does not identify whether additional features are enabled or not under \"Enforce feature control\" of the McAfee Application Control Options ePO policy, this is a finding.","fixText":"Follow the formal change and acceptance process to document any features needing to be enabled.","ccis":["CCI-001774"]},{"vulnId":"V-74205","ruleId":"SV-88879r1_rule","severity":"medium","ruleTitle":"The organizations written policy must include a process for how whitelisted applications are deemed to be allowed.","description":"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.","checkContent":"Consult with the ISSO/ISSM to review the organizational-specific written policy for the McAfee Application Control software.\n\nVerify the written policy includes a process for how applications are vetted and deemed to be allowed.\n\nIf no written policy exists, this is a finding.\n\nIf written policy does not include a process for vetting applications before allowing them, this is a finding.","fixText":"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.","ccis":["CCI-001774"]},{"vulnId":"V-74207","ruleId":"SV-88881r1_rule","severity":"medium","ruleTitle":"The organizations written policy must include procedures for how often the whitelist of allowed applications is reviewed.","description":"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.","checkContent":"Consult with the ISSO/ISSM to review the organizational-specific written policy for the McAfee Application Control software.\n\nVerify the written policy includes a process for how often the application whitelist is reviewed.\n\nIf no written policy exists, this is a finding.\n\nIf written policy does not include a process for how often the application whitelist is reviewed, this is a finding.","fixText":"Follow the formal change and acceptance process to update the written policy to include a process for how often the application whitelist is reviewed.","ccis":["CCI-001774"]},{"vulnId":"V-74209","ruleId":"SV-88883r1_rule","severity":"medium","ruleTitle":"The Solidcore client must be enabled.","description":"The Application Control whitelisting must be enabled on all workstation endpoints. To enable Application Control, the Solidcore client needs to be in enabled mode.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated and view its properties.\n\nClick on the \"Products\" tab.\n\nUnder \"Product\", verify the Solidcore 7 client is listed as a product. If exists, click on the row to review additional information. Verify status shows \"Enabled\".\n\nIf the Solidcore 7 client is listed as an installed product but the status is not \"Enabled\", this is a finding.","fixText":"Although there is more than one way to deploy and enable the Solidcore client, the following is the method described in the McAfee Application Control Installation Guide.\n\nFrom the ePO server console System Tree, select \"My Organization\" in the System Tree.\n\nTo deploy the Solidcore 7 client:\n\nSelect \"This Group and All Subgroups\".\nSelect the asset and view its properties.\nClick on the \"Actions\" button at the bottom of the screen.\nSelect \"Agent\".\nSelect \"Modify Tasks on a Single System\".\nClick \"Actions\".\nSelect \"New Client Task Assignment\" to open the \"Client Task Assignment Builder\" page.\nSpecify the task name and add descriptive information.\nSelect the target platform, subplatform, and version.\nSelect the \"Solidcore 7.0.0\" product from the \"Products and components\" list.\nSelect the \"Install\" action.\nSelect the language of the package.\nSpecify the branch where to add the package.\nClick \"Save\", then click \"Next to open the \"Schedule\" page.\nSpecify scheduling details, then click \"Next\".\nReview details, then click \"Save\".\n\nTo enable the Solidcore 7 client and scan for inventory:\n\nSelect \"This Group and All Subgroups\".\nSelect the asset and view its properties.\nClick on the \"Actions\" button at the bottom of the screen.\nSelect \"Agent\".\nSelect \"Modify Tasks on a Single System\".\nClick \"Actions\".\nSelect \"New Client Task Assignment\" to open the \"Client Task Assignment Builder\" page.\nSelect the \"Solidcore 7.0.0\" product and \"SC: Enable\" task type, then click \"Create New Task\".\n\nOn the \"Client Task Catalog\" page, specify the task name and add descriptive information.\nSelect the platform, subplatform, and version.\nSelect \"Application Control\".\nSpecify the scan priority.\nSpecify \"Full Feature Activation\".\nSelect \"Start Observe Mode\".\nSelect \"Pull Inventory\".\nClick \"Save\", then click \"Next\" to open the Schedule page.\nSpecify scheduling details, then click \"Next\".\nReview details, then click \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74211","ruleId":"SV-88885r1_rule","severity":"high","ruleTitle":"The Solidcore client Command Line Interface (CLI) must be in lockdown mode.","description":"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, however, be activated for troubleshooting efforts during which time the ePO settings will not be enforced. Leaving the CLI in an allowed status will prevent the endpoint from receiving changes from the ePO server for the Solidcore client.","checkContent":"Determine CLI status.\n\nAccess the system being reviewed. From an operating system command line, execute the following command:\n\nsadmin status <enter>\n\nIf the status for CLI is \"Allowed\", this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nClick \"Actions\".\nSelect \"New Client Task Assignment\" to open the Client Task Assignment Builder page.\n\nSelect the \"Solidcore 7.0.0 product\", \"SC: Change Local CLI Access\" task type, then click \"Create New Task\" to open the Client Task Catalog page.\n\nChange \"CLI status\" to \"Restrict\".\n\nClick \"Save\".","ccis":["CCI-001762"]},{"vulnId":"V-74213","ruleId":"SV-88887r1_rule","severity":"high","ruleTitle":"The Solidcore client Command Line Interface (CLI) Access Password must be changed from the default.","description":"The Solidcore client can be configured locally at the CLI, but only when accessed with the required password.\n\nSince 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. \n\nStrict management of the accessibility of the CLI is necessary in order to prevent its misuse.\n\nThe misuse of the CLI would open the system up to the possible configuration changes potentially allowing malicious applications to execute unknowingly.","checkContent":"This is a manual procedure to verify the CLI Access Password has been changed from its default setting by the ePO administrator. \n\nAsk the ePO admin, \"Has the CLI Access Password been changed from its default setting?\"\n\nIf the default password is being used, this is a finding. \n\nNote: The password does not need to be divulged during the review. An interview question of the SA to validate that it is not the default is sufficient.","fixText":"Change the CLI password with one other than the default, using administrative password complexity.\n\nFrom the ePO server console System Tree, select \"My Organization\".\n\nIn the \"Configuration (Client)\" category, click on the Organization's specific Configuration (Client) McAfee Default policy.\n\nIn the \"CLI\" tab, type a password other than the default, ensuring to conform to password complexity.\n\nConfirm the password.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74215","ruleId":"SV-88889r1_rule","severity":"medium","ruleTitle":"The organization-specific Rules policy must only include executable and dll files that are associated with applications as allowed by the organizations written policy.","description":"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.\n\nThe McAfee Application Control installs with two Default Rules policies.\n\nThe McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.\n\nThe McAfee Applications Default Rules policy include the whitelist for McAfee applications.\n\nBoth of these policies are at the \"My Organization\" level of the System Tree and must be inherited by all branches of the System Tree.\n\nOrganization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.","checkContent":"Obtain the organization's written policy for the McAfee Application Control software from the System or ePO Administrator.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select \"Solidcore 7.x: Application Control\".\n\nFor the \"Application Control Rules (Windows)\" Category, click on \"Edit Assignments\" under the \"Actions\" column.\n\nIdentify the organization-specific Rules policy applied to the system being reviewed.\n\nClick on \"Edit Policy\" beside the organization-specific Rules policy.\n\nVerify the list of applications under each of the \"Rules Groups\" in the organization-specific Rules policy against the written policy's list of allowed applications.\n\nIf the organization-specific Rules policy contains any applications not documented in the written policy as allowed, this is a finding.","fixText":"Obtain the organization's written policy for the McAfee Application Control software from the System or ePO Administrator.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nRemove any \"Rules Groups\" and/or applications under the \"Rules Groups\" that do not comply with the organization's written policy.\n\nIf applications are required, follow the formal change and acceptance process to document the applications in the organization's written policy.","ccis":["CCI-001774"]},{"vulnId":"V-74217","ruleId":"SV-88891r2_rule","severity":"medium","ruleTitle":"The McAfee Application Control Options Reputation setting must be configured to use the McAfee Global Threat Intelligence (McAfee GTI) option.","description":"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 on the McAfee ePO console.\n\nIf the GTI is being used, reputation for files and certificates is fetched from the McAfee GTI.\n\nFor both methods, the administrator can review the reputation values and make informed decisions for inventory items in the enterprise.","checkContent":"NOTE: This requirement is Not Applicable on a classified SIPRNet or otherwise closed network.\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset to be validated.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nVerify the \"Use McAfee Global Threat Intelligence (McAfee GTI)\" option is selected.\n\nNote: The \"McAfee GTI\" option must be selected, as a failover, even if an internal McAfee TIE server is configured.\n\nIf the \"McAfee GTI\" option is not selected, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nPlace a check in the \"Use McAfee Global Threat Intelligence (McAfee GTI)\" option.\n\nClick \"Save\".","ccis":["CCI-001240"]},{"vulnId":"V-74219","ruleId":"SV-88893r1_rule","severity":"medium","ruleTitle":"The use of a Solidcore 7.x local Command Line Interface (CLI) Access Password must be documented in the organizations written policy.","description":"The Solidcore client can be configured locally at the CLI, but only when accessed with the required password.\n\nSince 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. \n\nStrict management of the accessibility of the CLI is necessary in order to prevent its misuse.\n\nThe misuse of the CLI would open the system up to the possible configuration changes potentially allowing malicious applications to execute unknowingly.","checkContent":"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.\n\nConsult with the ISSO/ISSM to obtain a copy of the organization's documented policy for application whitelisting.\n\nReview the written policy for how and when the Solidcore CLI is used by the organization.\n\nIf the use of the CLI is not documented in the organization's written policy, this is a finding.","fixText":"Follow the formal change and acceptance process to update the organization's written policy with the use of the CLI.","ccis":["CCI-000200"]},{"vulnId":"V-74221","ruleId":"SV-88895r1_rule","severity":"medium","ruleTitle":"The Solidcore client Command Line Interface (CLI) Access password complexity requirements must be documented in the organizations written policy.","description":"The Solidcore client can be configured locally at the CLI, but only when accessed with the required password.\n\nThe 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.","checkContent":"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.\n\nSince the Solidcore CLI does not allow for technical enforcement of password complexity the enforcement will be via this written policy directive.\n\nConsult with the ISSO/ISSM to obtain a copy of the organization's documented policy for application whitelisting.\n\nReview the written policy for CLI password complexity requirements.\n\nVerify the policy requires the password to be 15 characters in length and contain a mix of at least one lower-case, one upper-case, one number, and one special character.\n\nIf the written policy does not document the requirement for password complexity and/or does not specify the password must be 15 characters in length and contain a mix of at least one lower-case, one upper-case, one number, and one special character, this is a finding.","fixText":"Follow the formal change and acceptance process to update the written policy with the CLI password complexity requirements.","ccis":["CCI-001619"]},{"vulnId":"V-74223","ruleId":"SV-88897r1_rule","severity":"medium","ruleTitle":"The McAfee Application Control Options Reputation-Based Execution settings, if enabled, must be configured to allow Most Likely Trusted or Known Trusted only.","description":"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 allowed. By configuring the setting to only \"Most Likely Trusted\" or \"Known Trusted\", the files with a reputation of \"Might be Trusted\" are blocked. While this may impact operationally in the beginning, after the inventories are vetted by the administrators, files with a \"Might be Trusted\" value may be recategorized in that organization.","checkContent":"If Reputation-Based Execution settings is not enabled, this check is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nVerify the \"Reputation-Based Execution Settings\" is configured to allow binaries with \"Most Likely Trusted\" and above.\n\nIf the allow binaries \"Most Likely Trusted\" and above is not selected for \"Reputation-Based Execution Settings\", this is a finding.","fixText":"If Reputation-Based Execution settings is not enabled, this check is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nPlace a check in the \"Reputation-Based Execution Settings: Allow binaries with\" check box and select \"Most Likely Trusted\" from the drop-down selection box.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74225","ruleId":"SV-88899r1_rule","severity":"medium","ruleTitle":"The McAfee Application Control Options Advanced Threat Defense (ATD) settings must not be enabled unless an internal ATD is maintained by the organization.","description":"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.","checkContent":"If an ATD server is not being used in the environment, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nVerify the option for sending binaries for analysis under the \"Advanced Threat Defense (ATD) settings\" is selected.\n\nConsult with the ISSO/ISSM to review the written policy to verify the usage of an ATD is documented.\n\nIf the option for sending binaries for analysis under the \"Advanced Threat Defense (ATD) settings\" is selected and the written policy does not include documentation on the usage of an ATD, this is a finding.","fixText":"If an ATD server is not being used in the environment, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nPlace a check in the \"Advanced Threat Defense (ATD) settings: Send binaries\" check box.\n\nClick \"Save\".\n\nUpdate the written policy to ensure the usage of an ATD is documented.","ccis":["CCI-001240"]},{"vulnId":"V-74227","ruleId":"SV-88901r1_rule","severity":"medium","ruleTitle":"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.","description":"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.\n\nThe files with \"Might be Trusted\" reputation may be redesignated as \"Trusted\" after analysis.","checkContent":"If an ATD server is not being used in the environment, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control. From the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nIf the option for sending binaries for analysis under the \"Advanced Threat Defense (ATD) settings\" is selected, verify the level of binaries to be sent for analysis is \"Might be Trusted\" and below.\n\nIf the level of binaries to be sent for analysis is not \"Might be Trusted\", this is a finding.","fixText":"If an ATD server is not being used in the environment, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nIn the drop-down selection box of the \"Advanced Threat Defense (ATD) settings: Send binaries\" option, select \"Might be Trusted\".\n\nClick \"Save\".","ccis":["CCI-001240"]},{"vulnId":"V-74229","ruleId":"SV-88903r1_rule","severity":"medium","ruleTitle":"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.","description":"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.","checkContent":"If an ATD server is not being used in the environment, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nIf the option for sending binaries for analysis under the \"Advanced Threat Defense (ATD) settings\" is selected, verify the \"Limit file size to\" option is set to 5 MB or less.\n\nIf the \"Limit file size to\" option is not set to 5 MB or less, this is a finding.","fixText":"If an ATD server is not being used in the environment, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nSelect the \"Reputation\" tab.\n\nIn the drop-down selection box of the \"Advanced Threat Defense (ATD) settings: Limit file save\" text box, enter a value of 5 MB or less.\n\nClick \"Save\".","ccis":["CCI-001240"]},{"vulnId":"V-74231","ruleId":"SV-88905r1_rule","severity":"medium","ruleTitle":"Organization-specific McAfee Applications Control Options policies must be created and applied to all endpoints.","description":"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) policy.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\" that is specific for the asset being reviewed.\n\nIf the only \"Application Control Options\" policy applied to the system is the \"McAfee Default\" policy, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Actions\" column, select \"Edit Assignment\" for the \"Application Control Options (Windows) Category\".\n\nNext to \"Assigned policy:\", click on drop-down selection box and choose an organization-specific Application Control Options policy for the asset being reviewed.\n\nClick \"Save\".\n\nIf no organization-specific Application Control Options policy exist, click on \"New Policy\".\n\nChoose \"McAfee Default\" for \"Create a policy based on this existing policy\".\n\nType a unique Policy Name.\n\nClick \"OK\".\n\nConfigure the \"Self-Approval\", \"End User Notifications\", \"Features\", \"Inventory\", and \"Reputation\" tabs according to the organization's written policy and remaining STIG settings.","ccis":["CCI-001774"]},{"vulnId":"V-74233","ruleId":"SV-88907r1_rule","severity":"medium","ruleTitle":"The McAfee Application Control Options policy must be configured to disable Self-Approval.","description":"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.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"Self-Approval\" tab, verify the \"Enable Self-Approval\" check box is not selected.\n\nIf the \"Enable Self-Approval\" check box is selected, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"Self-Approval\" tab, de-select the \"Enable Self-Approval\" check box.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74235","ruleId":"SV-88909r1_rule","severity":"medium","ruleTitle":"The McAfee Application Control Options policy End User Notification, if configured by organization, must have all default variables replaced with the organization-specific data.","description":"The \"User Message\" option will show a dialog box when an event is detected and display the organization-specified text in the message.","checkContent":"If \"End User Notification\" is not used by the organization, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"End User Notification\" tab, determine if the \"User Message:\" option \"Show the messages dialog box when an event is detected and display the specified text in the message.\" is selected.\n\nIf \"Show the messages dialog box when an event is detected and display the specified text in the message.\" is not selected, this is Not Applicable.\n\nIf \"Show the messages dialog box when an event is detected and display the specified text in the message.\" is selected, consult with the ISSO/ISSM to review the organizational-specific written policy for the McAfee Application Control software.\n\nVerify the usage of \"End User Notification\" is documented in the written policy and verify criteria for configuration.\n\nIf \"End User Notification:\" variables are not configured to written documentation, this is a finding.\n\nIf \"End User Notification\" is not documented in written policy, this is a finding.","fixText":"If \"End User Notification\" is not used by the organization, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"End User Notification\" tab, select or de-select the \"Show the messages dialog box when an event is detected and display the specified text in the message.\" based upon organization's written policy.\n\nIf \"Show the messages dialog box when an event is detected and display the specified text in the message.\" is de-selected based upon written policy, populate \"Helpdesk Information\" with information from the written policy.\n\nClick \"Save\".\n\nIf \"Show the messages dialog box when an event is detected and display the specified text in the message.\" is selected based upon written policy, populate \"Helpdesk Information\" with information from the written policy.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74237","ruleId":"SV-88911r1_rule","severity":"medium","ruleTitle":"The McAfee Application Control Options policies Enforce feature control memory protection must be enabled.","description":"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 to be bypassed and in doing so renders the McAfee Application Control less effective.","checkContent":"If HIPS/ENS is enabled and enforced, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"Features\" tab, review options selected.\n\nIf the \"Enforce feature control\" check box is not selected and \"Memory protection\" is selected, this is a finding.","fixText":"If HIPS/ENS is enabled and enforced, this is Not Applicable.\n\nFrom the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"Features\" tab, place a check in the \"Enforce feature control\" check box.\n\nPlace a check in the \"Memory protection\" check box.\n\nSelect or de-select remaining features, based upon written policy.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74239","ruleId":"SV-88913r1_rule","severity":"medium","ruleTitle":"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.","description":"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 to be bypassed and in doing so renders the McAfee Application Control less effective.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control. From the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"Features\" tab, review options selected.\n\nIf the \"Enforce feature control\" check box is selected with any features, consult with the ISSO/ISSM to review the written policy and ensure the usage of additional features are documented.\n\nIf the usage of additional features are not documented in the written policy, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control. From the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"Features\" tab, remove any features selected.\n\nIf features are required technically that are not documented in the organization's written policy, document the use of those features following the formal change and acceptance process as documented in the organization's written policy.","ccis":["CCI-001774"]},{"vulnId":"V-74241","ruleId":"SV-88915r1_rule","severity":"medium","ruleTitle":"The McAfee Application Control Options Inventory option must be configured to hide OS Files.","description":"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 <system drive>\\Windows folder which are signed by the Microsoft certificate and all files in the <system drive>\\Windows\\winsxs folder will not be included in the inventory.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"Inventory\" tab, review options selected.\n\nIf the \"Hide Windows OS Files: Inventory items signed with Microsoft certificates will not be sent to McAfee ePO.\" option is not selected, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control. \n\nFrom the \"Policy\" column, select the policy associated with the Category \"Application Control Options (Windows)\".\n\nOn the \"Inventory\" tab, place a check in the \"Inventory: Hide Windows OS Files: Inventory items signed with Microsoft certificates will not be sent to McAfee ePO.\" check box.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74243","ruleId":"SV-88917r2_rule","severity":"medium","ruleTitle":"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.","description":"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 execute. An executable binary, script, or process that is not in the whitelist is said to be unauthorized and is prevented from running.  McAfee Application Control uses a centralized repository of trusted applications and dynamic whitelisting to reduce manual maintenance effort.\nRunning frequent Pull Inventory tasks ensures inventory information does not become stale. There must be the minimum interval between consecutive inventory pull runs (when the inventory information is fetched from the endpoints). By default, this value is 7 days and is the recommended setting. Pulling at an interval of greater than 7 days will allow for the inventory of endpoints to become stale.","checkContent":"Consult with the ISSO to determine the endpoints used for the sampling of inventory pulls.\n\nFrom the McAfee ePO console, select Menu >> Systems >> System Tree.\n\nIf sampling is a group, select the group in the System Tree and switch to the “Assigned Client Tasks” tab.\n\nOtherwise, select each endpoint on the “Systems” page and then click Actions >> Agent >> Modify Tasks on a Single System.\n\nConfirm a client task exists with an “SC: Pull Inventory” task type. Review the task properties to validate the task is configured to run at least as frequently as every 7 days.\n\nIf a sampling of endpoints does not have a “Pull Inventory” task type applied and/or the “Pull Inventory” task is not configured to run at least as frequently as every 7 days, this is a finding.","fixText":"From the McAfee ePO console, select Menu >> Systems >> System Tree.\n\nTo apply a client task to a group, select a group in the System Tree and switch to the “Assigned Client Tasks” tab.\n\nTo apply a client task to an endpoint, select the endpoint on the “Systems” page and then click Actions >> Agent >> Modify Tasks on a Single System.\n\nClick Actions >> New Client Task Assignment to open the “Client Task Assignment Builder” page.\n\nSelect “Solidcore 7.x” for the product and “SC: Pull Inventory” for the task type and then click “Create New Task” to open the “Client Task Catalog” page.\nSpecify the task name and add any descriptive information.\n\nClick “Save”.\nClick “Next” to open the “Schedule” page. Schedule the task to run at least as frequently as every 7 days and then click “Next”.\n\nReview and verify the task details and then click “Save”.","ccis":["CCI-001774"]},{"vulnId":"V-74247","ruleId":"SV-88921r1_rule","severity":"medium","ruleTitle":"The McAfee Applications Default Rules policy must be part of the effective rules policy applied to every endpoint.","description":"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.\n\nThe McAfee Application Control installs with two Default Rules policies.\n\nThe McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.\n\nThe McAfee Applications Default Rules policy include the whitelist for McAfee applications.\n\nBoth of these policies are at the \"My Organization\" level of the System Tree and must be inherited by all branches of the System Tree.\n\nOrganization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFor the \"Application Control Rules (Windows)\" Category, click on \"Edit Assignments\" under the \"Actions\" column.\n\nVerify that the McAfee Applications Default Rules policy is part of the assigned policies applied to the system being reviewed.\n\nIf the McAfee Applications Default Rules policy is not part of the assigned polices applied to the system being reviewed, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFor the \"Application Control Rules (Windows)\" Category, click on \"Edit Assignments\" under the \"Actions\" column.\n\nClick on the \"New Policy Instance\" button at the bottom of the screen.\n\nScroll down to locate the new policy instance just created.\n\nClick on the drop-down selection box for \"Assigned policy:\" and choose \"McAfee Applications (McAfee Default)\".\n\nSelect the \"Locked (prevent breaking inheritance below this point)\" radio button.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74249","ruleId":"SV-88923r1_rule","severity":"medium","ruleTitle":"A copy of the McAfee Default Rules policy must be part of the effective rules policy applied to every endpoint.","description":"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.\n\nThe McAfee Application Control installs with two Default Rules policies.\n\nThe McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.\n\nThe McAfee Applications Default Rules policy include the whitelist for McAfee applications.\n\nBoth of these policies are at the My Organization level of the System Tree and must be inherited by all branches of the System Tree.\n\nOrganization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\". \n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control. \n\nFor the \"Application Control Rules (Windows)\" Category, click on \"Edit Assignments\" under the \"Actions\" column.\n\nVerify that a Rules policy copied from the McAfee Default Rules policy is part of the assigned policies applied to the system being reviewed. \n\nIf a Rules policy copied from the McAfee Default Rules policy is not part of the assigned policies applied to the system being reviewed, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\". \nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\". \n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFor the \"Application Control Rules (Windows)\" Category, click on \"Edit Assignments\" under the \"Actions\" column.\n\nClick on the \"New Policy Instance\" button at the bottom of the screen.\n\nScroll down to locate the new policy instance just created. Click on the drop-down selection box for \"Assigned policy:\" and choose \"McAfee Default)\".\n\nSelect the \"Locked (prevent breaking inheritance below this point)\" radio button.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74251","ruleId":"SV-88925r1_rule","severity":"medium","ruleTitle":"The organization-specific Rules policies must be part of the effective rules policy applied to all endpoints.","description":"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.\n\nThe McAfee Application Control installs with two Default Rules policies. \n\nThe McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.\n\nThe McAfee Applications Default Rules policy include the whitelist for McAfee applications.\n\nBoth of these policies are at the \"My Organization\" level of the System Tree and must be inherited by all branches of the System Tree.\n\nOrganization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFor the \"Application Control Rules (Windows)\" Category, click on \"Edit Assignments\" under the \"Actions\" column.\n\nVerify that there exists at least one organization-specific Rules policy as part of the assigned policies applied to the system being reviewed.\n\nIf an organization-specific Rules policy is not part of the assigned polices applied to the system being reviewed, this is a finding.\n\nIf the only \"Application Control Rules\" policy applied to the system is the \"McAfee Default\" policy, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\". \nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: Application Control.\n\nFor the \"Application Control Rules (Windows)\" Category, click on \"Edit Assignments\" under the \"Actions\" column.\n\nClick on the \"New Policy Instance\" button at the bottom of the screen.\n\nScroll down to locate the new policy instance just created. Click on the drop-down selection box for \"Assigned policy:\" and choose the organization-specific policy for the system being reviewed.\n\nIf one does not exist, click \"New Policy\" and create a new policy based upon organization's written policy.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74253","ruleId":"SV-88927r1_rule","severity":"medium","ruleTitle":"The organization-specific Solidcore Client Policies must be created and applied to all endpoints.","description":"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 created.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: General.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Configuration (Client)\" that is specific to the organization.\n\nIf the only \"Configuration (Client)\" policy applied to the system is the \"McAfee Default\" policy, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: General.\n\nFrom the \"Actions\" column, select \"Edit Assignment\" for the \"Solidcore (Client)\" Category.\n\nNext to \"Assigned policy:\", click on the drop-down selection box and choose an organization-specific \"Solidcore (Client)\" policy.\n\nClick \"Save\".\n\nIf no organization-specific Solidcore (Client) policy exists, click on \"New Policy\". Choose \"McAfee Default\" for \"Create a policy based on this existing policy\".\n\nType a unique Policy Name.\n\nClick \"OK\".","ccis":["CCI-001774"]},{"vulnId":"V-74255","ruleId":"SV-88929r1_rule","severity":"medium","ruleTitle":"The Throttling settings must be enabled and configured to settings according to organizations requirements.","description":"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 threshold value is reached. After the cache is full, new data for that category is dropped and not sent to the McAfee ePO. As such, settings must be high enough to allow for all data to reach the McAfee ePO.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: General.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Configuration (Client)\" that is specific to the organization and select the \"Throttling\" tab.\n\nVerify the \"Enable Throttling\" check box is selected.\n\nVerify the throttling settings are configured according to organization's written policy.\n\nIf the \"Enable Throttling\" check box is not selected, this is a finding.\n\nIf the throttling settings do not match the organization's written policy or the settings are not documented in the written policy, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: General.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Configuration (Client)\" that is specific to the organization and select the \"Throttling\" tab.\n\nPlace a check in the \"Enable Throttling\" check box.\n\nConfigure the throttling settings based upon organization's written policy.\n\nClick \"Save\".","ccis":["CCI-001774"]},{"vulnId":"V-74257","ruleId":"SV-88931r1_rule","severity":"medium","ruleTitle":"The Solidcore Client Exception Rules must be documented in the organizations written policy.","description":"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 and is required to be under CAB/CCB oversight.","checkContent":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\n\nSelect the asset to be validated.\n\nSelect \"Actions\".\n\nSelect \"Agent\".\n\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: General.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Exception Rules (Windows)\" that is specific to the organization.\n\nIf the \"Exception Rules (Windows)\" policy applied to the system has exceptions documented, verify the exceptions are documented in the organization's written policy.\n\nIf the Exceptions are not documented, this is a finding.","fixText":"From the ePO server console System Tree, select the \"Systems\" tab.\n\nSelect \"This Group and All Subgroups\".\nSelect the asset.\nSelect \"Actions\".\nSelect \"Agent\".\nSelect \"Modify Policies on a Single System\".\n\nFrom the product pull-down list, select Solidcore 7.x: General.\n\nFrom the \"Policy\" column, select the policy associated with the Category \"Exception Rules (Windows)\" that is specific to the organization.\n\nRemove any exceptions which are not documented in the organization's written policy.\n\nIf any exceptions are required, follow the formal change and acceptance process to document the required exceptions in the organization's written policy.","ccis":["CCI-001774"]},{"vulnId":"V-74258","ruleId":"SV-88932r1_rule","severity":"high","ruleTitle":"The version of McAfee Application Control running on the system must be a supported version.","description":"Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously.\n\nOrganization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw).\n\nThis requirement will apply to software patch management solutions that are used to install patches across the enclave and to applications that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality, will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process.\n\nThe application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).","checkContent":"McAfee Application Control 7.0 Managed Desktop is no longer supported by the vendor. If the system is running McAfee Application Control 7.0 Managed Desktop, this is a finding.","fixText":"Upgrade to a supported version.","ccis":["CCI-002605"]}]}