| | | | [1] | Although print job content is not captured, some of the information about the print job may be considered sensitive including user login name, computer name and domain name. Since print job information is able to be sent to the vendor for analysis, users interested in this solution must contact their local ISO (Information Security Officer) to ensure VA sensitive data in transit and at rest is properly protected in compliance with VA Handbook 6500. | | | [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] | Trialware must be removed or purchased upon expiration date of trial period. Trialware is subject to freeware constraint.
In the event the product and its associated components are used to store and process VA sensitive data, system owners must work with the vendor to ensure data at rest and in motion are protected using FIPS 140-2 encryption.
ROI Print Manager must be deployed only within the VA firewall, and no data can be transmitted outside of VA. Leveraging an external provider will require a VA approved MOU/ISA, VA contract or other VA approved agreement (e.g., Data Use Agreement, TIC) as noted in VA Directive 6513 - Secure External Connections, and VA Handbook 6500.
System owners must test the agents thoroughly in an isolated environment and install the agents to a handful of "live" workstations prior to enterprise-wide deployment. | | | [4] | 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. | | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
In the event the product and its associated components are used to store and process VA sensitive data, system owners must work with the vendor to ensure data at rest and in motion are protected using Federal Information Processing Standards (FIPS) 140-2 encryption.
ROI Print Manager must be deployed only within the VA firewall, and no data can be transmitted outside of VA. Leveraging an external provider will require a VA approved Memorandum of Understanding (MOU), VA contract or other VA approved agreement (e.g., Data Use Agreement, TIC) as noted in VA Directive 6513 - Secure External Connections, and VA Handbook 6500.
System owners must test the agents thoroughly in an isolated environment and install the agents to a handful of live workstations prior to enterprise-wide deployment. | | | [7] | In the event the product and its associated components is used to store and process VA sensitive data, system owners must work with the vendor to ensure data at rest and in motion are protected using Federal Information Processing Standards (FIPS) 140-2 encryption.
ROI Print Manager must be deployed only within the VA firewall, and no data can be transmitted outside of VA. Leveraging an external provider will require a VA approved MOU/ISA, VA contract or other VA approved agreement (e.g., Data Use Agreement, TIC) as noted in VA Directive 6513 - Secure External Connections, and VA Handbook 6500.
System owners must test the agents thoroughly in an isolated environment and install the agents to a handful of `live` workstations prior to enterprise-wide deployment.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [8] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [9] | 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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [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] | 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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [12] | 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 Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [13] | 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). |
|
