<Past |
Future> |
1.x (Lite) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.x (Enterprise) |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [8, 9, 10, 11] |
Approved w/Constraints [8, 9, 10, 11] |
Approved w/Constraints [8, 9, 10, 11] |
Approved w/Constraints [8, 9, 10, 11] |
1.x (Professional) |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 7] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [8, 9, 10, 11] |
Approved w/Constraints [8, 9, 10, 11] |
Approved w/Constraints [8, 9, 10, 11] |
Approved w/Constraints [8, 9, 10, 11] |
| | [1] | 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). | | [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] | 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. | | [4] | Only the Professional and Enterprise editions are approved for use. The Lite edition of this software uses the Firebird database which is Unapproved technology and therefore must not be used. | | [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] | 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 application is being managed nationally for the enterprise by OIT ITOPS National Centralized Printer Management (OITITOPSNationalCentralizedPrinterManagement@va.gov) and OIT ITOPS SO IO PS ESL Back Office Printer Mgmt (OITITOPSSOIOPSESLBackOfficePrinterMgmt@va.gov) organizations and no other installations are allowed. | | [8] | This application is being managed nationally for the enterprise by OIT ITOPS National Centralized Printer Management (OITITOPSNationalCentralizedPrinterManagement@va.gov) and OIT ITOPS SO IO PS ESL Back Office Printer Mgmt (OITITOPSSOIOPSESLBackOfficePrinterMgmt@va.gov) organizations and no other installations are allowed.
Users must ensure that Firefox, Microsoft Internet Explorer (IE),
Microsoft Internet Information Services (IIS),
Microsoft Structured Query Language (SQL) Server, and
Oracle Database associated are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [9] | 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. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [11] | 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). |
|
Note: |
At the time of writing, version DL01.02.01 is the latest version of this technology and was released on 08/09/2022. The Enterprise and Professional editions are listed in the matrix, however, the only edition of this technology is Lite. |