Search filters the loaded procedure list locally. Separate terms must all match (use quotes for an exact phrase). Cached STIG Search results apply when you arrive from Search.
Objective ID
Severity
Discussion
V-74175
medium
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.
V-74195
medium
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.
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.
V-74197
medium
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.
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.
V-74199
medium
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.
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.
V-74201
medium
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.
V-74203
medium
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.
V-74205
medium
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.
V-74207
medium
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.
V-74209
medium
The Application Control whitelisting must be enabled on all workstation endpoints. To enable Application Control, the Solidcore client needs to be in enabled mode.
V-74211
high
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.
V-74213
high
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.
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.
V-74215
medium
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 policies.
The McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.
The McAfee Applications Default Rules policy include the whitelist for McAfee applications.
Both of these policies are at the "My Organization" level of the System Tree and must be inherited by all branches of the System Tree.
Organization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.
The McAfee Application Control installs with two Default Rules policies.
The McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.
The McAfee Applications Default Rules policy include the whitelist for McAfee applications.
Both of these policies are at the "My Organization" level of the System Tree and must be inherited by all branches of the System Tree.
Organization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.
V-74217
medium
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.
If the GTI is being used, reputation for files and certificates is fetched from the McAfee GTI.
For both methods, the administrator can review the reputation values and make informed decisions for inventory items in the enterprise.
If the GTI is being used, reputation for files and certificates is fetched from the McAfee GTI.
For both methods, the administrator can review the reputation values and make informed decisions for inventory items in the enterprise.
V-74219
medium
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.
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.
V-74221
medium
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.
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.
V-74223
medium
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.
V-74225
medium
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.
V-74227
medium
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 files with "Might be Trusted" reputation may be redesignated as "Trusted" after analysis.
The files with "Might be Trusted" reputation may be redesignated as "Trusted" after analysis.
V-74229
medium
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.
V-74231
medium
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.
V-74233
medium
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.
V-74235
medium
The "User Message" option will show a dialog box when an event is detected and display the organization-specified text in the message.
V-74237
medium
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.
V-74239
medium
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.
V-74241
medium
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.
V-74243
medium
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.
Running 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.
Running 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.
V-74247
medium
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 policies.
The McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.
The McAfee Applications Default Rules policy include the whitelist for McAfee applications.
Both of these policies are at the "My Organization" level of the System Tree and must be inherited by all branches of the System Tree.
Organization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.
The McAfee Application Control installs with two Default Rules policies.
The McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.
The McAfee Applications Default Rules policy include the whitelist for McAfee applications.
Both of these policies are at the "My Organization" level of the System Tree and must be inherited by all branches of the System Tree.
Organization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.
V-74249
medium
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 policies.
The McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.
The McAfee Applications Default Rules policy include the whitelist for McAfee applications.
Both of these policies are at the My Organization level of the System Tree and must be inherited by all branches of the System Tree.
Organization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.
The McAfee Application Control installs with two Default Rules policies.
The McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.
The McAfee Applications Default Rules policy include the whitelist for McAfee applications.
Both of these policies are at the My Organization level of the System Tree and must be inherited by all branches of the System Tree.
Organization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.
V-74251
medium
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 policies.
The McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.
The McAfee Applications Default Rules policy include the whitelist for McAfee applications.
Both of these policies are at the "My Organization" level of the System Tree and must be inherited by all branches of the System Tree.
Organization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.
The McAfee Application Control installs with two Default Rules policies.
The McAfee Default Rules policy includes the whitelist for commonly used applications to the platform.
The McAfee Applications Default Rules policy include the whitelist for McAfee applications.
Both of these policies are at the "My Organization" level of the System Tree and must be inherited by all branches of the System Tree.
Organization-specific applications would be whitelisted with an organization-specific policy combined with the two Default policies into one effective policy.
V-74253
medium
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.
V-74255
medium
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.
V-74257
medium
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.
V-74258
high
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.
Organization-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).
This 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.
The 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).
Organization-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).
This 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.
The 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).