| 7.x |
Authorized w/ Constraints [3, 7, 9, 10, 12, 13] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
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) |
Authorized w/ Constraints (POA&M) |
| 8.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
Authorized w/ Constraints [3, 7, 9, 12, 13, 14, 15] |
| | | | [3] | 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] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [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 both VA Handbook 6500 and VA Directive 6500. | | | [10] | 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.
Per the Initial Product Review, users must abide by the following constraints:
- KWedge for Android will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI)/Personally Identifiable Information (PII) or VA sensitive information. It is important to note that most, if not all, Cloud Service Providers (CSPs) will have data at rest encryption built into the standard product.
| | | [12] | 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. | | | [13] | 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. | | | [14] | Users must ensure that Firefox, Google Chrome, and Microsoft Edge are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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 not utilize DuckDuckGo, as it, at the time of writing, requires a POA&M.
Per the Initial Product Review, users must abide by the following constraints:
- The product is not Federal Information Processing standards (FIPS) 140-2 (or its successor) certified and has the potential to collect, store, or transmit Personally Identifiable Information (PII) or Protected Health information (PHI). KWedge for Android will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI)/Personally Identifiable Information (PII) or VA sensitive information. It is important to note that most, if not all, Cloud Service Providers (CSPs) will have data at rest encryption built into the standard product.
| | | [15] | 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). |
|