| 1.0.13 |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
| | | | [1] | Users must ensure that Microsoft Outlook is implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review (IPR), users must abide by the following constraints:
- Box for Outlook add-in will require a 3rd party FIPS 140-2 (or its successor)certified solution for any data containing PHI/PII or VA sensitive information. For organizations needing to operate in a FIPS 140-2 compliant environment,
it`s important to understand that while Box and its integrations, such as the Outlook add-in, are designed with FIPS 140-2 in mind, achieving full compliance requires ensuring that other components of the IT infrastructure, including the operating system and any third-party integrations, also meet the necessary FIPS 140-2 requirements and are configured in a FIPS compliant mode.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Business Integration and Outcomes Service (BIOS) 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.
- Box for Outlook is designed to run in “trusted environments” and administrators should:
• Regularly install security patches provided by Microsoft and add-in vendors like Box.
• Only use add-ins from trusted sources and understand the permissions they request.
• Implement security best practices during add-in development, including secure coding, input validation, and encryption for sensitive data.
- OMB Memorandum M-22-18,” Enhancing the Security of the Software Supply Chain through Secure Software Development Practices,” and OMB Memorandum M-23-16, “Update to Memorandum M-22-18,” limit agencies’
ability to use software that is not developed using secure practices. The attestation form will allow software producers to confirm that they follow those practices.
| | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [3] | 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 ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [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, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [5] | 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. |
|