| 3.13.x |
Unapproved |
Approved w/Constraints
[4, 5, 6, 7] |
Approved w/Constraints
[4, 6, 7, 8] |
Approved w/Constraints
[4, 6, 7, 8] |
Approved w/Constraints
[4, 6, 7, 8] |
Approved w/Constraints
[4, 6, 7, 8] |
Approved w/Constraints
[4, 7, 9, 10, 11] |
Approved w/Constraints
[4, 7, 9, 10, 11] |
Approved w/Constraints
[4, 7, 9, 10, 11] |
Approved w/Constraints
[4, 7, 9, 10, 11] |
Approved w/Constraints
[4, 6, 7, 10, 11, 12, 13] |
Approved w/Constraints
[4, 6, 7, 10, 11, 12, 13] |
| | | | [1] | Product must remain properly patched in order to mitigate known or future security vulnerabilities. | | | [2] | 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. | | | [3] | 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. | | | [4] | 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. | | | [5] | Per the Initial Product Review, the following constraints must be followed:
Particular care must be given to physical access controls when using network TAP devices that are deployed in datacenters where personnel other than the device owner have access. It is imperative that these controls are able to mitigate potential compromise of sensitive data by unauthorized personnel.
As with all administrator access accounts, only authorized users must be given multi-factor, role-based access privileges to mitigate potential compromise of sensitive data by unauthorized personnel. | | | [6] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | | [7] | 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. | | | [8] | Per the Initial Product Review, the following constraints must be followed:
Particular care must be given to physical access controls when using network TAP devices that are deployed in datacenters where personnel other than the device owner have access. It is imperative that these controls are able to mitigate potential compromise of sensitive data by unauthorized personnel.
As with all administrator access accounts, only authorized users must be given multi-factor, role-based access privileges to mitigate potential compromise of sensitive data by unauthorized personnel. | | | [9] | Per the Initial Product Review, users must abide by the following constraints:
- Particular care must be given to physical access controls when using network TAP devices that are deployed in datacenters where personnel other than the device owner have access. It is imperative that these controls are able to mitigate potential compromise of sensitive data by unauthorized personnel.
- Only authorized users should be given multi-factor, role-based access privileges to mitigate potential compromise of sensitive data by unauthorized personnel.
| | | [10] | 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). | | | [11] | 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. | | | [12] | Per the Initial Product Review, users must abide by the following constraints:
- Particular care must be given to physical access controls when using network TAP devices that are deployed in datacenters where personnel other than the device owner have access. It is imperative that these controls are able to mitigate potential compromise of sensitive data by unauthorized personnel.
- Only authorized users should be given multi-factor, role-based access privileges to mitigate potential compromise of sensitive data by unauthorized personnel.
Users must ensure that Microsoft Internet Explorer (IE) and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [13] | 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). |
|
