McAfee Host Intrusion Prevention

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	McAfee Host Intrusion Prevention safeguards the operating system and applications against complex security threats that may otherwise be unintentionally introduced or allowed by desktop and laptop use.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v20.11
Decision Date:	11/02/2020
Introduced By:	SCCM
Vendor Name:	McAfee

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
8.0 (Win)	12/21/2010
8.0 Patch 1 (Win)	11/14/2011
8.0 Patch 2 (Win)	09/05/2012
8.0 Patch 3 (Win)	06/13/2013
8.0 Patch 4 (Win)	02/19/2014
8.0 Patch 5 (Win)	06/10/2015
8.0 Patch 6 (Win)	08/27/2015
8.0 Patch 7 (Win)	02/25/2016
8.0 Patch 8 (Win)	07/15/2016
8.0 Patch 9 (Win)	04/10/2017
8.0 Patch 10 (Win)	11/13/2017
8.0 Patch 11 (Win)	04/25/2018
8.0 Patch 12 (Win)	06/11/2019
8.0 Patch 13 (Win)	10/31/2018
8.0 Patch 15 (Win)	06/09/2020
8.0 (RHEL)	02/08/2011
8.0 Patch 1 (RHEL)	09/13/2011
8.0 Patch 2&3 (RHEL)	07/03/2012
8.0 Patch 4 (RHEL)	12/18/2013
8.0 Patch 5 (RHEL)	03/30/2015
8.0 Patch 6 (RHEL)	07/15/2015
8.0 Patch 7 (RHEL)	10/30/2015
8.0 Patch 8 (RHEL)	04/28/2016
8.0 Patch 9 (RHEL)	09/12/2016
8.0 Patch 10 (RHEL)	02/28/2017
8.0 Patch 11 (RHEL)	10/30/2017

Current Decision Matrix (10/29/2020)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2021

CY2022

CY2023

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

8.0 (Win)

Unapproved

8.0 Patch 1 (Win)

Unapproved

8.0 Patch 2 (Win)

Unapproved

8.0 Patch 3 (Win)

Unapproved

8.0 Patch 4 (Win)

Unapproved

8.0 Patch 5 (Win)

Unapproved

8.0 Patch 6 (Win)

Unapproved

8.0 Patch 7 (Win)

Unapproved

8.0 Patch 8 (Win)

Unapproved

8.0 Patch 9 (Win)

Unapproved

8.0 Patch 10 (Win)

Approved w/Constraints
[6, 9, 12, 14]

8.0 Patch 11 (Win)

Unapproved

8.0 Patch 12 (Win)

Unapproved

8.0 Patch 13 (Win)

Approved w/Constraints
[1, 6, 9, 12, 14]

8.0 Patch 15 (Win)

Unapproved

8.0 Patch 5 (RHEL)

Unapproved

8.0 Patch 9 (RHEL)

Unapproved

8.0 Patch 10 (RHEL)

Approved w/Constraints
[6, 9, 12, 14]

8.0 Patch 11 (RHEL)

Unapproved

Decision Constraints


[1]	This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population.

[2]	Only instances of this technology that have been deployed as of 10/1/2011 may continue to use this technology. This technology will receive a full assessment and decision.

[3]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for this software are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering, which must be followed and adhered to unless an appropriate waiver is granted.

[4]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[5]	Configuration and deployment standards for this software are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.

[6]	Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans.

[7]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[8]	Configuration and deployment standards for this software are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[9]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[10]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[11]	Configuration and deployment standards for this software are defined and maintained by the Desktop and Device Engineering organization within VA Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[12]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[13]	Configuration and deployment standards for this software are defined and maintained by the Desktop and Device Engineering organization within VA Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[14]	Configuration and deployment standards for this software are defined and maintained by the Desktop and Device Engineering organization within VA Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

Note:

Version 8.0 Patch 13 is the latest version assessed by Endpoint Engineering Desktop and Device Engineering to be a VA baseline.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
There are no references identified for this entry.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Security Network Security	Network Intrusion Detection and Prevention

Operating Systems Supported by the Technology

Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Comparable Technologies:

Companion Technologies/Supported Standards:

Virtualization and Consolidation of Servers (Server Virtualize First)

General Analysis

Adoption Benefits

This is a mature technology.
The technology has a comprehensive set of documentation.
This technology may be utilized to improve the Department`s security posture and compliance with Federal and Department security policies and regulations.
This technology can reduce time and costs with one unified console for deployment, management, reporting, and auditing of events, policies, and agents.
This technology allows users to manage compliance with actionable views, workflow, event monitoring, and reporting for prompt and proper investigation and forensics.

Adoption Risks

The technology has one or more Common Vulnerabilities and Exposures (CVEs).
Other approved solutions that provide similar functionality are available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
The use of scanning technologies require VA staff performing analysis to work closely with system owners to schedule and coordinate scans.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.

Architectural Benefits

The solution is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology is compatible with multiple TRM-approved McAfee products.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 22.8

General Information

Vendor Release Information

Current Decision Matrix (10/29/2020)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 22.8

General Information

Vendor Release Information

Current Decision Matrix (10/29/2020)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES