Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

HCL BigFix

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:	HCL BigFix (formerly known as IBM Endpoint Manager (IEM) and IBM Bigfix) provides endpoint management services, including asset inventory/discovery, security vulnerability detection and remediation, security policy enforcement, software distribution, Information Technology (IT) compliance reporting, patch management, and software license management. The BigFix client is installed on endpoints and tracked by a centralized BigFix server and console application. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO NOTE: IBM sold Bigfix to HCL.
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 v24.7
Decision Date:	07/10/2024 at 19:17:22 UTC
Aliases:	IBM BigFix; IBM Endpoint Manager (IEM); Tivoli Endpoint Manager (TEM); BigFix
Introduced By:	TRM Request
Vendor Name:	HCL Technologies, Limited

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
7.x	09/21/2008
8.1.x	02/11/2011
8.2.x	12/09/2011
9.0.x	03/13/2013
9.1.x	04/21/2014
9.2.x	10/20/2014
9.5.8.38	03/31/2016
9.5.9.62	04/10/2018
9.5.10.79	10/04/2018
9.5.11.191	12/18/2018
9.5.12.68	03/11/2019
9.5.13.x	05/19/2019
9.5.x	04/28/2020
10.0.x	04/30/2020
11.0.x	09/13/2023

Current Decision Matrix (07/08/2024)

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

CY2019

CY2020

CY2021

Future>

Release

9.0.x

Unapproved

9.1.x

Unapproved

9.2.x

Unapproved

9.5.8.38

Divest
[4, 7, 8, 11, 12]

Unapproved

9.5.9.62

Divest
[4, 7, 8, 11, 12]

Divest
[4, 7, 8, 12, 13, 14]

Unapproved

9.5.10.79

Divest
[4, 7, 8, 11, 12]

Divest
[4, 7, 8, 12, 13, 14]

Unapproved

9.5.11.191

Approved w/Constraints
[4, 7, 8, 11, 12]

Divest
[4, 7, 8, 12, 13, 14]

Unapproved

9.5.12.68

Unapproved

Approved w/Constraints
[4, 7, 8, 12, 13, 14]

Approved w/Constraints
[4, 7, 8, 12, 13, 15]

Divest
[4, 7, 8, 12, 15, 16]

Divest
[4, 7, 16, 17, 18, 19]

Divest
[4, 7, 16, 18, 19, 20]

Unapproved

9.5.13.x

Unapproved

Divest
[4, 7, 8, 12, 15, 16]

Divest
[4, 7, 16, 17, 18, 19]

Divest
[4, 7, 16, 18, 19, 20]

Unapproved

9.5.x

Unapproved

Divest
[4, 7, 8, 12, 15, 16]

Divest
[4, 7, 16, 17, 18, 19]

Divest
[4, 7, 16, 18, 19, 20]

Divest
[4, 7, 16, 18, 19, 20, 21]

10.0.x

Unapproved

Approved w/Constraints
[4, 7, 8, 12, 15, 16]

Approved w/Constraints
[4, 7, 16, 17, 18, 19]

Approved w/Constraints
[4, 7, 16, 18, 19, 20]

Approved w/Constraints
[4, 7, 16, 18, 19, 20, 21]

11.0.x

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]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for this product 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.

[3]	Service Delivery and Engineering (SDE) requires that every device connected to a VA information system that is capable of running the IEM agent will have it installed (VAIQ# 7297444).

[4]	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.

[5]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[6]	Service Delivery and Engineering (SDE) requires that every device connected to a VA information system that is capable of running the IBM Endpoint Management (IEM) agent will have it installed (VAIQ# 7297444). IBM Bigfix is only to be installed and operated by Office of Information Security (OIS) in a single VA enterprise instance. Additionally, OIS must keep the supporting platform (relays and core servers) patched and/or mitigated against any known security vulnerabilities. Moreover, older and potentially vulnerable client agents are only allowed for VA endpoints with End of Support (EOS)/End of Life (EOL) Operating Systems (OS) that have been allowed to remain on the VA network. A system Plan of Action and Milestones (POAM) must be entered and approved in the VA Governance, Risk and Compliance (GRC) system for the EOS/EOL OS endpoint. Version 9.2 can only be used in configurations that are not related to critical vulnerability in the Virtual Relay Appliance (CVE-2016-608). If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[7]	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.

[8]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[9]	Service Delivery and Engineering (SDE) requires that every device connected to a VA information system that is capable of running the International Business Machine (IBM) Endpoint Management (IEM) agent will have it installed (VAIQ# 7297444). IBM Bigfix is only to be installed and operated by Office of Information Security (OIS) in a single Veterans Affairs (VA) enterprise instance. Additionally, OIS must keep the supporting platform (relays and core servers) patched and/or mitigated against any known security vulnerabilities. Moreover, older and potentially vulnerable client agents are only allowed for VA endpoints with End of Support (EOS)/End of Life (EOL) Operating Systems (OS) that have been allowed to remain on the VA network. A system Plan of Action and Milestones (POAM) must be entered and approved in the VA Governance, Risk and Compliance (GRC) system for the EOS/EOL OS endpoint. Version 9.2 can only be used in configurations that are not related to critical vulnerability in the Virtual Relay Appliance (CVE-2016-608). If free trialware is utilized, the technology must be purchased or removed at the end of the trial period.

[10]	Service Delivery and Engineering (SDE) requires that every device connected to a VA information system that is capable of running the International Business Machine (IBM) Endpoint Management (IEM) agent will have it installed (VAIQ# 7297444). IBM Bigfix is only to be installed and operated by Office of Information Security (OIS) in a single Veterans Affairs (VA) enterprise instance. Additionally, OIS must keep the supporting platform (relays and core servers) patched and/or mitigated against any known security vulnerabilities. Moreover, older and potentially vulnerable client agents are only allowed for VA endpoints with End of Support (EOS)/End of Life (EOL) Operating Systems (OS) that have been allowed to remain on the VA network. A system Plan of Action and Milestones (POAM) must be entered and approved in the VA Governance, Risk and Compliance (GRC) system for the EOS/EOL OS endpoint. Version 9.2 can only be used in configurations that are not related to critical vulnerability in the Virtual Relay Appliance (CVE-2016-608). If free trialware is utilized, the technology must be purchased or removed at the end of the trial period.

[11]	Service Delivery and Engineering (SDE) requires that every device connected to a VA information system that is capable of running the International Business Machine (IBM) Endpoint Management (IEM) agent will have it installed (VAIQ# 7297444). IBM Bigfix is only to be installed and operated by Office of Information Security (OIS) in a single Veterans Affairs (VA) enterprise instance. Additionally, OIS must keep the supporting platform (relays and core servers) patched and/or mitigated against any known security vulnerabilities. Moreover, older and potentially vulnerable client agents are only allowed for VA endpoints with End of Support (EOS)/End of Life (EOL) Operating Systems (OS) that have been allowed to remain on the VA network. A system Plan of Action and Milestones (POAM) must be entered and approved in the VA Governance, Risk and Compliance (GRC) system for the EOS/EOL OS endpoint. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[12]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[13]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[14]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[15]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[16]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[17]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[18]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[19]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[20]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[21]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

Note:

At the time of writing, version 11.0.2.125 is the most current version.

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 10.0.10.46, and version 11.0.2.125 is under testing and development for six weeks from 07/08/2024.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	BigFix Enterprise Suite Download Center		This site provides download information for this technology.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

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.


Systems Management Systems Management Tools	Application Management
Systems Management Systems Management Tools	Asset Management

- The information contained on this page is accurate as of the Decision Date (07/10/2024 at 19:17:22 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (07/08/2024)

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

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (07/08/2024)

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

Architectural Risks

EMAIL UPDATES