<Past |
Future> |
1.49 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.50 |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Divest [4, 6, 7, 8, 9] |
Divest [4, 6, 7, 8, 9] |
Divest [4, 6, 7, 8, 9] |
Divest [4, 6, 7, 8, 9] |
Divest [4, 6, 7, 8, 9] |
Divest [4, 6, 7, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
1.80.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
1.81.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
1.82.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
Approved w/Constraints [4, 6, 7, 8, 9] |
| | [1] | 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 Firefox, Google Chrome, Microsoft .NET Framework, and Microsoft Internet Explorer (IE) are implemented within VA-approved baselines.
Users must refer to the 3D Printer Guidance section on the referenced Baseline Configuration document, which reads:
3D Printer Guidance
At the time of this writing the Office of Information Security (OIS) is requiring all 3D printing
technologies used within VHA to have a NISTIR 8023 Risk Assessment completed and
approved by Cybersecurity Technology and Metrics (CTM). Please check the Printer and
Multifunction Devices Page on the BCM Portal for vendor / model specific 3D printer
Implementation Guides currently approved under Supporting Documents section. If you
wish to add a printer not listed, please create a Service Now Request to start a security
review and create a 3D printer Implementation Standard. These devices normally should
not require an external vendor connection to support its operation however if it does, it will
also require an approved Memorandum of Understanding/Interconnection Security
Agreement (MOU/ISA) agreement. Healthcare Technologies Management (HTM) has
agreed to support these devices once approved. | | [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] | 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. | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [6] | 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. | | [7] | 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 Firefox and Google Chrome are implemented within VA-approved baselines.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must refer to the 3D Printer Guidance section on the referenced Baseline Configuration document, which reads:
3D Printer Guidance
At the time of this writing the Office of Information Security (OIS) is requiring all 3D printing
technologies used within VHA to have a NISTIR 8023 Risk Assessment completed and
approved by Cybersecurity Technology and Metrics (CTM). Please check the Printer and
Multifunction Devices Page on the BCM Portal for vendor / model specific 3D printer
Implementation Guides currently approved under Supporting Documents section. If you
wish to add a printer not listed, please create a Service Now Request to start a security
review and create a 3D printer Implementation Standard. These devices normally should
not require an external vendor connection to support its operation however if it does, it will
also require an approved Memorandum of Understanding/Interconnection Security
Agreement (MOU/ISA) agreement. Healthcare Technologies Management (HTM) has
agreed to support these devices once approved. | | [8] | 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. | | [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. |
|
Note: |
At the time of writing, version 1.82.7.32244 is the most current version and released 09/19/2023. |