| 3.x.x |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 10, 11, 12, 13, 14] |
| | | | [1] | Projects using this technology must meet Veterans Affairs (VA) Directive 6500 and implement Federal Information Processing Standards (FIPS 199) for all laptop devices and National Institute of Standards and Technology Special Publication 800-53 for all desktop devices when VA sensitive information is involved, or additional mitigating controls must be documented in an approved System Security Plan (SSP) to prevent potential disclosure of PII/PHI data. Additionally, projects which interface with external VA partners must have a Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), which detail the security requirements for users and systems that share information and resources outside of the VA production network. | | | [2] | 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.
| | | [3] | 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. | | | [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] | 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. | | | [6] | 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). | | | [7] | Users must ensure that Microsoft Internet Explorer (IE) is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [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] | 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. | | | [10] | 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. | | | [11] | Users must ensure that Google Chrome and Firefox are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users should not use Skype with this technology, as it is unapproved for use on the TRM.
Per the Application`s Security Assessment Review, users must abide by the following constraints:
- The program will need to be downloaded using Google Chrome and system owners/administrators have to select the unblock option in file properties to allow for installation.
- System administrators must ensure only an approved version [of 7-Zip] is being used.
- Ensure skype is not installed and only approved versions of Microsoft Visual C++ are used.
- File integrity checkers will be used to monitor for unauthorized changes.
- The ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.
- Firewalls will be locked down to the approved configuration, and application functionality shall be verified.
Per the Browser Extension`s Security Assessment Review, users must abide by the following constraints:
- The Atlantis 3D Editor v2.0.0 Chrome Extension uses permissions that may not be necessary for the extension to function. One medium risk permission for Chrome was noted. It is advised that permissions are verified with the
developer and removed if they are not necessary for the extension to function. Using permissions that are not essential to the extension’s functionality expose the system, using the Atlantis 3D Editor v2.0.0 Chrome
Extension, to potential vulnerabilities and additional risks that could otherwise be avoided by disabling nonessential permissions.
| | | [12] | 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). | | | [13] | Browser plug-ins and extensions may only be installed by VA IT Operations (ITOPS) and must be used with official VA browser installation packages that are managed by ITOPS. For installation, contact the National Service Desk [Mail Group: National Service Desk - Austin]. Browser extensions must be kept up to date with security patches and enhancements. | | | [14] | 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. |
|
