|
| [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. |
|
| [22] | 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, Google Chrome, Firefox, and Microsoft Internet Explorer are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
Users must not use Opera Desktop with this technology, it is unapproved at this time. Other approved internet browsers are available. See Category Tab for details. |
|
| [23] | 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 VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
| [24] | 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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. |
|
| [25] | Users should check with their supervisor, Information System Security Officer (ISSO) 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. |
|
| [26] | 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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. |
|
| [27] | 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 System Security Officer (ISSO) 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). |
|
| [28] | 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’)
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must not use Opera Desktop with this technology, it is unapproved at this time. Other approved internet browsers are available. See Category Tab for details. |
|
| [29] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. |
|
| [30] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Firefox, Google Chrome, Microsoft Edge, and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must not use Opera Desktop with this technology, it is unapproved at this time. Other approved internet browsers are available. See Category Tab for details. |
|
| [31] | 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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. |
|
| [32] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 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 or its successor 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 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device 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 System Security Officer (ISSO) 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). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. |
|
| [33] | 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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
