| 11.x |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
Approved w/Constraints
[13, 24, 25, 26, 27, 28] |
| | | | [1] | The following constraints were recommended in the Enterprise Security Solutions Services (ESSS) Initial Product Review (IPR) of Calabrio One and must be followed:
- Systems owners need to ensure VA sensitive information stored in the Calabrio One system, which includes a Microsoft SQL database component, must be encrypted using FIPS 140-2 certified cryptographic module. In addition, recordings that are generated by the system that contain VA sensitive information must be encrypted when transmitted over the network. The product should not be used for Moderate/High impact systems and should only be used for Low impact systems with appropriate Risk Based Decision (RBD) authorization.
- System owners should establish an authorization process and procedures for accessing the recorded calls. In addition, they should leverage Active Directory (AD) for role-based authentication to ensure the system is only accessible by authorized staff. Access logging should be enabled for continuous monitoring and auditing.
The product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. It is a requirement that VA sensitive data is properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and FIPS 140-2. | | | [2] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | | [3] | The following constraint was recommended in the Enterprise Security Solutions Services (ESSS) Initial Product Review (IPR) of Calabrio One and must be followed:
System owners should establish an authorization process and procedures for accessing the recorded calls. In addition, they should leverage Active Directory (AD) for role-based authentication to ensure the system is only accessible by authorized staff. Access logging should be enabled for continuous monitoring and auditing. | | | [4] | 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. | | | [5] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [6] | The following constraint was recommended in the Enterprise Security Solutions Services (ESSS) Initial Product Review (IPR) of Calabrio One and must be followed:
System owners must establish an authorization process and procedures for accessing the recorded calls. In addition, they must leverage Active Directory (AD) for role-based authentication to ensure the system is only accessible by authorized staff. Access logging must be enabled for continuous monitoring and auditing. | | | [7] | Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | | [8] | 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). | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [10] | 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). | | | [11] | 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). | | | [12] | Systems owners need to ensure Veterans Affairs (VA) sensitive information stored in the Calabrio One system, which includes a Microsoft Structured Query Language (SQL) database component, must be encrypted using Federal Information Processing Standards (FIPS) 140-2 certified cryptographic module. In addition, recordings that are generated by the system that contain VA sensitive information must be encrypted when transmitted over the network. The technology must not be used for Moderate/High impact systems and must only be used for Low impact system with appropriate Risk Based Decision (RBD) authorization.
System owners must establish an authorization process and procedures for accessing the recorded calls. In addition, they must leverage Active Directory (AD) for role-based authentication to ensure the system is only accessible by authorized staff. Access logging must be enabled for continuous monitoring and auditing. | | | [13] | 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. | | | [14] | Systems owners need to ensure Veterans Affairs (VA) sensitive information stored in the Calabrio One system, which includes a Microsoft Structured Query Language (SQL) database component, must be encrypted using Federal Information Processing Standards (FIPS) 140-2 certified cryptographic module. In addition, recordings that are generated by the system that contain VA sensitive information must be encrypted when transmitted over the network. The technology must not be used for Moderate/High impact systems and must only be used for Low impact system with appropriate Risk Based Decision (RBD) authorization.
System owners must establish an authorization process and procedures for accessing the recorded calls. In addition, they must leverage Active Directory (AD) for role-based authentication to ensure the system is only accessible by authorized staff. Access logging must be enabled for continuous monitoring and auditing. | | | [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 Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Systems owners need to ensure Veterans Affairs (VA) sensitive information stored in the Calabrio One system, which includes a Microsoft Structured Query Language (SQL) database component, must be encrypted using Federal Information Processing Standards (FIPS) 140-2 certified cryptographic module. In addition, recordings that are generated by the system that contain VA sensitive information must be encrypted when transmitted over the network. The technology must not be used for Moderate/High impact systems and must only be used for Low impact system with appropriate Risk Based Decision (RBD) authorization.
System owners must establish an authorization process and procedures for accessing the recorded calls. In addition, they must leverage Active Directory (AD) for role-based authentication to ensure the system is only accessible by authorized staff. Access logging must be enabled for continuous monitoring and auditing.
Per the Security Assessment Review, users must abide by the following constraints:
- Systems owners need to ensure VA sensitive information stored in the Calabrio One system, which includes a Microsoft SQL database component, must be encrypted using FIPS 140-2 certified cryptographic module. In addition, recordings that are generated by the system that contain VA sensitive information must be encrypted when transmitted over the network. The product should not be used for Moderate/High impact systems and should only be used for Low impact systems.
- System owners should establish an authorization process and procedures for accessing the recorded calls. In addition, they should leverage Active Directory (AD) for role-based authentication to ensure the system is only accessible by authorized staff. Access logging should be enabled for continuous monitoring and auditing.
- 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 technical oversight, acquisition, production, and sustainment provided by PSF.
| | | [20] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [21] | 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). | | | [22] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [23] | 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. | | | [24] | Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Systems owners need to ensure Veterans Affairs (VA) sensitive information stored in the Calabrio One system, which includes a Microsoft Structured Query Language (SQL) database component, must be encrypted using Federal Information Processing Standards (FIPS) 140-2 certified cryptographic module. In addition, recordings that are generated by the system that contain VA sensitive information must be encrypted when transmitted over the network. The technology must not be used for Moderate/High impact systems and must only be used for Low impact system with appropriate Risk Based Decision (RBD) authorization.
System owners must establish an authorization process and procedures for accessing the recorded calls. In addition, they must leverage Active Directory (AD) for role-based authentication to ensure the system is only accessible by authorized staff. Access logging must be enabled for continuous monitoring and auditing.
Per the Security Assessment Review, users must abide by the following constraints:
- Systems owners need to ensure VA sensitive information stored in the Calabrio One system, which includes a Microsoft SQL database component, must be encrypted using FIPS 140-2 certified cryptographic module. In addition, recordings that are generated by the system that contain VA sensitive information must be encrypted when transmitted over the network. The product should not be used for Moderate/High impact systems and should only be used for Low impact systems.
- System owners should establish an authorization process and procedures for accessing the recorded calls. In addition, they should leverage Active Directory (AD) for role-based authentication to ensure the system is only accessible by authorized staff. Access logging should be enabled for continuous monitoring and auditing.
- 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.
| | | [25] | 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. | | | [26] | 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. | | | [27] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | | [28] | 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). |
|
