| 4.x |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
Approved w/Constraints
[14, 21, 23, 24, 25] |
| | | | [1] | Security Engineering (SE) and IITOPS conducted a pre-assessment and security requirements verification of Aspera Connect Browser Plug-In and they recommend usage under the following constraints:
- Aspera makes use of FIPS 140-2 compliant libraries. It supports AES 128, 192, and 256 encryption. It also uses SHA-256-128 to guarantee data integrity of data transferred. Aspera servers can be configured to run in FIPS 140-2 mode with the update of a configuration option. When enabled, all file transfer attempts using ciphers and/or hash algorithms that are not FIPS compliant will be aborted by the server.
Aspera Connect Browser Plug-In makes use of the FIPS OpenSSL Toolkit, certification #1747. Some SSL-inspecting software fails to validate the certificates of systems that it connects to, which leaves users with not knowing if they are connected to a legitimate site. Upon detecting a certificate error, some SSL inspection applications will send the client`s request to the server prior to presenting a warning to the user, which could allow an attacker to view or modify sensitive data.
SSL and TLS do not provide the level of end-to-end security that users may expect. Even in absence of SSL inspection, there are problems with how well browsers are conveying SSL information to users. The fact that "SSL inspection" is a phrase that exists should be a red flag that what SSL is actually doing, is fundamentally broken. Compounding the problem are the mistakes that SSL inspection software authors are making.
- Aspera Connect Browser Plug-In is downloadable from Cloudfront, and Amazon`s Cloud Delivery Network (CDN). There is also the ability to install the Aspera Connect Browser Plug-In from a software installer (.msi for Windows, rpm for Linux). In addition, customers have the ability to host the plugin in their own website. Aspera Connect Browser Plug-In is not listed as a Federal Risk and Authorization Management Program (FedRAMP) authorized, ready, or in-process product. Future implementation at VA would necessarily require a FedRAMP approved CSP from a select list. VA is yet to approve its Cloud Security Handbook that will provide system owners guidance to leverage cloud services while adhering to VA security requirements.
- Per the Initial Product Review and the Security Review, it is important to note that due to the nature of this extension, it allows file sharing in a browser. This means users are able to upload and download files by dragging and dropping in a browser, resulting in files being transferred to and from the Internet. All security concerns with regards to uploading VA files to the Internet should be evaluated to ensure proper use and behavior are expected. Risks with uploading VA files to the Internet need to be examined.
| | | [2] | 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. | | | [3] | 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. | | | [4] | Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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). | | | [5] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [6] | Browser plug-ins and extensions may only be installed by VA IT Operations (ITOPS) and must be used with official VA browser installation packages that are managed by ITOPS. For installation, contact the National Service Desk [Mail Group: National Service Desk - Austin]. Browser extensions must be kept up to date with security patches and enhancements. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [8] | Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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, 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). | | | [10] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [11] | Security Engineering (SE) and IITOPS conducted a pre-assessment and security requirements verification of Aspera Connect Browser Plug-In and they recommend usage under the following constraints:
- Aspera makes use of FIPS 140-2 compliant libraries. It supports AES 128, 192, and 256 encryption. It also uses SHA-256-128 to guarantee data integrity of data transferred. Aspera servers can be configured to run in FIPS 140-2 mode with the update of a configuration option. When enabled, all file transfer attempts using ciphers and/or hash algorithms that are not FIPS compliant will be aborted by the server.
Aspera Connect Browser Plug-In makes use of the FIPS OpenSSL Toolkit, certification #1747. Some SSL-inspecting software fails to validate the certificates of systems that it connects to, which leaves users with not knowing if they are connected to a legitimate site. Upon detecting a certificate error, some SSL inspection applications will send the client`s request to the server prior to presenting a warning to the user, which could allow an attacker to view or modify sensitive data.
SSL and TLS do not provide the level of end-to-end security that users may expect. Even in absence of SSL inspection, there are problems with how well browsers are conveying SSL information to users. The fact that `SSL inspection` is a phrase that exists should be a red flag that what SSL is actually doing, is fundamentally broken. Compounding the problem are the mistakes that SSL inspection software authors are making.
- Aspera Connect Browser Plug-In is downloadable from Cloudfront, and Amazon`s Cloud Delivery Network (CDN). There is also the ability to install the Aspera Connect Browser Plug-In from a software installer (.msi for Windows, rpm for Linux). In addition, customers have the ability to host the plugin in their own website. Aspera Connect Browser Plug-In is not listed as a Federal Risk and Authorization Management Program (FedRAMP) authorized, ready, or in-process product. Future implementation at VA would necessarily require a FedRAMP approved CSP from a select list. VA is yet to approve its Cloud Security Handbook that will provide system owners guidance to leverage cloud services while adhering to VA security requirements.
- Per the Initial Product Review and the Security Review, it is important to note that due to the nature of this extension, it allows file sharing in a browser. This means users are able to upload and download files by dragging and dropping in a browser, resulting in files being transferred to and from the Internet. All security concerns with regards to uploading VA files to the Internet should be evaluated to ensure proper use and behavior are expected. Risks with uploading VA files to the Internet need to be examined.
| | | [12] | Security Engineering (SE) and IITOPS conducted a pre-assessment and security requirements verification of Aspera Connect Browser Plug-In and they recommend usage under the following constraints:- Aspera makes use of FIPS 140-2 compliant libraries. It supports AES 128, 192, and 256 encryption. It also uses SHA-256-128 to guarantee data integrity of data transferred. Aspera servers can be configured to run in FIPS 140-2 mode with the update of a configuration option. When enabled, all file transfer attempts using ciphers and/or hash algorithms that are not FIPS compliant will be aborted by the server.Aspera Connect Browser Plug-In makes use of the FIPS OpenSSL Toolkit, certification #1747. Some SSL-inspecting software fails to validate the certificates of systems that it connects to, which leaves users with not knowing if they are connected to a legitimate site. Upon detecting a certificate error, some SSL inspection applications will send the client`s request to the server prior to presenting a warning to the user, which could allow an attacker to view or modify sensitive data.SSL and TLS do not provide the level of end-to-end security that users may expect. Even in absence of SSL inspection, there are problems with how well browsers are conveying SSL information to users. The fact that `SSL inspection` is a phrase that exists should be a red flag that what SSL is actually doing, is fundamentally broken. Compounding the problem are the mistakes that SSL inspection software authors are making.
- Aspera Connect Browser Plug-In is downloadable from Cloudfront, and Amazon`s Cloud Delivery Network (CDN). There is also the ability to install the Aspera Connect Browser Plug-In from a software installer (.msi for Windows, rpm for Linux). In addition, customers have the ability to host the plugin in their own website. Aspera Connect Browser Plug-In is not listed as a Federal Risk and Authorization Management Program (FedRAMP) authorized, ready, or in-process product. Future implementation at VA would necessarily require a FedRAMP approved CSP from a select list. VA is yet to approve its Cloud Security Handbook that will provide system owners guidance to leverage cloud services while adhering to VA security requirements.
- Per the Initial Product Review and the Security Review, it is important to note that due to the nature of this extension, it allows file sharing in a browser. This means users are able to upload and download files by dragging and dropping in a browser, resulting in files being transferred to and from the Internet. All security concerns with regards to uploading VA files to the Internet should be evaluated to ensure proper use and behavior are expected. Risks with uploading VA files to the Internet need to be examined.
| | | [13] | Users must ensure that Microsoft Internet Explorer (IE), Firefox, and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
1. System administrators may wish to reassess whether they want to deploy SSL inspection capabilities with the VA environment. CERT Tapioca can be used to verify that the SSL inspection solution being used is doing its due diligence to minimize the increased risk to the users. At the very least, system administrators could contact the vendors of SSL inspection software to have them confirm the proper configuration options and behaviors. System owners should deploy FIPS compliant software to ensure VA sensitive data containing PII/PHI is protected with FIPS 140-2 validated technology.
2. If Aspera Connect Browser Plug-In is used to satisfy a VA project requirement, a FedRAMP compliant CSP must be utilized. Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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).
3. To address the generic concern of dragging and dropping files into a browser, all security concerns with regards to uploading VA files to the Internet should be evaluated to ensure proper use and behavior are expected. Risks with uploading VA files to the Internet need to be examined | | | [14] | 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. | | | [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 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). | | | [16] | 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. | | | [17] | 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). | | | [18] | 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). | | | [19] | Users must ensure that Microsoft Internet Explorer (IE), Firefox, and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
1. System administrators may wish to reassess whether they want to deploy SSL inspection capabilities with the VA environment. CERT Tapioca can be used to verify that the SSL inspection solution being used is doing its due diligence to minimize the increased risk to the users. At the very least, system administrators could contact the vendors of SSL inspection software to have them confirm the proper configuration options and behaviors. System owners should deploy FIPS compliant software to ensure VA sensitive data containing PII/PHI is protected with FIPS 140-2 validated technology.
2. If Aspera Connect Browser Plug-In is used to satisfy a VA project requirement, a FedRAMP compliant CSP must be utilized. Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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).
3. To address the generic concern of dragging and dropping files into a browser, all security concerns with regards to uploading VA files to the Internet should be evaluated to ensure proper use and behavior are expected. Risks with uploading VA files to the Internet need to be examined | | | [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 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). | | | [21] | Per the Initial Product Review, users must abide by the following constraints:
- System administrators may wish to reassess whether they want to deploy SSL inspection capabilities with the VA environment. CERT Tapioca can be used to verify that the SSL inspection solution being used is doing its due diligence to minimize the increased risk to the users. At the very least, system administrators could contact the vendors of SSL inspection software to have them confirm the proper configuration options and behaviors. System owners should deploy FIPS compliant software to ensure VA sensitive data containing PII/PHI is protected with FIPS 140-2 validated technology.
- 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.
- To address the generic concern of dragging and dropping files into a browser, all security concerns with regards to uploading VA files to the Internet should be evaluated to ensure proper use and behavior are expected. Risks with uploading VA files to the Internet need to be examined.
- System owners must ensure they are using the most recent version of Aspera Connect.
Per the Security Assessment Review, users must abide by the following constraints:
- The Aspera Connect Browser Extension uses permissions that may not be necessary for the extension to function. Two critical, three high, and three mediumrisk permissions were noted. It is advised that permissions are verified with the developer and removed if they are not absolutely necessary for the extension to function. Using permissions that are not essential to the extension’s functionality expose the system, using the Aspera Connect Browser Extension, to potential vulnerabilities and addition risk that could otherwise be avoided by disabling nonessential permissions.
| | | [22] | 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. | | | [23] | 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. | | | [24] | 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. | | | [25] | 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). |
|
