| 4.10.x |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24] |
| | | | [1] | 1) Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities.
2) This technology is approved for use only to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been approved by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO).
3) Should there be a need to use this technology for other purposes such as to allow access to another organizations network resources, those specific uses and instances of this technology must be approved by the Enterprise Security Change Control Board (ESCCB) along with a Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA) which detail the security requirements for those users and systems that share information and information resources. As a part of that documentation, specific approved instances of this technology, software version and any required patches must be address as part of the MOU/ISA. A link to the ESCCB approval process is provided in the reference section of this entry. | | | [2] | 1) Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities.
2) This technology is approved for use only to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been approved by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO).
3) Should there be a need to use this technology for other purposes such as to allow access to another organizations network resources, those specific uses and instances of this technology must be approved by the Enterprise Security Change Control Board (ESCCB), along with a Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), which detail the security requirements for those users and systems that share information and information resources. As a part of that documentation, specific approved instances of this technology, software version and any required patches must be address as part of the MOU/ISA. | | | [3] | This technology is approved primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been approved by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). Other uses of this technology should follow external data connection processes outlined in the constraint above. | | | [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] | 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. | | | [6] | 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. | | | [7] | This technology is approved primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been approved by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). Other uses of this technology must follow external data connection processes outlined in the constraint above. | | | [8] | 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. | | | [9] | 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. | | | [10] | This technology is approved primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been approved by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). Other uses of this technology must follow external data connection processes outlined in the constraint above.
The baseline approved version of this technology is version 4.6.04054. Only baselined version should be used at VA. | | | [11] | This technology is approved primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been approved by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). Other uses of this technology must follow external data connection processes outlined in the constraint above.
The baseline approved version of this technology is version 4.6.04054. Only the baseline version of this technology should be used at VA. | | | [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] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place. | | | [14] | 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. | | | [15] | This technology is approved primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been approved by the Cyber Security Operations Center (CSOC), Enterprise Systems Engineering (ESE) and the local Information System Security Officer (ISSO). Other uses of this technology must follow external data connection processes outlined in the constraint above.
The baseline approved version of this technology is version 4.9.01095. Only the baseline versions of this technology should be used within VA environments. | | | [16] | 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. | | | [17] | Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
This technology is approved primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been approved by the Cyber Security Operations Center (CSOC), Enterprise Systems Engineering (ESE) and the local Information System Security Officer (ISSO). Other uses of this technology must follow external data connection processes outlined in the constraint above.
Only VA Baselined versions of this technology are approved for use. For more information, please visit the baseline documentation for this technology via the “Reference” tab (within the VA network only). | | | [18] | 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). | | | [19] | 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. | | | [20] | 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. | | | [21] | 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 ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [22] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. 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 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 ISSO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | | [23] | 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. | | | [24] | 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). |
|
