2.24.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
| | [1] | Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Users must ensure that Microsoft Structured Query Language (SQL) Server, Citrix Virtual Apps and Desktops (CVAD), Microsoft Excel, and Microsoft Word are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Presidio Transplant Database will require Third-Party FIPS 140-2 (or its successor) certified solution for any data containing Personal Health Information (PHI) / Personally Identifiable Information (PII) or VA sensitive information.
- Any USB and/or network devices connecting with this application shall have gone through the applicable approvals to process VA data and connect with applicable Government Furnished Equipment. These devices shall also have gone through the appropriate approval and marking procedures commensurate to the sensitivity of the data being processed, prior to processing said data.
- All connections shall have the appropriate paperwork and approval including but not limited to the Authorization to Connect (ATC) and Interconnection Security Agreement (ISA). Due to potential information security risks, Software as a Service (SaaS)/Platform as a Service (PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC.
| | [2] | 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. | | [3] | 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. | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | [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 ISSO (Information System Security Officer) can advise on the ESCCB review process. | | [6] | 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. |
|