| 7.x |
Divest
[2, 3, 7, 8, 9, 10, 11] |
Divest
[2, 3, 7, 8, 9, 10, 11] |
Divest
[2, 3, 7, 8, 9, 10, 11] |
Divest
[2, 3, 7, 8, 9, 10, 11] |
Divest
[2, 3, 7, 8, 9, 10, 11] |
Divest
[2, 3, 7, 8, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 8.x |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[2, 3, 7, 8, 9, 10, 11] |
| | | | [1] | Users must ensure that Google Chrome and Firefox are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review for Circut Design Space desktop version, users must abide by the following constraints:
- Cricut Design Space may not be used for any data containing PHI/PII, sensitive information. Precautions not to post privacy and sensitive information in plain sight should be the normal practice.
- When establishing a password for the Cricut Design Space, ensure that all of the VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5 – Authenticator Management – sets a standard of at least 14 non-blank characters. They must contain characters from three (3) of the following (4) categories:
- English upper-case characters
- English lower-case characters
- Base-10 digits
- Non-alphanumeric special characters
- Six of the characters must not occur more than once in the password.
- Use of Cricut Design Space should be confined to an isolated, offline enclave. Cricut Design Space should be placed on an isolated VLAN or Special Purpose VLAN.
- Due to potential information security risks, SaaS/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), Project Special Forces (PSF), 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/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with te
| | | [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] | 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. | | | [4] | 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 with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [5] | 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. | | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | | [7] | 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. | | | [8] | Users must ensure that Google Chrome and Firefox are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize Bitmap Image File (BMP), as it is at the time of writing, is divested in the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- Cricut Design Space may not be used for any data containing PHI/PII, sensitive information. Precautions not to post privacy and sensitive information in plain sight should be the normal practice.
- Cricut Design Space shall be configured to meet minimum password-based authentication standards per VA Knowledge Service Control IA-5(1).
- Use of Cricut Design Space should be confined to an isolated, offline enclave. Cricut Design Space should be placed on an isolated VLAN or Special Purpose VLAN.
- Due to potential information security risks, SaaS/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.
| | | [9] | 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 approved and the user should take the proper steps to decline those installations. | | | [10] | 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). | | | [11] | 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. |
|
