| 1.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 2.x |
Approved w/Constraints
[16, 17, 18, 19, 20] |
Approved w/Constraints
[16, 17, 18, 19, 20] |
Approved w/Constraints
[16, 17, 18, 19, 20] |
Authorized w/ Constraints
[16, 17, 18, 19, 20] |
Authorized w/ Constraints
[16, 17, 18, 19, 20] |
Authorized w/ Constraints
[16, 17, 18, 19, 20] |
Authorized w/ Constraints
[16, 17, 18, 19, 20] |
Authorized w/ Constraints
[16, 17, 18, 19, 20] |
Authorized w/ Constraints
[16, 17, 18, 19, 20] |
Authorized w/ Constraints
[16, 17, 18, 19, 20] |
Authorized w/ Constraints
[16, 17, 18, 19, 20] |
Authorized w/ Constraints
[16, 17, 18, 19, 20] |
| | | | [16] | Users should check with their supervisor, Information System Security Officer (ISSO) 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 authorized and the user should take the proper steps to decline those installations. | | | [17] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review, users must abide by the following constraints:
- The Redshift ODBC Driver enables users to connect to Amazon Redshift clusters from many third-party SQL client tools and applications. Redshift is authorized and listed in the VAEC Service Catalog; however, project teams requiring the use of Redshift, must work with the VAEC Security Team to ensure that the Redshift data is brought in from a FedRAMP package. The VAEC Security Team will assist the project team in properly documenting the implementation.
A configuration baseline for Amazon Redshift ODBC must be developed, ratified by ITOPS Solution Delivery, and then published on the BCM website located at: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx. Currently, a baseline owner has been identified and the required baseline is being drafted and going through the ratification process.
Presently, this technology may only be used for development and testing activities and without the use of PHI, PII or VA sensitive data. Until the baseline is ratified, published and this entry updated, a POA&M is required to use this technology in production or with any PHI, PII or VA sensitive data.
To discuss status of the required baseline, please contact Baseline Configuration Management Team (VA email: VA IT BCM Intake) | | | [18] | 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. | | | [19] | 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. | | | [20] | 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). |
|
